ISYS3438 Chap.13 Assessment Playbook: Critique to Vodcast
Assessment Playbook: Critique to Vodcast
The published Semester 2 2026 assessment sequence has three connected tasks: a 30% Reflective Critique, a 40% visualisation report and Tableau project, and a 30% vodcast or narrated video. This chapter maps the evidence chain across them.
It uses the published Assessment 2 and Assessment 3 marking criteria to show where effort earns credit, while keeping the Assessment 1 boundary clear because its detailed brief was not present in the captured materials.
What this chapter covers
- 01
reflective critique
- 02
visualisation report
- 03
tableau packaged workbook
- 04
business insights
- 05
five-minute recording
- 06
rubric alignment
Worked example · free
Use one analysis for two audience products
- +1Define business problem, data, audience and headline findings.
- +1Justify each visual against its analytical task and alternative.
- +1Connect annotated insights to evidence-based recommendations.
- +1Compress the board route to problem, decisive evidence, action and uncertainty.
Key terms
- Reflective Critique
- Reflective Critique is the published title of the first assessment task, weighted at 30%.
- Packaged workbook
- A packaged workbook is a Tableau project file that includes the workbook and required local data assets.
- Evidence chain
- An evidence chain connects business problem, data, visual choice, insight and recommendation.
- Rubric alignment
- Rubric alignment assigns visible work to the criterion it is intended to satisfy.
Assessment Playbook: Critique to Vodcast FAQ
What is known about the first assessment?
The captured syllabus publishes its exact name, Reflective Critique, its 30% weight and due date. The detailed brief and rubric were not present, so use the current Canvas task page for format and marking criteria.
What files are required for the second assessment?
The published task page requires the individual report in Word or PDF format and the Tableau visualisation project as a packaged workbook. Confirm current naming and upload settings before submission.
Can the report be used as the recording script?
Not directly. The board-facing recording has a five-minute maximum and rewards audience fit, evidence-based narrative, storytelling technique and presentation quality. Compress and restructure rather than reading the report aloud.
Assessment move
Create an assessment matrix with rows for the business problem, data and task, design, justification, insight, recommendation, evidence-based narrative and presentation quality. Add the artifact or scene that demonstrates each row. Check the current Canvas task pages before relying on dates, upload settings or any rule not printed in the captured material. Maintain one evidence ledger across the three published tasks.
For every source, visual and business claim, record its purpose, provenance, transformation and interpretation boundary. The Reflective Critique entry should distinguish what the captured syllabus confirms from details that must be checked on the current Canvas task page. Do not invent absent rubric criteria.
Use the critique process to practise connecting a visible design choice to audience interpretation and a constructive redesign. For Assessment 2, begin with the business problem and intended decision, then audit the dataset at record level. Document fields, grain, missingness, calculated fields, filters and aggregation. Sketch alternatives before Tableau construction and preserve rejected options in the design log.
Build each visual around a question, then write an insight that points to a visible pattern and a limitation that prevents overclaiming. Keep report claims, workbook state and appendix definitions consistent. Trace report quality to reproducibility. Name the data source, define metrics and include enough method for another analyst to rebuild decisive results.
Use figure titles and annotations that explain the comparison, not generic labels. Check the packaged workbook on another machine, remove unused sheets and verify that filters open in the intended state. Follow the task page for current word-count rules, file formats, naming and submission settings; the source package gives the published brief but Canvas remains operationally authoritative.
For Assessment 3, re-author rather than read the report aloud. Choose the few exhibits needed by an executive board, preserve their evidence and translate software detail into business consequence. Storyboard context, tension, evidence and action, then rehearse within the five-minute maximum published in the task. Confirm legibility in the final recording and cite sources appropriately.
Use the available task criteria for alignment, while recognising that topic-specific model answers or a detailed Assessment 1 brief were not present in the captured source. Finish with a final cross-file audit so numbers, labels and recommendations agree. Create a final consistency table with rows for every metric, dataset, visual and recommendation and columns for the report, Tableau workbook and recording.
Check wording, units, periods, filters and values across all three. Resolve differences at the source rather than manually changing a screenshot. Add a submission check for filenames, packaged-workbook contents, links, citations, recording duration and accessibility. Keep published task requirements separate from personal planning assumptions, and verify operational details on the current Canvas page.
This table reduces last-minute contradictions and gives the final narrative a reliable evidence base. It also makes clear where the captured source is silent, so missing instructions are confirmed rather than invented. Schedule the final checks backwards from the published due dates, leaving separate time for analytical verification, workbook packaging, recording export and upload confirmation.
Preserve a read-only copy of the submitted files and the instructions used. This operational record cannot improve weak analysis, but it prevents a strong evidence chain from being undermined by inconsistent versions or avoidable format errors.