The Top 5 Qualities of a Good Product Owner — What Makes a Proven PO?

What are the qualities of a good product owner? It's one of the most common questions we get asked at Twenty2 Collective, and fair enough. The product owner role is one of the most misunderstood and underestimated in any organisation doing agile work. It's more than a job title. It's a leadership role, and becoming a great PO takes real effort over time.

Throughout my career I've been a product owner, coached product owners, and now I share what I've learned through the Proven Product Owner training course. During the course we find creative ways to let participants experience the five qualities I'll talk about today. So from my experience, here are the five qualities that make up a proven product owner.

1. A Clear Vision of the Future

Product owners need to see where their product is going and how to improve it. They need to know what the customer wants and needs, and what business goals they're trying to hit. I'll be honest, I used to think vision was something you wrote once on a slide deck and moved on. It's not. A strong product vision is something you keep returning to, sometimes weekly, sometimes daily when things get messy. It starts with a bold picture of where you're heading, but it shifts and sharpens as you and your team learn more. And sometimes it falls apart entirely and you have to rebuild it, which is uncomfortable but necessary.

If you've read any of our previous posts you'll know the importance we place on having a strong vision. A PO has to prioritise and delegate tasks according to that vision and the goals of the product. They also need to motivate and inspire their team. They're both visionary and task manager, so being able to do both is key. Without a clear destination, even the best agile team is just busy. Not effective.

We often talk about the value of roadmaps and outcome-based planning, and this ties directly back to the product owner's ability to hold and communicate that forward view.

2. Creativity and Confidence

I want to be careful here because I think people sometimes hear "creativity" and picture brainstorming sessions with sticky notes and marker pens. That's part of it, sure. But the creativity I'm talking about is more like the willingness to try a sideways approach when the obvious one isn't working, and frankly, the stubbornness to keep trying when the first three sideways approaches didn't work either.

What separates a good product owner from a great one is pairing that creative instinct with the confidence to stand behind a decision when it counts. Creative solutions aren't always possible, but creativity is a great tool when you're trying to solve complex problems. It helps you see things from a new perspective and makes your product strategy less predictable and more adaptable. In our Agile Renovation case study, creative thinking from the cross-functional team saved us on Day 3 when unforeseen issues appeared. That same mindset applies to product ownership every single day.

Now, confidence. This one is tricky because I've also seen confidence tip into stubbornness, and I've been guilty of that myself. A PO needs to envision success and know how to get there, but they also need to know when they're wrong. If you can't project confidence at all, you won't lead others with you or get them motivated around the goal you've set. Too much confidence and you stop listening. I don't have a clean formula for where the line sits. I think it moves depending on the team and the situation, and honestly that ambiguity still frustrates me.

3. Knowledge of Business Practices

This is one of the most important product owner skills because the PO is responsible for overseeing development of the product within a wider business context. For a product to succeed, it needs to be good business. Often the hardest part of being a product owner is understanding all of the different components that go into that. You need knowledge across areas such as:

• Marketing

• Sales

• Customer service

• Accounting and finance

• Market trends and the broader competitive environment

You need to know how your company makes money and how you can keep it going. This way you make sure your product doesn't lose money and vice versa. Knowing about your product alone isn't enough. You need to understand the other parts of the company too, which makes you a well-rounded product owner.

I should say, though, that this is where I've seen a lot of product owners quietly struggle, and where I've struggled too. Nobody walks into the role understanding finance, marketing, customer support, and market positioning all at once. You fake it for a while. You ask questions that feel embarrassingly basic. I remember sitting in a finance review meeting early in my career, nodding along at terms I didn't fully understand, and then spending the evening Googling half of what was discussed. That's just the reality of it. As we often say, agile is not the goal. The goal is business outcomes. A PO who understands the business can make sound decisions about customer feedback, strategy, and where to invest the team's limited capacity. But getting to that understanding takes time, and there are no shortcuts I've found that actually work.

4. Superior Communication Skills

Communication is the foundation of understanding within your team. We often joke about the three C's: communicate, communicate, communicate. The product owner leads discussions, makes decisions, and most importantly explains what needs to be done and why it matters.

Product owners need to communicate effectively with their customers, partners, stakeholders, and team members. This includes articulating goals in a way that actually lands with each audience, which is harder than it sounds because what makes sense to a developer often means nothing to a sales director, and vice versa. A PO needs to present an idea so everyone involved understands it. If they can't convey their vision in a way that connects with all members of their team, they can't do their job properly.

In our experience coaching teams, we've seen how poor stakeholder communication erodes trust. One operations manager once told me, "I know they are working as I am seeing things presented each week, I know I am being consulted often for my input to their plan, but I will be darned if I know what I am getting by Christmas." That quote still sticks with me because it's such a clear example of a gap that the PO probably didn't even realise existed. That gap is the product owner's responsibility to close, with tools like roadmaps, regular reviews, and clear outcome-based language.

