You can be humble now, or be humbled later.
How High Failure Rates Shaped Best Practise
Most product ideas fail. Not because your team aren’t smart and not because your team don’t care. They fail because it’s normal for them to fail. Marty Cagan famously declared that at least three-quarters of the ideas product teams build don’t pan out as expected. Alberto Savoia puts it more bluntly: most new products fail in the market, even when competently executed. Controlled experiments tell a similar story; an overwhelming proportion of ideas do not move the metric they were designed to improve. Some do nothing. Some make things worse. It’s a humbling reality. In product development, failure is the baseline. Failure is the expected result.
It’s a common mistake to treat the best idea in the room as though it’s likely to work. Before you know it, it has momentum and the team are invested in shipping it. The market, though, doesn’t care whether it beat a hundred other ideas, who sponsored it, or how elegant the logic was. Not knowing anything about the idea being discussed in your room, the outside view would probably rate its chances lower than you do. Not because your idea is bad. Because the base rate is. Expect the market to react with cold indifference. Better product judgement starts with knowing most ideas miss.
In an unforgiving environment where most ideas fail, the right mindset is one of intellectual humility. You need to be curious. When you accept that you are probably wrong more often than you feel, something shifts in how you work. You stop treating your current idea as a conclusion and start treating it as a hypothesis. You stop asking “how do we build this?” and start asking “how do we find out if we should?” You get curious about the ways you might be mistaken rather than defensive about the ways you might be right. That shift from conviction to inquiry is humility in practice. You need the willingness to ask: What has to be true for this to work? Where might we be wrong? What evidence would change our mind? How can we learn that before spending too long building the wrong thing?
Evidence that humility matters is embedded in the discipline itself. Product development is an arena where the odds are often poor, the signals are ambiguous, and failure is common. That has forged many of our modern best practices. They didn’t emerge from first principles but from repeated contact with failure.
Outcomes over outputs, because we learnt shipping is not proof of success.
Continuous discovery, because we learnt customer behaviour is hard to predict.
Small, frequent releases, because we learnt large releases can become expensive failures.
Iteration, because we learnt the first version is rarely good enough.
Assumption testing, because we learnt our beliefs often do not survive contact with reality.
Problems over solutions, because we learnt we are bad at predicting what will work.
These practices are scar tissue. Humility made structural. Forged by failure the way floodwater shapes a landscape. Over time, the practices that depended on certainty were washed away. The ones that survived are those that help teams learn faster, commit later, and recover when reality disagrees with the plan.
Don’t mistake the fact that humility is necessary to mean that confidence isn’t required. Being timid is problematic. You can’t hide behind uncertainty, always waiting for more information. The best product managers are ambitious, act with conviction, and move at pace. They still need to make calls with incomplete information. They still need to persuade teams to move toward uncertain futures. The difference is that humble product managers place better bets. They want the outcome more than they want to be right. They know confidence alone is dangerous. Confidence without curiosity becomes stubbornness. Act with humility: be bold about the problem, ambitious about the outcome, and humble about the solution.
You can’t be right every time, but you can increase the odds. Moving a product team from a 25% to a 40% hit rate is enormously valuable. Ask sharper questions, place smaller bets, gather better evidence, get faster feedback, and have the discipline to adapt when the world pushes back.
Failure isn’t an edge case in product work. It’s the norm. So you have a choice. You can adopt humility before the market forces it on you. You can let market reality change how you think, how you plan, how you test, and how you lead. Or you can take your chances.
You can be humble now, or be humbled later.