Identifying a Problem or Need

students, every successful design project begins with a clear reason to exist. A product, system, or service is not designed just because it is possible to make one; it is designed because someone has a problem, limitation, or need that should be improved. In IB Design Technology HL, identifying a problem or need is the first major step in the design process, and it shapes every decision that follows. If the problem is poorly understood, the rest of the project can drift off track. If the need is carefully defined, the designer can create a focused, realistic, and useful solution. 🚀

In this lesson, you will learn how designers identify problems and needs, how to separate a real need from a guess, and how this step connects to the full design project and practical programme. You will also see how evidence, research, and evaluation help turn a vague idea into a strong design brief.

What Does It Mean to Identify a Problem or Need?

Identifying a problem or need means finding a situation where improvement is required and explaining it clearly. In design technology, this is more than saying, “I want to make something cool.” Instead, the designer asks: What is wrong, missing, inconvenient, unsafe, inefficient, expensive, uncomfortable, or inaccessible? Who is affected? Why does it matter?

A problem is often a difficulty that can be observed. For example, a school corridor may be too narrow during break time, causing crowding. A need is something that helps people achieve a goal more effectively. For example, students may need a better way to carry lunch without spills. Sometimes the problem and need overlap. A cyclist may have trouble riding safely in the dark, so there is a need for better lighting and visibility.

In IB Design Technology HL, this stage is important because it starts the chain that leads to research, modelling, testing, development, and final communication. The stronger the problem statement, the more meaningful the project becomes.

Client, Target Audience, and End-User

To identify a problem or need properly, students, you must know who the design is for. These three terms are closely related but not identical.

The client is the person, company, or organization that asks for the design or commissions the work. The client might also set expectations, constraints, or goals. For example, a school principal could be the client for a new student seating area.

The target audience is the group of people the design is intended to reach. This group may be broad. For example, a water bottle brand may target teenagers who play sports.

The end-user is the person who will actually use the final design. In many school projects, the client and end-user may be different. A teacher may request a classroom storage solution, but the end-users are the students who open and close it every day.

This distinction matters because the real need must come from the end-user’s experience, not just from assumptions. A design can look good to a client but still fail if it does not suit the people who use it most often.

How Designers Discover Problems and Needs

Designers do not usually invent a need out of thin air. They use evidence. Evidence can come from observation, interviews, surveys, measurements, market research, photographs, or product analysis. In practical terms, this means watching how people behave, listening to complaints, and checking whether a problem actually exists.

For example, if students notices that many students carry books, devices, and sports gear at the same time, that observation may suggest a need for better organization. But the idea becomes stronger if interviews show that students often drop items, struggle to keep things dry, or forget equipment at home. That extra evidence turns a guess into a real design opportunity.

Useful questions include:

What is happening now?
Who is experiencing the problem?
How often does it happen?
What causes it?
What happens if nothing changes?
What evidence shows that the issue is real?

These questions help the designer avoid solving the wrong problem. A common mistake is focusing on a visible symptom instead of the root cause. For example, if students are late to class, the problem may not be the students themselves. The real issue might be overcrowded lockers, poor timetable planning, or long distances between rooms.

From Broad Problem to Clear Design Brief

A good problem or need statement becomes the foundation for the design brief. The design brief is a short statement that describes what needs to be designed and why. It usually includes the client, end-user, context, and purpose.

A weak statement might say, “Students need a better desk.” This is too vague. What is wrong with the desk? Who needs it? Where will it be used?

A stronger statement might say, “Secondary students in shared study spaces need an adjustable desk organizer that keeps stationery and devices separated, because current flat surfaces become cluttered and reduce study efficiency.” This version identifies the user, the setting, the issue, and the reason it matters.

Notice that the statement does not yet include exact design solutions. That comes later. At this stage, the designer is defining the challenge, not finalizing the product.

A strong design brief should be:

specific
realistic
based on evidence
linked to the user
open enough to allow creative solutions

This balance is important in IB Design Technology HL because the project must show both creativity and clear reasoning.

