How do you use feedback from real users to suggest honest improvements to your product?
Gather feedback from users on a finished product and use it to suggest realistic improvements
A focused answer to the N(A)-Level D&T outcome on user feedback. How to gather honest feedback through trials and questions, separate opinion from useful data, and turn feedback into realistic suggested improvements.
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
SEAB wants you to gather feedback from real users on your finished product and use it to suggest realistic improvements. Testing against the specification checks the numbers; user feedback checks the experience. The skill is collecting honest feedback and turning it into sensible, doable changes.
The answer
Why ask users
You are too close to your own product to see all its faults. Real users meet it fresh and use it in real situations, so they notice problems you missed, such as a pocket that is awkward to reach. Users are also the people the product is for, so their needs matter most. Their feedback is more honest and useful than your own opinion.
Ways to gather feedback
- User trial. Let users actually use the product for a real task while you watch. Observation reveals problems people do not think to mention.
- Questionnaire. Ask several users short, clear questions: what they liked, what was difficult, what they would change. Gives suggestions and some numbers.
- Interview. Talk to a few users in depth for the reasons behind their views.
Ask fair, unbiased questions. A leading question such as "you loved it, didn't you?" gives useless answers.
Turning feedback into improvements
Feedback is only useful if you act on it. A sensible process:
- Collect the comments from your trials and questions.
- Group similar comments together, so you see the common themes.
- Prioritise the most common or most important problems.
- Suggest a realistic improvement for each, one that could actually be made.
A realistic suggestion is specific, such as "enlarge the pen pocket from 20 mm to 30 mm so wider pens fit", not "make it better".
Honesty matters
Record the negative feedback too. Admitting a flaw and suggesting a fix is a strong evaluation; pretending users loved everything is weak and unconvincing.
Examples in context
Example 1. A reusable lunch box. A trial with classmates shows the lid is hard to open with one hand, a problem the maker never noticed. The grouped feedback leads to a realistic improvement: a larger lip on the lid so it opens easily.
Example 2. Honesty strengthens the report. A student writes that several users found a bag strap dug into the shoulder and suggests a wider padded strap. This honest admission and fix reads as a far stronger evaluation than claiming everyone was happy.
Try this
Q1. Name two ways to gather feedback from users. [2 marks]
- Cue. Any two of a user trial or observation, a questionnaire, an interview.
Q2. Rewrite this leading question to be fair: "This is much better than the old one, isn't it?" [2 marks]
- Cue. Ask neutrally, for example "How does this compare with what you used before, and what would you change?"
Q3. Explain why a suggested improvement should be specific and realistic. [3 marks]
- Cue. A specific, realistic change such as widening a base by 20 mm can actually be made and clearly solves the problem, while a vague idea like "make it better" gives nothing to act on.
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 marksA student has made a desk organiser and wants feedback from classmates who will use it. Describe two ways to gather useful feedback, and explain how the student should turn the feedback into improvements.Show worked answer →
Way 1: a user trial, letting classmates actually use the organiser for a task while the student watches how they get on. This shows real problems, such as a pocket that is hard to reach.
Way 2: a short questionnaire or a few interview questions asking what they liked, what was difficult, and what they would change. This gives reasons and suggestions.
Turning feedback into improvements: group similar comments, pick the most common or important problems, and suggest a realistic change for each, such as enlarging the pocket that several users found too small.
What markers reward: two genuine feedback methods (trial or observation, and questions or questionnaire), and a clear process of grouping feedback and turning the common, important points into realistic improvements.
Original4 marksExplain why feedback from real users is more useful than the designer's own opinion when evaluating a product.Show worked answer →
The designer is close to the product and may not notice its faults, while real users meet it fresh and use it in real situations, so they reveal problems the designer missed. Users also represent the people the product is for, so their needs matter most. This makes their feedback more honest and useful for improving the product than the designer's own opinion.
What markers reward: the idea that users notice faults the designer overlooks, that users are the target audience whose needs count, and that this gives more honest, useful evidence than self-opinion.
Related dot points
- Test a finished product against each point of the specification and record clear pass or fail results
A focused answer to the N(A)-Level D&T outcome on testing a product. How to turn each specification point into a fair test, record clear pass or fail results, and use them to judge whether the product solved the problem.
- Evaluate a product for its impact on the environment and society, using ideas such as the 6 Rs and material life cycle
A clear answer to the N(A)-Level D&T outcome on sustainability. Judging a product against the 6 Rs, thinking about a material's life cycle from source to disposal, and balancing environmental and social impact with cost.
- Plan and carry out user and market research using methods such as surveys, interviews and observation, and use the findings to inform the design
A practical answer to the N(A)-Level D&T outcome on user and market research. Choosing methods such as surveys, interviews and observation, the difference between primary and secondary research, and turning findings into design decisions.
- Write a design specification as a list of clear, measurable requirements drawn from research, and use it to guide and later test the design
A focused answer to the N(A)-Level D&T outcome on writing a specification. How to turn research into measurable requirements covering function, size, materials, safety, cost and appearance, and how the specification is used to test the product.
- Select the most suitable idea against the specification and develop it through stages, justifying each improvement
A focused answer to the N(A)-Level D&T outcome on developing ideas. How to choose an idea against the specification, improve it in stages with reasons, and show clear development rather than a single finished drawing.