Evaluating options before committing to a design direction
Making design decision-making visible at the point where it is most likely to be bypassed
The condition
Students in Technology can now generate multiple design concepts quickly using AI tools. The speed of generation has shifted the pressure point: the difficulty is no longer producing options, it is evaluating them. Students who cannot explain why they chose one direction over another, or what they rejected and why, have completed the design process without doing the design thinking.
The move — Evaluation Gate
Two candidates, three criteria, one justified choice — all collected before development begins.
Before any design development begins, students produce two candidate concepts or directions for their technology task. These can be generated with any tool, including AI, or developed independently.
Students write down three criteria their final design must meet. These come from the brief, from class discussion, or from the students' own analysis of the user need.
Students compare both candidates against the three criteria. A short paragraph per candidate is enough, naming where it meets, partially meets, or does not meet each criterion.
Students write one sentence justifying their chosen direction and one sentence naming what they are setting aside and why. Both must be specific to their brief and context.
Collect the gate artefact — two candidates, three criteria, the comparison, the justification, and the rejection note — before development begins.
What the student produces
A brief gate record naming two candidates, three criteria, a comparison against those criteria, and a justified choice with a named rejection. This is the intellectual work of design thinking made visible before the development phase begins. The teacher can assess the quality of the criteria, the rigour of the comparison, and the reasoning in the justification.
Why it holds up
AI tools can generate design options fluently. They cannot evaluate those options against a student's specific brief, context, and design criteria. The Evaluation Gate places the core Technology thinking — evaluative reasoning about fitness for purpose — at a point in the task sequence where it cannot be bypassed or outsourced.
Teacher judgement note
If a student's three criteria are vague — for example, "good," "useful," "nice-looking" — treat this as the teaching moment the gate was designed to surface. Work with the student to sharpen the criteria before the comparison proceeds.
Governance reminder
Make the gate artefact a standard part of every design development task in Technology. When students know they will always name their criteria and justify their choice before developing, they engage with the brief more carefully from the start. Brief your faculty: the gate is assessed before development begins, not alongside it.
NZ Curriculum connection: Technology — Technological practice; Design thinking; Brief development and evaluation
Print or save this resource as a PDF using your browser.
