When a strategy stops working, the question that gets asked first—by a board, by a team, by the leader themselves in the quiet moments—is almost always some version of “what did we get wrong.” It’s a reasonable instinct, and it’s also a question that quietly assumes a specific kind of failure: an error in the original thinking, a flaw in the plan that a smarter version of the team should have caught. Sometimes that’s exactly what happened. But often, the more accurate answer is that the plan was sound, built on the best available read of conditions at the time, and the conditions themselves are what moved. Those are genuinely different situations, and treating them as the same one costs a leader something real, in both directions.
The distinction matters first because of what it does to trust in your own judgment going forward. A leader who concludes “I was wrong” when the actual story is “conditions changed in a way nothing available at the time would have predicted” starts discounting their own decision-making process even though the process was sound. That discounting has consequences: it produces excessive hedging on the next decision, a loss of conviction that has nothing to do with the quality of the next decision’s underlying logic, and sometimes a retreat into overly conservative calls made not because they’re right, but because confidence in your own judgment has been damaged by a misdiagnosis of what actually happened last time.
The Distinction Cuts Both Ways
It matters just as much in the other direction, because there’s a real failure mode this distinction is not meant to excuse: mistaking a genuine planning error for unfortunate external change, as a way of avoiding the harder, more useful work of examining what should have been anticipated. If the plan failed to account for something that was reasonably knowable at the time—a competitive move that industry peers saw coming, a risk that was flagged internally and dismissed, an assumption that was fragile on its face—that’s a real error, and it deserves to be named as one, not absorbed into a comfortable narrative about unpredictable circumstances. The discipline here cuts both ways: don’t manufacture a personal failure out of an external shift you couldn’t have seen, and don’t manufacture an external shift out of a planning failure you should have caught.
How to Tell Them Apart
The way to actually tell the two apart is more concrete than it might sound: go back to the assumptions the plan was built on, and ask, specifically, which ones turned out to be false, and whether a reasonable, well-informed version of the team could have known that at the time, with the information actually available. If the assumption was reasonable given what was knowable, and the world subsequently moved in a way that invalidated it, that’s environmental change, not a planning failure—and the correct response is to build a new plan based on the new conditions, not to relitigate the old plan as though better people would have avoided the failure. If the assumption was fragile, contested internally, or contradicted by information that was available and ignored, that’s a real error, and the correct response is a genuine post-mortem on why the team missed or dismissed it, separate from any conversation about changing external conditions.
Sometimes we were wrong. Sometimes the world moved. Accuracy in which is which matters.
How You Frame the Pivot Shapes What Comes Next
This distinction becomes especially important in how a leader communicates a pivot to their team or board, because the two framings produce very different downstream effects on how the team operates afterward. “We got this wrong, here’s what we missed” appropriately triggers scrutiny of the planning process and a search for the specific gap. “The plan was sound for the conditions it was built for, and those conditions changed faster or differently than any of us could have reasonably anticipated” appropriately triggers a shift toward the new plan, without an unnecessary and inaccurate crisis of confidence in the team’s judgment. Applying the wrong framing to either situation produces the wrong organizational response—either false confidence that persists past a real planning flaw, or unwarranted self-doubt that undermines a team’s willingness to commit fully to their next well-reasoned call.
None of this is a search for a way to avoid accountability. It’s an argument for accuracy in where accountability actually belongs. A leader who can hold both possibilities honestly—sometimes we were wrong, sometimes the world moved—builds a team that trusts its own process enough to commit fully to the next plan, precisely because that team has seen its leader distinguish real errors from real change, rather than treating every failed outcome as evidence of the same underlying flaw.
If you’re in the middle of a plan that isn’t working and haven’t yet done the honest work of separating what you got wrong from what simply changed, that’s the conversation worth having before you build the next plan. Explore coaching services.
Frequently asked questions
If a plan stops working, does that mean we got it wrong?
Not always. Sometimes the plan was sound for conditions at the time and the world moved. Treating environmental change as a planning failure damages confidence in sound judgment; treating a real planning error as bad luck avoids the post-mortem you need.
How do you tell a planning error from a world that changed?
Return to the plan’s assumptions. Ask which turned false and whether a well-informed team could have known that with information available then. Reasonable assumptions invalidated later = environmental change. Fragile, contested, or ignored knowable risks = real error.
Why does the framing matter when communicating a pivot?
“We got this wrong” triggers scrutiny of the planning process. “Conditions changed faster than we could reasonably anticipate” shifts energy to the new plan without an inaccurate crisis of confidence. Wrong framing produces the wrong organizational response.