There’s a plan I wrote in July. A real one — quarterly goals, sequenced work, the kind of document I was proud of for a week. I opened it last Monday to update it and realized I’d been executing against a version of it I stopped revising in August. Not a different plan. The same file. I’d just stopped editing it while still treating it as the plan.
The strange part was that nothing had obviously broken. Work was shipping. The team was moving. But the plan on the screen described a set of priorities that hadn’t matched what we’d actually been doing for two months. We’d quietly shifted — a client priority changed, an opportunity appeared, a piece of work turned out harder than expected — and none of those shifts had made it back into the document.
When the plan becomes a relic
I used to think a stale plan was a planning problem. It’s not. It’s a coordination problem wearing a planning costume.
The plan was never the point. The point was shared understanding. The document was just where we’d frozen that understanding so everyone could reference it. The moment the understanding moved and the document didn’t, the document stopped being a reference and started being a fiction — a fiction we were all politely pretending was still operative.
That pretense has a cost. New people read the plan to get oriented and get oriented to a version of reality that no longer exists. I reference the plan in updates and quietly translate between what it says and what we’re doing, which takes a small amount of energy every time. Decisions get made against the stated priorities, not the real ones, and then have to be re-litigated when the gap surfaces.
Why I kept not updating it
Here’s what I noticed: I’d avoided opening the file for weeks. Not because I forgot. Because updating it would have required me to admit that two of the priorities I’d been confident about in July were no longer the priorities.
That’s the admission the stale plan protects you from. As long as the document still says X, you can tell yourself you’re still working toward X. The moment you edit it to Y, you’re acknowledging that you changed your mind — and acknowledging a change of mind feels, in the moment, like a small failure of conviction.
So the plan stays frozen, and the conviction it represents stays technically intact, and the work drifts further from what the plan describes, and the gap between the two grows until someone — usually a new hire, or a stakeholder, or yourself three months later — trips over it.
The difference between a plan and a decision log
What I’ve started doing is treating the plan document less like a charter and more like a living decision log. Instead of one static set of priorities, it now carries the sequence of revisions: what we believed in July, what changed in August, why we shifted in September.
This sounds like more work. It’s actually less, because the alternative — maintaining a fiction and translating against it in every conversation — was the expensive part. Writing down the revision takes two minutes. Carrying the gap in my head for two months took something out of me every day, in small enough increments that I didn’t notice until I stopped.
The other thing it does: it makes the changes legible to the team. When someone asks why we deprioritized the thing that was top of the list in July, the answer is in the document instead of in my memory. That’s not just convenience. It’s trust. A plan that silently changes erodes trust in the planner. A plan that visibly changes, with reasons, builds it.
The signal I was ignoring
The clearest signal that the plan had gone stale was the simplest one: I’d stopped wanting to open it. Not because I was busy. Because opening it would have forced a conversation with myself about whether the work still matched the intent.
I’ve started treating that reluctance as data. If I’m avoiding the planning document, the planning document is almost certainly out of sync with reality. The avoidance isn’t a character flaw. It’s the plan telling on itself.
What I’d tell myself from July
A plan is not a promise you make to your future self. It’s a snapshot of a decision under the conditions you had then. The conditions change. The snapshot is allowed to change with them — but only if you keep taking new ones.
The plan you stopped updating isn’t protecting your priorities. It’s freezing a version of your thinking that you’ve already moved past, and then charging you rent every day to pretend you haven’t. Open the file. Make the edit. The two minutes of discomfort are cheaper than two more months of executing against a version of your own judgment that you no longer hold.