What is a Product Owner?

Demystifying the delivery-side of product roles

When we talk about building great digital products, we often hear about Product Managers — but what about the Product Owner?

In Agile teams, especially those following Scrum, the Product Owner (PO) plays a pivotal role in bridging the gap between business priorities and the development team. In fact, in many of the teams I’ve worked with, I wore both the PO and PM hat — especially in smaller or resource-constrained organisations.

What is a Product Owner?

A Product Owner is responsible for maximising the value of the product resulting from the work of the development team. That’s the textbook definition — but in practice, it’s a mix of backlog management, clarity, and prioritisation.

The PO works closely with developers to ensure they’re always working on the most valuable tasks, and that there’s a clear understanding of what’s needed.

Key Responsibilities of a Product Owner

• Manages the product backlog
  Organising, refining, and prioritising tasks to make sure the team knows what to work on next.

• Acts as the voice of the customer
  Representing user needs, business goals, and stakeholder input within every sprint.

• Defines acceptance criteria
  Ensuring that work is “done” to an agreed standard — which is more than just working code.

• Collaborates daily with the team
  The PO is always available to answer questions, resolve blockers, and help refine user stories.

• Owns sprint goals
  Works with the team to define realistic objectives and then guides delivery without micromanaging.

Product Owner vs Product Manager

While the Product Owner focuses more on the delivery side, the Product Manager focuses more on the strategic side.

In reality, I’ve often found myself toggling between the two roles — setting the product vision and then switching hats to prioritise the next sprint’s backlog or write acceptance criteria. Particularly during my time at Drinkstuff, I managed the backlog, led the eCommerce redesign, and directly supported the in-house development team with day-to-day decisions and feedback.

The PO Role in Resource-Constrained Teams

In lean teams, the Product Owner can be a lifeline. When I was the only product-facing person working with a single developer, backlog clarity and prioritisation were essential. We didn’t have time to waste, and the business expected visible outcomes every sprint.

I introduced techniques like structured user stories, consistent acceptance criteria, and “project” spikes to help our developer scope things clearly. We also used Jira and Trello to keep communication transparent for the business.

What Makes a Great Product Owner?

• Strong communication skills — able to listen, prioritise, and explain clearly
• A good understanding of Agile practices
• An eye for detail and a feel for user experience
• Empathy for both the business and the development team
• And above all: clarity and focus

Final Thoughts

I earned my Certified Scrum Product Owner (CSPO) certification in 2018, trained by Agile expert Mike Cohn, which helped solidify my foundation in Agile delivery and Scrum practices. The Product Owner might not always get the spotlight, but it’s a role that can make or break a team’s delivery. It’s not just about tickets in a backlog — it’s about making sure the right work gets done, at the right time, for the right reasons.

If you're looking to strengthen your delivery team or improve how your backlog is managed, I’d be happy to help. I’m Duncan Hann — a UK-based product professional with experience across Product Ownership, Product Management, UX, and Agile delivery in fast-paced environments.