When you don't understand why the customer isn't buying, or your team keeps building things people don't use, you're in discovery-and-understanding territory.

This is the domain where the question itself is the question - where the honest first move is to admit you don't yet know what's going on, and to find out before you act. It shows up whenever understanding has to come before doing, and the temptation to skip it is strongest exactly when you can least afford to.

This work is uncomfortable because it asks a leader to slow down in the one direction everyone is pushing to speed up. The pressure is always to do something. But action aimed at the wrong problem is worse than no action, because it burns the time and the credibility you'd need to fix the real one. What helps here isn't a research method - it's a worked-through answer to the specific thing you don't understand.

The discovery situations leaders meet

There's the mood you can't source: morale has dropped and you can't tell why, where finding the real cause beats applying the obvious fix to the wrong thing. There's the commercial mystery: you don't understand why the customer isn't buying, where the answer is usually in a conversation you haven't had yet.

There's the brief with a hole in it: you've been asked to launch something and you don't know what users actually need, where a small amount of learning first saves a large amount of building wrong.

There's the pattern that should worry you: you keep building things people don't use, where the problem is upstream of the building. There's the diagnostic moment: you need to work out what's actually wrong before you can fix it, where resisting the first plausible cause is the whole skill.

And there's the moving target: a stakeholder keeps changing their mind and you can't lock the scope, where the churn usually means they haven't understood their own need yet.

Each of these is a Playbook. Each names the kind of question it is, hands you two Plays to choose between, shows you the tools in sequence, and ends with the leaders who worked out the same kind of thing before you.

Why understanding is worth getting right

A team that understands its problem before it acts wastes far less of itself. It builds things people use, because it found out what they needed first. It fixes the cause rather than the symptom, so the same problem doesn't come back in a new costume next quarter. And it earns the right to move fast later, precisely because it was willing to be slow at the start. Understanding is what makes confident action safe.

The opposite is expensive in a way that's easy to miss, because it looks like progress. A team that skips discovery is always busy - shipping, launching, fixing - and always solving the wrong thing slightly. The cost shows up as the feature nobody uses, the customer who still won't buy, the morale fix that didn't help. Most of that traces back to a question someone didn't stop to ask.

The discipline this domain asks for is genuinely hard to hold, because it runs against the grain of how busyness is rewarded. Stopping to understand looks, from the outside, like not doing anything - right up until it's the reason the next thing works.

A leader who can protect that pause, and aim it at the right question, saves the team from months of confident motion in the wrong direction. The Playbooks below are built for exactly those moments where the honest move is to find out first.

Start with what you don't understand

You don't need a research function. You need the one thing you can't currently explain. Pick the situation below that matches it and open your Playbook - or read more about what a leadership playbook is first. The shortest path from "I don't understand this" to "now I do" is usually one click.