Why good products fail

These days, while running and thinking about the next roadmap planning, I found myself wondering: Which items should make it onto the roadmap, and which ones are most likely to create real business impact?

I've been in product management for more than four years now, and I've seen quite a few products being launched.

Some succeeded. Others… not so much.

What made the difference?

Remember my previous article about roadmap preparation? Yep, the same principles still apply. But is there one extra ingredient that can make or break a product's success?

🧩 The missing piece in the roadmap

At this point, I have quite a few items assessed in my backlog. I look at their potential business impact, their impact on customer experience, feasibility, risks, why AI makes sense (or doesn't), and so on and so forth.

But what was missing?

That was the question bothering me. Until I had a moment of clarity in the field.

Of course. It's the people who make the difference.

When you've been working in the same company, team, and domain for a few years, you start to recognize patterns. You get a sense of which initiatives are likely to receive support and which ones might struggle to gain traction.

And sometimes, you learn this the hard way.

🎬 A real example from experience

There was a period when my team and I had to support a particular department in the organization I was working with AI solutions. As the product person, I had to identify opportunities for future improvement.

Feedback on the department's pain points was limited, but that's fine. Part of the job is to dig deeper, ask questions, and uncover opportunities.

So, what did the process look like?

I identified opportunities and assessed their potential impact. I held sessions with stakeholders to specify requirements. Implementation began, and we launched experiments.

So far, so good.

Here's where things got interesting.

Whether the experiments succeeded or failed, the results didn't seem to translate into much urgency or follow-through from the business side. The potential impact was clear on paper, but turning it into action proved more challenging than expected.

I tried speaking the language of business impact and financial value. Still, progress was slow.

One delay followed another, with dependencies and outstanding actions taking time to resolve. Quarter after quarter passed, and only a few experiments were launched, with limited business impact.

And then I started asking myself some uncomfortable questions.

💥 "If it weren't for me and the team bringing forward a new solution, could the stakeholder carry on with what they already had? " ...

💥 "Was there enough motivation and organizational readiness to change the existing way of working?"...

💥 "Was the stakeholder able to provide the support needed for the product to succeed?"...

💡 The realization: alignment isn't commitment

Suddenly, things became clearer.

The business rationale was there, but the level of ownership and urgency needed to move things forward wasn't consistently reflected in actions.

Maybe the problem wasn't the solution itself. Maybe the expected improvement wasn't compelling enough to justify changing established ways of working. Or perhaps other priorities, limited capacity, or organizational constraints made it difficult to give the initiative the attention it needed.

Whatever the reason, one thing became clear to me: having a business case doesn't automatically mean having a business that is ready to act on it.

So I changed my approach.

I became much more selective about the initiatives I pursued under these circumstances. Priorities became clearer, and I started paying closer attention to the level of commitment behind an opportunity—not just its potential value.

Because the business case alone isn't enough. The expected impact alone isn't enough, either.

You need a solid support system to push for change as much as you do. 

Of course, commitment doesn't mean that everything will go according to plan. Priorities change, unexpected obstacles emerge, and sometimes experiments fail. That's part of the process.

What matters is how we respond: Do we address the obstacles together? Do we revisit our assumptions? Do we take responsibility for the actions we've agreed on?

Because alignment is not the same as commitment.

Looking back, I also wonder whether I could have explored the readiness for change earlier, before investing so much effort in the solution. I learned that identifying an opportunity is only part of the job; understanding whether the organization is ready to act on it matters just as much. And that's something I now pay closer attention to.

🤝 What if you're already in this situation?

This might sound obvious, but if you've worked in a large corporation, you know these situations do happen.

If you feel trapped in something similar, I wouldn't necessarily recommend cutting the product or abandoning the initiative straight away. Before making that call, try a few less drastic approaches.

For example, I used to require explicit sign-offs in PRDs. I also shared meeting minutes in common communication channels, documenting the agreements reached during calls and the outstanding actions.

Not the most glamorous part of product management, I know. But sometimes, a little structure can save you a lot of frustration later.

I've also recently read The Communication Book: 44 Ideas for Better Conversations Every Day by Mikael Krogerus and Roman Tschäppeler. One concept that resonated with me was the importance of shared responsibility.

It reminded me of something worth reinforcing more often: you and your stakeholders are partners in this.

You're not simply there to deliver a solution, you should work as one team, with shared ownership of the outcome and clear responsibilities on both sides.

And that responsibility needs to be reflected in actions, not just in meeting notes or project kick-offs.

Of course, stakeholders have competing priorities, limited capacity, and their own organizational constraints. Sometimes, a lack of follow-through isn't about a lack of interest at all. It might be a sign that the initiative isn't sufficiently prioritized, that responsibilities aren't clear, or that the organization isn't ready to support the change.

That's precisely why it's important to make commitments explicit and revisit them when circumstances change.

Sometimes, the solution isn't to push harder. It's to have an honest conversation about whether the problem is important enough, whether the timing is right, and whether the people involved can realistically support the initiative.

And if the answer is no? That's valuable information, too.

It can help you reassess the opportunity, adjust your approach, or decide whether the initiative should remain on the roadmap.

🚀 So, when do products succeed?

To answer the question in the title, I'd say:

Products succeed when people care.

Not just when the numbers look good. Not just when the roadmap makes sense. And not just when everyone agrees that an idea sounds promising.

They succeed when people are willing and able to work together to turn that promise into reality.

At least, that's what my experience has taught me so far.

Now I'm curious: What's the key differentiator in your experience? What's the biggest challenge you face when trying to deliver real value?

Let's discuss! 👇