I wrote last week about treating a bottleneck, a constraint, as simply real: something to map and work with. But that reframe only works if you actually know where your constraints are.
What I've noticed is that companies often skip this step for various reasons: enthusiasm to start a new project, immediate needs of the business, or simply the goal of making money. However, skipping the step of understanding what blocks your company from its true potential could turn a new project or initiative into a train wreck.
Companies tend to base decisions on the known story: the one repeated in status meetings, the version of the budget and delivery numbers that sound acceptable enough to move past. But that story rarely tells us about the constraints. It rarely gives us the map to navigate whatever objectives we may set (and that's another topic for another day).
Mapping the constraints and finding the gaps means taking a step that, while it may feel useless, time-consuming, or even uncomfortable, will ensure half the success. And that step is most often a discovery process. That thorough, in-depth look at what's actually happening in the business. What's true about your budget. What's true about your operations. What's true about delivery to your customers, measured against what everyone assumed was true. And, equally important, what are the missing pieces and links in the story everyone in the company tells.
I advocate for discovery as the key to what's happening inside a business: a structured deep dive under the hood. At the end of the day, you can only fix what you've properly defined. If this step is skipped, you solve whatever story made it into the deck.
When was the last time you dug into a number in your business and found something different from what the story said?
