Why projects feel harder than they should (and what to do about it)
A few weeks into any plan, reality starts to take over.
Good intentions meet deadlines.
New habits collide with existing routines.
And the way things actually work begins to show through.
At that point, the most useful question isn’t:
“What did I plan to change?”
It’s:
“What actually changed once the pressure came back?”
For most people, the honest answer is: not much.
And that’s not a failure.
It’s a signal.
Where the Friction Really Comes From
Systems don’t break when things are quiet.
They break under pressure.
That’s when the friction shows up:
- Things take longer than they should
- You find yourself chasing updates
- Decisions need repeating
- Important details live in your head instead of somewhere visible
Individually, these feel like small annoyances.
But together, they create a constant background load.
And that’s where the real cost sits.
The Hidden Pattern Most People Miss
When systems aren’t doing their job, people compensate.
Quietly.
Without even realising it.
You might notice it in your own work:
- You remember things instead of recording them
- You double-check work that should already be controlled
- You follow up more than you should need to
- You carry risk information in your head
It works, for a while.
But it doesn’t scale.
And it’s exhausting.
The Question That Changes Everything
If you want to improve how your projects run, start here:
Where am I currently compensating for the absence of a proper system?
That question cuts straight to the real issue.
Because the problem usually isn’t effort.
It’s structure.
What Good Looks Like (Without Overcomplicating It)
There’s a common misconception, especially in SMEs, that improving structure means adding bureaucracy.
It doesn’t.
In fact, the opposite is true.
The goal is simple:
Structure should support the work, not increase the burden.
In practice, that might look like:
- A clear owner for each task
- A simple shared tracker instead of chasing updates
- A decision log that removes the need to re-explain things
- A visible risk list instead of relying on memory
Small changes.
But they remove a surprising amount of friction.
A Note on AI (and Where It Actually Helps)
There’s a lot of focus on AI right now.
Most of it is centred around tools.
But the real value is much more practical than that:
- Drafting and refining documents faster
- Summarising meetings and extracting actions
- Stress-testing plans and assumptions
Used well, it frees up time and mental energy.
But it doesn’t fix broken systems.
If anything, it highlights them.
Because if the underlying structure isn’t clear, you just end up automating confusion.
A Simple Way to Start Improving Things
You don’t need a full overhaul.
Just pick one pressure point.
Something small, but persistent.
For example:
- Chasing updates → introduce a shared tracker
- Repeating decisions → start a simple decision log
- Holding risks mentally → create a visible risk list
Fix one thing properly.
That’s enough to start shifting how the whole system feels.
Final Thought
Most people try to improve performance by working harder.
The real improvement comes from reducing the need to.
What are you still managing personally that really ought to be handled by a system?
That’s usually where the next step is.
If This Feels Familiar…
If you’re constantly holding things together through effort, it’s usually a sign that the system isn’t doing enough of the work.
I help SMEs put simple, right-sized delivery systems in place so projects run with less friction, more clarity, and far less reliance on individual effort.