Why Your Vision Doesn't Stick

At mile thirty of a hundred-mile race, something happens that no training plan fully prepares you for.

The finish line. The thing that got you out of bed at 4am for eighteen months of preparation and that sat on your refrigerator and your screensaver and in the back of your mind during every hard training run is suddenly theoretical. Not gone, but just very, very far away. And the terrain between you and it has stopped resembling the map.

The ultra-marathoner who survives mile thirty isn’t the one with the clearest vision of the finish line. It’s the one with a race plan broken into segments, paced against terrain, adjusted at checkpoints, and built to survive the moment when the original plan meets the actual mountain.

The finish line is the destination. The race plan is how you actually get there.

Remove the race plan and leave only the finish line, and you don’t have a runner with a vision. You have someone standing at the start with good intentions and no idea what to do when the weather changes at mile forty-seven and the path they’d planned stops making sense.

Most organizational visions are the finish line without the race plan.

Leaders spend significant time crafting the vision. The right words, the right aspiration, and the right balance between ambitious and achievable. They present it at the all-hands, reference it in the quarterly business review, put it on the website. Then they return to their offices, and somewhere between the announcement and the execution, between the leadership offsite and the team standup on a Tuesday morning, the thread gets lost.

By the time the vision reaches the person doing the work, the one whose daily decisions will either move the organization toward it or quietly away from it, it has been translated six times, diluted twice, and now exists somewhere in the space between “grow the business” and “don’t mess anything up.”

The vision didn’t fail. The translation system was never built.

“We communicated it. They know the direction.”

Communication and comprehension are not the same thing. Announcing a vision is not the same as translating it. Most people in an organization can recite the company’s stated priorities when asked. Far fewer can explain in one sentence, without a slide deck, without a moment of hesitation, how what they’re working on today connects to that priority.

The gap between those two things is the vision not sticking.

The second version of the lie is subtler and more common among leaders who have actually thought hard about strategy: “They’re not aligned because they don’t understand the strategy.”

Often the real problem is different. They understand the strategy fine. They just don’t see how their work connects to it. Understanding and connection are not the same problem and they don’t have the same solution.

Understanding is a communication problem. You fix it with better messaging, clearer narrative, more consistent reinforcement of the direction.

Connection is a translation problem. You fix it with better systems. The graduated cascade from annual direction to quarterly commitment to weekly priority that gives every person in the organization a visible thread between what they’re doing today and where the organization is trying to go.

Most leaders invest heavily in the first fix and barely at all in the second. The vision gets communicated more clearly, more often, with better slides. The translation system never gets built. And the gap between the boardroom and the person doing the work stays exactly where it was.

Most vision statements operate at the level of aspiration. Be the leading provider of X. Transform Y for customers. Build the organization people are proud to be part of. These aren’t wrong, aspiration is the point. But aspiration without graduated translation is the space station without a landing strip.

The team can see the sky. They cannot find the runway.

The distance between transform how our customers experience financial services and what should I prioritize in my sprint this week is not a distance most teams can cross on their own. Without something in between such as annual anchors, quarterly commitments, team-level objectives that connect explicitly to the direction, the vision floats above the work, inspiring in the abstract and useless in the specific.

What organizations need is not a better vision. They need a better ladder between the vision and the Tuesday.

There is a meaningful difference between a team that has been handed an objective and a team that has participated in defining how they’ll contribute to one. The first executes. The second is committed. Both look the same for the first few weeks. By month three, they look very different.

When people own the metric, when they’ve had a hand in defining what success looks like and how they’ll pursue it, their focus increases in a way that assignment cannot produce. They make better decisions under pressure because they understand the intent, not just the instruction. They flag problems earlier because they care about the outcome, not just the deliverable.

This is not an argument for endless collaboration or consensus by committee. Leadership still sets the direction. The question is whether teams are empowered to define how they’ll contribute to it. Or whether the how arrives from above, already decided, already allocated, already owned by someone else before the team ever touched it.

The organizations where vision sticks are almost always the ones where the answer to what are we doing this quarter and why was partly shaped by the people being asked to execute it.

Annual planning in a world that changes quarterly is a calendar problem disguised as a strategy problem.