Why Evidence Matters in IB Design Technology HL

In the IB course, design choices should be justified. That means students must be able to explain why a need is important and how research supports the project direction. Evidence can include user feedback, measurements, existing product analysis, safety information, and environmental data.

For example, if the problem involves carrying a laptop safely, then weight, size, material strength, and comfort become relevant facts. If the issue is accessibility, then dimensions, grip, height, reach, and usability for different users matter. If the need is for an environmentally responsible product, then lifecycle, recyclability, durability, and repairability may be important.

Evidence is useful because it helps the designer avoid personal bias. A designer may think a product is convenient, but users may disagree. Real design decisions should be based on what users actually need, not only on what the designer prefers.

A practical example is a reusable lunch container. The designer might think the main need is style, but research may show that leaks, dishwasher safety, and size for school bags are more important. In that case, the real problem statement changes, and the design direction becomes more accurate.

Connecting This Step to the Full Design Project

Identifying a problem or need is not an isolated task. It links directly to the whole design project and practical programme. Once the need is established, the designer can create research questions, develop specifications, build prototypes, test ideas, and improve the solution through feedback.

This stage connects to later steps in several ways:

Research becomes focused because the designer knows what information is needed.
Modelling becomes purposeful because prototypes are made to test specific ideas.
Testing becomes meaningful because results can be compared with the original need.
Development becomes logical because improvements are based on real user feedback.
Documentation becomes stronger because the design process has a clear starting point and reason.

If the problem statement is weak, the whole project can become confusing. If the problem statement is strong, every later page in the design folder has a clear purpose.

Example: Turning an Observation into a Design Need

Imagine students is researching the school environment and notices that students often carry wet umbrellas into classrooms after rain. Water drips onto floors, making them slippery and messy.

At first, the observation is just a situation. After asking questions and gathering evidence, the designer learns that the problem happens often during the rainy season, especially in busy hallways. The users affected are students, teachers, and custodial staff. The need is not simply “an umbrella product.” The real need may be a compact, easy-to-clean umbrella storage solution near classroom entrances.

A possible design brief could be: “Students and staff need a convenient way to store wet umbrellas near classroom entrances to reduce slipping hazards and water damage during rainy periods.”

This example shows how observation becomes a defined need. It also shows how design thinking is practical and human-centered. 🌧️

Common Mistakes to Avoid

When identifying a problem or need, students sometimes make these mistakes:

Being too vague: saying the problem is “bad organization” without explaining what is disorganized.
Jumping to a solution too early: deciding on a product before understanding the need.
Ignoring the end-user: focusing on the client’s wishes but not the actual user’s experience.
Using no evidence: relying only on assumptions or personal opinion.
Describing symptoms instead of causes: noticing clutter, for example, without finding out why it happens.
Making the challenge unrealistic: choosing a problem that is too large, expensive, or broad for a student project.

Avoiding these mistakes helps keep the project manageable and credible.

Conclusion

Identifying a problem or need is the starting point of effective design in IB Design Technology HL. It requires observation, evidence, and clear thinking. students, when you can explain who has the problem, what the problem is, why it matters, and how it affects the user, you are already thinking like a designer. This step connects directly to the design brief, research, modelling, testing, and development that follow. A strong problem statement does not just begin the project; it gives the whole project purpose. ✅

Study Notes

Identifying a problem or need means finding a real situation that requires improvement.
A client is the person or organization requesting the design.
A target audience is the group the design is intended to reach.
An end-user is the person who will actually use the final product.
Good design problems are specific, realistic, and based on evidence.
Evidence can come from observation, interviews, surveys, measurements, and product analysis.
A strong problem statement helps create a clear design brief.
The design brief should state what needs to be designed and why, without choosing the final solution too early.
This stage connects to research, modelling, testing, development, and documentation.
Avoid vague statements, assumptions, and jumping to solutions before understanding the real need.
In IB Design Technology HL, identifying a problem or need makes the whole project more focused and meaningful.