The full title is What kind of problem is this? A Scrum Master’s field guide to using Cynefin in real team situations.
It is a practical book for Scrum Masters, Agile Coaches, Product Owners, delivery leaders and anyone who works with Scrum but has sometimes wondered why the same practices work beautifully in one situation and fall flat in another.
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.
I use analytics cookies (Microsoft Clarity) to understand how the site is used and improve content.
