The Toolbox

A method you can run beats a methodology you can recite.

The rest of the playbook tells you what to do: find the right problems, talk to customers, run an experiment before you build. This part hands you the literal how. The recipe you can carry into a room on Tuesday morning and run.

Because you've been there. The playbook's loop for finding and validating work says "now ideate" or "now run a lean experiment," and you're standing in front of a blank wall. Okay. But what do I actually run?

So this is the shelf. You don't read it front to back. You grab the tool you need and go.

Each page is a recipe, not a chapter

Every tool here is built the same way, so you can scan it fast and run it the same day:

• What it is in one breath, and who it's borrowed from. Most of these aren't mine. Decision Jam, AJ&Smart's hour-long way to get a group to a real decision, came from them. The Design Sprint, a focused week to take a fuzzy problem to something real users have touched, is Jake Knapp and the team at GV. I'll credit the source every time and tell you what's actually my contribution: the judgment about when to reach for which one.
• When to reach for it. The single hardest part isn't running a method. It's knowing which method the moment in front of you calls for.
• How to run it. Numbered steps, real timings, what you put on the wall (sticky notes, a printout, a drawing). Written so a first-timer can facilitate it. To facilitate here just means you guide the group through the steps. You're not the one with the answers. You're the one who runs the clock and keeps the format intact.
• How to know it worked. What you walk out of the room with. If you can't name that, you ran a meeting, not a method.

Each recipe stands on its own, so start with whichever one your week needs.

"These are just workshop gimmicks"

I can hear the pushback, because I've heard it in the room. Sticky notes and voting dots. Silent timers. It can look like arts and crafts for adults.

It isn't.

The structure is the point. The timer, the silence, the dots. Those are the only reliable way I've found to get the quiet expert's idea the same weight as the loudest person's, or the highest-paid person's opinion (the HiPPO). Take the structure away and the room defaults right back to whoever talks the most. Every time.

So no, the format isn't decoration. It's what keeps the decision honest.

When to grab which tool

Here's the fast map. Match the moment to the method.

• You need a decision out of a group in about an hour. Reach for the Decision Jam. Ranked problems, ranked solutions, one or two scoped experiments with names on them, and the highest-paid person in the room didn't decide it for everyone.
• You've got a big, risky bet that's worth going deep on. Run a Design Sprint, or raid it for the parts that matter. A focused week to get from a fuzzy problem to something real users have touched, before you commit a quarter to building it. The Sprint page breaks it into its days so you know which parts you'd be pulling.
• You need confidence before you build. Run a lean experiment, a cheap, fast test aimed at your riskiest assumption. Buy the answer in days instead of finding out the expensive way after launch.
• You've already done the research and need to turn it into something usable. Build a Design Thinking artifact, a persona, a journey map, an empathy map, or an interview guide. These aren't sessions you book a room for. They're things you make, on your own or with a teammate, to turn a wall of customer research into one picture the team can act on.

The first three are the big group sessions. They're built out of smaller brainstorming and sketching moves, and you can also run any one of those moves on its own when you just need raw ideas worth testing. The Design Thinking artifacts are the quieter end of the shelf, what you reach for after the talking, to make sense of what you heard.

Where the tools sit

These pages are the how. They aren't the why.

If you want the reason you run any of this, the craft of discovery and the case for experimenting at all, that's in Discovery. If you want where each tool slots into the actual loop of finding and validating the right work, that's the Opportunity Backlog.

This part assumes you already buy the why. You're here for the recipe.

So grab one and go run it.