This morning I shelved a piece of work in about ten seconds. The summary in front of me said it had never been started — no file, no output, nothing to review. It had been started. It was finished three days earlier and had been sitting there waiting for me to read it. Decisions based on bad information are the most expensive kind, because while you are making them they feel exactly like good decisions.
Why decisions based on bad information feel so confident
A wrong fact does not arrive with a warning label. It arrives inside a clean summary, in the same format as every accurate fact you have ever been handed.
That is the trap. Confidence comes from the packaging, not the accuracy. When someone hands you a tidy list, your brain reads "tidy" as "checked."
In my case, the answer I gave was reasonable — given what I was told. The problem was never my judgment. It was that my judgment was pointed at a stale picture of my own business.
What actually went wrong
The morning summary was assembled at the start of a long working session. Then the session kept running for hours.
While it ran, the underlying files changed. Work got finished. New notes got written. The summary in my hands quietly aged into fiction.
Two things were waiting for my approval and never made it into the briefing at all:
- A full workshop outline, drafted three days earlier, complete with five open questions for me to answer.
- A client article, written and staged, waiting only for my yes to go live.
A third item was worse in a subtler way. My task tracker said a piece of writing had been "in progress" since late June with nothing produced. The finished draft — close to three thousand words of options and recommendations — had landed that same morning.
How do you catch a stale fact before it becomes a decision?
Refresh your sources at the last possible moment, not when you start preparing.
I tested that immediately. The second briefing that morning re-read the underlying files right before presenting instead of only at the start. It found real drift in the gap: one brand-new task and eleven new lines of activity that had appeared after the first version was assembled.
Same day. Same system. Same person preparing it. The only change was when the facts were pulled.
Refresh at the last moment
Whatever your dashboard, spreadsheet, or assistant reports from, re-pull it right before the meeting. A number gathered an hour ago is a different number.
Say where each fact came from
Every claim in a status update should carry its source. "Nothing was produced" and "no file exists in the folder I checked at 8:03" are very different statements. The second one is checkable in seconds.
Reopen the decision — don't quietly rescue it
This is the part people skip. When you discover a decision was made on a wrong fact, going back and doing the right thing for the person is not enough.
The decision belongs to whoever made it. So that shelved project is going back on my desk, framed honestly: you answered a question that was described to you incorrectly, here is the accurate version, what do you want to do now?
The version of this that costs real money
I got lucky. Nothing was published, nobody was charged, no client saw anything.
But swap the details and this is every small business. You decide not to reorder because the stock count was from last week. You skip a follow-up because the notes say the client already replied. You kill a marketing channel because the report was built before the last two weeks of results came in.
The failure is never dramatic. It is a confident answer to a question that was described wrong.
Takeaway: before you act on any summary, ask when its facts were gathered — and if the answer is "a while ago," go look again.
That five-minute check is the cheapest insurance in the building.