Design Thinking for Real Problems

What Is Design Thinking?

Design thinking is a problem-solving methodology that puts people at the center of every decision. Originally developed in the world of product design and engineering, it has become one of the most effective approaches for tackling complex real-world challenges. Its power lies in a simple principle: the best solutions come from deeply understanding the people you are designing for, not from assuming you already know what they need.

For product building, this matters enormously. Well-intentioned projects fail all the time, not because the people behind them lacked passion or resources, but because they designed solutions based on their own assumptions rather than the lived experiences of the communities they aimed to help. Design thinking provides a structured process for avoiding that trap.

The methodology consists of five phases: Empathize, Define, Ideate, Prototype, and Test. These phases are not strictly linear. You will often loop back to earlier stages as you learn more. That iterative quality is a feature, not a flaw. It ensures that your solution keeps improving based on real feedback.

If you completed the root cause analysis in Chapter 3: Understanding Root Causes, you already have a strong foundation for the first two phases. Now you will learn how to move from understanding to action.

Phase 1: Empathize

Empathy is the foundation of human-centered design. In this phase, your goal is to understand the experiences, emotions, needs, and motivations of the people affected by the problem you are working on. This goes far beyond reading statistics or news articles. It requires direct, respectful engagement with real people.

Conducting Empathy Interviews

An empathy interview is a one-on-one conversation designed to uncover how someone experiences a particular situation. It is not a survey or a questionnaire. It is an open-ended dialogue that follows the interviewee's lead.

Preparation. Identify people who are directly affected by the issue. Approach them respectfully and explain who you are, what you are working on, and why their perspective matters. Make it clear that there are no right or wrong answers and that they can stop the conversation at any time.

During the interview. Ask open-ended questions that invite stories rather than yes-or-no answers. "Tell me about a time when..." is more productive than "Do you think...?" Listen actively. Follow up on emotional cues. If someone mentions feeling frustrated, ask what that frustration felt like and what caused it. Take notes, but maintain eye contact and genuine presence.

Key questions to consider:

• Can you walk me through a typical day as it relates to this issue?
• What is the hardest part of dealing with this challenge?
• What have you tried in the past, and how did it work?
• If you could change one thing about this situation, what would it be?
• Is there anything I have not asked about that you think is important?

After the interview. Write up your notes immediately while the conversation is fresh. Look for themes, surprises, contradictions, and emotional moments. These are the raw materials for the next phase.

Immersion and Observation

Interviews are powerful, but they capture what people say, which is not always what people do. When possible, supplement interviews with direct observation. Spend time in the environments where the problem occurs. Visit the school, the neighborhood, the clinic, or the community center. Pay attention to how people interact with their surroundings, what workarounds they have developed, and what barriers are visible in the physical space.

Phase 2: Define

In the Define phase, you synthesize everything you learned during empathy work into a clear, actionable problem statement. This is one of the most important steps in the entire process because it determines the direction of everything that follows.

Synthesizing Your Research

Gather your interview notes, observation records, and any data you have collected. Look for patterns. What needs came up repeatedly? What emotions were most common? What surprised you?

Create an empathy map for the people you spoke with, organized around four quadrants: what they Say, what they Do, what they Think, and what they Feel. The gaps between these quadrants are often where the most important insights live. Someone might say they are fine with a situation while their behavior reveals significant frustration.

Crafting a Problem Statement

A strong problem statement follows this format:

[Specific group of people] need [specific need] because [insight from your research].

For example: "Students at Lincoln High who rely on public transit need a way to access after-school tutoring because the last bus leaves 20 minutes before tutoring sessions end, making it impossible for them to attend without missing their ride home."

Notice how specific this is. It identifies a particular group, a concrete need, and a research-backed reason. Compare that to a vague statement like "Students need better academic support." The specific version gives you something to design for. The vague version gives you almost nothing.

Avoid embedding a solution in your problem statement. "Students need a later bus" is not a problem statement; it is a premature solution. The problem is that students cannot access tutoring. A later bus is one possible solution, but there might be others, and you will discover them in the next phase.

Phase 3: Ideate

Ideation is where creativity takes center stage. The goal is to generate as many potential solutions as possible without judging them. Quantity matters more than quality at this stage because breakthrough ideas often emerge from unexpected combinations of ordinary ones.

Brainstorming Techniques

