Defining Problems and Design Briefs

Welcome, students 👋 In IB Design Technology SL, every successful design starts with one essential step: understanding the problem clearly. If the problem is vague, the solution will usually be weak, expensive, or unusable. If the problem is defined well, the rest of the design process becomes much easier.

In this lesson, you will learn how designers identify real needs, turn them into clear problem definitions, and write effective design briefs. You will also see how this fits into the broader Process topic, which includes research, prototyping, iteration, sustainability, and design decision-making.

By the end of this lesson, you should be able to:

Explain the main ideas and key terms behind defining problems and design briefs.
Apply IB Design Technology SL reasoning to a design situation.
Connect problem definition and design briefs to the wider design process.
Use examples and evidence to show how a strong brief guides design work.

Why problem definition matters

A design project usually begins with a situation, need, or challenge. For example, a school cafeteria may need a better way to reduce food waste 🍽️, a student may need a better way to carry books, or a community may need safer lighting for a pathway at night 💡. At first, these are broad issues. Designers must investigate them and identify the real problem before making solutions.

A common mistake is jumping straight to ideas. For example, if the problem is “students are uncomfortable in class,” a student designer might immediately suggest a new chair. But the discomfort might actually come from poor posture support, the height of desks, room temperature, or long sitting time. Defining the problem correctly prevents wasted effort.

In design technology, a good problem definition is:

Clear and specific.
Based on evidence, not guesses.
Focused on the user and context.
Narrow enough to be solvable, but broad enough to allow creativity.

This is why defining the problem is part of the design process, not a separate activity. It shapes every later stage, including research, specification writing, prototyping, testing, and evaluation.

From a need to a design problem

A need is often the starting point. It may come from a user, a business, a community, or a global issue. However, a need is not yet a design problem. Designers must transform the need into a solvable problem.

Here is the difference:

Need: “Students need a way to keep lunch boxes cold during travel.”
Problem statement: “How might students transport lunch so it stays cool for at least $4$ hours without using electricity?”

The second version is more useful because it includes a goal and a measurable expectation. It also hints at constraints such as no electricity, which is important in real design work.

Good problem definition usually involves research. Designers gather evidence through observation, interviews, surveys, measurements, and existing information. For example, if a designer wants to reduce plastic waste in a school, they might measure how many disposable cups are used each day, ask students why they use them, and examine current disposal systems. This evidence helps define the real issue.

A strong problem definition should answer questions like:

Who is the user?
What is the need or difficulty?
Where and when does the problem happen?
Why does it matter?
What limits or constraints exist?

What is a design brief?

Once the problem has been defined, the next step is the design brief. A design brief is a short statement that explains what the designer intends to create in response to the problem.

It is not a full solution and not a detailed plan. Instead, it sets the direction for the project. The design brief helps the designer stay focused and gives everyone involved a shared understanding of the task.

A design brief often includes:

The user or audience.
The problem to be solved.
The intended outcome.
Important context or constraints.

For example:

“Design a portable lunch container for secondary school students that keeps food cool for a school day, is easy to carry, and uses durable materials.”

This brief is useful because it tells the designer what kind of solution is needed without deciding the exact shape, size, or mechanism too early. That leaves room for creativity and iteration.

A design brief is linked closely to the specification, but they are not the same. The brief is a general statement of intent. The specification is more detailed and includes measurable requirements the final product must meet.

Writing a strong problem definition and brief

To write a strong design brief, students, you must first make sure the problem has been defined properly. A weak problem definition leads to a weak brief. A strong one leads to better design decisions.

A useful approach is to follow these steps:

Identify the user and context 🧍

Who needs help, and where is the problem happening?

Collect evidence 🔎

Use observations, surveys, interviews, and existing data.

Analyse the findings

Look for patterns. What is the real issue?

State the problem clearly

Turn the need into a focused problem statement.

Write the design brief

Describe the intended design response.

Here is an example in a school context.

Observation: Many students carry heavy bags and complain of shoulder pain.
Research finding: A large number of students walk long distances between home and school.
Problem statement: Students who walk to school need a way to carry books and devices more comfortably and safely.
Design brief: Design a carrying solution for walking students that reduces strain, protects contents, and is practical for daily use.

Notice how the brief is broader than a final product idea. It does not say “design a backpack with six pockets and blue fabric.” That would be too narrow too early.

Connection to sustainability and circular design

In IB Design Technology SL, problem definition should also consider sustainability 🌱. Designers should think beyond appearance and cost. They must consider materials, energy use, durability, repairability, and end-of-life options.

For example, if the problem is that students throw away broken plastic pencil cases, the design brief might encourage a repairable or recyclable solution. This links to circular design, where products are made to last longer, be repaired, reused, or recycled rather than quickly discarded.

A sustainability-aware brief might include points such as:

Use materials with lower environmental impact.
Make the product durable and repairable.
Reduce unnecessary components.
Consider how the product will be disposed of or reused.

This matters because the design process is not only about solving a user problem. It is also about making responsible decisions. In IB Design Technology SL, the best solutions balance user needs, technical feasibility, and environmental responsibility.

How this fits into the wider process

Defining the problem and writing the design brief are early stages of the design process, but they affect everything that comes after.

If the problem is unclear, research will be unfocused, ideas may be random, and prototypes may not solve the real issue. If the brief is strong, the designer can create relevant specifications, generate ideas, test prototypes, and evaluate results against clear goals.

Here is how it connects:

Research: gathers evidence to define the problem.
Problem definition: identifies the core need.
Design brief: states the design intention.
Specification: lists measurable requirements.
Prototyping: develops possible solutions.
Testing and iteration: improves the solution.
Evaluation: checks whether the final design meets the brief and specification.

For example, if the brief is to design a low-cost desk lamp for shared study spaces, the research stage might investigate lighting levels, user preferences, and energy use. The prototype stage may explore shape and light distribution. Testing might measure whether the lamp provides enough light for reading. Evaluation checks whether the final product meets the original brief.

This is why defining the problem is not a small first step. It is the foundation of the entire project.

Conclusion

Defining problems and writing design briefs are essential parts of the design process in IB Design Technology SL. A strong design process starts with evidence, careful thinking, and a clear understanding of the user and context. students, when you define the problem well, you improve the chances of creating a solution that is practical, meaningful, and sustainable.

A good designer does not rush to make ideas before understanding the issue. Instead, the designer researches, defines the need, writes a focused brief, and then develops solutions that can be tested and improved. This is how problem definition supports successful design work across the whole Process topic.

Study Notes

A need is a situation where something is missing, difficult, or ineffective.
A problem definition turns a broad need into a clear, evidence-based design problem.
A good problem definition is specific, focused on the user, and based on research.
A design brief is a short statement that explains what the designer intends to create.
The design brief is broader than a specification and does not give all the exact details.
Research helps designers avoid guessing and identify the real issue.
Strong briefs leave room for creativity while still giving clear direction.
Sustainability should be considered early, including materials, durability, repairability, and end-of-life.
Problem definition connects directly to research, prototyping, iteration, and evaluation.
In IB Design Technology SL, a strong process begins with defining the problem well.