Day: 14 January 2026

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.