The goal was set in January. By April, everyone involved knew it was the wrong goal. By December, they hit it anyway. And celebrated.

This pattern repeats constantly in organizations. A strategy is developed, goals are set, and incentives are aligned to those goals. Then reality intervenes. Market conditions shift. New information emerges. A key assumption proves false. The original plan no longer makes sense.

But the plan has weight. It’s in the budget. It’s tied to bonuses. It’s been communicated to the board. Careers are attached to its completion. So the organization executes a strategy it knows is flawed, because the cost of changing course feels higher than the cost of being wrong.

This is how organizations optimize for plan completion rather than outcomes.

The Commitment Trap

Annual planning processes create commitments that are difficult to escape.

Goals become contracts. What starts as a planning assumption becomes a target, then a commitment, then an obligation. The goal takes on a life of its own, independent of whether it still makes sense. Questioning the goal feels like questioning the people who set it.

Incentives lock in direction. When compensation is tied to specific metrics (revenue targets, project completions, cost reductions), people will pursue those metrics even when they recognize the underlying logic has changed. The rational individual response is to hit the number, even if the rational organizational response would be to change the number.

Admitting error has costs. Changing direction mid-year requires acknowledging that the original plan was wrong, or at least that circumstances have changed enough to warrant revision. This admission has political costs. Leaders who championed the plan may resist revisiting it. No one wants to explain to the board why the strategy shifted.

Sunk costs create momentum. Resources have already been committed. Teams have been assembled. Vendors have been engaged. The investment already made creates pressure to continue, even when continuing no longer makes sense. Stopping feels like wasting what’s already been spent.

The result is predictable: organizations execute strategies they no longer believe in, pursuing goals they know are suboptimal, because the planning process has more inertia than the learning process.

Real-World Patterns

This dynamic appears across different types of strategic commitments.

The system implementation that shouldn’t finish. A major technology project is approved based on certain assumptions about business needs. Midway through, those needs change: maybe a process is eliminated, maybe an acquisition changes the landscape, maybe a better solution emerges. But the project has momentum, budget, and careers attached. It gets completed and deployed, even though everyone involved knows it’s no longer the right solution. The organization now owns a system it didn’t need.

The market entry that lost its logic. An expansion into a new geography or segment is planned based on competitive dynamics that shift before launch. The opportunity that justified the investment no longer exists in the same form. But the team has been hired, the infrastructure has been built, and the commitment has been made. The launch proceeds, and the organization spends years trying to make a fundamentally flawed position work.

The cost reduction target that causes damage. A headcount or expense reduction is mandated to hit a financial target. As the year progresses, it becomes clear that the cuts are damaging critical capabilities or customer relationships. But the target is the target. Managers make cuts they know are harmful because their compensation depends on hitting the number.

The product launch that should be delayed. A release date is set and communicated. Development reveals that the product isn’t ready: not just late, but fundamentally not right. Launching on schedule will damage the brand and require costly fixes. But the date has been promised to customers, announced to investors, and built into sales forecasts. The product launches anyway, and the organization spends the next year recovering from a preventable failure.

In each case, the organization had information that should have changed the decision. In each case, the structure of commitments prevented that information from changing anything.

Why Organizations Resist Adaptation

The inability to adapt mid-course isn’t stupidity. It’s the rational response to how most organizations are structured.

Annual planning cycles assume predictability. The premise of annual goal-setting is that the future is knowable enough to set targets twelve months out. This premise is often false, but the process proceeds as if it were true. Goals set in January reflect January’s understanding; they may not reflect April’s reality.

Incentive systems reward hitting targets, not judgment. Most performance management systems evaluate whether goals were achieved, not whether they should have been achieved. The manager who hits a bad target is rewarded; the manager who misses a good target is penalized. This creates obvious incentives to pursue the target regardless of whether it still makes sense.

Governance structures aren’t designed for revision. Changing a board-approved strategy or budget requires formal process: re-approval, re-communication, explanation. The friction of changing course often exceeds the friction of continuing on the wrong course. Inertia wins by default.

Accountability structures punish changing direction. Leaders are accountable for plans they’ve committed to. Changing those plans feels like admitting failure, even when it’s actually responding to new information. The political cost of adaptation often exceeds the business cost of staying wrong.

Building Adaptive Capacity

Organizations that adapt successfully build mechanisms that make mid-course correction possible.

Separate targets from forecasts. A target is an aspiration; a forecast is an expectation. When these are conflated, updating the forecast feels like lowering the target. Keep them distinct. Forecasts should be updated as information changes; targets can remain stable as stretch goals while the organization adapts its approach.

Build revision into the process. Rather than annual plans that are set and forgotten, create explicit checkpoints where strategy is revisited. Quarterly reviews that genuinely reassess direction, not just report progress, make adaptation part of the normal process rather than an exception.

Incentivize outcomes, not plan completion. Where possible, tie incentives to business outcomes rather than activity completion. Did we achieve the result the project was supposed to produce? Not just: did we finish the project? This requires more sophisticated performance management but creates better alignment.

Reduce the cost of changing direction. Make it politically safe to raise concerns about plan validity. Celebrate leaders who surface problems early rather than those who hide them until it’s too late. Create governance processes that permit mid-year revision without excessive friction.

Distinguish commitment from stubbornness. Commitment to a goal is valuable; stubbornness in the face of contradicting evidence is not. The ability to distinguish between temporary setbacks (which require persistence) and fundamental changes (which require adaptation) is a critical leadership skill.

The Planning Paradox

Organizations need plans. Without goals and commitments, coordination is impossible and accountability disappears. But plans are hypotheses, not prophecies. They’re based on assumptions that may prove wrong and conditions that may change.

The best organizations hold plans firmly enough to execute with discipline, but loosely enough to adapt when evidence warrants. They understand that the purpose of a plan is to achieve an outcome, not to complete a document. When the plan stops serving the outcome, the plan should change.

Hitting the wrong goal isn’t success. It’s the most expensive kind of failure: one where you pay the cost of execution and get none of the benefit.

The question isn’t whether you completed the plan. It’s whether the plan was still worth completing.