Understanding Design Thinking

User experience is where design begins

Before a designer chooses a form, feature or material, somebody is already having an experience. Imagine carrying a bento box to work. It leaks into your bag before lunch. The compartments let curry soak into the salad. One section is too small for the food you enjoy, and the latch refuses to close when your break is nearly over. The object may still look attractive, but the experience includes anxiety, mess, wasted time and a meal that no longer fits your needs.

That experience is larger than the object itself. It begins with expectation and continues through carrying, opening, eating, cleaning and storing. It is also shaped by context: the size of a work bag, access to a microwave, the length of a lunch break, dietary goals and whether the box feels appropriate in a professional setting. Design starts by making this full journey visible.

A designer cannot learn all of this by relying on personal taste. Interviews reveal what people remember and value. Observation reveals workarounds and friction they may no longer mention. Surveys can show whether a pattern appears across a larger group. Product reviews and other secondary research expose recurring failures. Each method adds evidence, but none is automatically the truth on its own.

Design thinking turns experience into a learning process

Design thinking is a human-centred way of moving through uncertainty. It gives a team enough structure to understand a situation, choose a meaningful problem, explore alternatives and learn from things they make. It is useful when the answer is not obvious and when human needs, technical possibilities and real-world constraints must be considered together.

The familiar five modes—Empathize, Define, Ideate, Prototype and Test—are best treated as a map, not a conveyor belt. A test can expose a weak assumption and send the team back to research. A prototype can reveal that the problem was framed too narrowly. New evidence can reopen ideation. Moving backward is not failure; it is the method working.

Implementation brings a tested direction into the world through engineering, production, launch and delivery. Iteration continues after launch as real use produces new evidence. These activities extend the loop; they do not turn design into a one-way sequence with a permanent finish line.

Where the method came from

Design thinking did not appear as one invention at one moment. It grew from a longer conversation about design methods, systems and human-centred practice. Industrial designers, researchers and interdisciplinary teams developed ways to study people, externalize ideas and test possibilities before committing to expensive solutions.

IDEO helped popularize the language of design thinking in business and public problem-solving during the 1990s and 2000s. Stanford’s d.school made a five-mode model widely teachable through project-based learning and an open collection of methods. These models are influential, but they are not universal laws. Different teams name and organize the work differently; the durable principle is to learn about people and the problem while making the solution.

The five working modes

You do not need every method in the table to follow this reading. The worked example uses four: interviews and observation to gather evidence, a point of view to frame it (one sentence naming who needs what, and why), sketching to generate alternatives and a simple prototype to test. Affinity mapping, How Might We questions, SCAMPER and SWOT are optional tools to reach for when a project needs them.

1. Empathize: understand experience in context

Empathy in design is not guessing how another person feels. It is the discipline of noticing where your own experience stops being reliable and gathering evidence from the people affected. Ask about recent events rather than ideal behaviour: “Tell me about the last time you packed lunch” is usually more revealing than “Would you buy a better lunchbox?”

• Listen for goals, trade-offs and language—not only requested features.
• Observe sequence, environment and workarounds. What happens before and after the obvious interaction?
• Separate what a participant says from what you observed and what you inferred.
• Include people whose bodies, routines and constraints differ from the easiest user to recruit.

2. Define: turn research into a useful frame

The Define mode compresses scattered observations into a point of view. A useful frame names a specific person or group, a meaningful need and the insight that makes the need worth addressing. It avoids prescribing the solution too early. “Add more compartments” is a feature; “help office workers keep different foods fresh and separate without carrying several containers” leaves room to design.

A How Might We question turns that frame into an invitation. It should be broad enough to permit several answers but narrow enough to guide a team. For example: “How might we help Priya carry a varied homemade lunch that stays fresh, separate and easy to manage through her workday?”

3. Ideate: create alternatives before choosing

Ideation is deliberate divergence. Generate different approaches before polishing one: removable modules, flexible dividers, a separate sauce vessel, a compact vertical form, an insulating sleeve, fewer parts, or a service that supports shared office storage. Sketching and mind mapping help ideas become discussable. Constraints such as cost, cleaning, material safety and manufacturability can then help the team compare directions.

Tools have different jobs. Brainstorming and SCAMPER help generate possibilities. A SWOT analysis does not prove that an idea is good, but it can expose internal advantages and limitations alongside external opportunities and threats. Use it as one decision aid, not as a substitute for user evidence.

4. Prototype: make the question tangible

A prototype is not a cheaper final product; it is a question made tangible. Its fidelity should match what the team needs to learn. Cardboard and foam may be enough to test size, grip and bag fit. Removable plastic inserts may test compartment proportions. A functional seal is necessary only when the question concerns leakage.

