Defining Problems and Design Briefs

Welcome, students 👋. In IB Design Technology HL, the Process is not just about making a prototype and hoping it works. It starts much earlier, with figuring out the real problem and turning that into a clear design brief. If the problem is unclear, every later decision can go in the wrong direction. If the brief is strong, the whole project becomes easier to guide, test, and improve.

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

• explain what a design problem and design brief are,
• distinguish between a vague need and a well-defined problem,
• create a design brief using evidence and user needs,
• connect this stage to research, prototyping, sustainability, and iterative development,
• use IB Design Technology HL reasoning to justify why a project should move forward.

A good starting question is this: Are we solving the right problem? 🤔 In design, that question matters as much as the final product itself.

What it means to define a problem

Defining a problem means identifying exactly what needs to be improved, for whom, and under what conditions. In IB Design Technology HL, this is part of the early design process methodology. It happens before detailed sketches, before CAD modelling, and before prototype testing. A designer must first understand the situation, not just the product.

A problem statement is different from a solution. For example, saying “Students need a better chair” is too broad. A stronger problem definition might be: “Students in a computer lab need seating that supports posture during $2$-hour lessons, fits under fixed-height desks, and can be cleaned easily.” That statement identifies a user group, a context, and a set of needs.

A well-defined problem usually includes:

• the user or stakeholder,
• the context or environment,
• the need or difficulty,
• any relevant constraints such as cost, size, materials, time, or safety.

This stage matters because design decisions depend on accurate information. If a product is built for the wrong need, even a beautifully made prototype can fail in practice.

From need to design brief

Once the problem is clearly defined, the next step is writing a design brief. A design brief is a short, clear summary of what the designer intends to do. It explains the design challenge and sets the direction for the work that follows.

A design brief is not yet a full list of specifications. It is broader than a specification sheet. Think of it as the bridge between understanding the problem and planning the solution. It answers questions like:

• What is being designed?
• Who is it for?
• What purpose will it serve?
• What general approach or direction is suitable?

For example, if the problem is that a student carries too many loose items between classes, a design brief might be: “Design a lightweight, durable organizer that helps secondary school students carry and access essential stationery efficiently during a busy school day.”

Notice that the brief is specific enough to guide design decisions, but not so narrow that it already decides the final shape. That balance is important in HL design work.

Using research and evidence to define the problem

Good problem definition is based on evidence, not guessing. In IB Design Technology HL, research supports stronger design decisions throughout the process. Designers often use:

• user interviews,
• observations,
• questionnaires,
• measurements,
• product analysis,
• case studies,
• market research.

For example, if a school wants a better lunch container, a designer might observe how students actually use containers, note common spills, measure bag space, and compare existing products. This research may reveal that the real issue is not just keeping food fresh, but also fitting a container into a crowded backpack and making it easy to open quickly.

Evidence helps define the true problem. It also avoids designer assumption, where a solution is based on what the designer thinks users want rather than what users actually need. In HL terms, the quality of early research affects the quality of the whole project.

A strong design brief should therefore be linked to evidence. For example, if research shows that many students reuse plastic bottles but lose them often, the design brief may focus on a bottle accessory, a tracking feature, or a secure carrying system. The evidence shapes the direction.

Constraints, criteria, and success factors

A design brief becomes more useful when it leads into clear design criteria. These are the features the final solution should meet. They are often written as measurable or testable points. For example:

• the product should weigh less than $500\ \text{g}$,
• the product should fit within a backpack space of $300\ \text{mm} \times 200\ \text{mm} \times 80\ \text{mm}$,
• the product should be easy to clean with common school cleaning methods,
• the product should use materials suitable for repeated daily use.

A good project also considers constraints. Constraints are limits that designers must work within, such as budget, available tools, production time, sustainability goals, and safety standards. In the Process topic, these constraints matter because they affect prototype choices and final feasibility.

