Understanding how to simplify project management tools is crucial for enhancing productivity and clarity. Walk into any large programme today and you’ll see the same scene.
A project manager has Jira open for delivery items, Teams for chatter, Outlook for approvals, Confluence for “the latest” documents, SharePoint for “the real latest” documents, a PowerPoint deck for the steering pack, Excel for RAID logs, a PPM tool for portfolio reporting, plus two dashboards that don’t agree with each other. And somewhere in the mix, someone’s still running a “quick tracker” in a private spreadsheet because it’s faster than fighting the system.
That’s not a tech stack. That’s a hedge maze.
And here’s the uncomfortable bit: none of this is rare. It’s almost normal. We keep buying tools, then we wonder why delivery feels foggier, not sharper.
You know what? The irony is brutal. We invested in software to make work visible. Instead, we made visibility harder to trust.
The real problem isn’t that PMs have tools. It’s that they have too many truths
Senior leaders often ask for “a single source of truth”. Sensible request. Then, without meaning to, the organisation funds five sources of truth and tells the PM to reconcile them weekly.
So the PM does what PMs always do: they cope. They build a manual bridge between systems. They copy status updates from one place to another. They chase approvals across channels. They translate the same message for ten stakeholder groups who each want it presented “their way”.
That coping looks like productivity. It isn’t. It’s survival.
Asana’s research has been banging this drum for years: a large share of the working day gets swallowed by “work about work” – coordination, chasing updates, hunting for information, sitting in meetings that exist mainly to confirm what nobody can see clearly in the tools. Their Anatomy of Work Index puts that figure at around 60%. In the UK findings, the split is even more explicit: 61% “work about work”, 27% skilled work, 12% strategy.
If that makes you wince, good. It should. Because it means we’re paying highly skilled people to operate a human middleware layer between apps.
“We’ve digitised the work” – yes. We’ve also digitised the noise.
Tool overload doesn’t fail loudly. It fails quietly.
- A risk gets logged in one place, discussed in another, and mitigated in a third.
- A dependency is “owned” by three teams, so it’s owned by nobody.
- A stakeholder reads last week’s deck and believes it’s current.
- A PM spends Friday afternoon stitching a narrative, not managing outcomes.
Then Monday comes, and we do it again.
Microsoft’s Work Trend Index has described a working pattern that many leaders recognise instantly: the day gets chopped into tiny fragments by meetings, emails, and notifications. Microsoft’s telemetry suggests employees using Microsoft 365 are interrupted every two minutes on average.
Every two minutes. That’s not a workday. That’s a pinball machine.
And when people can’t hold focus, they cling to signals. More dashboards. More check-ins. More “just a quick update” messages. The toolset expands again, like foam filling every gap.
Context switching: the hidden tax nobody budgets for
Tool sprawl has a very dull name for a very expensive behaviour: context switching.
It’s not just that people click between apps. It’s that their brain reloads the rules, the data, the thread, and the “where were we?” every time. That reload time doesn’t show up on a timesheet, so it gets treated as free. It isn’t.
A 2025 report on tool fatigue highlighted how common this has become: 79% of employees said their company hadn’t taken steps to reduce tool fatigue or consolidate platforms; 22% said they lose two or more hours a week to tool fatigue.
Two hours a week per person doesn’t sound dramatic until you scale it. Multiply that across a 300-person change portfolio and you’re staring at a quiet bonfire of capacity.
Now add the PM factor. Project managers are the professional context switchers. They’re expected to have the full picture, all the time. When the picture is spread across ten tools, “full picture” becomes a heroic fantasy.
Why executives should care (and not just because people are tired)
This isn’t a wellness poster. This is delivery economics.
PMI’s Pulse of the Profession has repeatedly pointed to a stubborn reality: a meaningful slice of investment gets wasted through poor project performance. In PMI’s 2020 Pulse, that figure was 11.4% of investment wasted on average.
You can’t blame that on tools alone. But tool chaos plays a role because it makes three things harder:
- Fast, confident decisions (leaders don’t trust the data, so they ask for more data)
- Early warning (signals are buried in noise, so risks surface late)
- Clear accountability (ownership blurs across systems and teams)
And when those three wobble, cost and time wobble right behind them.
Here’s the mild contradiction: sometimes adding a tool does help. A new planning view can expose dependencies. A better intake form can stop random work landing on the wrong team. A decent dashboard can cut meetings.
The catch is the word “sometimes”. Without rules and ownership, every “helpful” addition becomes one more place where the truth might live.
The mistake we keep repeating: buying clarity instead of designing it
Organisations often treat clarity like a feature you can purchase.
- “We need a new PPM tool.”
- “We need a better reporting platform.”
- “We need an AI copilot to summarise updates.”
- “We need workflow automation.”
Those can all be useful. Yet the deeper issue usually sits elsewhere:
- Incentives: Teams are rewarded for local optimisation, not shared outcomes.
- Governance: No one has the authority (or patience) to say “no” to yet another system.
- Operating model gaps: Nobody owns the cross-team process from intake to delivery to benefits.
- Status theatre: Reporting exists to look controlled, not to run the work.
So PMs become translators. They don’t just manage work; they interpret it.
And let’s be honest: the more senior the audience, the more pressure there is to make the story look neat. That’s how you end up with green dashboards built on red reality.
The IT myths we’ve already buried… and the one we haven’t
We’ve retired some famous ideas.
“The paperless office.” We didn’t remove paper; we added PDFs, screenshots, chat threads, and duplicated files. Paper didn’t die. It got reborn in five formats.
“One ERP system will fix the business.” ERPs brought structure, yes. They also brought workarounds, shadow processes, and a cottage industry of “just export it to Excel”.
“Cloud automatically cuts cost.” Cloud can reduce spend. It can also inflate it fast when governance is soft and consumption is invisible.
“Agile means no governance.” That one still pops up at parties, usually right before a portfolio misses its commitments.
Now, the myth that’s still alive, still cheerful, still causing mischief:
“If we add the right tool, clarity will follow.”
It won’t. Clarity follows decisions. Decisions follow ownership. Ownership follows a design that people can actually live with.
Tools can support that. Tools can’t replace it.
What “enough clarity” looks like (without turning the place into a museum)
Clarity isn’t about having less information. It’s about having fewer arguments over what’s true.
In a healthy delivery set-up, you see a few characteristics:
- One place to plan work (for that layer of delivery)
- One place to track delivery status (with definitions that people agree on)
- One place to store key artefacts (with version control that isn’t “final_v7_reallyfinal.pptx”)
- Clear ownership for data fields (who updates what, and when)
- A reporting rhythm that reflects decisions (not performance art)
Notice what’s missing: a demand that every team uses the exact same tool for everything. Standardisation has value, sure, but forced uniformity often creates rebellion. And rebellion usually shows up as… another tool.
So aim for consistency where it matters (definitions, critical workflows, governance), while allowing flexibility where it doesn’t (personal notes, team-level ways of working, lightweight collaboration).
The “tool reset” leaders can actually execute
This isn’t a moonshot. It’s housekeeping with teeth.
- Start with the work, not the software catalogue
- Pick a small number of “systems of record”
- Fix definitions before you fix dashboards
- Reduce “status work” by changing the rules of engagement
- Integrate, but don’t create a spaghetti monster
- Put PMO leadership in the driver’s seat (with real authority)
A quick reality check: AI will help… and it might make the mess bigger
Yes, AI copilots can summarise meetings, draft updates, and pull actions from threads. That’s helpful. It can also encourage more noise, because “it’s easy to generate”.
If your underlying system is messy, AI can become a turbocharger for the mess.
So treat AI as an assistant, not a substitute for operating discipline. Use it to reduce admin, not to excuse poor structure.
Where this lands: fewer tools, fewer truths, better decisions
There’s a version of the future where project managers spend more time leading, shaping, and unblocking, and less time copying, pasting, chasing, and reconciling.
It doesn’t start with a new platform. It starts with a choice:
- Do we want more data, or more clarity?
- Do we want more reporting, or better decisions?
- Do we want more tools, or fewer truths?
Honestly, most organisations don’t need another system. They need a cleaner story about how work moves, who owns the truth, and what leaders will actually use to steer.
Then the tools can do what they were meant to do: support delivery, not swallow it.
