NCEA Level 3 Technology common mistakes
NCEA Level 3 Technology · Understand the traps and how to avoid them.
Writing a technological outcome description that names only the final product (e.g. "a chair") without stating the intended user, the need or opportunity it addresses, and the physical and functional specifications it was built to meet.
Candidates treat the outcome as a product label rather than as evidence of a design decision; they have practised describing what they made rather than justifying why it takes that form for a specific stakeholder.
What to do instead
For every outcome, draft a one-sentence statement of the form: for [specific stakeholder] who needs [need], the outcome is [what it is] that meets [measurable specifications]. Then attach at least two specifications with numbers or testable criteria, and one sentence explaining a design trade-off you accepted (e.g. weight versus strength).
Presenting a linear, tidy design process (brief, research, concept, prototype, final) with no record of iterations, dead ends, or changes of direction.
Candidates retrofit their process to look competent after the fact, and schools often scaffold projects in neat stages, so the messy evidence of real practice is never captured or is edited out.
What to do instead
Keep a dated decision log during the project, not afterwards. For each entry record what you tried, what evidence you gathered (test result, stakeholder feedback, measurement), what you changed and why. Submit at least three documented iterations, including one abandoned concept with the reason it was dropped.
Describing stakeholder consultation as a single survey or one conversation, without showing how the feedback changed the design.
Candidates treat consultation as a box to tick and report it as an activity ('we surveyed 20 students') rather than as evidence that informed decisions.
What to do instead
For each consultation, state who was consulted and why they are the right stakeholder, summarise what they said, then explicitly link it to a design change with a before-and-after description. Use at least two different stakeholder groups (e.g. end user and manufacturer or client) and show where their priorities conflicted and how you resolved it.
Confusing the three components of technological knowledge - technical knowledge, technological modelling, and technological products - and describing a material's properties without linking them to why it was selected for the outcome.
The achievement standard language is abstract, and candidates memorise definitions without practising applying them to their own materials and tests.
What to do instead
For each material or component used, write three linked sentences: the property (e.g. tensile strength, thermal conductivity, cost per unit), the evidence you have for it (data sheet, your own test), and the functional requirement it satisfies in the outcome. Name which knowledge component you are drawing on in each case.
Using modelling only as a way to present a finished idea (a final render or a single mock-up) rather than as a tool for testing and informing decisions at different stages.
Candidates equate modelling with 'making a model of the final thing', so the functional, prototype and augmented models that actually drive decisions are absent.
What to do instead
Show at least two distinct model types used for different purposes: for example a functional prototype to test a mechanism, and a scale or computer model to test ergonomics or appearance. For each, state the question the model was built to answer, the result, and the design decision that followed.
Explaining how a technological product works without identifying the subsystems and how they interact, or without explaining the scientific or technical principle behind each.
Candidates describe inputs and outputs at a surface level ('the battery powers the motor') and skip the mechanism, often because they have not taken the product apart or researched the principle.
What to do instead
Draw a system diagram with inputs, processes, outputs and feedback. For each subsystem, name the principle involved (e.g. electromagnetic induction, lever mechanics, resistance and heat) and explain in two or three sentences how a change in one subsystem affects another.
Treating 'Nature of Technology' as a history-of-inventions narrative - listing dates and inventors - instead of analysing how technology interacts with society, culture, and the environment.
Candidates default to storytelling because it is easier to write, and they have not been taught to separate description from analysis of consequences and influences.
What to do instead
For each case study, structure the answer around three explicit questions: what social or cultural condition drove or shaped the development; what consequences (intended and unintended) it produced for different groups; and who benefited and who bore costs. Support each claim with a specific example, and avoid biography and dates unless they are causally relevant.
Ignoring the environmental and social impacts of the materials and manufacturing chosen for their own outcome, discussing sustainability only in general terms such as 'it is recyclable'.
Candidates see sustainability as a generic add-on paragraph and lack the habit of tracing their specific material or process through its lifecycle.
What to do instead
For the two main materials or processes in your outcome, trace one impact each from extraction or production through use to disposal, with a concrete figure or source where possible, then state one design change you made or would make in response and the trade-off it introduces.
Answering 'explain' or 'justify' questions with description only, so the response restates what happened without giving reasons, evidence, or a judgement.
Candidates misread the command word under time pressure and are not in the habit of checking their draft against the verb; description feels safer than committing to a justified position.
What to do instead
Before writing, underline the command word and write a one-line plan that matches it: explain = because plus mechanism; justify = claim plus evidence plus why alternatives were rejected; evaluate = criteria plus judgement. After drafting, check that every paragraph contains the word 'because' or an explicit reason clause.
Producing a portfolio that is long but unevidenced - pages of reflection and screenshots with no measurements, test data, or records of stakeholder feedback that a reader could verify.
Candidates equate effort with length and believe more writing earns more credit, so they pad with narrative instead of collecting hard evidence during the project.
What to do instead
Audit the portfolio against a checklist before submission: every claim about performance, user need, or fitness for purpose must have an attached artefact (measurement table, test photo with a caption, feedback record, or specification with tolerances). Delete or convert to a single sentence any paragraph that cannot be backed by one of these artefacts.