←Back to the Kraken The Kraken · Arm Nº 06 · Blurred responsibility

Product Owner vs.
Product Manager vs.
vs. Project Manager

Not who holds the title.
Who is allowed to decide.

The short answer

Three titles, one question: who is allowed to decide?

A Project Manager manages resources: budget, schedule, scope, and how something gets delivered. A Product Manager, in the classic setup, decides what gets built and passes decisions down to the team. A Product Owner keeps the balance between what the crew wants to build and what the company needs: the product’s biggest fan, who hears every side, then has the final word.

A title without the helm is only a hat. The helm is handed over by the whole ship.

Who does what on board

The captain

Product Owner

Sets the course and keeps the balance between crew and owners. Hears every side, then has the final word.

The shipowner

Product Manager

Decides ashore where the voyage goes. The orders arrive by letter, the crew carries them out.

The purser

Project Manager

Keeps provisions, money and schedule. Decides how the voyage is supplied, not where it goes.

The ship’s crew

The team

Makes the ship move. Speaks up when the course seems wrong.

Give the role a name.
The rest follows, right?

But …

A crew follows a captain, not a hat

Every title comes with expectations, from the system and from the people in it.
Without the mandate behind it, the title promises what the role cannot keep.

1

Unofficial leaders

The captain has the hat, not the trust.
People turn to the one they trust.

2

A captain without a mandate

A captain worth following, overruled.
Who do we follow now?

3

The crew stops following

Hat and mandate, but the wrong calls.
The crew works around the captain.

Kinds of blurred responsibility

Five ways responsibility blurs

Where roles stay unclear, the space between them never stays empty. Something always fills it.

A hat without a helmThe title is there. The mandate is not.
Everyone was in the roomThe whole crew was in the meeting. Nobody was enabled to carry its outcome forward.
Not our deckWhere mistakes are not allowed, responsibility means blame. So it gets passed on.
The gap fills itselfNobody decides who carries it, so the system does. The wrong person steps in, or the right one walks away.
No two compasses agreeAsk who decides, and every answer points somewhere else.

How blurred responsibility shows

Typical indicators. Not a complete list, but the ones that show up most often.

Sign 1Nobody wants to own it, because owning means owning everythingSign 2Ask five people who decides, get five answersSign 3The Product Owner has the title, not the standingSign 4The crew says no, someone above says yes, and the crew is ignoredSign 5Those who take responsibility end up carrying everyone’sSign 6“Whose job is that?” stays unansweredSign 7Emails go out “for the record”, with half the company in CCSign 8Someone decides who has no mandate for itSign 9Mistakes start a search for someone to blame

Who holds which part of the helm

There is more than one good way to share responsibility.
Each one works, as long as everyone knows which one they sail by.

The captain’sThe crew’s
Set the course
Pick the crew members
Run the watch
Sail the ship
1Captain-led
2Self-managing
3Self-designing
4Self-governing
After J. Richard Hackman’s authority matrix for teams.
The golden rule

Responsibility needs a clear role, the mandate to decide, and a system that honours both.

Carrying responsibility is not the problem. Carrying it without a mandate is, or carrying it alone. Management is there to manage resources, and that includes the system people work in: roles that are clear, decisions that stay made, mistakes the crew can learn from.

Self-check: whose call is it?

Pick a role. For each of its decisions, play the card you think it deserves.

Choose a role
·
Decision of 5

How should the make this decision?

Your cardATypical agile viewCTypical classic view

Would your colleague play the same cards?

Where the cards differ, responsibility starts to blur.

After the seven levels of delegation by Jurgen Appelo.

Is the hat on the right head?

A free discovery call, 30 minutes, remote. No slide deck, no obligation.

Send a signal
Talk with us in English · in German