Many teams already know where the friction is. They live with it every day. The challenge isn’t awareness. It’s creating the conditions for that knowledge to surface in a form the business can actually use.
This is one of the more consistent patterns I see when I start working with a new operation. The business leader has spent months managing symptoms, running adjustments, trying different fixes. But the people doing the work have often understood the real problem clearly for a long time. They’ve just had nowhere useful to put that understanding.
The bottleneck in many operations isn’t access to the right thinking. Many leaders have encountered Lean concepts, or worked somewhere that ran a process improvement exercise. The frameworks aren’t the problem. Getting from knowing about waste to actually mapping it, in the real business with the people doing the work, is where it usually stalls. That is an adoption problem, not a knowledge problem.
Lean has a specific and honest word for activities that consume time and effort without creating value: waste. The insight isn’t complicated, but it is uncomfortable. In many growing businesses, a significant proportion of the team’s effort doesn’t go towards the thing the customer is paying for. It goes towards managing the overhead of a system that isn’t running cleanly.
That overhead is hard to see precisely because it feels like work. Waiting for a decision feels like part of the process. Going back to fix something feels like due diligence. Sitting in a meeting that doesn’t change anything feels like staying across things. None of it registers as waste in the moment. That’s what makes it persistent.
Making waste visible is the first move. It usually means tracing how a specific piece of work actually moves through the operation, from the moment it starts to the moment it’s done. Not the org chart version. The real version, with the waiting, the rework, and the handoffs included.
When that map exists, the waste tends to announce itself. People don’t need to be told what they’re seeing. They recognise it immediately because they’ve been navigating around it. What changes is that it now has a structure, a shared name, and a reason to be addressed rather than tolerated.
That’s where the real work begins. Not in naming the problem, but in building the conditions where what everyone already knows can be said out loud, taken seriously, and acted on. A team with that capability, running it consistently, is the one that improves over time rather than just managing what’s already breaking.
A simple way to start: take one piece of work that took longer than it should have and walk it backwards with the people who touched it. Ask where it sat waiting, where it went back for rework, where a handoff lost context. Don’t frame it as a performance review. Frame it as a map. That conversation usually surfaces more than months of reporting would.
The knowledge is already in the room. The work is creating the conditions to use it.
Creating those conditions in the real business, with the real teams, is what Create Momentum is designed to do.