Month: January 2026

Scrum embodies ‘wu wei’ – effortless alignment with complexity

In Taoism, wu wei is often translated as “doing without forcing”.

I briefly studied Taoism at university, and the idea has stayed with me – especially in the last week, where many conversations have circled around complexity, uncertainty and change.

Scrum, at its best, doesn’t try to dominate complexity.
It creates a rhythm that allows teams to move with emergent reality.

Sprint planning, reviews and retrospectives are not control mechanisms. They’re sensing points. Moments to notice what is actually happening, then adjust without drama or over-correction.

The most effective Scrum Masters I’ve worked with don’t push progress.
They cultivate conditions where progress feels natural.

Less force.
More responsiveness.
Alignment rather than control.

That, to me, is wu wei in practice.

When Scrum feels heavy, it’s often because we’re trying too hard to make reality behave.

I’m increasingly convinced that many Agile struggles come from treating complexity as a problem to solve, rather than a condition to work within.

Helmet / Silver Cord Sessions

It was back in the mid-90s, on the irreverant US adult cartoon Bevis and Butthead that I first encountered Helmet. The song was “Wilma’s Rainbow” and I was hooked.

The eponymous hosts were commenting on how ordinary the band members looked, and that if you saw them walking down the street, you wouldn’t realise how cool they were. Cos they’re in a band.

Ladies and gentlemen – and Betty… and Wilma – Helmet live at Silver Cord Studio, New York in March 2025.

Track listing

00:00 Wilma’s Rainbow
04:15 I Know
08:04 Milquetoast

Band

  • Page Hamilton—Vocals and guitar
  • Dan Beeman—Rythm guitar and backing vocals
  • Dave Case—Bass and backing vocals
  • Kyle Stevenson—Drums and backing vocals

Capture isn’t about organisation

People often think capture – writing down tasks, ideas and reminders – is about organisation.

Get things out of your head.
Put them in the right place.
Build a trusted system.

That’s all true, but it’s not the first thing capture is doing.

What capture really does is lower background anxiety.

When something pops into your mind and stays there, your brain keeps rehearsing it. Not because it’s important, but because it might be a threat. Something you could forget. Something that could come back to bite you later.

So your mind keeps looping.

Writing it down doesn’t help because you’ve organised it.
It helps because you’ve told your nervous system: this is safe now.

That’s why partial capture feels worse than none at all.
A half-written thought doesn’t close the loop. It leaves the brain on watch.

I’ve noticed that when my head feels busy, it’s rarely because I have too much to do. It’s because too many things are asking to be remembered.

Capture isn’t about being productive.
It’s about giving your mind permission to stop scanning for danger.

And once that quiets down, clearer thinking tends to follow.

The Product Owner is the moral philosopher of the system

Photo by Taitopia Render on Unsplash

The Product Owner role is often described in economic terms.

Value maximisation.
Prioritisation under scarcity.
Return on investment.

All of that is true, but it is incomplete.

Because the Product Owner is not only making economic choices. They are making moral ones.

Every decision to prioritise one thing is also a decision to delay or deny something else. Time, attention and energy are finite. Choosing where they go is an ethical act, whether it is acknowledged or not.

At a practical level, the Product Owner balances cost and value.
At a deeper level, they translate collective intent into action.

They answer questions like:

  • What matters most now?
  • Who benefits from this decision?
  • Who carries the cost if we get this wrong?
  • What kind of system are we becoming through these choices?

This is why backlog refinement is never just administrative.

It is a repeated confrontation with opportunity cost.
A conversation about trade-offs under uncertainty.
A quiet negotiation between competing goods.

In that sense, the Product Owner’s work is philosophical.

Not abstract philosophy, but lived philosophy – deciding what deserves attention in a world where not everything can be done, and certainty is always partial.

When the role is reduced to ‘writing user stories’ or ‘keeping the backlog tidy’, something essential is lost.

The Product Owner is not the owner of tasks.
They are the steward of meaning.

The highest level of Scrum maturity is invisibility

The upper towers of the Golden Gate suspension bridge emerging from fog against a blue sky.
When structure is trusted, it no longer needs to be visible
Photo by Joshua Earle on Unsplash+

At the beginning, Scrum is very visible.

There are named roles, scheduled events, artefacts with capital letters. Stand-ups are announced. Refinement is booked in advance. The backlog is a thing that needs managing.

This visibility is not a failure. It is scaffolding.

Scrum exists to create just enough structure to help a team notice reality more clearly: what is actually happening, where value is flowing, and where it is getting stuck.

But something interesting happens as a team matures.

The more deeply the principles are understood and embodied, the less the framework itself needs to be seen.

Inspection and adaptation stop being calendar events and start becoming habits.
Planning becomes a shared conversation about intent and trade-offs, not a meeting.
Leadership emerges where the work is, not where the job title sits.

At that point, Scrum begins to dissolve.

Not because it has failed, but because it has succeeded.

Shu – ha – ri … obey – detach – transcend.

There are no ceremonies’, only natural rhythms of checking in and adjusting course.
There are no ‘roles’, only people taking responsibility when it is needed.
There is no ‘backlog’, only a clear and continuously updated sense of what matters most next.

The danger is that organisations often mistake invisible Scrum for no Scrum.

From the outside, it can look informal. Unstructured. Even chaotic.
But inside the team, clarity is high. Feedback is fast. Decisions are grounded in value rather than habit or hierarchy.

This is agility as a state of being, not a process.

Scrum, at its best, is not something a team does.
It is something a team grows out of.

When that happens, the framework quietly steps back, having done its job.

—

Where does your team sit – still building scaffolding, or afraid to let go of it?