The direction set in January may be exactly right. The tactics decided in January to achieve that objective are almost certainly at least partially wrong by April. The market shifts, competitors move, and each quarter teaches the organization something it didn’t know when the plan was made. Without a regular cadence of genuine recalibration, the organization keeps executing a plan that has stopped fitting the terrain. This is not just tracking against targets, but honestly asking is this still the right thing to be doing.

The ultra-marathoner doesn’t check the map once at the start and then run. They check it at every aid station, adjust for what’s changed, and make the call on whether the next segment of the plan still makes sense given what the previous segment taught them. The discipline of that recalibration, not the original plan, is what gets them to the finish.

Two tools, run in sequence. The first makes the vision translatable. The second makes it executable.

Before any goal-setting framework, the vision needs to be expressed in a form that can cascade. So that it can travel from the leadership team through the organization and arrive at the team level still meaningful and still connected to the original intent.

Four questions. Every leader should be able to answer them. More importantly, every leader should be able to help their team answer them.

What are we here to do?

The purpose: the why that doesn’t change even when the strategy does. NASA’s purpose was space exploration. That purpose survived the moon landing and every subsequent shift in how they pursued it. Nike’s purpose is inspiring athletes. That purpose survived multiple strategy pivots, divestitures, and market shifts. The purpose is the anchor. Everything else, the strategy, the objectives, the tactics, is how you pursue it in this particular moment.

If your team can’t articulate the purpose without reading from a website, the cascade hasn’t started yet.

What are we trying to achieve right now?

The direction: the what for this period. Specific enough that people can point to it, ambitious enough that it actually moves something, time-bound enough that it creates urgency without becoming wallpaper. This is where the vision lands closest to the work. The thing that, if achieved in the next twelve months, represents genuine progress toward it.

A good direction statement passes the how will we decide test: if you can use it to resolve a resource conflict or a prioritization debate (which of these two options gets us closer to where we said we’re going right now?) it’s specific enough. If it doesn’t help you decide, it isn’t specific enough.

Why does this matter to the people doing the work?

This is the question most leaders skip, because it feels like motivation rather than strategy. It is both. The connection between the direction and the individual: what this means for the person doing it, why their specific contribution matters to the outcome. This is not a feel-good addition to a strategy document. It is the mechanism that turns comprehension into commitment.

The manager in customer support who’s been asked to work on an internal initiative doesn’t need a memo explaining the strategy. They need to understand how this initiative connects to something they care about: the customer experience, the team’s ability to deliver, or the problem they came to work every day to help solve. Without that connection, they execute the task. With it, they pursue the outcome.

How will we know we’re moving toward it?

The leading indicator, not the final result, but the early signal that tells you you’re on course before the results arrive. This is the question most leaders answer last and think about least, and it’s frequently where the translation system collapses.

If the only signal is the end-of-year result, the team is flying blind from January to December. They’re working hard, delivering against tasks, and have no idea whether what they’re doing is moving the needle until it’s too late to change course. The leading indicator, the metric that moves first and predicts the result, is what allows for real-time navigation rather than annual postmortem.

Get clear on this before you set the goals. It changes both what you measure and what you decide to do.

Once the vision is expressible, once the four canvas questions have clear answers, you need a mechanism to translate it into owned, executable commitments at every level of the organization. That mechanism is OKRs: Objectives and Key Results.

The framework is simple. The discipline required to use it well is not.

Qualitative and aspirational. Inspiring enough that people know why it matters. Specific enough that everyone is pointing at the same thing. Action-oriented, it starts with a verb and names a direction, not a state.

Dominate the enterprise segment in the Pacific Northwest is an objective. Be good at enterprise sales is not. It describes a characteristic, not a direction, and you can’t point to it when a resource conflict needs resolving.

Quantitative, outcome-focused, verifiable. Three to five per objective, maximum. Not tasks, but evidence. This is the distinction that separates the organizations that use OKRs from the ones that are OKR-driven.

Launch three new ad campaigns is a task. If you launch them and nothing changes for the business, you’ve succeeded by this measure and failed by any measure that matters.

