Lessons Learned in Product Decisions

The challenge I usually face with product decisions isn’t having enough information, but it’s having the wrong relationship with uncertainty. I want decisions to feel certain, so I either delay until I have “enough” data (which never comes) or I pretend I’m more confident than I really am.

But I know that great product decisions embrace uncertainty rather than hiding from it.

Setting the Context

Product decisions matter more than ever because the pace of change has accelerated. You can’t wait for perfect information; by the time you have it, the market has moved. But you also can’t be reckless - resources are finite and mistakes are costly.

The teams that navigate this well have developed decision-making as a core competency. They’re not just smart about individual choices; they’re systematic about how choices get made.

This matters especially now because the cost of indecision has risen. Competitors move fast. User expectations shift. Being right slowly often loses to being roughly right quickly.

Putting It Into Practice

Implementation Tips

Classify decisions by reversibility: Not all decisions are equal. Reversible decisions (can undo or adjust later) deserve faster, lighter processes. Irreversible decisions (can’t easily undo, high switching costs) deserve more deliberation.

Most decisions are more reversible than they feel in the moment. Recognising this liberates faster action on decisions that don’t require extensive analysis.

Make decision rights explicit: Who decides what? Ambiguity about decision rights creates either endless discussion or unexpected vetoes. Document who owns different types of decisions and what input processes exist.

Time-box deliberation: Open-ended decision processes expand to fill available time. Set deadlines. “We’ll decide by Friday with whatever information we have” forces focus on what actually matters.

Document the decision and rationale: Writing down what you decided and why serves multiple purposes. It forces clarity of thinking. It enables learning from outcomes. It prevents revisiting the same debates.

Distinguish disagreement from misunderstanding: When people disagree, often they’re not actually talking about the same thing. Before debating, ensure shared understanding of the question, the options, and the criteria.

Measuring Success

How do you know if your decision-making is effective?

Decision velocity: Are decisions happening at appropriate speed? Too slow suggests excessive deliberation or unclear decision rights. Too fast might indicate insufficient consideration of important factors.

Decision quality: Do decisions lead to expected outcomes? Track predictions against results. This calibration improves future decision-making.

Team confidence: Do people feel confident in how decisions are made, even when they disagree with specific choices? Process legitimacy matters for execution.

Revisitation rate: How often are decisions reopened? Some revisiting is healthy as you learn. Constant revisiting suggests decisions aren’t sticking or initial analysis was poor.

“The best decision-makers I know are wrong fairly often. What makes them effective is that they decide quickly, learn quickly, and adjust quickly.”

A Practical Framework

Step-by-Step Approach

Here’s a framework for making product decisions well:

1. Frame the decision clearly

What exactly are you deciding? What are the options? What’s the timeframe? Fuzzy framing leads to fuzzy decisions.

Write down the question you’re answering. If you can’t state it clearly, you’re not ready to decide.

2. Identify what matters

What criteria should influence this decision? List them explicitly. Prioritise them—not everything matters equally.

Common criteria include user impact, business impact, effort required, risk level, strategic alignment, and opportunity cost.

3. Gather relevant information

Notice: relevant information, not complete information. Focus on what would actually change your decision. Ignore interesting-but-irrelevant data that consumes time without informing the choice.

Ask: “What information would make us choose differently?” Seek that specifically.

4. Consider multiple options

Avoid binary framing when possible. “Should we build Feature X?” is less useful than “What are our options for solving Problem Y?” Multiple options often reveal better choices than the first one considered.

5. Make the decision

Choose. Document the choice and the reasoning. Communicate it clearly to people who need to know.

The perfect option rarely exists. Choose the best available option with the information you have.

6. Commit and execute

Half-hearted execution of good decisions produces bad results. Once decided, commit. Save second-guessing for explicit retrospection moments, not daily doubt.

7. Learn and adapt

After decisions play out, review. What happened versus what you expected? Why? What does this teach you about future decisions?

Real Examples from Product Teams

A consumer app team was debating whether to rebuild their onboarding flow. The discussion had been going for months. Some people wanted comprehensive redesign; others wanted incremental improvement.

When we applied structure, the problem became clear. They’d been debating solutions without agreeing on the problem. Once we framed the question clearly - “How do we improve Day 7 retention by at least 10%?” - the discussion changed entirely.

They realised they didn’t need to choose between complete rebuild and incremental changes. They could run experiments to identify which onboarding elements mattered most, then invest proportionally.

The reframed decision was made in a week. The previous framing had generated months of inconclusive debate.

Understanding the Fundamentals

Core Concepts Explained

Decisions under uncertainty: All product decisions happen with incomplete information. The skill isn’t eliminating uncertainty but making good decisions despite it.

Asymmetric outcomes: Some decisions have asymmetric consequences—limited downside but significant upside, or vice versa. Recognising asymmetry enables appropriate risk-taking.

Opportunity cost: Choosing one option means not choosing others. The cost of a decision isn’t just what you spend; it’s also what you can’t do because resources are committed elsewhere.

Second-order effects: Decisions have consequences beyond their immediate effects. Good decision-makers consider these ripples, though not to the point of analysis paralysis.

Why This Matters for PMs

Product managers are decision-makers by definition. The quality of your decisions directly impacts product success.

But it’s not just about your decisions. You also shape how decisions happen across your team. The frameworks, norms, and processes you establish affect everyone’s decision quality.

Good PMs create environments where decisions happen well—where information flows appropriately, where people feel empowered to decide what they should decide, and where learning from decisions is normal.

Key Takeaways

Embrace uncertainty rather than waiting for certainty that never comes
Classify decisions by reversibility—most deserve faster, lighter processes than they get
Frame decisions clearly before deliberating; fuzzy framing leads to fuzzy outcomes
Document decisions and rationale to enable learning and prevent relitigating
Build decision quality as a team competency, not just an individual skill

Resources for Deeper Learning

The best way to improve at decisions is structured reflection. After significant decisions play out, review what you expected versus what happened. This feedback loop calibrates your judgment over time.

Discuss decisions with peers who have different perspectives. Diverse input surfaces considerations you might miss.

And practice deciding. Decision-making is a skill that improves with exercise. Don’t avoid decisions to avoid being wrong; embrace them as opportunities to learn and improve.

Have questions or thoughts? Get in touch - I’d love to hear from you!