I'll add something that might be slightly controversial. I think many POs over-communicate in one direction, usually upward to stakeholders, and under-communicate in the other, toward their delivery team. I've caught myself doing this. You get so focused on managing expectations at the leadership level that you forget the people building the thing also need context and motivation. I don't think I've fully solved that imbalance in my own practice, if I'm being honest.

5. The Ability to Assess Different Viewpoints

A great product owner can assess situations from different points of view. They need strong emotional intelligence to listen to multiple needs and wants, then translate these into the highest-value goals the team will work towards within their limited capacity.

Product owners must assess different perspectives to make the best decisions for the business. They need to see things from both team and customer perspectives while also considering how their decisions affect stakeholders. We use techniques like personas in our training to build empathy and help product owners step into the shoes of the people they're solving for.

A great product owner balances all these factors and still gets the job done. They listen deeply, take everything they've heard, make sense of the contradictions, and then make a call. Sometimes the wrong call. That's the part nobody likes to talk about. You can listen perfectly, weigh every perspective with genuine care, and still choose wrong. It takes courage and empathy and a lot of practice, but even with all three you'll occasionally get it wrong, and you have to be okay with that. Or at least okay enough to keep going.

Product Ownership is a Capability, Not Just a Role

I see product ownership as a capability that needs maturing in many organisations I work with. Too often companies assign the PO title without investing in the skills, coaching, and support the person needs to succeed. The Scrum Guide outlines the accountabilities, but building a truly effective product owner takes intentional, sustained growth across all five of these qualities. That growth isn't linear, either. I've seen experienced POs plateau or even regress when they switch organisations or product domains, and it can be demoralising. It doesn't mean they've lost the capability. It just means the context changed and they need to rebuild parts of it.

Whether you're stepping into the role for the first time or looking to sharpen your product owner competencies, the work never stops. The best POs we work with keep learning and keep listening. But I'd be lying if I said they never lose sight of the outcome. They do. Everyone does at some point. The ones who stand out find their way back, usually because someone on their team or a coach pulls them aside and asks the uncomfortable question. That's not a tidy conclusion, I know. But product ownership isn't tidy.

Frequently Asked Questions

What does a product owner actually do day to day?

A product owner is responsible for maximising the value of the product. Day to day this includes maintaining and prioritising the product backlog, talking to stakeholders and customers to understand their needs, working closely with the development team, and deciding what to build next based on the highest value outcomes. Some days it's very strategic, you're thinking about where the product needs to be in six months. Other days it's entirely tactical, you're clarifying acceptance criteria or unblocking someone on the team. It shifts constantly, and honestly some days you feel like you're doing neither well.

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

This one comes up a lot, and the honest answer is: it depends on the organisation. A product owner typically works more closely with the delivery team within an agile framework, focusing on backlog prioritisation and sprint-level decisions. A product manager often has a broader strategic remit across market positioning, pricing, and go-to-market strategy. In many organisations the roles overlap significantly, and I've worked in places where the distinction was essentially meaningless. The qualities we describe above apply equally to both, though I think product managers tend to spend more time in the business knowledge space and product owners more in the team communication space. But that's a generalisation and there are plenty of exceptions.

Can someone without a technical background be a good product owner?

Yes. Some of the best POs we've coached come from marketing, operations, or customer service backgrounds. While technical understanding can help, I'd actually argue it sometimes gets in the way, because technically minded POs can fall into the trap of solutioning with the development team instead of focusing on the problem and the value. The most important qualities of a good product owner are vision, communication, business knowledge, creativity, and empathy. What matters most is the ability to understand customer needs and translate them into clear priorities for the team. That said, you will hit moments where a lack of technical knowledge slows you down or makes you feel out of your depth. That's normal. It doesn't disqualify you.

How can I develop my product owner skills?

Start by investing in formal training such as the Proven Product Owner course where you can practise these five qualities in a safe, hands-on environment. Beyond that, seek coaching, ask for feedback from your team and stakeholders, and study how high-performing POs operate. I'd also say, and this might sound odd, pay attention to where you feel most uncomfortable in your role. That discomfort is usually pointing at the skill you most need to develop. Product ownership is ongoing work, not a box to tick, and there's no point at which you're simply "done" learning.

Why is emotional intelligence important for a product owner?

Product owners sit between multiple perspectives: customers, stakeholders, leadership, and the delivery team. Emotional intelligence allows the PO to listen actively, manage competing demands with empathy, and build the trust needed to make tough prioritisation decisions. Without it, even the most technically skilled PO will struggle to bring people along. I will say, though, that emotional intelligence is one of those things that's much easier to talk about than to practise under pressure. When a stakeholder is frustrated because their feature got deprioritised, or the team is exhausted and pushing back, your emotional intelligence gets tested in ways that no training course can fully prepare you for. It matters enormously. It's also really hard.

Ready to Build Your Product Owner Capability?

If you're a product owner looking to sharpen your skills, or a leader wanting to invest in your PO capability, we'd love to help. Our Proven Product Owner training course gives participants a hands-on experience of these five qualities in a practical, engaging environment. Reach out to us at Twenty2 Collective or book a complimentary 30-minute coaching call to chat about how we can support you.