Somewhere between the second and third year of running a design project, it happens: your inbox becomes the project. The decisions are in there. The approvals are in there. The consultant coordination is in there. The client comments are in there.
And finding anything requires twenty minutes of searching, a vague memory of when the relevant conversation happened, and a good deal of luck.
This is the natural end state of running a design project over email. It's not that email doesn't work: it does, at a certain scale, for a certain duration. The problem is that it degrades. The longer the project runs and the more parties are involved, the worse email gets as a coordination system.
Most firms live with this degradation because they don't have a concrete sense of what it's costing them. Let's change that.
What Email Does Well (and Where It Breaks Down)
Email is excellent at a few things that are genuinely important on a design project:
- Formal correspondence. Contracts, legal communications, official project notices — these belong in email because email provides a date-stamped record that both parties have access to.
- External communication with parties who aren't on your internal system. Permit offices, city agencies, specialty consultants you work with infrequently. Email is the right channel.
- One-to-one conversations that don't need team visibility. A quick note to the structural engineer about a scheduling question doesn't need to be in the project record.
Email breaks down when it becomes the primary channel for coordination among a team working on a shared project. The specific failures:
Institutional knowledge trapped in inboxes. When a project decision is made over email, it lives in the inboxes of the people who were on that thread. Anyone who joins the project later, or wasn't CC'd, doesn't have access to it. The team's collective knowledge isn't shared, it's distributed across private inboxes.
Context collapses across threads. A conversation about a structural detail gets started in one email thread. Someone responds with a different question and the thread bifurcates. Two weeks later, there are four email threads nominally about the same detail, and the resolution is in the third one that most people stopped following.
The CC problem. To prevent information from being missed, people add more CCs. More CCs means more email volume for everyone. More volume means people read less carefully. Reading less carefully means information gets missed. Which leads to more CCs to prevent information from being missed. It's a loop.
No connection to the work. Email is a general-purpose communication tool. When a decision is made over email and the relevant drawings or documents aren't integrated into the same space, the decision is disconnected from the work it affects. Finding that connection later requires manual reconstruction.
The Invisible Cost
The cost of email as a project coordination system is almost entirely invisible because it's diffuse and never attributed to its cause.
A PM who spends forty minutes a day searching through email threads for project information is spending over three hours a week on information retrieval. On a twelve-month project, that's over a week and a half of productive time, per PM, per project. Multiply across multiple PMs and multiple projects.
A junior team member who misses a critical update because it was buried in a thread they'd stopped following doesn't log "missed email" as a cause when the resulting problem surfaces. They log the symptom — wrong information used, coordination issue, rework required.
The root cause of those problems is often communication system failure. It just never gets identified as such. The 2018 Autodesk/FMI "Construction Disconnected" study put a number on it: 52% of all rework on construction projects stems from poor data and miscommunication. PMI's research is even broader, finding that communication failures contribute to one-third of all project failures across industries.
What the Alternative Looks Like
The goal isn't to eliminate email from the project: some things genuinely belong there. The goal is to move project coordination out of email and into a system designed for it.
What that system needs to do:
Be organized by project, not by person. Conversations live in the project, visible to everyone with appropriate access. Not in individual inboxes.
Connect communication to context. A message about a drawing should be linkable to that drawing. A question about a task should be linkable to that task. Context is what makes communication searchable and retrievable.
Support file sharing without creating version chaos. Files shared in a conversation should be linked to the project document system, not floating in a message thread as attachments that may or may not be the current version.
Give external parties appropriate access. Consultants should be able to communicate in the project context without having access to everything in the project. Clients should have their own access layer. The system should handle these distinctions without manual management.
Persist. When a team member joins a project six months in, they should be able to review the communication history and understand what's been decided, discussed, and resolved.
The Transition
Changing the communication system on an active project is difficult. The practical approach:
- Don't try to migrate old projects. Let them finish in email. Start new projects in the new system from day one.
- Establish clear norms at project kickoff. Where does project communication go? What stays in email? Brief the whole team, including consultants, on the protocol before work begins.
- Lead from the top. If the PM or principal defaults back to email, the team will too. Consistent behavior from project leadership sets the pattern.
The tools that make this possible have changed significantly in the past few years. Olumba builds project messaging directly into the project — conversations organized by project, file attachments connected to the document system, access levels that work for internal teams, consultants, and clients. If email chaos is a daily experience on your projects, consider checking out what a purpose-built alternative looks like.
