Skip to main content
Published in Product Insights

Do You Actually Have a Product Owner?

Do You Actually Have a Product Owner?
Table of contents
  1. What is a product owner, according to the Scrum Guide?
  2. What makes a good product owner?
  3. What essential skills does a good product owner need?
  4. What are a product owner's key responsibilities, from backlog management to releases?
  5. How is a product owner different from a Scrum Master or the Developers?
  6. What is the difference between a product owner and a product manager?
  7. How much technical knowledge does a product owner need?
  8. Where does a product owner's time go in each Sprint with the development team?
  9. Should the product owner be on your team or the software company's?

A good product owner holds two things at once: the authority to make product decisions and the product knowledge to make them well. This guide is for CEOs, COOs and engineering leaders deciding who should own a software product, including when an outside company handles the software development. It covers what the 2020 Scrum Guide holds the role accountable for, the skills the role needs, and whose team the owner belongs on. This matters because this post, from March 2025, says: "Since the Gnar started in 2015 our most successful projects have had a capable product owner." Its added sections quote sources read on November 18 and 19, 2026.

Is your product struggling? It might be because you don't have a real product owner.

We have a core belief that product owners are the most important role on a technical team (yes, technical team). In fact, if you were to build a technical team with just one person, we think it should be the product owner. Since the Gnar started in 2015 our most successful projects have had a capable product owner.  

But, like most good things, there are imposters and fakes out there. If your product is struggling, you probably don't have a real product owner. Here are the three phonies you may find once you pull off the mask (and what the real deal looks like).

Matrix titled Do you really have a product owner: product knowledge against authority to make decisions, with quadrants Product Expert, Product Owner, Product Placeholder and Disconnected Director

Imposter #1: Product Expert

This person seems like the ideal product owner, at first glance. They know everything about the product: its history, its quirks, and its current challenges. They're the one everyone goes to with questions about functionality, features, or context. They may run demos for potential prospects and new internal team members. They hear all of the feedback on the product first hand, both positive and constructive. They may be even the primary QA tester before code releases.

But there's a fatal flaw: they don't have the authority to make decisions that stick, leading to changing priorities for the development team.

The primary contact is often trapped in a middle-management role or working under the shadow of a higher-up who has the final say. They might offer suggestions or guidance, but they can't give a definitive answer, which means every decision gets bogged down in approval cycles. This leads to delays, frustration, and a product that stalls instead of moving forward.

Imposter #2: Disconnected Director

This is the most dangerous imposter of all, they have authority without the knowledge.

The Disconnected Director sits high enough in the org chart to make decisions and understand the priorities of the organization, but they're far removed from the day-to-day realities of the product. They might not know how the product works, what the users need, or what's technically feasible. Instead, they rely on intuition, abstract strategy, or secondhand information.

While their authority means they can push decisions through, the decisions they make can be misinformed, disconnected, or require far more effort than they anticipate. That means features nobody wants, technical debt, or wasted time chasing the wrong priorities.

This is the most dangerous stand-in of all, but be careful, this person might be you.

Imposter #3: Product Placeholder

When you're stuck with a Product Placeholder, you're in trouble.

The Placeholder is someone who lacks both authority and product knowledge. They can't make decisions that mean anything, nor can they offer meaningful insight into how the product works or what it needs.

They often play a passive role, nodding along in meetings, deferring questions to others, and taking a "just here to facilitate" stance. They might be seen as a temporary fix, a body filling the seat of a product owner, but their presence can sap momentum, confuse communication, and leave the team without clear direction. This person needs to develop their understanding of the product, then advocate for the authority to set product priorities and roadmap.

The Real Product Owner

So, what does the real deal look like?

Authority: They can make strategic decisions about the product and tactical calls in the moment. When they make a choice, it sticks.

Knowledge: They deeply understand the product, its features, its users, and its technical constraints. They might not be an engineer, but they know enough to have meaningful conversations with the technical team and spot when something doesn't add up.

Decision-Making Skills: They balance user needs, business goals, and technical realities to make choices that move the product forward. They don't rely on gut feelings or abstract strategies; they use data, input from the team, and a clear vision to guide the way.

With a real product owner at the helm, your team can build momentum, ship meaningful features, and deliver a product that truly works.

