What did you choose — material, method, feature, or arrangement — that could have gone differently?
Why did you make each choice? What need, constraint, or criterion drove the decision?
What from class resources, testing, or your brief supports each decision?
Introduce the Trace Map at the start of the design phase, not as a submission requirement students complete at the end. Students who fill it in retrospectively are describing what happened. Students who fill it in during the design process are doing the design thinking the learning area is built around.
The most valuable entry on a Technology Trace Map is often the rejected option: "I rejected the other material because it would fail under load." That sentence demonstrates evaluative design thinking that no correct product can evidence on its own. Make the rejected option a required part of at least one of the three decisions.
Evidence points must come from the brief, class materials, or testing the student conducted — not from AI-generated lists. This is the constraint that makes the Trace Map secure: the evidence predates the solution or comes from first-hand testing, so it cannot be reverse-engineered from a finished product.
Name the Trace Map on the assessment rubric and assign marks to it. A Trace Map that is not assessed will not be completed with care. A Trace Map that carries marks signals to students that the decisions — not just the product — are what the task is designed to develop.
A student designing a bridge component who writes "I chose cardboard layered at 90 degrees because our testing showed that cross-lamination increased load capacity, and I rejected single-sheet cardboard because it buckled at 200g in our class test" has done the evaluative design thinking. The decision, the reason, and the evidence are all present and grounded in class experience.
A student who writes "I decided to add a lip to the container edge because the brief required liquids to be stored safely, and a flat edge failed our pour test" has connected a design feature to a functional requirement and to evidence from testing. That is design thinking. A student who writes "I added a lip to make it look better" has described aesthetics, not design reasoning.
If students used AI to generate options during the design phase, the Trace Map makes the choice visible: "AI suggested three materials. I chose aluminium foil because it was the only one we had in class and the brief required a reflective surface. I rejected the other two because they weren't available and one would have been too heavy." That is selection informed by constraints — which is design reasoning.
A student who writes "I chose this material because it is lightweight and I rejected the other because it would fail under load" has done the design thinking. A student who cannot is showing the product was completed but the learning was not. The Trace Map makes that distinction visible — to the teacher and to the student — at the point where it can still be addressed.
The Trace Map is most useful when introduced at the start of a unit as a normal part of design process — not as a compliance requirement added at the end. Students who understand from the outset that they will need to account for their decisions tend to make more deliberate decisions. The Trace Map changes the thinking, not just the recording of it.