Classic brainstorming. Gather your team, state the problem, and generate ideas freely for a set period of time, usually 15 to 30 minutes. Write every idea on a sticky note or whiteboard. The rules are simple: no criticism, no evaluation, and no "yes, but" responses. Build on each other's ideas with "yes, and" instead.

Worst possible idea. Deliberately brainstorm the worst solutions you can imagine. This technique loosens creative tension and often leads to surprisingly good ideas when you flip the bad ones on their head. If the worst idea is "make tutoring even less accessible," the flip might be "bring tutoring directly to the bus stop."

How Might We. Reframe your problem statement as a series of "How might we..." questions. Each question opens a different angle on the problem. "How might we bring tutoring to students who cannot stay after school?" "How might we make the bus schedule work for students?" "How might we create tutoring experiences that do not require being physically present?"

SCAMPER. This technique asks you to Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, or Reverse elements of existing solutions to generate new ones.

Selecting Ideas to Pursue

After brainstorming, you will have a large collection of ideas. Now it is time to evaluate them. Consider each idea against three criteria: Desirability (do people actually want this?), Feasibility (can you realistically build or implement this with available resources?), and Impact (will this meaningfully address the problem?).

You do not need to select a single idea. In fact, it is often better to carry two or three promising concepts into the next phase and let prototyping reveal which one works best.

Phase 4: Prototype

A prototype is a quick, low-cost representation of your idea that you can put in front of real people to get feedback. The purpose of prototyping is not to build a finished product. It is to learn as fast as possible what works and what does not.

Rapid Prototyping Principles

Keep it simple. Your first prototype should take hours to build, not weeks. If you are designing a physical space, use cardboard and tape. If you are designing a service, create a storyboard that walks through the user experience step by step. If you are designing a digital tool, sketch the screens on paper before writing a single line of code.

Make it tangible. People respond better to something they can see, touch, or interact with than to a verbal description. Even a rough prototype gives people something concrete to react to, and those reactions are gold.

Build to learn, not to impress. The goal is to test your assumptions, not to demonstrate your skills. A prototype that reveals a fatal flaw in your concept is far more valuable than one that looks polished but teaches you nothing.

Types of Prototypes

• Storyboards: A series of drawings or images that depict how someone would experience your solution from start to finish.
• Role-playing: Act out the experience with team members playing different roles. This is especially useful for service-based solutions.
• Paper mockups: Hand-drawn sketches of screens, forms, flyers, or physical spaces.
• Landing pages: A simple web page that describes your concept and gauges interest before you build anything.
• Pilot programs: A small-scale version of your initiative, run with a limited group, to test the core concept in real conditions.

Phase 5: Test

Testing means putting your prototype in front of the people you designed it for and observing what happens. This is where your empathy skills come back into play because you need to listen without defensiveness and learn without ego.

How to Run a Useful Test

Recruit real users. Test with people who represent the community you are designing for, not with your friends, your family, or your team. Their feedback is well-meaning but unreliable because they are not the ones who will use your solution.

Observe before you ask. Watch how people interact with your prototype before asking them questions. Do they understand how to use it? Where do they hesitate or get confused? What do they ignore? Behavior reveals truths that words sometimes hide.

Ask open-ended questions. "What did you think?" is more useful than "Did you like it?" Encourage honest, critical feedback by making it clear that you want to improve the solution, not defend it.

Document everything. Take notes on what worked, what did not, and what surprised you. Each piece of feedback is data that will inform your next iteration.

Iteration: The Cycle Continues

Testing will almost certainly reveal that your solution needs changes. That is expected and welcome. Revise your prototype based on what you learned, then test again. Each cycle of build-test-learn brings you closer to something that genuinely serves the community.

Some tests will send you all the way back to the Define phase because you will discover that you were solving the wrong problem. That is not failure. It is the design process working exactly as intended.

Applying Design Thinking at Loona

Design thinking is woven into every program we offer at Loona. Whether you are building a tool for environmental data, a health and wellness app, or an educational platform, you will use these five phases to develop products that are grounded in real human needs rather than abstract assumptions.

You can also find stories of design thinking in action in our articles section, where we profile young founders who have used these methods to build products that made a genuine difference in their communities.

In the next chapter, Building Your Team, you will learn how to assemble and lead the group of people who will help you bring your design-thinking process from prototype to reality.