Capturing User Needs 👥

Introduction: Why user needs matter

students, every successful product starts with a real human problem. A great design is not just something that looks good or uses strong materials; it is something that actually helps the people who will use it. In Design, Materials and Manufacturing 2, capturing user needs means finding out what users truly want and require before any detailed engineering work begins.

The main objectives of this lesson are to help you:

explain the key ideas and terms behind capturing user needs,
apply simple design reasoning to gather and sort user needs,
connect user needs to the wider topic of Requirements and Stakeholders,
summarize how user needs become the starting point for engineering requirements,
use examples and evidence to show why this step matters in design and manufacturing.

A product can fail even if it is technically clever if it ignores the people using it. For example, a school backpack made from a strong material might still be a poor design if it is too heavy, uncomfortable, or difficult to open. Capturing user needs helps avoid this kind of mistake. 🎒

What are user needs?

User needs are the wants, problems, expectations, and limits that people have when using a product. They describe what users need the product to do in real life. These needs can include comfort, safety, ease of use, size, appearance, cost, durability, and accessibility.

It is important to understand that a need is not always the same as a solution. A user may say, “I want a bigger button,” but the real need may be “I need the product to be easier to control.” Designers must listen carefully so they do not jump too quickly to a bad solution.

For example:

A student might say a water bottle needs a lid that does not leak.
An athlete might need a bottle that can be opened quickly with one hand.
A commuter might need a bottle that fits in a bike holder.

Each of these is a different user need, even though they are all about the same product. This shows why products must often be designed for more than one user group.

User needs can be explicit or implicit. Explicit needs are stated directly by users, such as “I need this chair to be adjustable.” Implicit needs are not always said out loud, but they are still important, such as the need for the chair to support posture safely over long periods.

Who are the users and stakeholders?

In Requirements and Stakeholders, a stakeholder is anyone who is affected by the product or can affect its success. Users are a major stakeholder group, but not the only one.

Examples of stakeholders include:

end users, who use the product directly,
buyers, who choose or pay for it,
clients, who request the product,
manufacturers, who produce it,
retailers, who sell it,
maintenance staff, who repair it,
regulators, who make safety rules,
society, which may be affected by waste, energy use, or accessibility.

A product may need to satisfy several stakeholders at once. For example, a classroom chair must be comfortable for students, durable for the school, affordable for the buyer, safe under regulations, and efficient to manufacture. This means capturing user needs is only one part of the bigger requirements picture, but it is the most human-centered starting point.

If designers only ask the client what they want, they may miss important needs from actual users. If they only ask users, they may ignore cost, production, or legal limits. Good design balances all relevant stakeholders. ⚖️

How user needs are captured

Capturing user needs means collecting information from users in a structured way. Designers use different methods depending on the product, the user group, and the available time.

Common methods include:

interviews,
questionnaires,
observations,
focus groups,
user testing of existing products,
asking for feedback from complaints or reviews,
studying how people use similar products in real settings.

Interviews

Interviews allow designers to ask open questions and get detailed answers. For example, a designer could ask, “What is difficult about using your current lunch box?” This can uncover needs that a survey might miss.

Questionnaires

Questionnaires are useful when many people need to be asked. They can show patterns, such as how many users want a lighter product or a larger display. The drawback is that responses may be shorter and less detailed than interviews.

Observation

Observation is powerful because people sometimes cannot accurately describe what they do. A designer watching how students carry notebooks might notice that they often use one hand while holding a phone in the other. That may reveal the need for a handle, strap, or easier grip.

Existing products and feedback

Reviews, returns, complaints, and product testing can reveal what users like and dislike. If many people say a phone charger cable frays quickly, that is evidence of a durability need that the next design should address.

Turning comments into design information

Raw user comments are often messy. Designers must sort them into useful information. This step is important because user statements are often vague, emotional, or solution-focused.

For example, a user might say:

“This is annoying to carry.”
“It is too bulky.”
“I can never find the switch.”
“It hurts my hand.”

These comments need to be translated into clearer need statements such as:

