Organizations rarely fail from a single bad decision. They drift, because the assumptions underneath a good decision quietly stop being true.
A few years ago I started what was supposed to be a routine piece of work: a current-state analysis for one business unit inside a larger system. Standard stuff. Pull the numbers, describe where things stand, hand it to the executive team.
Partway in, the numbers stopped agreeing with the story. Not dramatically. The proforma that governed the unit’s planning had been built carefully by capable people, and every individual assumption in it had been defensible when it was made. But several of them had been made at different times, by different people, under different conditions, and nobody had ever put them side by side and asked whether they still described the same world.
So we rebuilt the proforma from the ground up. The revised version showed a material gap between the trajectory everyone believed they were on and the one they were actually on. The organization corrected course. Without that correction, days cash on hand would have declined to a genuinely uncomfortable place.
I think about that project often, because of what it was not. It was not a story about incompetence. Nobody was careless. It was not a story about a bad decision, either. The original decisions were reasonable.
It was a story about maintenance.
Strategy has a maintenance problem
We treat strategy as an event. There is a planning process, a retreat, a document, a board approval. Then the strategy is understood to exist, and attention moves to execution.
But a strategy is not a document. It is a set of claims about the world: about what your market wants, what your costs will do, what your competitors will attempt, how long a project will take, what capital will cost. Every one of those claims has a shelf life. Some of them expire loudly, in a way that forces a response. Most expire quietly.
The quiet ones are the dangerous ones, because organizations are structured to notice variance in results, not variance in assumptions. Your board packet will tell you that occupancy is down two points. It will not tell you that the demographic projection underpinning your entire expansion thesis was built on a five-year-old study.
What actually helps
I have not found a clever solution to this. I have found a few unglamorous ones.
Write the assumptions down separately. Not embedded in a model, not implied by a slide. A short list, in plain language, of the things that have to be true for the plan to work. Ten or twelve of them, usually. If you cannot write them down, you do not have a strategy, you have a direction.
Attach a tripwire to each one. What observation would tell you this has stopped being true? Be specific enough that someone other than you could notice it.
Assign each one to a person. Not a committee. Shared responsibility for noticing is the same as no responsibility for noticing.
Put the list on a calendar. Once or twice a year, someone reads the list out loud in a leadership meeting and the group says yes or no to each item. The whole exercise takes forty minutes and it is the highest-return forty minutes on the strategic calendar.
The uncomfortable part
The reason this does not happen is not that leaders do not know it would help. It is that going back to check an assumption is an implicit challenge to whoever made it, and often that person is still in the room, and often it is you.
An organization that can revisit its own assumptions without anyone feeling accused is doing something culturally difficult. It requires having established, in advance and out loud, that assumptions aging out is normal and expected rather than evidence of a mistake.
That is a leadership decision, not an analytical one. It is also, in my experience, the single thing that most separates organizations that adjust in time from organizations that adjust after it costs them.