So, take a look at your team: do you have a real product owner, or just an imposter in disguise?

What is a product owner, according to the Scrum Guide?#

A product owner is the person accountable for the value of a product. The 2020 Scrum Guide says "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team." It adds: "How this is done may vary widely across organizations, Scrum Teams, and individuals."

The guide also says "The Product Owner is also accountable for effective Product Backlog management, which includes:" the items in this table.

What the Product Owner is accountable forThe 2020 Scrum Guide's words
Product Goal"Developing and explicitly communicating the Product Goal"
Backlog items"Creating and clearly communicating Product Backlog items"
Order"Ordering Product Backlog items"
Transparency"Ensuring that the Product Backlog is transparent, visible and understood"

The guide lets the owner share the work. It says "The Product Owner may do the above work or may delegate the responsibility to others. Regardless, the Product Owner remains accountable." In its definition of Scrum, it adds "A Product Owner orders the work for a complex problem into a Product Backlog."

This post, from March 2025, says: "We have a core belief that product owners are the most important role on a technical team (yes, technical team)." The Gnar Company's Minimum Viable Technical Team post, published March 13, 2025, says: "We've simply identified the one role that nearly all successful products have: a product owner."

What makes a good product owner?#

A good product owner has authority and product knowledge, and the organization around them backs that authority. This post, from March 2025, describes authority this way: "Authority: They can make strategic decisions about the product and tactical calls in the moment. When they make a choice, it sticks."

The 2020 Scrum Guide puts the same demand on the organization: "For Product Owners to succeed, the entire organization must respect their decisions." It says "These decisions are visible in the content and ordering of the Product Backlog, and through the inspectable Increment at the Sprint Review."

The guide also names who holds the role. It says "The Product Owner is one person, not a committee."

As general advice, the Scrum.org page What is a Product Owner? lists stances a Product Owner takes. It says "These stances include the Visionary, Collaborator, Customer Representative, Decision Maker, Experimenter and Influencer."

Without that authority, this post says, "every decision gets bogged down in approval cycles".

What essential skills does a good product owner need?#

As general advice, the Scaled Agile Framework (SAFe) Product Owner page, last updated January 24, 2025, says the role "requires vision, excellent communication skills, and exceptional decision-making." Scrum.org's 2016 blog post The 18 Characteristics of a Great Product Owner and Mountain Goat Software add more skills. The table shows those and two SAFe lines.

SkillSourceIts words
Business valueSAFe"primarily responsible for maximizing the value delivered by the team by ensuring that the team backlog is aligned with customer and stakeholder needs"
FeedbackSAFe"By managing the backlog, gathering feedback, and promoting teamwork"
Product knowledgeScrum.org, 2016"A great Product Owner has in depth functional product knowledge and understands the technical composition."
Face-to-face communicationScrum.org, 2016"User stories are explained in a personal conversation."
AvailabilityScrum.org, 2016"A great Product Owner is available for the stakeholders, the customers, the development team and the Scrum Master."
Developers' opinionsMountain Goat Software"considering developers’ opinions on priorities."

This post, from March 2025, ties the skills to the product owner's daily work. It says "They might not be an engineer, but they know enough to have meaningful conversations with the technical team and spot when something doesn't add up." It adds "Decision-Making Skills: They balance user needs, business goals, and technical realities to make choices that move the product forward."

What are a product owner's key responsibilities, from backlog management to releases?#

As general advice, Atlassian's agile scrum roles guide, published November 4, 2025, lists three key responsibilities for a product owner: backlog management, stakeholder management and release management. The table shows each one.

ResponsibilityAtlassian's words
Backlog management"ultimately they are responsible for the backlog that the development team pulls to deliver from"
Stakeholder management"Any product will have many stakeholders involved ranging from users, customers, governance and organizational leadership."
Release management"It is important for the product owner to know when things can and should be released."

The same page says "Since agile teams are, by design, flexible and responsive, it is the responsibility of the product owner to ensure that they are delivering the most value." It adds "Each role has distinct responsibilities, but they work closely together to achieve sprint goals."

