Design Thinking — The Product Playbook

Design thinking is a human-centered toolkit. You point it at a real person with a real problem, and it hands you a way to understand them well enough to build the right thing.

This page is the build shelf, the make-it companion to the Discovery chapter. You're not here for the case that empathy matters, the five phases, or why you ask people about their past instead of pitching your idea (because what they actually did is evidence, while a reaction to your pitch is a polite guess). That's the craft, and it lives back in Discovery, in Design Thinking & Experimentation, where the why and the teaching are. You're here because you've done that part, you've got a wall of research, and now you need to turn it into something your team can actually use.

So grab the artifact your project needs and go build it.

Four artifacts, four jobs

These four come out of the same lineage the Discovery page credits, the design-thinking work popularized by the design firm IDEO and Stanford's d.school. Discovery tells you what each one IS and why it earns its place after Synthesis, the step where you boil raw research down into themes. Here you build it. Each of the four pages below is the recipe: the blank template, a worked example, and the read on when to reach for it instead of the other three.

Persona. One named, made-up character who stands in for a real pattern of customers, so "the user" stops being an abstraction everyone quietly fills in with themselves. Reach for it when the team keeps building for a vague someone and you need one face to aim at.
Journey Map. The step-by-step path a customer walks to get a job done, start to finish, with the highs and lows marked along the way. Reach for it when the problem is a sequence and you need to show where in the flow it breaks.
Empathy Map. What one person says, thinks, does, and feels about one moment, laid out so the gap between what they say and what they do is impossible to miss. Reach for it when someone's words and actions don't line up and that gap is the whole point.
Interview Guide. The actual question set you walk into a customer conversation with, built so you ask about their past instead of pitching your idea. Reach for it before you talk to anyone, so the conversation gets you a real story you can verify instead of a polite hypothetical.

You don't need all four on every project. Pick the artifact that turns your conclusion into something a teammate can see.

The sketching and brainstorming moves live in the Sprint

You came here expecting the rapid sketching and idea-generating exercises: Crazy 8s, the Four-Step Sketch, How Might We, and dot voting. They're not on this page, and that's on purpose.

Those moves aren't standalone artifacts you build once and hang on the wall. They're timed exercises that only make sense inside a facilitated session, with a clock running and a group in the room. So they live where they actually get run, inside the Design Sprint, broken out by the day they belong to. Duplicating them here would just give you a second copy to keep in sync, and a worse one, because it'd be missing the room they happen in.

If you need to generate options and pressure-test them as a group, go run the Sprint, or raid it for the one exercise you need. If you need to capture what you've already learned about a real person, you're in the right place. Pick an artifact above and build it.