• Write the learning question before building: what must this prototype teach us?
• Build only enough detail for someone to understand and try the relevant part.
• Avoid polishing uncertain ideas; visual finish can make teams and participants reluctant to criticize them.
• Label what is simulated so test participants do not mistake theatre for working functionality.

5. Test: learn, do not seek approval

Testing asks people to use a prototype in a realistic task while the team watches what happens. Instead of presenting the concept and asking whether it is liked, ask someone to pack a typical meal, place the box in their bag, open it at a desk, reheat what they would normally reheat and clean it. Behaviour reveals friction that opinions alone may hide.

Capture success, hesitation, errors, comments and surprises. One session can identify a problem; repeated patterns across participants give stronger direction. A failed test is valuable when it reduces uncertainty. The next move may be to adjust the design, test a different idea or return to the problem frame.

Worked example: a bento box for Priya

Priya is a 30-year-old office worker who enjoys bringing healthy homemade lunches to work. She packs salads, rice and curry, often in multiple containers. The containers crowd her bag; sauces sometimes spill; foods mix; and cleaning several pieces at the end of the day feels tiring. She also wants something microwave-safe and visually appropriate at her desk. This is a teaching scenario, so its findings are hypotheses until real research supports them.

Empathize with more than an interview

• Interview Priya about the last several lunches she packed, what she chose not to bring and why.
• Observe her packing the meal, fitting it into her bag, reheating it and cleaning up.
• Ask colleagues with different diets and commutes about similar routines without assuming Priya represents everyone.
• Review competing products and complaints to identify common issues such as leakage, staining, trapped odours and difficult seals.

Says should come from direct statements. Does should come from observation. Thinks and Feels are interpretations that need checking. Keeping those categories distinct prevents an empathy map from becoming a polished collection of assumptions.

Define the problem and opportunity

The evidence suggests four connected needs: keep foods fresh and separate, prevent leaks, simplify packing and cleaning, and suit the routines of an office day. A working point of view could be: Priya needs a compact way to carry a varied homemade lunch because managing several containers creates spills, mixed food and avoidable effort before and after eating.

• How might we keep wet and dry foods separate without multiplying containers?
• How might we make every food-contact surface easy to reach and clean?
• How might we support reheating one part of the meal without heating everything?
• How might we make correct closure obvious before the box enters a bag?

Ideate, then inspect the leading direction

The team sketches several systems before selecting one direction: a shallow box with removable sealed modules, colour or texture cues that show where each module belongs, a compact sauce container, a lid that confirms closure, and dishwasher-safe parts without narrow crevices. The concept remains provisional; each feature carries an assumption to test.

Prototype the riskiest assumptions first

A cardboard volume model tests whether the box fits Priya’s bag and desk. Foam blocks stand in for a typical meal so compartment sizes can change quickly. A second prototype uses food-safe sample containers to test removal and reheating. Only after those questions are answered does the team invest in a functional seal prototype for leakage and durability.

Test the whole lunch journey

Priya packs and uses the prototype across several workdays while keeping a short diary. The team observes at least one complete cycle and records whether the box fits her bag, stays closed, keeps foods separate, makes reheating clear and can be cleaned within her normal routine. Other participants test it too, because a solution tailored only to Priya may fail people with different grip strength, bag sizes, meal types or access to appliances.

Suppose testing shows that the large latch is secure but hard to operate, and that removable compartments solve reheating but create too many pieces to wash. Those are not cosmetic notes. They change the next prototype: explore a closure requiring less force, reduce part count and retest leakage rather than moving directly to production.

Use the process without becoming trapped by it

Design thinking is useful because it makes reasoning visible. It does not guarantee a good outcome, remove the need for domain expertise or represent every design practice. Research can be biased, workshops can create false consensus, and a neat process diagram can hide difficult decisions about cost, access, safety and whose needs receive priority.

1. Name the decision you are trying to make.
2. Write down the evidence you have and the assumption you are making.
3. Choose the cheapest responsible action that could reduce the important uncertainty.
4. Make the result visible through notes, sketches, prototypes and test observations.
5. Decide whether to continue, revise the idea, reframe the problem or stop.

To try the loop once, pick one object you use every day that annoys you. Watch yourself use it for a day and note one moment of friction. Write one sentence naming who needs what, and why. Sketch three different responses, make the cheapest from paper or tape and use it for a day. What you notice decides whether you revise, reframe or stop.

The point is not to perform every method. It is to keep the connection between a person’s experience, the problem you chose, the thing you made and what you learned. When that chain is visible, design becomes a disciplined practice of inquiry rather than a defence of the first idea.