Evaluate a product or prototype systematically against each point of the design specification, reaching evidenced judgements and identifying improvements

What this dot point is asking

SEAB wants you to evaluate a product or prototype systematically against each point of the design specification, reaching judgements backed by evidence and identifying improvements. Evaluation is not a vague "is it good?"; it is a structured, point-by-point check against the requirements the product was meant to meet. This skill is assessed in both the written paper and the Design Journal.

The answer

Why evaluate against the specification

The specification is the agreed list of what the product had to do for its user. Evaluating against it checks whether the product actually meets those requirements, rather than whether the designer happens to like it. A point-by-point evaluation is fair and structured: it shows exactly which requirements are met, which are partly met, and which are not, so the designer knows precisely what to improve. This is the proper, objective way to judge a design.

Working through the specification point by point

A systematic evaluation takes each specification point in turn and tests the product against it:

1. Read the specification point.
2. Test or measure the product against it.
3. Record the result as evidence.
4. Judge whether the point is met, partly met, or not met.

For "must hold the phone at 55 to 65 degrees", measure the actual angle. For "must not tip when tapped", tap it and observe. Going through every point ensures nothing is missed and the judgement is complete.

Judgements backed by evidence

Each judgement must be supported by evidence, not opinion. "It works well" is a subjective claim that could be biased or wrong. "It held the phone at 58 degrees, within the requirement" is evidence that proves the point is met. Measurements, test results and user feedback are the evidence that makes an evaluation honest and credible, and lets anyone see exactly how the product performed.

Identifying improvements

Evaluation is not just a verdict; it points the way forward. For each point that is not fully met, the designer identifies a specific improvement: "the stand tipped when tapped, so the base should be widened or weighted." Even points that are met can suggest refinements. This links evaluation back into the iterative process, because the improvements feed the next cycle of development.

Honesty matters

Examiners reward honest evaluation. Admitting that a point was not met, with evidence and a proposed fix, shows good design thinking and earns more than pretending everything succeeded. A balanced evaluation that recognises both strengths and weaknesses is far stronger than uncritical self-praise.

Examples in context

Example 1. Evaluating a children's torch. Against the specification, the designer measures the beam brightness, times the battery life, checks the switch can be found in the dark, and confirms there are no small loose parts. Each result is recorded and judged against the requirement. The brightness and battery pass, but the switch is hard to find, judged not met with evidence, leading to a raised, textured switch as the improvement. The point-by-point method makes the evaluation thorough and useful.

Example 2. Evaluating a flat-pack stool. The designer tests load (it held the required weight), assembly time (within the target), stability (it wobbled slightly, not fully met), and folded size (within the limit). The honest finding that it wobbles, backed by observation, drives a specific fix (a cross-rail to triangulate the legs). Recognising the weakness with evidence is exactly what markers reward over claiming the stool is perfect.

Try this

• Cue. Describe the steps to evaluate a product against one specification point. Answer: read the point, test or measure the product against it, record the result as evidence, and judge whether it is met, partly met or not met.

• Cue. Rewrite "the bag is comfortable" as an evidenced evaluation statement. Answer: e.g. "users carrying a 5 kg load for 10 minutes reported no discomfort, and the straps are 55 mm wide, meeting the comfort requirement."

• Cue. Explain why an honest evaluation that admits a fault is better than uncritical praise. Answer: it shows real design judgement, identifies what to improve with evidence, and is more credible, which markers reward over pretending everything succeeded.