Success factors may also include usability, durability, aesthetics, and environmental impact. For instance, a solution may be successful if it uses recycled material, is easy to repair, and lasts a long time. This connects directly to sustainability and circular design. Designing for reuse, repair, disassembly, and material efficiency can begin right at the problem-definition stage.

Sustainability and circular design in problem definition

In modern design, the best problem definition does more than describe user inconvenience. It also considers environmental responsibility. Circular design aims to keep materials and products in use for as long as possible, reducing waste and extending life cycles ♻️.

When defining a problem, designers can ask:

• Can the product be repaired instead of replaced?
• Can it be made from recycled or responsibly sourced materials?
• Can parts be separated for recycling at the end of life?
• Can the design reduce energy or material use during production?

For example, if a broken plastic school tray is being replaced, the real problem might not simply be “make a new tray.” A more thoughtful problem could be: “Design a durable, easy-to-clean tray system that reduces replacement frequency and supports recycling at end of life.” That wording points toward longer-lasting and lower-impact solutions.

In IB Design Technology HL, this kind of thinking shows understanding of the broader Process. The process is not only about solving a user problem today; it also considers long-term effects on people and the environment.

Iterative development begins with a good brief

Iteration means improving a design through repeated testing and refinement. However, iteration works best when the original problem definition is accurate. If the brief is weak, designers may keep improving the wrong thing.

For example, imagine a prototype for a reading lamp. If the real problem is glare causing eye strain, but the brief focuses only on style, the prototype may look attractive but still fail in use. A stronger brief would include lighting quality, adjustable angle, and user comfort. Then prototypes can be tested against those needs.

This is why defining the problem and writing the brief are not “admin tasks.” They are active parts of the design process. They shape the questions that prototypes must answer, such as:

• Does the solution meet the user need?
• Does it fit within the constraints?
• Does it solve the right issue efficiently?
• Does it support sustainability goals?

When a prototype is tested, designers compare results with the brief and criteria. If the answer is no, the design may need to be revised. This is a normal and important part of iterative development.

Example: turning a vague issue into a strong brief

Let’s look at a real-world school example. Suppose students say, “Our art room is messy.” That is a complaint, not a design brief.

A designer would investigate further and might discover:

• tools are shared by many students,
• small items are lost easily,
• cleaning takes too long between classes,
• storage is limited,
• some containers break after repeated use.

A stronger problem definition could be: “The art room needs a storage solution that helps students and teachers keep small tools organized, visible, and easy to access during short class periods.”

A design brief based on that might be: “Design an affordable, durable, and space-efficient storage system for an upper secondary art room that improves organization, reduces time spent searching for tools, and supports easy maintenance.”

This brief gives direction without fully deciding the final solution. It leaves room for creativity while still keeping the project focused.

Conclusion

Defining problems and writing design briefs are essential first steps in the IB Design Technology HL Process. They help designers identify the real user need, use evidence instead of assumptions, and create a clear direction for research, prototyping, and evaluation. A strong problem definition leads to a stronger brief, which leads to better design decisions throughout the project.

When you understand this stage, you can connect it to the full design process: research informs the brief, the brief guides prototyping, testing supports iteration, and sustainability strengthens the quality of the final outcome. For HL work, this means thinking carefully, justifying choices with evidence, and designing with both users and the wider world in mind 🌍.

Study Notes

• A design problem explains what needs to be improved, for whom, and in what context.
• A design brief is a short statement that sets the direction for the design task.
• Good problem definition is based on evidence, not assumptions.
• Research methods may include interviews, observations, questionnaires, measurements, and product analysis.
• A brief should be clear but not over-specific; it should guide creativity, not replace it.
• Constraints can include cost, time, safety, size, tools, and available materials.
• Design criteria are the features the final solution should meet and can often be tested.
• Sustainability and circular design can be built into the brief by considering repair, reuse, recycling, and material efficiency.
• Iteration works best when the original problem is correctly defined.
• In IB Design Technology HL, defining the problem and writing the brief are foundational parts of the broader Process.