The product should be easy to carry.
The product should have a compact shape.
The control should be easy to locate.
The handle should be comfortable to hold.

A useful way to organize needs is to group them into categories:

functional needs: what the product must do,
ergonomic needs: how it fits the body and movement,
aesthetic needs: how it looks and feels,
performance needs: how well it works,
safety needs: how it prevents harm,
environmental needs: how it affects materials, energy, and waste.

This classification helps designers make sure they do not focus only on appearance while ignoring safety or usability.

Example: capturing user needs for a school desk

Imagine a school is replacing old desks. At first, a teacher might say the new desk should be “strong and modern.” That is a starting point, but it is not enough.

A design team could collect user needs from students, teachers, and cleaners.

Students may want:

enough space for books and devices,
comfortable seating height,
a hook or storage area for bags,
smooth edges to avoid discomfort,
a desk surface that is easy to clean.

Teachers may want:

desks that can be moved quickly,
surfaces that resist damage,
low noise when desks are moved,
designs that support different classroom layouts.

Cleaners may want:

materials that can be wiped down easily,
no hidden areas that collect dust,
durable finishes that resist stains.

From this information, the team can identify shared needs and conflicts. For example, students may want more storage, but that could make the desk heavier. Designers then have to decide how to balance needs using evidence and priorities.

This process shows why capturing user needs is not just asking, “What do you want?” It is about understanding real use in context. 🧠

From user needs to engineering requirements

Once needs are collected, they must be translated into engineering requirements. A user need is usually broad, but an engineering requirement is specific and testable.

For example:

User need: “The bottle should be easy to carry.”
Engineering requirement: “The bottle mass shall be less than $500\,\text{g}$ when empty.”

Another example:

User need: “The seat should be comfortable.”
Engineering requirement: “The seat height shall be adjustable between $400\,\text{mm}$ and $500\,\text{mm}$.”

This translation matters because engineers need clear targets. Requirements should be measurable where possible. They often include words such as “shall,” values, tolerances, time limits, or performance levels.

A helpful rule is that a good requirement should be:

clear,
specific,
measurable,
realistic,
linked to a user need.

If a requirement cannot be checked, it is hard to know whether the product meets it.

Why capturing user needs is important

Capturing user needs improves the chance that a product will be useful, safe, and successful. It reduces the risk of redesign later, saves time and money, and helps the final product fit real-world use.

It also supports fairness and accessibility. If designers only think about an average user, they may exclude people with different body sizes, strengths, abilities, or habits. By asking a wider group of users, designers can create products that work better for more people.

For example, a door handle should be usable by a child, an older person, or someone carrying bags. A website should be readable on a small screen and usable by someone with limited vision. In both cases, capturing user needs leads to better inclusion.

In manufacturing, user needs also influence material choice and production methods. A product meant for outdoor use may need weather-resistant materials. A product for young children may need rounded edges and non-toxic finishes. So user needs shape not only the final design but also the way it is made.

Conclusion

students, capturing user needs is the first major step in turning an idea into a successful product. It means finding out what users really need by using interviews, observation, questionnaires, testing, and feedback. Those needs are then organized, compared, and translated into clear engineering requirements. This process sits at the heart of Requirements and Stakeholders because design must satisfy users while also respecting other stakeholders, including manufacturers, buyers, and regulators. A strong product is not built from guesses; it is built from evidence about real people and how they use things. ✅

Study Notes

User needs are the real wants, problems, and expectations people have when using a product.
A need is not always the same as a solution; designers must look for the deeper problem.
Stakeholders include users, buyers, clients, manufacturers, retailers, regulators, and society.
Capturing user needs is part of the wider topic of Requirements and Stakeholders.
Common methods include interviews, questionnaires, observation, focus groups, testing, and feedback.
Raw user comments must be translated into clear design information.
Needs can be grouped into functional, ergonomic, aesthetic, performance, safety, and environmental categories.
User needs should be turned into measurable engineering requirements.
Good requirements are clear, specific, measurable, realistic, and linked to a user need.
Capturing user needs helps make products safer, more useful, more accessible, and more successful.