Part of the Agile Product Hub “Deep Dive” series on product leadership, decision systems, and organisational agility. (The views expressed in this article are solely those of the author)

Many organisations invest heavily in improving how products are delivered.

They introduce Product Owners, define backlogs, adopt Agile delivery cycles, and talk about empowering teams. The intention is clear. Teams should be able to move quickly while staying aligned with customer needs and organisational goals.

Yet when an important decision appears, something unexpected often happens.

The Product Owner hesitates to decide. The Product Manager is not part of the delivery conversation. Stakeholders step in to clarify direction. Engineering leaders raise technical constraints.

The decision gradually becomes collective.

At first this feels collaborative. Over time it creates something else entirely.

Decision ownership becomes blurred.

This question has appeared frequently in conversations I have had recently, including a discussion in my podcast episode “Who Actually Owns the Decision?” where we explored how decision authority often shifts as organisations scale.

The Illusion of Shared Decision Making

Most organisations believe their decisions are collaborative. Many people contribute insights, constraints, and perspectives. Alignment sessions are held. Leadership reviews occur. Cross-functional workshops are organised.

On the surface this appears healthy.

However, collaboration only works when decision boundaries remain clear.

Someone must ultimately own the call.

When ownership is unclear, collaboration gradually becomes diffusion. Every participant influences the outcome, yet no one carries full responsibility for the decision itself.

This pattern rarely appears intentionally. It emerges quietly as organisations grow and governance structures expand.

An Idea discussed in an upcoming book - Product Agile Harmony

“Clarity in decision ownership is not about control, it is about enabling learning to happen quickly.”

When decisions cannot be traced back to a clear owner, organisations lose something critical: the ability to learn quickly from outcomes.

Where Product Management and Product Ownership Diverge

One of the biggest contributors to blurred decision ownership is how organisations interpret the relationship between Product Managers and Product Owners.

In many companies the difference between the roles is explained simply.

Product Managers focus on the direction of the product. They analyse markets, understand customers, shape strategy, and connect the product to business outcomes.

Product Owners focus on enabling delivery. They work closely with engineering teams, structure the backlog, clarify requirements, and guide day-to-day prioritisation within the delivery environment.

When this relationship works well, the roles complement one another.

The Product Manager shapes where the product should go. The Product Owner enables the team to build the right things effectively.

But in practice the boundary between these roles is often unclear.

Some organisations expect Product Owners to perform the full Product Manager role. Others separate the roles but fail to define how decisions flow between them. In some cases the Product Manager becomes detached from delivery altogether.

Each variation changes how product decisions are made.

A Concept discussed in the Agile How To Series

“Product roles should never exist as isolated silos. Strategy and delivery must continuously inform each other.”

When strategy and delivery operate too far apart, the decision space between them begins to fragment.

The Training Gap That Reinforces the Problem

This confusion is often reinforced by how people are trained.

Product Owner training frequently focuses on delivery mechanics. It teaches backlog management, sprint planning, user stories, and prioritisation within Scrum events. These skills are important for supporting delivery.

However, Product Owners are rarely trained in the broader capabilities associated with product management.

Similarly, Product Manager training often focuses heavily on strategy artefacts and frameworks. It teaches roadmaps, business cases, market analysis, and stakeholder alignment.

These skills are important for shaping direction. However, Product Managers are rarely trained in the practical mechanics of how decisions flow through delivery organisations, or how ownership interacts with roles such as Product Owners, architects, UX, and engineering.

The result is a gap in the middle. Product Owners understand delivery mechanics but may lack strategic product capability. Product Managers understand strategic framing but may lack deep experience of how delivery systems actually operate.

Without strong integration between these roles, decision ownership becomes fragmented.

From How to Navigate the Agile Journey as a Scrum Master

“Agile roles should be understood in the context of the whole product system, not just the ceremonies that support delivery.”

Training that focuses only on delivery mechanics often unintentionally reinforces the separation between product thinking and product delivery.

How Decisions Start to Drift

When Product Managers define direction but are not present in delivery discussions, and Product Owners manage delivery but cannot alter product strategy, a gap appears.

Important questions begin to fall between the two roles: Should the team pursue this opportunity now or later? Does customer feedback justify a roadmap change? Is the current solution the best way to solve the problem?

The Product Owner understands the delivery implications.

The Product Manager understands the strategic implications.

If the boundary between these perspectives is unclear, neither role may feel fully able to make the final call.

At that point the system adapts.

Stakeholders step in to provide direction. Governance forums review priorities. Leadership discussions settle trade-offs.

Over time decisions migrate away from the team and toward organisational forums.

Alignment increases.

Decisiveness decreases.

An Idea discussed in Product Agile Harmony (upcoming book)

“When decisions travel too far from the teams doing the work, feedback loops slow down and value discovery becomes harder.”

The organisation becomes more coordinated, but less adaptive.

The Impact on Product Teams

When decision ownership becomes blurred, the consequences are subtle but significant.

Teams begin to focus on completing work rather than learning about the product.

Roadmaps gradually turn into commitments rather than evolving hypotheses.

Product Owners spend increasing time negotiating priorities instead of shaping delivery.

Product Managers become further removed from the realities of how the product is built.

None of these outcomes occur because people lack capability.

They emerge because the system separating product direction from delivery execution has grown too wide.

This is often the point where organisations begin introducing more governance in an attempt to restore clarity.

Ironically, that governance often reinforces the very separation that caused the problem.

Reconnecting Strategy and Delivery

Healthy product organisations recognise that Product Management and Product Ownership represent two perspectives on the same product.

One connects the product to markets, customers, and business outcomes.

The other connects the product to engineering delivery and implementation.

Both perspectives need to influence product decisions.

This does not require merging the roles or collapsing responsibilities.

It requires clarity about how decisions move between them.

Product Managers need visibility into delivery realities. Product Owners need understanding of customer problems and product direction.

When this connection is strong, decision ownership becomes easier to locate.

A System Signal

When organisations struggle to identify who owns product decisions, it rarely indicates a problem with individual roles.

It usually signals that the system separating product strategy and product delivery has grown too wide.

Product Managers operate in one space.

Product Owners operate in another.

Stakeholders and governance groups attempt to connect the two.

The result is a system where many people influence decisions, yet ownership itself becomes difficult to identify.

Recognising this pattern is the first step toward improving it. Because when decision ownership becomes clear again, teams move faster, learning accelerates, and products evolve more effectively.

Closing Thought

Product organisations succeed when decisions connect strategy with delivery.

Product Managers bring the market and customer perspective.

Product Owners bring the delivery and engineering perspective.

When these perspectives work together within a system that respects clear decision ownership, teams can move with confidence and learn continuously.

When that connection weakens, decisions begin to drift.

And eventually the organisation finds itself asking a familiar question.

Who actually owns the decision?

Continue the Conversation

If this topic resonates, you may also find these useful:

Podcast: Who Actually Owns the Decision?

Article: When Product Owners Are Accountable but Not Empowered

Upcoming book: Product Agile Harmony. Exploring how organisations align product thinking, Agile delivery, and decision systems.