The Gnar Company's post 3 Scrum Rules We Break and Why, published July 9, 2025, describes how its own project managers and Scrum Masters work with the owner: "We might drive the backlog refinement process, but we want the PO to inform us of the best route to take."

As general advice, Mountain Goat Software's Product Owner Role and Responsibilities in Scrum is written for "people who want a practical understanding of the Product Owner role in Scrum." It says "Stakeholder management is a major part of product ownership." It says the owner "explains the goals behind the work, answers questions, clarifies acceptance criteria, and helps Developers understand what outcome matters." Its article on what teams want includes the heading "Successful Product Owners Collaborate with All Stakeholders."

SAFe says "By managing the needs of stakeholders, the PO guides the evolution of the Solution to deliver maximum value."

How is a product owner different from a Scrum Master or the Developers?#

A product owner answers for the product's value, and a Scrum Master answers for Scrum. The Developers are committed to creating any aspect of a usable Increment each Sprint. The guide sets no hierarchy between the three. The 2020 Scrum Guide says "Scrum defines three specific accountabilities within the Scrum Team: the Developers, the Product Owner, and the Scrum Master." It also says "Within a Scrum Team, there are no sub-teams or hierarchies."

AccountabilityThe 2020 Scrum Guide's words
Product Owner"accountable for maximizing the value of the product"
Scrum Master"accountable for establishing Scrum as defined in the Scrum Guide"
Developers"committed to creating any aspect of a usable Increment each Sprint"

The Scrum Master also serves the owner. The guide lists "Facilitating stakeholder collaboration as requested or needed."

As general advice, Scrum.org lists misunderstood stances, "which include the Product Owner being viewed as the Story Writer, Project Manager, Subject Matter Expert, Clerk, Gatekeeper or Manager." On product management, SAFe says the Product Owner is "part of the larger Product Management function." It adds "Together with Product Management, they ensure that product strategy and implementation remain connected across teams."

The Gnar Company's post 3 Scrum Rules We Break and Why describes how its own staff fill those roles next to a client's owner: "Our Project Managers (PMs) and Scrum Masters (SMs) (a role that is often blended on our team) become deeply involved in product backlog management."

What is the difference between a product owner and a product manager?#

As general advice, Scrum.org's 2025 blog post on the difference says "A Product Manager is a job title, while a Product Owner is an accountability in Scrum." The same post asks whether a product manager can be the product owner and answers "Yes, provided they have full authority over the product."

Atlassian's Product Manager page says a product manager is "responsible for identifying customers' needs and the larger business objectives that a product or feature will fulfill". It also says "the product owner should work more closely with the development team to execute against the goals that the product manager helps to define."

Atlassian's tableProduct managerProduct owner
Owns"Owns vision, marketing, ROI""Owns team backlog and fulfillment work"
Stakeholders"Works with outside stakeholders""Works with internal stakeholders"
Vision"Helps to define the product vision""Helps teams execute on a shared vision"

The two Atlassian pages differ on stakeholders. This table puts the product owner with internal stakeholders, while Atlassian's scrum roles page lists users and customers among the product owner's stakeholders.

Atlassian's Product Manager page also says "If the team isn’t doing Scrum (say, they’re doing kanban or something else), the product manager might end up doing the prioritization for the development team and play a larger role in making sure everyone is on the same page." This post, from March 2025, ties the owner to authority: "When they make a choice, it sticks."

How much technical knowledge does a product owner need?#

A product owner needs enough technical knowledge to follow the engineers, and the 2020 Scrum Guide gives the sizing of work to the Developers. This post, from March 2025, says the owner "might not be an engineer" and still needs enough knowledge to spot "when something doesn't add up."

DecisionWho has itThe 2020 Scrum Guide's words
SizingDevelopers"responsible for the sizing"
Trade-offsDevelopers, with the Product Owner's input"may influence the Developers by helping them understand and select trade-offs"
Who does what and howScrum Team"self-managing, meaning they internally decide who does what, when, and how"
Cancelling a SprintProduct Owner"Only the Product Owner has the authority to cancel the Sprint."

The Gnar Company's post The Minimum Viable Technical Team, published March 13, 2025, says this about a product that already exists: "And if the product already exists, they know how the system works and the improvements needed to grow users."

Where does a product owner's time go in each Sprint with the development team?#