Generate 1,500 qualified leads from new campaigns is a result. It can be verified. It connects the work to the outcome. It answers the question: if we do this and it works, what will be different?

Always ask: if we complete this and nothing changes for the customer or the business, have we actually succeeded? If the answer could be yes, you have a task masquerading as a key result. Replace it.

Ruthless focus. Three to five objectives per quarter, maximum. This constraint is the feature, not the limitation. The organizations that struggle with OKRs are almost always the ones that treat them as a comprehensive list of everything they’re working on rather than a declaration of what matters most. Saying yes to the most important things is only possible if you’re genuinely willing to say no to everything else. That willingness is harder than it sounds and more important than it looks.

Bottom-up ownership. Leadership sets the direction. Teams define how they’ll contribute. This is the step that converts assignment into ownership and execution into commitment. Give teams the quarterly intent (our priority this quarter is to stabilize churn to build the foundation for growth) and ask them to draft their own objectives in response. What they come back with will often be more creative and more specific than what a top-down allocation would have produced. And they’ll defend it when it gets hard, which top-down assignments rarely survive.

Regular cadence. The plan is not the strategy. The cadence that keeps the plan honest as the terrain changes is the strategy. Weekly check-ins: fifteen minutes, confidence scores, obstacle identification. Mid-quarter reviews that ask not just how are we tracking but is this still the right thing to be tracking. Quarterly retrospectives before the next cycle begins, so the learning from this quarter shapes the direction for the next one.

An OKR that sits in a spreadsheet unread is not a management system. It is a document. The cadence is what makes it a system.

The vision is not for the leader. It’s for the people executing it.

This sounds obvious. It is rarely practiced. Most vision work is done in a room with the people who already understand the direction and need it least. The test of a vision isn’t whether the leadership team can articulate it; they’re the ones who built it. The test is whether the person three layers below, making daily decisions that either serve or undermine the direction, can articulate how what they’re doing today connects to where the organization is trying to go.

That person is the finish line of the translation system. Everything between the boardroom and their desk is the work. If the thread makes it to them, clear, specific, owned, and connected to something they care about, then the vision sticks. If it doesn’t, the vision lives in slide decks and lobby walls and quarterly all-hands presentations, inspiring in the abstract and absent from the actual work.

The ultra-marathoner finishes because they have both the vision of the finish line and the system that gets them there one segment at a time. The vision without the system is a beautiful destination with no road to it.

Build the road.

One question to ask: Can every person on your team answer, in one sentence, how their current work connects to the organization’s top priority right now? Not the mission statement, but the current priority. If you’re not sure, ask one of them today. Their answer will tell you more about how well the vision has been translated than any strategy document or all-hands replay.

One behavior to stop: Stop treating the annual plan as the strategy. The plan is what you decided in January. The strategy is what you do in April when the plan meets the terrain and one of them has to give. Build the review cadence before you build the plan. Without it, the plan becomes a document you defend rather than a direction you navigate.

One action this week: Run the four Vision Narrative Canvas questions on your current priorities. What are we here to do? What are we trying to achieve right now? Why does this matter to the people doing the work? How will we know we’re moving toward it? Write the answers in one sentence each. If any of them takes more than one sentence, then that’s where the vision is evaporating. And that’s where to start.

At mile eighty of a hundred-mile race, the finish line is no longer theoretical. It is close enough to be real, far enough to be genuinely in doubt. Every runner at mile eighty has a vision. Not all of them have the system that gets them there.

The ones who finish are the ones who built the race plan, ran the aid station check-ins, adjusted for the terrain they didn’t predict, and kept the thread intact between the destination and the next mile marker. They didn’t run the finish line into existence through vision alone. They ran it one committed, recalibrated segment at a time.

That’s the work of leading the system. Not the announcement, the translation. Not the destination, the road. Not the aspiration, the owned, specific, regularly recalibrated commitment that connects what happens on a Tuesday to where the organization decided it was going.

Your vision is probably fine. The road between it and your team’s Tuesday is where the work is.

Build the road. Check it regularly. Adjust when the terrain changes.

The finish line will still be there.

If this landed, share it with a leader who has a vision worth translating.

Share