A recurring theme in IT project conversations lately, with colleagues and clients, is: “How come everything we do feels harder?”
We have an ever-expanding set of digital tools and solutions, hybrid and more distributed teams for our convenience, and an ever-connected, always-plugged-in culture (adopted by many teams). They haven’t always made things better.
There, I’ve said it out loud. That, actually, feels better.
In a world where teams are under increasing and evolving pressures, it is important that we do talk about this. As we hear on every UK train journey:
“See it. Say It. Sorted”
There is usually someone within earshot, on the other end of a phone call or email, who can offer a new perspective, a word or two of wisdom or just help brainstorm a solution.
If you’re leading IT change and quietly wondering why everything feels heavier than it used to, this one’s for you.
In this blog, I’m going to recreate and combine four watercooler interactions and the kernels of insight I have heard in response. These aren’t single conversations but amalgamations of several that illustrate the shared experience of leading IT projects in these changing and fragmented times.
How come everything we do feels harder – and what can we do about it?
Strategy, Focus And Knowing What To Stop
A growing challenge in project work is deciding what you should pass, pause or pivot. And, let’s be honest, what you will politely but deliberately ignore!
With increasingly slick tools and constant input, almost everything now looks simultaneously possible and urgent.
Solution: a weekly “do‑not‑do” list.
Write down the initiatives, requests and ideas you’re consciously leaving alone, circulate it and then hold the line when the noise inevitably creeps back in.
In terms of importance, the “do‑not‑do” list sits alongside the roadmap, rather than beneath it. Strategy decays often faster than it ever has, so you need a solid document to refer to.
Stopping work or killing a project has also become more politically charged and harder than starting it. In our experience, teams are keeping initiatives alive because ending them feels uncomfortable, not because they’re still the right course of action.
Solution: Schedule explicit “stop points” alongside greenlights, where the default is to re‑justify the work, not to rubber‑stamp its continuation.
This is where PMaaS can quietly help, too. An external delivery capability is less emotionally attached to legacy projects and can provide evidence‑based recommendations on what to pause or stop, backed by capacity plans, risk views and commercial impacts rather than internal politics.
Alignment In A Fragmented, Hybrid World
Keeping different teams genuinely aligned has become trickier in hybrid and remote environments. Priorities shift, tools multiply and a slow erosion of shared understanding creates delivery risk long before anyone updates a RAID log.
Solution: A single, “central source of truth” for decisions, trade‑offs and ownership, plus a short weekly narrative explaining why things changed. That combination keeps people in sync and stops small gaps turning into big problems.
In hybrid settings, people often feel informed but still aren’t actually coordinated.
To counter that, enforce early clarity by documenting in your “central source of truth” and revisiting it at key milestones. This reduces rework and protects momentum as context inevitably fades. Managing focus is also harder when attention is scattered across too many tools and channels, so short, protected work blocks become non‑negotiable.
In practice, this is where platforms like Stoneseed’s P3MO can help. By harnessing the Microsoft 365 ecosystem you can turn a sprawl of tools into an integrated project, programme and portfolio environment: Planner or Microsoft Project for scheduling, Teams for collaboration, PowerApps and Automate for workflow, Forms for data capture and Power BI for reporting.
Instead of each team improvising its own way of working, P3MO gives you a consistent governance layer and real‑time business intelligence that keeps everyone aligned on the same story.
For many organisations, it’s not about buying yet another toolset, but unlocking the value of investments they already have. A structured P3MO implementation on Microsoft 365 can provide that stable backbone for alignment.
And PMaaS can act as a stabilising layer: a consistent governance and reporting rhythm, a standard way of documenting decisions across all projects, and practitioners whose job is to maintain alignment even as internal teams rotate or reorganise.
Money, Risk And The Invisible Edges Of Delivery
It’s increasingly difficult to make risk decisions when you never have the full picture. In compliance‑heavy work, waiting for perfect clarity often means acting too late, but moving too early can expose you to audit and security issues.
Solution: Set clear decision bars in advance: what’s enough to move forward, what triggers a pause and what needs escalation.
Rising compliance and cybersecurity requirements multiply complexity fast, so these demands need to be built into the project from day one, with every related step mapped early rather than bolted on at the end.
Modern projects also carry more invisible complexity in their architecture.
In Agile teams, the rush to ship features can hide small architectural shortcuts that turn into expensive technical debt later. So, plan specific “health check” sprints where you stop adding features, inspect core systems and pay down that debt before it starts to threaten delivery dates and budgets.
These are the edges of delivery that don’t show on a basic RAG report, but they are often where time and money quietly disappear.
Here, PMaaS gives you flexibility on both risk and cost. You can bring in specialist capability for spikes in regulatory work or technical‑debt sprints, without hard‑coding permanent headcount. At the same time, outcome‑based PMaaS contracts make financial trade‑offs more explicit, tying spend to risk reduction and value delivery rather than just time and materials.
Delivery Discipline In A Noisy Environment
The daily reality of delivery is now a constant negotiation between speed, complexity and attention.
Dependencies span security, regulation, suppliers, APIs and AI governance, and decisions stall more easily in hybrid and async work where silence can look like agreement but often hides drift.
Solution: Keep things moving by precisely defining what “done” looks like, limiting how long decisions can sit, surfacing risks early and reviewing them every week.
Every decision gets an owner, clearly articulated options with trade‑offs and a deadline; if it doesn’t affect architecture or budget, the owner decides within 48 hours.
Timelines are hardest when everyone asks for “just a few more days.”
One of my schoolteachers used to say, “The calendar doesn’t bend.”
Deadlines are fixed, communicated clearly and treated as immovable, which forces more honest planning from the start.
At the same time, set outcome‑led metrics early, make progress visible and iterate often so you’re measuring real impact, not just activity.
PMaaS can reinforce that delivery discipline by providing a standing playbook: standard definitions of “done”, agreed escalation paths, and experienced PMs who are comfortable saying “no” to date‑slippage and scope‑creep. Instead of each project inventing its own rules, you effectively rent a delivery operating system that keeps teams honest and aligned with the business case and project goals.
Honestly, writing this may have been as much personal therapy as it was anything else. To realise that you’re not alone and that, somewhere, someone is feeling the way you and I feel is good for your mental health.
It’s important to name the IT project delivery hurdles and challenges out loud and remember that you’re not alone, even if you’re working remotely on your own.
Mostly, remember that there’s always a solution.
If any of this sounds familiar, we’re always up for a no-pressure conversation about what’s making delivery harder in your world.
Let’s talk. Call today on 01623 723910 or contact us here.