In the 2020 Scrum Guide, the Product Owner prepares for Sprint Planning, takes part in it, joins scope talks during the Sprint, and is part of the Scrum Team at the Sprint Review. In Sprint Planning, "The Product Owner proposes how the product could increase its value and utility in the current Sprint."

WhenWhat the 2020 Scrum Guide says
Preparing for Sprint PlanningThe Product Owner "ensures that attendees are prepared to discuss the most important Product Backlog items and how they map to the Product Goal"
Sprint Planning"Through discussion with the Product Owner, the Developers select items from the Product Backlog to include in the current Sprint."
During the Sprint"If the work turns out to be different than they expected, they collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint without affecting the Sprint Goal"
Sprint Review"The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed."

The Agile Manifesto principles say "Business people and developers must work together daily throughout the project." As general advice, Mountain Goat Software's article Be a Great Product Owner: Six Things Teams and Scrum Masters Need lists "Good Product Owners Are Available" first.

The Gnar Company's post 3 Scrum Rules We Break and Why, published July 9, 2025, names the time problem on client teams: "Clients often lack access to someone who can dedicate the necessary time for effective product ownership." It adds "Sometimes the designated PO is spread across multiple initiatives."

Should the product owner be on your team or the software company's?#

The Gnar Company's post 3 Scrum Rules We Break and Why, published July 9, 2025, says where the product owner belongs: "Ideally, this person is on the client’s team and has a deep understanding of the business, a clear product vision, and the authority to make those decisions." The Gnar Company's post The Minimum Viable Technical Team says "You can outsource nearly anything: development, design, maintenance. But you can't outsource ownership."

That post adds "If you have a product that users rely on, you need someone internally to own it." The 3 Scrum Rules post also says what happens when the owner is thin: "While we always advocate for including a strong PO (and we've seen projects struggle when that role is absent or filled by the wrong person), we're also realistic about stepping in where gaps exist."

The Gnar Company's How We Work page ties three engagements to where your team stands today.

Where your team standsWhat How We Work says
Knows what to build, needs engineers"If your team knows what to build and needs more engineers, Embed fits."
Needs the plan and the price first (Gnar Discovery and Design)"If you need the plan and the price first, start with Discovery."
Unsure which ideas are worth building"Not sure which ideas are worth building? Start with Compass, which ranks them."

If your owner is still a placeholder, this post's own fix applies: "This person needs to develop their understanding of the product, then advocate for the authority to set product priorities and roadmap."

Frequently asked questions

Why might a product expert struggle as a product owner?

They may know the product deeply but lack authority to make decisions that stick. That can cause changing priorities, delays and repeated approvals.

What is a Product Placeholder?

It is someone who lacks both authority and product knowledge. They need to develop their understanding of the product, then advocate for authority to set priorities and the roadmap.

Does a product owner need to be an engineer?

Not necessarily. They need enough knowledge of the product and its technical constraints to have meaningful conversations with engineers and notice when something does not add up.

What does the Scrum Guide say a product owner is accountable for?

The 2020 Scrum Guide says "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team." That includes developing and communicating the Product Goal, creating and ordering Product Backlog items, and keeping the backlog transparent.

Can a committee act as the product owner?

The 2020 Scrum Guide says "The Product Owner is one person, not a committee." It adds that those wanting to change the Product Backlog "can do so by trying to convince the Product Owner."

Can a product owner delegate backlog work?

Yes, and the accountability stays with the owner. The 2020 Scrum Guide says "The Product Owner may do the above work or may delegate the responsibility to others. Regardless, the Product Owner remains accountable."

Should the product owner work for us or for the software company we hire?

The Gnar Company's post 3 Scrum Rules We Break and Why says "Ideally, this person is on the client’s team and has a deep understanding of the business, a clear product vision, and the authority to make those decisions."

Is a product owner the same as a project manager?

The two roles are different. Scrum.org lists "Project Manager" among the misunderstood stances of the role, and the 2020 Scrum Guide names three accountabilities, which are the Developers, the Product Owner and the Scrum Master.

Stay In The Loop

Never miss an update. Get the latest blogs, webinars, and expert insights straight to your inbox from The Gnar.