Why working harder isn’t the answer to sustainable delivery
This month has felt like a bit of a turning point.
After a sustained period of pushing hard to get work over the line, I’ve found myself reflecting more on what actually makes delivery sustainable. Not just getting things done, but doing it in a way that doesn’t rely on constant effort and firefighting.
It’s easy to fall into the trap of thinking progress comes from working harder. In reality, it usually comes from stepping back, putting a bit of structure in place, and being more intentional about how you move forward.
That’s probably been the common thread running through everything I’ve been writing and thinking about recently.
From Effort to Intentional Systems
There’s a point where more effort stops being the answer.
Most teams, and most individuals, respond to pressure in the same way. They push harder. Work longer. Try to stay on top of everything through sheer force.
It works, for a while.
But without something to hold it all together, knowledge gets lost, direction drifts, and the same problems come back around again.
The alternative isn’t complexity or heavy process. It’s simple, intentional systems.
A way of capturing what’s happening.
A way of deciding what matters.
A way of maintaining direction over time.
Not bureaucracy. Just enough structure to stop you starting from scratch every time.
Watch for When Effort Becomes the Only Strategy
If the only way things get done is by people pushing harder, working longer, or “just getting through it”, that’s usually a sign that something is missing underneath.
It might be:
- No clear way of capturing lessons as you go
- No shared view of priorities or risks
- No mechanism for maintaining direction between milestones
At that point, the issue isn’t capability or commitment.
It’s the absence of a system.
And that’s where most of the real gains are.
What This Looks Like in Practice
Over the past few weeks, I’ve been exploring this idea from a few different angles:
Getting Over the Hump
The danger of normalising brute force delivery and sustained overwork. If you don’t capture what you’ve learned immediately after a milestone, you lose it, and the next phase becomes just as difficult.
The Project Memory Problem
Why businesses repeat the same mistakes. Lessons learned get documented but not used. The real shift comes from embedding them into simple tools and ways of working, creating a single source of truth.
Managing Change
Without a clear direction, it’s easy to drift and react to whatever shows up. A defined goal, supported by simple systems, allows you to stay aligned and move with intent.
One Practical Move
Run a 30-minute post-milestone reset before moving on.
After your next milestone, don’t just roll straight into the next phase.
Instead:
- Capture 3–5 things that caused friction
- Capture 3–5 things that worked well
- Choose one change you will actually carry forward
Write it down somewhere visible and use it immediately in the next phase.
It’s not a full lessons learned session. Just a quick reflection.
Done consistently, this compounds. Over time, you build an effective, repeatable system without overcomplicating things.
On Reflection
It’s easy to drift.
To follow whatever is in front of you.
To react to whatever shows up.
To accept the way things are because it’s easier than changing them.
But a few simple systems, a bit of intentionality, and the willingness to pause, reflect, and adjust…
That’s usually enough.