Signs You’re Failing as a Product Owner: How to Take Control and Deliver Real Value

Published on
3 minute read

As a product owner, I often reflect on what failure truly looks like in our role. It’s a topic that resonates deeply with me, and I believe it’s essential for anyone in this position to understand the signs of a failing product owner.

Recognising the Signs of Failure

From my experience, failure as a product owner can be quite quantifiable. Here are some key indicators that suggest we might not be hitting the mark:

  • Poor Quality or Low Value: If the product we’re delivering lacks quality or fails to provide value, it’s a clear sign that something is amiss. A product that doesn’t meet user needs or expectations is a reflection of our inability to guide its development effectively.

  • Inconsistent Delivery: When delivery timelines are erratic, it often points to a lack of control over the product’s evolution. As product owners, we should strive for consistency, ensuring that our teams are aligned and focused on delivering value regularly.

  • Requirement-Driven Mindset: If I find myself merely writing requirements and taking orders from others, I know I’m not fulfilling my role. A product owner should be actively involved in shaping the product, not just documenting what others want.

  • Lack of Vision: If team members or stakeholders can’t articulate the product vision, we’re failing. It’s crucial that everyone involved understands what we’re trying to achieve. If the vision is buried in a wiki and not communicated effectively, we’re missing the mark.

  • Inability to Influence Direction: While it may not be an outright failure, if I’m not able to influence the product’s direction based on market understanding, it’s a sign that I need to step up my game. A product owner must be in tune with the market and able to steer the product accordingly.

Taking Ownership

One of the most critical aspects of being a successful product owner is taking ownership of the product. This means:

  • Making Decisions: We need to be the ones making decisions about the product, taking calculated risks, and managing the budget. It’s our responsibility to ensure that the product aligns with both user needs and business goals.

  • Focusing on Reality Over Perception: It’s easy to get caught up in vanity metrics—those numbers that look good on paper but don’t reflect the true state of the product. For instance, a burn down chart might show progress, but if the product is still lacking in quality, what does that really tell us?

  • Understanding the Bigger Picture: I often think of Satya Nadella’s decision to write down eight billion dollars for Nokia. That was a moment of clarity, recognising the reality of the situation rather than clinging to the hope of success. As product owners, we must be willing to make tough decisions when necessary.

Conclusion

In summary, a failing product owner can be identified by poor product quality, inconsistent delivery, a lack of vision, and an inability to take ownership. It’s vital that we focus on delivering real value rather than getting lost in metrics that merely serve to make us look good.

If you’re in a product owner role, I encourage you to reflect on these points. Are you truly owning your product? Are you delivering value? If you’d like to discuss this further or share your experiences, I’d love to chat. Feel free to book a coffee with me through Naked Agility.

Thank you for reading, and I look forward to your thoughts!

What does failure look like for a product owner? Um, I think it’s very quantifiable what failure looks like for a product owner. Um, if you see a product that has poor quality or low value, inconsistent delivery, probably a sign of a failing product owner. Um, if the product owner is sitting there just writing the requirements, I’m not doing much else, they’re just writing the requirements, perhaps ordering them, but they’re taking orders from somebody else, that’s probably a failing product owner.

If you ask people in the organisation or even on the team what is the vision of the product, what is it that we’re trying to achieve, and they don’t have an answer or say, “Well, that sits on the wiki,” right? If people don’t intrinsically know what that is, then we’re probably failing as a product owner. Um, if we’re, as the product owner, not in control of the evolution and direction of the product, um, I maybe wouldn’t put that in the absolute failing category, but we’re definitely not doing very well as a product owner if we’re not able to influence and control the direction of the product based on our understanding of the market, right? That’s something that we really do need to be able to do.

Um, not taking actual ownership of the product—this is our product, we’re building this product, we are making decisions, we’re taking the risks, we’re spending the money. It needs to be our product, so taking that ownership of that is really important. Um, and if it’s all about perception over reality, then that’s definitely a failing product owner.

Um, do we want the numbers to look good, or do we want to actually deliver value in the product, which brings in more revenue, brings in more capability to the organisation? Um, there’s a lot of focus on vanity metrics in the industry, and metrics, if you don’t know that expression, are metrics that just make us look good, like a burn down being on the line, right? So what does that actually tell us about the product? Can you be on that line and things still suck? Yes, of course you can.

So let’s focus on vanity metrics more on the reality of the product, what’s going on, what we need to do. Like, uh, Satya, um, writing down eight billion dollars for Nokia—that’s looking at the reality of the situation, um, and understanding it, rather than reaching for fairies and magic that we’re going to be successful with this. No, we’re done; we need to cut our losses on that.

That’s what being a product owner— that’s what a failing product owner looks like, right? Thanks for watching the video. If you enjoyed it, please like, follow, and subscribe. I always reply to comments, and if you want to have a chat about this or anything else, Agile, Scrum, or DevOps, then please book a coffee with me through Naked Agility.

Product Owner People and Process Agile Product Management Accountability Agile Project Management Pragmatic Thinking

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Cognizant Microsoft Business Group (MBG) Logo
Graham & Brown Logo
Qualco Logo

CR2

MacDonald Humfrey (Automation) Ltd. Logo
Slaughter and May Logo
Emerson Process Management Logo
ProgramUtvikling Logo
New Signature Logo
Milliman Logo

NIT A/S

Slicedbread Logo
Capita Secure Information Solutions Ltd Logo
Microsoft Logo
Flowmaster (a Mentor Graphics Company) Logo
Genus Breeding Ltd Logo
Big Data for Humans Logo
Deliotte Logo
New Hampshire Supreme Court Logo
Ghana Police Service Logo
Nottingham County Council Logo
Washington Department of Enterprise Services Logo
Department of Work and Pensions (UK) Logo
Washington Department of Transport Logo
Slicedbread Logo
Lockheed Martin Logo
Epic Games Logo
Boeing Logo
Akaditi Logo
ALS Life Sciences Logo