Design Thinking

Most failed solutions are not badly built; they are built for a problem nobody actually had. Design thinking is a discipline for staying anchored to real human needs while you invent, so that effort flows toward something people genuinely want rather than something that merely seemed clever in a meeting.

It also lowers the cost of being wrong. By putting rough prototypes in front of real people early, you discover a flawed assumption when it costs a sketch, not when it costs a launch.

The five modes

Empathize — observe and talk to the people who have the problem. Define — turn what you learned into a sharp problem statement. Ideate — generate many options before judging any of them. Prototype — build a rough, tangible version. Test — put it in front of users and learn. These are modes, not fixed steps: testing sends you back to redefine or re-ideate, and you loop until the need is genuinely met.

Start from the user, not the solution

Design thinking is human-centered: the process begins with a person's actual experience, not with a technology or an org chart. A good problem statement names a user, a need, and an insight — "a busy parent needs a faster way to get a healthy dinner on the table" — rather than "we need an app." Naming the user keeps the whole team honest about who they are serving.

Prototype to think

A prototype is a question made tangible. Its job is to provoke a reaction and expose wrong assumptions cheaply — a paper sketch, a cardboard mock-up, a role-play in an empty room. Fidelity should match the question you are asking: if you only need to know whether people understand a menu, do not build the whole kitchen.

A campus team wants students to eat more healthily. Instead of designing an app, they spend a day watching the dining hall (empathize) and notice that students skip the salads because the salad line is slow and the plates are small. They define the problem: "Students who want a healthy option need it to be as fast and filling as the burger line." They ideate dozens of ideas, then prototype the simplest: they move a cart of pre-made salads next to the fast line with a hand-lettered sign, and test it for a week. Sales triple. The winning insight — convenience, not persuasion — came from watching real behaviour, and the test cost almost nothing.

Design thinking is not a licence to skip rigour. A team that "empathizes" by guessing what users want, runs one brainstorm, and calls its favourite idea a prototype has performed the ritual without the substance. If you never actually observe users and never test with them, you have simply decorated an ordinary opinion with sticky notes. The value lives in real contact with real people and honest feedback — not in the vocabulary.

The intellectual root is Herbert Simon's 1969 book The Sciences of the Artificial, which framed design as a rigorous activity rather than mere decoration: "everyone designs who devises courses of action aimed at changing existing situations into preferred ones."

The modern practice was popularized by the design firm IDEO and by Stanford's Hasso Plattner Institute of Design — the "d.school" — founded in 2005 with IDEO co-founder David Kelley among its founders. A widely cited demonstration aired in 1999, when ABC's Nightline filmed IDEO redesigning the humble shopping cart in five days (the episode "The Deep Dive"). The team observed shoppers and store staff, generated a wall of ideas, built a rough prototype, and produced a cart with a modular basket system, better maneuverability, and child-safety features — empathy, ideation, and rapid prototyping compressed into one visible loop. The five-mode model taught today (empathize–define–ideate–prototype–test) is the version associated with the d.school.

• "It's just brainstorming." Ideation is one mode; empathy and testing carry equal weight.
• "Prototypes must be polished." A rough sketch that answers the question beats a costly build that doesn't.
• "It's only for physical products." The method applies to services, processes, and policy just as well.
• "One pass is enough." It is iterative; results from testing routinely send you back to redefine the problem.

Take a solution-shaped request such as "build us a mobile app," and rewrite it as a user-need statement that names a person, a need, and an insight. Then list two cheap prototypes you could put in front of real users this week.

Think Like a Maester: Fall in love with the user's problem, not with your first solution.

1. Name the five modes of design thinking and explain why they form a loop rather than a straight line.
2. What does it mean to write a problem statement from the user's point of view?
3. What is the purpose of a rough, low-fidelity prototype?
4. How does design thinking lower the cost of being wrong?
5. What did Herbert Simon mean by design as "changing existing situations into preferred ones"?

Design thinking keeps problem-solving anchored to real people. Empathize to understand, define a sharp user-centered problem, ideate widely, prototype cheaply, and test to learn — then loop. The discipline is not the vocabulary but the habit of genuine contact with users and cheap experiments before expensive commitment.

• Creative Problem Solving
• Problem-Solving Under Constraints