Hangarau 92055: Te whakawhanake otinga hangarau
This domain tests technological practice: developing an outcome from a brief through planning, making, testing, and evaluation. Questions ask you to show how stakeholder feedback and your own testing shaped the final outcome, not just what you built.
Core rules and concepts
- A brief states the need, the people affected, and the boundaries (time, materials, safety).
- Specifications must be measurable: “holds 20 kg”, not “strong”.
- Plan the sequence: research, concept sketches, mock-up, prototype, evaluation.
- Stakeholder voice must appear as evidence, not opinion.
- Evaluate against the specifications and suggest one real improvement.
Worked example
A marae wants a bench for kaumātua at the back of the wharenui. Brief: seat three people, easy to move, no sharp edges, materials available on site.
Reasoning: specifications = 1.5 m long, under 15 kg, rounded edges, timber from the old kitchen. Concept sketches compare a fixed bench and a removable top. A cardboard mock-up checks seat height (450 mm). Stakeholder feedback says the back needs support, so add a low backrest. Test with three kaumātua: stable and easy to move. Evaluation: meets all specs; improvement = add rubber feet to protect the floor.
Traps that cost marks
- Writing a brief that is just a product name (“make a bench”) with no need or people.
- Using vague specs like “looks good”.
- Doing no mock-up or test, then claiming it works.
- Ignoring stakeholder feedback or adding it after the design is fixed.
- Evaluating only what went well; missing a specific next step.