Design Thinking Process

In 2011, a hospital in Ohio asked designers to fix something surprising: kids were terrified of the MRI machine, and many had to be sedated just to hold still for the scan. Instead of redesigning the machine, designer Doug Dietz repainted it like a pirate ship and trained staff to turn the scan into an adventure story. Fear scores dropped and sedation rates fell sharply. He solved the real problem -- fear -- not the machine itself. That is design thinking in action.

- The five stages of the design thinking process - Why "empathize" comes before "build" - How prototypes are meant to fail fast and cheap - How to apply the process to a real problem you pick yourself

Empathize means talking to and observing the actual people who have the problem, not guessing what they need. Dietz sat and watched kids in the waiting room before he touched the machine. Define means turning what you learned into one clear problem statement. His problem was not "the MRI machine looks scary" -- it was "children are so afraid they need to be sedated, which is risky and expensive." A sharp problem statement points you toward the right solution.

Ideate means generating many possible solutions without judging them yet -- quantity over quality at first. Prototype means building the cheapest, fastest rough version of an idea just to test it. A prototype can be a cardboard box, a paper sketch, or a piece of tape on the floor. The goal is never a finished product; it's answering the question "does this idea actually work?" as quickly as possible.

You show your prototype to real users and watch what happens. Dietz's team tested pirate-ship stickers and a script the technologist could read ("you're on a pirate ship, stay very still so the water doesn't splash") with real families before repainting a single machine. Testing almost always reveals the prototype needs work -- so you loop back to ideate or even redefine the problem. Design thinking is a cycle, not a straight line.