Evaluate a design solution against the criteria to evaluate success, using ongoing and final evaluation methods to judge fitness for purpose and inform improvement

What this dot point is asking

NESA wants you to evaluate a design solution against the criteria to evaluate success, using both ongoing and final evaluation to judge fitness for purpose and to drive improvement. Evaluation is the analytical engine of the design process and a heavily weighted part of the Major Design Project folio.

The answer

Criteria to evaluate success

Evaluation only works if you have something to measure against. The criteria to evaluate success are derived from the design brief and written early, before designing begins. Good criteria are:

• Specific and measurable, so a judgement can be made objectively where possible.
• Comprehensive, covering function, aesthetics, ergonomics, safety, cost, durability, sustainability and any user-specific requirements.
• User-focused, reflecting the needs of the intended user, not just the designer's preferences.

For example, a criterion such as the product must support a load of at least 100 kilograms without permanent deformation is measurable and testable, whereas the product should be strong is not.

Ongoing evaluation

Ongoing (formative) evaluation happens continuously throughout the design process. At every stage you ask whether the current decision, sketch, prototype or production step still meets the criteria. This is what makes the design process iterative: a prototype that fails an ongoing evaluation sends you back to develop a better solution. Ongoing evaluation is documented in the portfolio through annotated tests, feedback and revised decisions.

Final evaluation

Final (summative) evaluation assesses the completed solution against the original criteria to determine fitness for purpose, whether the product, system or environment actually meets the identified need. It also reflects on the design process itself: what worked, what would be done differently, and what the limitations are. A strong final evaluation reaches a clear, evidence-based judgement rather than a vague claim of success.

Methods of evaluation

A range of methods provides the evidence for a judgement:

• Testing, applying loads, measuring performance, checking dimensions and tolerances against specifications.
• User trials, observing real users interacting with the solution and gathering structured feedback.
• Expert appraisal, seeking the opinion of teachers, clients or industry specialists.
• Comparison to existing solutions, benchmarking against competitor products.
• Surveys and questionnaires, gathering quantitative and qualitative user responses.

Triangulating several methods produces a more convincing evaluation than relying on a single test.

Fitness for purpose

The central question of all evaluation is fitness for purpose: does the solution do the job it was designed to do, for the intended user, within the constraints of the brief? Fitness for purpose ties together function, safety, usability and quality, and is judged directly against the criteria to evaluate success.

Feeding evaluation back into design

Evaluation is valuable only when it informs action. Ongoing evaluation should visibly change the design in the portfolio, showing improvement driven by evidence. Final evaluation should identify realistic improvements and future directions. This closes the loop of the iterative design process and demonstrates the reflective practice NESA rewards.

How it is examined and assessed

Evaluation appears in both the written paper and the Major Design Project. In the folio, markers look for measurable criteria, documented testing, and judgements that reference the criteria with evidence. In the written paper you may be asked to explain how a designer would evaluate a solution or why ongoing evaluation matters. Generic, unsupported claims of success score poorly.