The tolerated pain
Relying on email threads and private spreadsheets to manage complex projects creates a fog of information. Status updates get buried in inboxes, decisions lag behind activity, and critical dependencies go unseen until late in the cycle.
It usually begins sensibly. A small project needs a quick tracker, so someone builds a spreadsheet. Updates arrive by email because everyone already uses it. As the project grows, the spreadsheet is copied, renamed and versioned. Each team lead keeps their own. Decisions are made in reply-all threads that new joiners never see. Eventually nobody can say with confidence which version of the plan is current, who owns a task, or whether a dependency has slipped.
Why businesses tolerate it
- The tools are already there. Email and spreadsheets cost nothing extra and need no training.
- Flexibility feels like control. A private spreadsheet can be shaped exactly as its owner wants, which makes it hard to give up.
- Coordination cost is spread thinly. Each person loses a few minutes at a time chasing updates, so the total is never seen.
- Previous tool rollouts failed. Teams that have seen a project platform abandoned are sceptical of trying again.
Operational consequence
The visible symptoms include duplicated effort, misaligned timelines and frequent rework as teams discover gaps in context or ownership only after work has begun. Teams lose alignment across departments, which raises the risk of missed milestones, budget creep and unsynchronised handoffs.
Status meetings become the only place where the true picture is assembled, so more meetings are added. Project managers spend their time collecting and reconciling updates rather than managing risk. When a key person is away, their spreadsheet and inbox go with them. Leaders receive a status report that was accurate when it was compiled and has been drifting since.
Survey evidence points in the same direction. Microsoft's 2023 Work Trend Index found that the average employee spends 57% of their time in Microsoft 365 apps communicating through meetings, email and chat, and that 62% of respondents say they struggle with too much time spent searching for information. Asana, a work-management vendor whose findings should be read with that interest in mind, reports in its Anatomy of Work Index that 88% of knowledge workers agree time-sensitive projects and large initiatives have fallen behind or through the cracks because of the volume of tasks on their plate.
Private spreadsheets add a separate risk. Raymond Panko's long-running research on spreadsheet errors concluded that such errors are both common and non-trivial. A project tracker that only one person maintains, with no review, is exactly the kind of spreadsheet in which an error can sit unnoticed until a deadline is missed.
How it becomes money
The money here is not only in wasted labour but in delayed time-to-market for initiatives that drive growth or maintain service levels. The cost model combines lost productivity, rework, delayed benefit and diminished confidence in programme governance.
An illustrative cost model
All figures are illustrative assumptions chosen to show the arithmetic. They are not benchmarks, and the result is not a prediction for any particular business.
| Cost element (illustrative) | Assumptions | Annual result |
|---|---|---|
| Coordination overhead | A 12-person project team at an assumed loaded cost of R500/hour, each spending an assumed 3 hours a week chasing updates, searching threads and reconciling spreadsheet versions, over 46 working weeks (12 × 3 × 46 × R500) | R828,000 |
| Rework | An assumed 2 incidents a month where work proceeds on outdated information, each needing an assumed 16 hours to correct (24 × 16 × R500) | R192,000 |
| Delayed benefit | One initiative expected to deliver an assumed R250,000 a month in savings or revenue is delivered an assumed 6 weeks late (R250,000 × 6 ÷ 4.33) | R346,420 |
| Total illustrative annual cost | R1,366,420 |
The coordination line is the easiest to verify: ask the team to log time spent finding, chasing and reconciling project information for two weeks. The delay line is the most consequential and the hardest to see, because a late benefit never appears as an expense. It simply arrives later than the business planned for.
Some costs are deliberately left out because they are difficult to price honestly: budget creep from changes approved by email without a record, reputational damage from missed client commitments, and the time leaders spend in meetings that exist only because the status is not visible anywhere else. They are real, but they should be estimated by the business rather than assumed.
Commercial trigger
The trigger is usually one of these: more than one version of the plan in circulation, a milestone missed because a dependency was not visible, a key person's absence stalling a project, or a growing number of status meetings. A new programme of work, a client demanding delivery reporting, or an audit of change approvals are also strong moments to act, because each needs a single, trustworthy record of who agreed what and when.
The same pattern appears when other important processes run on inboxes and personal files, as explored in the cost of running important business processes manually.
What good looks like
Remediation emphasises centralised, collaborative project-management platforms, standardised workflows and transparent dashboards. By consolidating communication, file sharing and task assignment in a single, auditable system, organisations gain clarity on progress, ownership and risk. Implementing governance around change requests and approvals further reduces ambiguity and accelerates decision cycles.
Every task has one owner and one due date. Decisions are recorded where the work lives, not in a reply-all thread. Status is visible without a meeting. Changes to scope, budget or timeline follow a light but explicit approval path, so that the record of what was agreed survives staff changes. The tool matters less than the operating rhythm around it: a platform that nobody updates is just a more expensive spreadsheet.
Resolution
- List active projects and where each one's plan, tasks and decisions currently live.
- Agree a minimum standard for every project: owner, milestones, dependencies, risks and decision log.
- Choose one shared system and migrate live projects into it, starting with the most cross-functional.
- Define how change requests and approvals are recorded.
- Replace status-collection meetings with dashboards drawn from the shared system.
- Review after one quarter whether coordination hours, rework and delays have fallen.
Where projects span several teams and systems, digital operations improvement can design the shared operating rhythm and the tooling to support it.
Bottom line
Better outcomes arise when teams move away from ad hoc channels to a shared operating rhythm. With improved visibility, project teams can anticipate bottlenecks, align resources and deliver commitments with greater reliability, translating into steadier execution and more predictable financial performance. Email and private spreadsheets feel free. The cost is paid in coordination time, rework and benefits that arrive late.
Sources and further reading
- https://www.microsoft.com/en-us/worklab/work-trend-index/will-ai-fix-work (last verified 10 October 2026)
- How Work About Work Gets in the Way of Real Work [2026] • Asana (last verified 10 October 2026)
- Spreadsheet Errors: What We Know. What We Think We Can Do (last verified 10 October 2026)
Related Mellorca reading
- Invoice Approvals Stuck in Inboxes
- The Hidden Productivity Cost of Poor Office Wi-Fi
- The Cost of Retyping Customer Details into Every System