Designing for user needs — Design, 11–13 years
Good design starts by understanding the people who will use something, not by guessing what they want.
What users really need
A design is for someone, so begin with that person’s real situation: what they do, notice, find difficult and value. Asking, watching and listening usually reveal more than designing from your own habits. The aim is not to please everyone, but to help a clear group with a real need.
Why start with people?
Many unwanted products were made because a designer assumed that everyone lived, moved or understood things in the same way. User research solves that guessing problem before time and materials are spent. It can also uncover needs people do not mention until you watch what actually happens.
Worked example: a better school bag
A team wants to improve a school bag. First, they watch three pupils pack it and find that books bend, water bottles fall over and small items disappear. They ask what matters most, then choose two priorities: keeping books flat and finding small objects quickly. Their next sketch includes a stiff sleeve and a labelled pocket.
The trap: designing for yourself
It feels sensible to design what you would choose, because your own experience is immediate and easy to remember. But you may have different strength, height, routines or preferences from the intended user. Treat your idea as a starting guess, then check it with real people before calling it a need.
Where this appears
You see this approach in apps, furniture, playgrounds, public signs and kitchen tools. A bus stop, for example, must work for someone waiting briefly, someone carrying bags and someone who cannot read small print. Designers learn about those situations so one feature does not quietly exclude people.
Keep exploring
Other languages
Loading MyLeoNes™…