Technological Practice
Technological Practice is the domain that examines how technologists move from a need or opportunity to a realised outcome. At Level 3 the exam tests your ability to justify decisions across the whole practice: establishing a client and stakeholder relationship, developing a brief with specifications, generating and selecting design ideas, planning resources and procedures, and evaluating the outcome against fitness for purpose.
The practice cycle
- Brief development: define the need, the client, and the specifications (functional, aesthetic, environmental, legal, cultural).
- Planning: identify resources, time, skills, and risk controls; complex procedures need sequenced steps and quality checks.
- Modelling: use functional models and prototypes to test specific design features before committing.
- Evaluation: compare results with specifications, and feed evidence back into the design.
Worked example
A student designs a hydroponic herb unit for a school canteen. The client needs low maintenance and a $150 budget; the stakeholder (canteen manager) needs food-safe materials. The student writes specifications: holds six plants, uses no mains power, fits a 1.2 m bench, and can be cleaned in 10 minutes. They build a cardboard functional model to test pipe angles, then a prototype with food-grade PVC. A leak test fails at the bulkhead, so they revise the seal and record the change in the planning. Evaluation against specifications shows all met except cleaning time (14 minutes), so they add a removable tray. This evidence-led iteration is what earns Excellence.
Traps
- Describing steps without justifying why they suit the context.
- Treating the brief as fixed; at Level 3 specifications should be refined as evidence emerges.
- Confusing a functional model (tests a feature) with a prototype (tests the whole outcome).
- Ignoring stakeholder consultation until evaluation.