Why Product Projections Fail (And What to Do Instead)

"Reduce churn by 1.5%."

That was the goal a product leader shared with me. One number. One projection. No range, no scenarios, no conditions under which that number might be wrong.

I asked: "What happens if you reduce churn by 0.8% instead?"

Dead silence. Nobody had thought about it. The entire roadmap — every feature, every sprint, every hiring decision — was built on a single point in space. And nobody had a plan for what to do if that point was wrong.

It was wrong.

Product Algebra Is Running Your Roadmap

Most product teams project the future the same way: take a current number, add a desired outcome, draw a straight line between the two.

"We're at 8% churn. We want 6.5%. Therefore, reduce churn 1.5%."

That's algebra. Input, operation, output. It feels rigorous. It looks great in a board deck. And it's almost always wrong.

I call this Product Algebra — the belief that product outcomes can be predicted with linear equations. It's comfortable. It's clean. And it's the enemy of good product thinking.

The problem isn't that the math is wrong. It's that the math is incomplete. A single-point projection tells you what you're hoping for. It tells you nothing about what's likely, what's possible, or what you'd do if reality disagrees.

Why Single-Point Projections Fail

Three reasons. Every time.

• They ignore variance. "Reduce churn 1.5%" treats all churn the same. But churn from bad onboarding is different from churn due to a competitor launch. The causes have different timelines, different costs to fix, and different probabilities. One number hides all of that.
• They create false confidence. A single number feels certain. Your board sees "1.5%" and plans around it. Your engineering team staffs for it. Your sales team prices around it. When the number's wrong, the entire system built on top of it is wrong too.
• They punish honest analysis. The PM who says "I think we can reduce churn somewhere between 0.5% and 2%, depending on three variables" sounds uncertain. The PM who says "1.5%" sounds confident. Your org rewards the second one — and they're both guessing.

So what? You can't just stop making projections. Your leadership needs numbers. Your investors need numbers. The business needs to plan.

You need better numbers.

Scenario Planning: Replace Prediction with Preparation

The fix isn't more accurate projections. It's multiple projections.

Scenario planning replaces "what will happen" with "what could happen — and what would we do in each case." Instead of one number, you build three:

• Base case: Your best estimate given current trends and known variables. This is what's likely if nothing unexpected happens. (Something unexpected always happens.)
• Upside case: What happens if two or three things go better than expected. Which investments would you accelerate? What would you double down on?
• Downside case: What happens if the market shifts, a key hire falls through, or a major customer churns. What would you cut? What would you protect?

The value isn't in predicting which scenario will play out. It never is. The value is in having a response ready for each one.

That team with the 1.5% churn goal? If they'd built three scenarios, they would've known exactly what to do when churn dropped only 0.8%. Instead, they spent two months debating whether the original goal was still achievable before anyone adjusted the roadmap. Two months of building toward a number that was already dead.

Three Red Flags Your Projections Are Failing You

How do you know your team is stuck in Product Algebra?

• One number, no range. "We'll grow revenue 20%" instead of "We expect 12-25%, depending on enterprise close rates." No range means no analysis — just aspiration wearing a spreadsheet.
• No trigger points. You haven't defined what happens if you're 50% off by mid-quarter. There's no survival metric that forces a conversation when things go sideways. You're flying with one engine and no parachute.
• The projection survives reality. It's March. Q1 is clearly off-track. And the original annual projection is still in every deck because changing it feels like admitting failure.

If any of these sound familiar, your team isn't planning. It's predicting. And prediction without preparation is the easiest way to look strategic while being fundamentally unreliable.

What Changes When You Use Scenarios

When you have scenarios, your roadmap reviews become decision points instead of status updates.

Instead of "are we on track?" the question becomes "which scenario are we in, and what does that mean for our next move?" That's a different conversation. The first one produces excuses. The second one produces decisions.

Here's what shifts:

• Resource allocation gets faster. You're not debating from scratch every time reality shifts. You've already thought through the options.
• Leadership conversations improve. Instead of presenting a number and hoping nobody asks hard questions, you present a range with clear decision criteria. That's the rigor executives actually trust.
• Teams stop feeling like failures. When the base case doesn't hit, it's not a failure — it's a scenario you planned for. The team shifts to the downside playbook and keeps moving.

Your planning process starts to look more like product discovery — informed by evidence instead of assumption.

Start Here

You don't need to redesign your planning process. Start with one change.

The next time someone presents a projection, ask: "What's the range?"

If there isn't one, send them back with a simple assignment: give me a base case, an upside, and a downside. For each, tell me what we'd do differently.

That one question shifts your team from prediction to preparation. From Product Algebra to Product Calculus. From false certainty to honest strategy.

Want to replace predictions with preparation?

In my Survival Metrics workshop, product teams build scenario plans and define tripwire metrics for every active initiative. A half-day session, built around your roadmap. The output: a decision framework that replaces "are we on track?" with "what's our next move?"

Book a Clarity Call — 30 minutes, no pitch. Just clarity on whether this is right for your team.

Not ready for a call? Subscribe to The Adam Thomas for frameworks and honest takes on product leadership, delivered biweekly.