How do designers find out whether a design works, and how do they use that feedback to improve it?
Test designs with users, evaluate against criteria, gather and act on feedback, and iterate to improve a design
A focused answer on testing and evaluation for O-Level Design Studies. User testing, evaluating against the specification, gathering qualitative and quantitative feedback, iteration, and the difference between feedback and opinion.
Reviewed by: AI editorial process; not yet individually human-reviewed
Have a quick question? Jump to the Q&A page
Jump to a section
What this dot point is asking
This dot point asks you to test designs, evaluate them against criteria, gather and act on feedback, and iterate. Testing finds out whether a design actually works for its users; evaluation judges it against the specification and goals; iteration uses what you learn to improve the design and test again. You should know how to run a simple user test, the difference between qualitative and quantitative feedback, how to evaluate against criteria, and why design improves through repeated loops. The key idea is that designers do not guess whether a design works - they test it and act on the evidence.
The answer
Testing with users
User testing puts a prototype in front of real members of the target audience and observes them using it. Watching what people actually do is more reliable than asking what they think they would do. Good practice uses realistic tasks ("show me how you would open this"), encourages users to think aloud, and notes where they hesitate, struggle or succeed. Even a handful of testers reveals most major problems.
Evaluating against criteria
Evaluation judges a design against the specification and success criteria set earlier, not against personal taste. By checking each requirement (is it legible? does it suit the audience? does it meet the constraints?), the designer makes an objective assessment of strengths and weaknesses. A clear specification makes evaluation honest and focused.
Qualitative and quantitative feedback
Feedback comes in two forms. Qualitative feedback is descriptive: opinions, feelings and reasons expressed in words, gathered through interviews, comments and observation. Quantitative feedback is numerical: measurable data such as how many people completed a task or how long it took. The two complement each other: numbers show what is happening, words explain why.
Feedback versus opinion
Not all comments carry equal weight. A useful designer distinguishes signal from noise: patterns shared by several users matter more than a single off-hand remark, and feedback from the actual target audience matters more than from people outside it. Feedback should be weighed against the specification, not simply obeyed; the designer decides which problems to act on.
Acting on feedback and iterating
Testing only helps if you act on it. The designer gathers the results, identifies the most important and most common problems, prioritises them, and redesigns to address them, then tests the improved version. This loop, test then refine then test again, is iteration, and it is how a design steadily improves. Each cycle should leave the design measurably better against its criteria.
Examples in context
Example 1. Usability testing a website. A team watches five people try to complete a purchase on a new website and records where each gets stuck. The same checkout step trips up four of them, so the team redesigns it and tests again. Observing real behaviour, not asking opinions, pinpoints the fix, illustrating evidence-led iteration.
Example 2. A/B testing a poster headline. A designer prints two versions of an event poster with different headlines and measures which leads more people to recall the date. The version that performs better on this quantitative measure is kept. Here numerical feedback decides between options, showing quantitative evaluation guiding a design choice.
Try this
Cue. Give a design you have made (a sign, a label, a layout) to someone in its target audience and set them a realistic task. Watch silently and note every point where they hesitate, without explaining anything.
Cue. For one design, write three success criteria, then evaluate the design honestly against each. Identify the criterion it meets least well and describe one change to improve it.
Cue. Think of feedback you once received on your work. Separate the comments into qualitative (reasons and feelings) and quantitative (anything measurable), and decide which single piece you would act on first and why.
Exam-style practice questions
Practice questions written in the style of SEAB exam questions on this dot point, with worked answer explainers. The year tag is the paper they imitate, not the source.
Original6 marksDescribe how you would test a prototype of a new packaging design with users, and explain how you would use the results to improve it.Show worked answer →
Testing approach: give the prototype packaging to several people from the target audience and observe them using it - opening it, reading it, handling it - in a realistic setting. Ask them to think aloud, then ask focused questions: Was it easy to open? Could you find the key information? What did you think it was for?
Using the results: gather the feedback, look for patterns (problems several people share matter more than one-off comments), compare the design against the specification, and prioritise the biggest issues. Then redesign to fix them and test again.
For example, if most testers struggle to open it, redesign the opening mechanism; if they miss the product name, increase its size and contrast.
What markers reward: a realistic testing method (real users, observation, focused questions), the idea of finding patterns and comparing against criteria, and a clear loop of acting on feedback then re-testing.
Original4 marksExplain the difference between qualitative and quantitative feedback, and give one example of each that could be gathered when testing a poster.Show worked answer →
Qualitative feedback is descriptive: it captures opinions, feelings and reasons in words. Quantitative feedback is numerical: it captures measurable data in numbers.
Example of qualitative feedback for a poster: comments from viewers explaining what mood the poster gave them or which part confused them.
Example of quantitative feedback: the number or percentage of viewers who could correctly recall the event date after looking at the poster, or how many seconds it took them to find it.
What markers reward: a correct distinction (words and reasons versus numbers and measurements), and one appropriate, specific example of each tied to testing the poster.
Related dot points
- Describe the stages of the design process - empathise, define, ideate, prototype and test - and explain why it is iterative rather than linear
A focused answer on the design process for O-Level Design Studies. The stages of design thinking from empathise to test, why the process is iterative and cyclical, and how each stage feeds the next.
- Explain the purpose of prototyping and create low- and high-fidelity prototypes and mock-ups to test and develop a design
A focused answer on prototyping for O-Level Design Studies. The purpose of prototypes, low- versus high-fidelity, paper prototypes and mock-ups, fail fast and cheap, and how prototyping develops a design.
- Use ideation techniques and annotated sketching to generate a range of ideas and communicate design thinking on paper
A focused answer on ideation and sketching for O-Level Design Studies. Brainstorming, mind-mapping and SCAMPER, thumbnail sketches, annotation, and how to generate and communicate a range of ideas quickly.
- Write a design specification from research and explain how constraints such as budget, materials, audience and time shape design decisions
A focused answer on specifications and constraints for O-Level Design Studies. Writing a design specification, success criteria, and how constraints such as budget, time, materials and audience shape design decisions.
- Explain user-centred design - understanding users, usability and feedback - and apply it to keep the user's needs central to design decisions
A focused answer on user-centred design for O-Level Design Studies. Putting users first, usability, personas, accessibility, testing with users, and keeping the user's needs central to every decision.