Writing a design brief and evaluation criteria for an end-user: VCE Product Design and Technologies
“Developing a design brief for an end-user and writing evaluation criteria, in the form of questions, that will measure the success of the finished product”
Here you start the School-Assessed Task. You investigate a real end-user or stakeholder, then write a design brief that states the problem, the constraints and the considerations the product must satisfy. From the brief you derive evaluation criteria, written as questions, that you will use in Unit 4 to judge whether the finished product succeeded. The brief and criteria must align tightly, because the criteria test the brief.
What this dot point is asking
This is where your folio becomes a personal project. Everything downstream, the design options, the production, the final evaluation, traces back to the quality of the brief and criteria you write here.
Start with the end-user
A design brief for an end-user begins with understanding that person, not with the product. You investigate their needs, preferences, context and any constraints they bring, through methods such as interviews, observation and surveys. Designing for a named end-user keeps the project grounded; generic briefs produce generic products.
A design brief is a written statement of the design problem that defines what a product must achieve for its end-user, including the constraints (fixed limits such as budget, size, materials or deadline) and considerations (factors to weigh, such as aesthetics, function, sustainability and safety). The brief frames the problem; it does not prescribe the solution.
Constraints versus considerations
A strong brief distinguishes the two clearly. Constraints are non-negotiable limits the product must respect, such as a maximum cost, available materials or a fixed deadline. Considerations are factors the designer must balance, such as durability against weight, or aesthetics against cost. Confusing the two weakens the brief, because constraints are pass-or-fail while considerations are matters of degree.
Constraints are fixed limits the product must meet to be acceptable; considerations are competing factors the designer balances. Listing every requirement as a constraint makes a brief rigid and unrealistic; listing everything as a consideration makes it toothless. The skill is sorting each requirement into the right category, which directly shapes how you later write evaluation criteria.
Evaluation criteria as questions
The study design requires evaluation criteria phrased as questions. Each criterion asks whether the product met a specific requirement from the brief, in a form that can be answered with evidence. A good criterion is specific and measurable; a weak one is vague. The criteria you write now are the exact yardstick you will apply to your product in Unit 4, so they must cover function, aesthetics, the end-user's needs, sustainability and any constraints.
An end-user is a keen home cook with limited bench space who wants a wall-mounted spice rack. The brief states constraints (under a set budget, no wider than 400 mm, made from materials in the school workshop) and considerations (must look at home in a modern kitchen, hold at least twelve jars, be cleanable). The evaluation criteria become questions such as: Does the rack hold at least twelve standard jars? Does it fit within 400 mm width? Did it stay within budget? Does the end-user judge it suitable for a modern kitchen? Is it easy to wipe clean? Each question maps to a brief requirement and can be answered with evidence in Unit 4. That alignment, brief to criterion, is what the outcome assesses.
Why alignment is everything
The brief and criteria form a contract. If a criterion tests something the brief never required, or the brief includes a requirement no criterion checks, the evaluation in Unit 4 will be incoherent. Before moving on, check that every constraint and key consideration in the brief has a matching evaluation question, and that no question floats free of the brief.
The most damaging mistake is writing evaluation criteria as vague statements rather than answerable questions, for example the product should look good. That cannot be tested. Write a specific question tied to evidence: Does the end-user agree the finish suits their kitchen? Equally damaging is letting the brief and criteria drift apart, so the Unit 4 evaluation measures things the brief never asked for. Keep them locked together from the start.
When your design brief names a real end-user, sorts requirements cleanly into constraints and considerations, and pairs each with a specific, answerable evaluation question, you have met this dot point and laid a sound foundation for the rest of the School-Assessed Task.
Exam-style questions
Questions in the style of VCAA exam questions on this dot point, each with a worked answer. They are written by ExamExplained unless tagged "Past paper"; the year shows the paper a question is modelled on.
Practice4 marksExplain the difference between a constraint and a consideration in a design brief, using one example of each.Show worked answer →
Four marks for distinguishing the two and grounding each in an example, so the marker rewards accurate definitions plus applied evidence.
Define a constraint as a fixed, non-negotiable limit the product must meet to be acceptable (for example a maximum budget, a fixed size or a deadline) and a consideration as a competing factor the designer must balance (for example aesthetics against cost, or durability against weight).
Then give an example of each tied to a product. The strongest answers stress that constraints are pass-or-fail while considerations are matters of degree, and note that sorting requirements into the right category shapes how the evaluation criteria are later written.
Practice5 marksExplain why evaluation criteria should be written as specific questions, and describe how they should align with the design brief.Show worked answer →
Five marks, so the marker wants the reason for question-form criteria plus the principle of brief-to-criteria alignment.
Explain that each criterion should be a specific, answerable question tied to evidence (for example asking whether the product fits within a stated size, or whether the end-user judges the finish suitable), because vague statements such as the product should look good cannot be tested in Unit 4.
Then explain alignment: every constraint and key consideration in the brief should have a matching evaluation question, and no question should float free of the brief, so the brief and criteria form a contract. Strong answers note that misaligned criteria make the final evaluation incoherent.