🎬 C4 Design Ideas and Evaluation Explained
Two short videos walking through how C4 works — what you produce for your design pack, how the evaluation matrix supports the choice of which design proceeds, and what scores well at each VCAA band.
Watch in order. Each video pairs with one assessment package.
Don't just press play. For each video: read the 🎯 Watch for line first, keep the ✍️ While you watch artefact open beside you, hit pause at the ⏸ marks to predict before the narrator answers, then do the Check Your Understanding questions from memory. Unfold (▸) only after you've answered.
1. Design Ideas — C4-1
VCAA Criterion 4, Indicator 1 · Design defence presentation with your printed design pack
📊 Two pictures to hold in your head — glance at these before you watch, then again after.
Five tools, one problem — different lenses, not five copies:
flowchart LR
L1["Design-ideas list"]
L2["Mood board"]
L3["Brainstorm"]
L4["Mind map"]
L5["Annotated sketches"]
P(("ONE design<br/>problem"))
L1 --> P
L2 --> P
L3 --> P
L4 --> P
L5 --> P
The pack sets the ceiling; the pitch confirms how high you actually stand:
flowchart LR
A["Strong, original pack<br/>+ owns every decision"] --> A2(["9–10"])
B["Strong pack<br/>+ vague pitch"] --> B2(["caps at a MIDDLE band"])
C["Thin pack<br/>+ eloquent pitch"] --> C2(["can't reach the top —<br/>can't defend what isn't there"])
🎯 Watch for: this video reframes the assessment as a design studio pitch — you're the junior designer, your teacher is the client. Listen for the one sentence-shape that proves you've justified a decision rather than just described it.
▶ Watch on YouTube: https://youtu.be/Pfo-ksEHb64
✍️ While you watch: have your design pack open. Pick one decision in it — a layout, a colour, a flow — and write a single sentence defending it as the video shows you how.
⏸ Pause and predict
- 1:50 — You've just heard the five artefacts (ideas list, mood board, brainstorm, mind map, annotated sketches). Predict: are these five copies of the same thing, or something else?
...
Five different lenses on the same design problem — not duplicates. Each tool views the one design from a different angle.
- 5:05 — A student has a strong design pack but pitches it vaguely. Predict the highest band they can reach.
...
A middle band only. "The pack sets the ceiling, but the pitch confirms the level" — you can't claim top marks for decisions you can't defend out loud.
Check Your Understanding
- In one sentence, what's the difference between an annotation that describes and one that justifies?
...
Describing says how something looks or works; justifying names an alternative you rejected and gives the reason.
- A student's pitch is fluent and confident, but their design pack is thin. Can they reach 9–10? Why or why not?
...
No. You can't defend artefacts that don't exist — the pack is the floor of the evidence, and the pitch only confirms the level the pack already supports.
- Fill in the trade-off sentence shape examiners listen for: "I considered ___, I chose ___, because ___."
...
considered X / chose Y / because Z — naming the rejected alternative is what lifts a decision from describe to justify.
2. Evaluation Criteria — C4-2
VCAA Criterion 4, Indicator 2 · Written evaluation test with your printed evaluation outline and design pack
📊 Two pictures to hold in your head — glance at these before you watch, then again after.
Each criterion is a bridge-plank between what the software MUST do and how it COULD be built:
flowchart LR
SRS["📋 SRS<br/>what it MUST do"]
DES["🎨 Design ideas<br/>how it COULD be built"]
SRS ==>|"efficiency criterion<br/>name · link · measure"| DES
SRS ==>|"effectiveness criterion<br/>name · link · measure"| DES
The rubric is a staircase — each step up unlocks a stronger verb:
flowchart BT
I["identify<br/>names measures, no matrix"] --> O["outline<br/>linked, basic matrix"]
O --> DA["develop & apply<br/>matrix filled with evidence · bands 1–6"]
DA --> E["explain<br/>which elements proceed · bands 7–8"]
E --> J["justify<br/>names the rival + accepts the trade-off · bands 9–10"]
🎯 Watch for: this video reframes C4-2 as writing a product review (think Choice or Wirecutter). Listen for the difference between an explain statement and a justify statement — it's the single highest-leverage move in the rubric.
▶ Watch on YouTube: https://youtu.be/aQaV2Gb_CLE
✍️ While you watch: have your SRS and evaluation outline open. Take one vague criterion (e.g. "easy to use") and rewrite it as a measurable test as the video shows you how.
⏸ Pause and predict
- 2:46 — The narrator says a good matrix needs both columns. Predict: what do you miss if you score only effectiveness? Only efficiency?
...
Effectiveness-only: you don't know if the software actually runs well (speed, resource use). Efficiency-only: you ignore whether it actually works for the humans using it.
- 3:33 — "The design must be user-friendly." Predict how you'd turn this into something you could actually score.
...
Give it a measurable test — e.g. "a new user completes the core task in under 90 seconds, unassisted." If you can't point to what you'd look at, you can't measure it.
- 8:15 — A student explains why Design A scores well but never mentions Design B. Predict the highest band they can reach.
...
Capped at 8. To reach 9–10 you must name the rival — weigh the competing design and explicitly accept the trade-off.
Check Your Understanding
- What three parts must every evaluation criterion contain?
...
A name (what's measured), a link (to a specific SRS requirement), and a measure (the concrete, testable way you'll check it).
- Which column holds speed of processing, and which holds usability?
...
Speed of processing → efficiency. Usability → effectiveness. VCAA names 3 efficiency measures and 11 effectiveness measures. See Efficiency vs Effectiveness.
- The matrix and the recommendation paragraph evidence different band ranges. Which is which?
...
Matrix = the floor, evidences bands 1–6. Recommendation paragraph = the ceiling, evidences bands 7–10. You need both.