QCAA Design common mistakes
QCAA Design · Understand the traps and how to avoid them.
Describing the design process as a rigid linear sequence (research, then ideate, then prototype, then make) and never showing loops back to earlier stages when testing reveals a problem.
Candidates memorise a simplified flowchart in class and treat it as the model answer, so they narrate stages in order rather than describing what actually drove decisions and revisions.
What to do instead
Write process accounts as a decision trail: state the problem at a checkpoint, what evidence triggered a return to an earlier stage, and what changed as a result. Use phrases like 'testing showed X, so I returned to ideation to...'. Aim to include at least one documented iteration loop with cause and effect.
Listing materials, tools and manufacturing steps without explaining why each choice suits the design context (cost, durability, user need, available equipment).
Students treat 'knowledge and skills' as a recall list and assume naming a process earns the justification marks, when the syllabus rewards reasoning about suitability and constraints.
What to do instead
For every material or process named, add a sentence linking it to a specific requirement: strength-to-weight for a portable frame, ease of joining for a school workshop, cost per unit against a stated budget. Convert every list into paired 'choice + reason + constraint' statements.
Producing concept sketches with no annotation, labels, dimensions or indication of scale, then relying on the final product to explain the thinking.
Candidates focus on drawing quality as artwork rather than as communication, and underestimate how much of the mark comes from the sketch conveying information to a reader who never saw the object.
What to do instead
Annotate every sketch with function notes, key dimensions, materials, and arrows showing movement or assembly. Include at least one sketch with a human figure or known object for scale, and one exploded or sectional view where construction matters. Treat each drawing as a message to a stranger.
Writing an evaluation that only praises the outcome ('it worked well and looked good') with no criteria, evidence or comparison to the original brief and specifications.
Students evaluate the product emotionally at the end of a project rather than against the success criteria set at the start, and they lack recorded test data to cite.
What to do instead
Restate each specification as a measurable criterion, then judge the outcome against it with evidence (test results, user feedback, measurements, photos of failure points). Include at least one limitation and one specific improvement with reasoning. Set up the criteria table at the start so evaluation is a comparison, not an opinion.
Ignoring the user and context: designing for personal taste without defining who the user is, their needs, abilities, environment or cultural setting.
School projects often have the teacher as the only audience, so candidates skip user research and assume their own preferences represent the market.
What to do instead
Write an explicit user profile and use scenario before ideating: age, ability, setting, frequency of use, constraints. Reference that profile when justifying each design decision, and gather at least some real feedback (survey, interview, observation) to cite as evidence.
Treating sustainability as a single mention of 'recyclable materials' rather than analysing lifecycle impacts, energy, waste, disposal and social consequences.
Sustainability is often taught as a vocabulary list, so candidates drop in buzzwords without tracing them to specific decisions in their own design.
What to do instead
Map the product lifecycle (material extraction, manufacture, use, end of life) and identify two or three significant impacts with a concrete mitigation for each, such as designing for disassembly, reducing material variety, or choosing reclaimed stock. Discuss trade-offs honestly rather than claiming a design is fully sustainable.
Presenting research as a stack of copied facts and statistics with no synthesis into design requirements or opportunity statements.
Candidates equate volume of research with quality and never convert findings into actionable design criteria, so the research sits disconnected from the design.
What to do instead
End each research section with a short 'what this means for the design' statement that converts a finding into a requirement or constraint. Build a requirements table from the research and refer back to it during ideation and evaluation so the link is visible.
Using technical terms loosely or incorrectly, for example calling any drawing an 'orthographic projection' or any model a 'prototype', which undermines the credibility of the communication.
Terminology is absorbed from peers and online sources without checking definitions, and candidates fear leaving a term out more than using it wrongly.
What to do instead
Keep a personal glossary of the drawing conventions, modelling terms and manufacturing processes you use, with a one-line definition and an example from your own work. Before submitting, check each technical term against that glossary and replace any term you cannot define precisely.
Failing to identify or analyse ethical, legal and social issues such as intellectual property, accessibility, safety, privacy or cultural appropriation when they are relevant to the design context.
Candidates see ethics as a separate topic rather than part of design decision-making, and they do not check whether their chosen product or imagery raises these issues.
What to do instead
Run a short ethics and impact screen on every project: who benefits, who could be harmed, whose knowledge or imagery is being used, what standards or regulations apply. Record the screen in the folio and show at least one decision changed because of it.
Managing the project poorly: no timeline, work left to the final weeks, and no record of testing or client feedback, leaving the folio thin on evidence.
Candidates underestimate the documentation workload and treat the folio as something written after making, when it must be built alongside the design work.
What to do instead
Create a simple Gantt-style plan at the start with milestones for research, concepts, prototyping, testing and evaluation, and update it with dated entries. Photograph and date every test and iteration as it happens, so the folio is a running record rather than a reconstruction.