When I was 35, I had a big, beautiful binder sitting on a shelf in my office.
My team and I had spent real time building it. Pages of outcome data, well-reasoned goals, and clear action steps. The leadership team was committed. There was genuine energy in the room when we finalized it. We were proud of what we’d built.
We launched the plan. Not much changed.
There was nothing wrong with the strategy. What we were missing was the bridge. The system that connects the plan on paper to the work that happens on Monday morning.
That gap is more common than most organizations want to admit. And in my experience, it almost always shows up in one of three places.
We mistake symptoms for root causes.
It feels like progress to name a problem and move toward a solution. The momentum of deciding something can be mistaken for the momentum of changing something. But when we skip the hard work of diagnosis, we end up treating symptoms, and the underlying condition keeps producing new ones.
Here’s a pattern that shows up more than it should. An organization sees rising customer attrition and immediately reaches for a product fix or a marketing adjustment. Both might be reasonable responses. But neither asks the harder question. Why are customers actually leaving?
Sometimes discontinuance isn’t about the product at all. Economic pressure shifts buying behavior. Customers who genuinely value what you offer make a different choice because they have to. The product isn’t the problem. The context changed, and the organization didn’t see it because they were already in solution mode.
Other times, the signal points inward. Maybe the issue lies in the customer experience after the sale. Onboarding, support, the gap between what was promised and what was delivered. Or maybe the data being used to diagnose the problem is lagging so far behind reality that the organization is solving for a condition that no longer exists.
The instinct to solve is not the problem. The problem is solving before you’ve accurately named what you’re solving for.
This is where most strategic plans begin to fail. Not in execution, but in the assumptions baked into the plan before execution ever starts. When diagnosis is rushed or skipped entirely, every subsequent decision is built on uncertain ground. You can execute the plan flawlessly and still move confidently in the wrong direction.
Learning gets treated as an event, not a system.
So let’s say your diagnosis was solid. You identified the right problem, built a thoughtful response, and invested in equipping your people. You ran the training. The workshop landed well. People left energized.
Six weeks later, not much has changed.
This is the second place plans stall, and it’s one of the most frustrating because it looks like failure at the individual level when the failure is actually structural. The learning happened. The behavior didn’t follow. And the gap between those two things isn’t a motivation problem. It’s a design problem.
Information alone doesn’t change behavior. If it did, everyone who has ever read a book about exercise would be in the gym. People need context, repetition, application, and feedback. And they need those things woven into the flow of actual work, not isolated in a conference room for a day and a half.
The organizations that get this right don’t just train people. They build learning into the rhythm of how work gets done. They create space for reflection after key decisions. They use structured conversations to surface what’s working and what isn’t before the next cycle begins. They treat learning not as preparation for the work but as part of the work itself.
When that system is missing, even well-designed training fades. People return to existing habits. Not because they’re resistant, but because the environment around them didn’t change. You can’t expect new behavior to survive in an unchanged system.
Execution gets left to individuals.
This is where the plan often quietly dies.
After the planning retreat, after the training, after the rollout, implementation gets handed to individuals who are already carrying full loads. The expectation is that people will absorb the new direction, integrate it into their daily work, and sustain it through their own discipline and commitment.
Some will. Most won’t. Not because they don’t care, but because sustained behavior change under conditions of competing priorities is genuinely hard. And when the structure isn’t there to support it, the path of least resistance wins every time.
This isn’t a character flaw. It’s a systems problem. When execution depends on individual willpower rather than embedded structure, clear roles, recurring touchpoints, shared accountability, visible progress, the plan erodes in ways that are entirely predictable and entirely preventable.
The people who were most energized in the planning room gradually get pulled back into the urgent and familiar. The plan doesn’t get abandoned. It just gets quietly deprioritized. And a year later, someone pulls out a binder or opens a slide deck and wonders what happened.
The pattern compounds.
These three failure points don’t operate in isolation. They build on each other.
When diagnosis is skipped, your learning strategy is misaligned from the start. You’re building capability around the wrong problem. When learning is treated as an event, there’s no behavior change to anchor execution. And when execution depends on individual effort rather than embedded structure, even the right people working on the right problem run out of runway.
The result is a strategic plan that was reasonable on paper, launched with real commitment, and still didn’t move the organization. The team didn’t fail. The bridge was missing.
What the bridge actually looks like.
Building that bridge doesn’t require a different strategy. It requires a different relationship between the plan and the work.
It starts with staying in the diagnostic phase longer than feels comfortable. Asking what’s actually true about your current state before deciding what to do about it. It continues with designing learning that’s embedded in the work rather than extracted from it, so that new knowledge has a place to land and practice has a place to happen. And it holds through execution by building the structural conditions, the rhythms, the roles, the feedback loops, that make sustained effort possible without requiring heroics.
This is what I think about when I talk about a Live. Learn. Lead. framework. Not as a methodology to be implemented, but as a way of asking three questions. Are we seeing our situation clearly? Are we building the capability to respond to it? And are we creating the conditions for that response to actually hold?
Those three questions, asked consistently and honestly, are the bridge.
If your plan feels stalled, it is worth asking which of these three places the gap lives.
That is usually where the conversation starts, and it is one I am always glad to have. If this resonates, connect with me here on LinkedIn or reach out directly. The bridge is buildable. Sometimes you just need a second set of eyes on where it is missing.
Leave a Reply