"I Think It's in Email": The Five Words That Cost Every Project More Than They Should
There is a sentence you can hear in almost any project status meeting. Someone asks where the approval is, or the latest drawing, or the decision from three weeks ago. The answer comes back: "I think it's in email." Five words said a thousand times a day across every industry — and they are among the most expensive words in project work.
They are expensive not because of the one document that is hard to find. They are expensive because of what the phrase reveals: a diagnosis about how the entire project stores its memory.
Email Is Where Decisions Go to Disappear
A decision that lives in email is personal — sitting in one person's inbox, invisible to everyone else. It is unstructured — filed under no project, no matter, findable only by whoever remembers the right search term. And it is unshared — a decision that only one human can produce on demand. A decision in email is a decision the project does not really own. It owns a person who owns the decision, which is a very different and far more fragile thing.
Multiply that across hundreds of decisions on a live project and you get a memory made of individual inboxes — a memory that fragments a little more with every person who leaves, every mailbox that fills up, every thread that gets archived and forgotten. The project looks organized from the outside. Inside, its most important information is scattered across dozens of private accounts, and no one can see the whole picture.
The Retrieval Tax: A Budget Line Nobody Approved
Here is the cost that never shows up on a budget line. It is not the occasional email you cannot find; it is the retrieval tax you pay on every search. Picture a team of ten, each losing twenty minutes a day to "where is that" — hunting inboxes, asking colleagues, waiting for someone to forward a thread. That is a quiet, permanent full-time salary spent finding information the project already has. Nobody approved that hire. It accumulates twenty minutes at a time, invisible because it never arrives as a single bill.
The deeper cost is downstream: a change approved in a thread that nobody filed becomes a change nobody can verify. A scope adjustment emailed at 4 p.m. on a Friday and never recorded anywhere central becomes the source of a dispute when the invoice arrives. A contractor's claim rests on a thread the owner's representative deleted six months ago. The email was not the problem; the absence of a record was.
The One-Question Fix
You do not fix this by banning email. People will always email. You fix it by changing what happens to a decision once it is made. Before you let an approval, a change, or a commitment live only in a thread, ask one question: if this person were unreachable tomorrow, could anyone else find this? If the honest answer is no, the decision does not belong only in email — it belongs somewhere the whole project can see, in a place that does not depend on one memory and one inbox.
Practical Rules for Breaking the Email Habit
Treat email as a notification channel, not a filing system. When an approval or decision arrives by email, move it to the project record before you close the tab.
Apply the stranger test to every significant decision. If a stranger cannot reconstruct it from the project record alone, it is not recorded — it is merely sent.
Establish a single authoritative location for approvals, scope changes, and commitments — and enforce it at project kickoff, not in the aftermath of a dispute.
Count the phrase at your next status meeting. "I think it's in email" is not a minor inconvenience — it is a measurement of how often the project cannot see its own decisions.
The Bottom Line
"I think it's in email" is not a location. It is a confession about how a project manages its memory. The retrieval tax it generates is real, compounding, and entirely avoidable. The cure is not a cultural campaign or a strict email policy — it is one operational rule enforced at kickoff: a decision that only lives in email is a decision the project does not own. Listen for the phrase this week. Each time you hear it, you are hearing the sound of a project paying a bill it never had to incur.
This content was generated by AI.
Comments