experimentation with media technologies, codes, conventions and production processes, and the documentation of experimental findings to inform a production design

What this dot point is asking

This dot point sits alongside research in Outcome 2, but it is a separate skill. Research is finding out about a form; experimentation is testing what you can actually do with the technologies and techniques of that form. The assessable difference is documentation: the SAT rewards a visible, reasoned trail from experiment to decision, not a polished outcome that appears from nowhere.

What you experiment with

VCAA points you at four targets for experimentation.

• Technologies: the cameras, microphones, lenses, editing software, recording equipment or layout tools of your chosen form. You test what each can and cannot do.
• Codes: trialling technical, symbolic, written and audio codes to see what meaning they construct, for example testing whether hard side-lighting or soft top-lighting better suits your intended mood.
• Conventions: testing genre and form conventions to see whether meeting or subverting them serves your intention.
• Processes: the workflows of production, such as a recording pipeline, an editing sequence or a print layout method.

Purposeful, not random

The strongest experimentation is hypothesis-driven. Instead of trying things at random, set a question: does a shallow depth of field make my subject feel more isolated than a deep focus? Then run the trial, capture both versions, and compare. A purposeful experiment produces a finding you can act on. Random experimentation produces footage but no justified decisions, which is what the SAT actually assesses.

Documenting findings

Documentation should capture four things for each experiment: what you tested, why you tested it, what you found, and what you decided as a result. Keep evidence, frames, audio samples, layout drafts, screenshots, alongside short written reflections. The reflection is where marks live: it shows you understood the result and used it. A log entry that reads as a sentence of justification (this lighting test confirmed that low-key side-light constructed the threatening mood my narrative needs, so I will adopt it) is worth far more than a folder of untagged files.

Feeding the production design

Experimentation is not an end in itself; it exists to inform the production design plan you build in Outcome 3. Every documented finding should be traceable into a design decision. If you experimented with three opening shots and chose one, your design plan should state the chosen approach and reference the experiment that justified it. This continuity, research to experimentation to design to production, is what makes the SAT read as a coherent, iterative process rather than a series of disconnected tasks.

Working efficiently

Run experiments early, before equipment and time pressures mount. Test the few choices that matter most to your intention rather than every possible variable. Keep your documentation as you go, not retrospectively, because reconstructed logs lose the genuine reasoning the assessment looks for.

Experiment with purpose, document the finding and the decision it drives, and connect every result to your production design. That visible, reasoned trail is what turns experimentation from busywork into assessable, design-shaping evidence.