Establishing specific, measurable design criteria — like the exact load a structure must safely carry, or a maximum acceptable production cost — provides a concrete, objective way to judge whether a designed solution has actually succeeded, rather than relying on a vague sense of whether it 'looks right'. Evaluating a solution against these criteria means making a genuine judgement, informed by testing or measurement, about whether each specific requirement has actually been met. This process often reveals where a design needs further refinement, since a first attempt rarely satisfies every criterion perfectly on the first try.
Example
A design brief for a phone stand might specify criteria like "must hold a phone at a 60-degree angle" and "must not tip over when a finger taps the screen" — testing a finished prototype against these specific, measurable criteria (rather than just eyeballing whether it looks stable) gives an objective basis for judging whether the design actually succeeds or needs further refinement.
Key terms
Design criteria:
Specific, measurable requirements a successful design solution must meet.
Evaluation:
Judging whether a design meets its criteria, informed by testing or measurement.
Questions
1. Design criteria are:
Specific, measurable requirements a solution must meet
Vague, unclear preferences with no measurable standard
Irrelevant to judging a design's success
Only ever about appearance, with nothing else considered
2. Evaluating a design against its criteria involves:
Making a judgement informed by testing or measurement
Simply guessing whether it looks acceptable
Ignoring all criteria completely
Assuming every design automatically meets every requirement
3. Specific, measurable criteria are useful because they:
Provide an objective basis for judging success
Make evaluation impossible
Have no connection to whether a design actually works
Are always identical for every single project
4. A first design attempt:
Rarely satisfies every criterion perfectly on the first try
Always perfectly satisfies every criterion immediately
Never needs to be evaluated at all
Requires no testing of any kind
5. An example of a measurable design criterion is:
A structure must safely carry a specific load
The designer simply likes how it looks
No requirement at all
A criterion that can never be tested
6. Testing a prototype against its criteria helps:
Reveal where a design needs further refinement
Guarantee the design needs no further work, always
Replace the need for any design criteria
Have no effect on the design process
7. Evaluation informed by measurement is more useful than a vague impression because it is:
Objective and based on evidence
Always completely subjective with no evidence involved
Irrelevant to whether a design actually succeeds
Impossible to actually carry out in practice
8. Why might establishing measurable criteria before starting production (rather than only judging a finished product informally) lead to a better final design?
Having a clear, specific target from the outset helps guide design decisions throughout the process, rather than only checking suitability at the very end
Measurable criteria established beforehand have no real influence on decisions made during the design process
Judging a design only after it is fully finished always produces exactly the same quality of outcome
Establishing criteria in advance provides no genuine benefit over evaluating informally after completion
9. Why might a design that "looks right" still fail to meet its actual functional criteria?
Visual appearance and functional performance are different things, so a design can look appealing while still failing to perform as required
A design's appearance always perfectly and reliably predicts whether it will meet its functional requirements
Functional criteria and visual appearance are always exactly the same consideration in design evaluation
A design that looks acceptable can never actually fail to meet its intended functional criteria
10. Why might testing a prototype under realistic conditions (rather than only in ideal, controlled conditions) give a more accurate evaluation of whether it meets its criteria?
Realistic conditions can reveal problems or limitations that might not appear under ideal, best-case circumstances
Testing under ideal conditions always reveals exactly the same information as testing under realistic conditions
The conditions under which a prototype is tested have no bearing on the accuracy of its evaluation
A prototype that performs well under ideal conditions is always guaranteed to perform identically in real use
11. Why might a design that meets most, but not all, of its criteria still require further refinement before being considered complete?
Even a single unmet criterion could represent a genuine failure to satisfy an important requirement of the original design brief
Meeting most criteria is always considered fully sufficient, regardless of whether any specific requirement remains unmet
An unmet criterion never actually has any real bearing on whether a design should be considered complete
Design criteria are always equally unimportant, so any that remain unmet can simply be disregarded
12. Why might two different evaluators, using the same measurable design criteria, be more likely to reach the same conclusion about a design's success than if using only subjective impressions?
Specific, measurable criteria reduce the role of personal opinion, providing a more consistent, shared basis for judgement
Measurable criteria always produce completely random, inconsistent judgements between different evaluators
Subjective impressions always produce more consistent results between different evaluators than measurable criteria
The type of evaluation method used has no bearing on how consistent different evaluators' conclusions are likely to be
13. Why might a maximum acceptable production cost be considered just as legitimate a design criterion as a functional or safety requirement?
Cost constraints are a genuine, practical requirement that a real-world design solution needs to satisfy alongside its functional and safety requirements
Cost has no legitimate place among design criteria and should never be considered alongside functional requirements
Functional and safety requirements are always considered more important than cost in every single design context
Cost constraints are always completely irrelevant to whether a design can be considered genuinely successful
14. Why might involving someone other than the original designer to carry out the evaluation of a prototype help reduce bias in the assessment?
A designer may be inclined to judge their own work more favourably, so an independent evaluator can offer a more objective assessment against the stated criteria
The person conducting an evaluation never actually has any bearing on how objective or biased the resulting assessment is
A designer evaluating their own work is always exactly as objective as an independent evaluator would be
Involving an independent person in evaluation never actually reduces bias in a design assessment
15. Why might an iterative process (test, evaluate, refine, test again) generally produce a stronger final design than a single evaluation at the very end of production?
Repeated cycles of testing and refinement allow problems to be caught and addressed progressively, rather than discovering them only once fully finished
A single evaluation performed only at the very end always produces exactly as strong a final design as multiple rounds of testing
Iterative testing and refinement never actually improves a design's ability to meet its original criteria
The number of times a design is tested and refined has no bearing on the quality of the eventual outcome
16. Why might a design team need to make trade-off decisions when two different criteria (like low cost and high durability) are in tension with each other?
Improving performance against one criterion can sometimes come at the expense of another, requiring a considered judgement about which trade-offs best serve the overall design brief
Design criteria are always perfectly compatible with each other, with no possibility of any genuine trade-off
Trade-offs between competing criteria never actually need to be considered during a real design process
Cost and durability are always completely unrelated criteria with no possible tension between them
17. Why might evaluating a design solely against the criteria set out in the original brief sometimes miss important considerations that weren't anticipated when the brief was first written?
Unanticipated issues (like unintended side effects or edge cases) might only become apparent during testing, even though they weren't part of the original stated criteria
The original design brief always anticipates every single possible consideration relevant to evaluating the finished design
Testing and evaluation never actually reveal any considerations beyond what was already specified in the original brief
Unanticipated issues discovered during testing have no real bearing on how a design should ultimately be evaluated
18. Why might documenting the specific reasons a prototype failed to meet a criterion be more valuable for the design process than simply noting that it failed?
Understanding the specific cause of a failure provides the insight needed to make a targeted, effective refinement, rather than guessing at a fix
Simply noting that a criterion was not met always provides exactly as much useful information as understanding the specific cause
The specific reason behind a design failure has no bearing on how effectively it can be addressed through refinement
Documenting the cause of a design failure never actually leads to a more effective or targeted refinement
19. Why might a design evaluated against criteria developed collaboratively with stakeholders be considered more trustworthy than one evaluated purely against criteria a single designer invented alone?
Criteria shaped by genuine input from those affected by the design are more likely to reflect real-world requirements, rather than one person's isolated assumptions
Criteria developed entirely by a single designer, with no outside input, are always exactly as trustworthy as collaboratively developed ones
Who develops the evaluation criteria has no real bearing on how trustworthy the resulting evaluation actually is
Stakeholder involvement in developing criteria never adds any genuine value to the evaluation process
20. Why might a design that exceeds a criterion by a large margin (like a shelf that can hold far more weight than required) not necessarily represent the "best" possible solution?
Significantly over-engineering beyond what is genuinely required can involve unnecessary cost, materials or complexity that may not serve the overall design brief well
Exceeding a criterion by the largest possible margin is always automatically the best and most desirable outcome for any design
The amount by which a design exceeds a specific criterion has no bearing on whether it represents an effective, well-balanced solution
Over-engineering a solution beyond its actual requirements never has any negative cost, material or complexity implications
21. Understanding how to evaluate designs against criteria mainly helps you to:
Objectively judge whether a design solution meets its specific, measurable requirements
Assume a design that looks visually appealing always meets its functional requirements
Ignore the need for further refinement when a design fails to meet a specific criterion
Treat design evaluation as a purely subjective process with no role for testing or measurement
Answer key (parent copy)
1. Specific, measurable requirements a solution must meet
2. Making a judgement informed by testing or measurement
3. Provide an objective basis for judging success
4. Rarely satisfies every criterion perfectly on the first try
5. A structure must safely carry a specific load
6. Reveal where a design needs further refinement
7. Objective and based on evidence
8. Having a clear, specific target from the outset helps guide design decisions throughout the process, rather than only checking suitability at the very end
9. Visual appearance and functional performance are different things, so a design can look appealing while still failing to perform as required
10. Realistic conditions can reveal problems or limitations that might not appear under ideal, best-case circumstances
11. Even a single unmet criterion could represent a genuine failure to satisfy an important requirement of the original design brief
12. Specific, measurable criteria reduce the role of personal opinion, providing a more consistent, shared basis for judgement
13. Cost constraints are a genuine, practical requirement that a real-world design solution needs to satisfy alongside its functional and safety requirements
14. A designer may be inclined to judge their own work more favourably, so an independent evaluator can offer a more objective assessment against the stated criteria
15. Repeated cycles of testing and refinement allow problems to be caught and addressed progressively, rather than discovering them only once fully finished
16. Improving performance against one criterion can sometimes come at the expense of another, requiring a considered judgement about which trade-offs best serve the overall design brief
17. Unanticipated issues (like unintended side effects or edge cases) might only become apparent during testing, even though they weren't part of the original stated criteria
18. Understanding the specific cause of a failure provides the insight needed to make a targeted, effective refinement, rather than guessing at a fix
19. Criteria shaped by genuine input from those affected by the design are more likely to reflect real-world requirements, rather than one person's isolated assumptions
20. Significantly over-engineering beyond what is genuinely required can involve unnecessary cost, materials or complexity that may not serve the overall design brief well
21. Objectively judge whether a design solution meets its specific, measurable requirements