Main idea

People readily answer that what matters is what you do, not what you're called. That is right in principle and wrong in its effects. The title distributes authority before any negotiation takes place: a Product Manager is held to own their scope, a Product Owner is held to be the one who prepares the team's work. Colleagues grant or withhold arbitration on the basis of that label, before having assessed the person.

In practice, the Product Owner title has often served to compartmentalize product responsibility without granting the decision mandate. It assigns a load and withholds the power. A role without an arbitration mandate isn't a role: it is an uncomfortable position.

Layer added by "PM, Developers, and AI: Roles Are Blurring, Responsibilities Remain" (2026-08-01). The opposite position is stated plainly for the product roles that appear alongside tooling: the important point isn't the title but the responsibility, and the useful question becomes "what are you capable of judging, building, guaranteeing, evaluating, or maintaining?" rather than "what is your role?". The two readings meet on one observation — a title without a mandate produces nothing — and diverge on the order of operations: name the responsibility first, or first the title that will make it credible to other teams.

Why it matters

This makes the choice of a title contestable: naming a role is an act of organization, not an administrative convenience, and it commits what its holder will be able to decide.

And it explains a common form of suffering without invoking incompetence: the person is held responsible for what they have no latitude to settle.

Nuances and limits

The relation doesn't reverse mechanically. Renaming a role doesn't grant the missing mandate: a Product Manager locked into operations and firefighting, without the latitude to define a product strategy, will be busy without producing anything useful. The title steers how the mandate is assigned, it doesn't replace it — and insisting on vocabulary can obscure the fact that the mandate is the real subject.

The weight of the title also varies with culture: in a small structure where everyone knows everyone else's work, the label counts for much less than accumulated trust.

Open questions

• How does an organization explicitly assign an arbitration mandate, independently of the title, and make it verifiable by other teams?