The Expected Value Framework For Choosing What To Test Next

When my experiment backlog gets long, my decision quality drops fast. Everything looks “important,” every stakeholder has a favorite, and the loudest idea starts to win.

That’s when I fall back on the expected value framework. Not because it’s fancy, but because it forces one thing: dollars first, opinions second.

If you’re a founder or product owner under pressure, you don’t need more ideas. You need a clean way to pick the next test that’s most likely to pay for itself, while keeping risk under control.

Why expected value beats “high impact” scoring in real life

!A mid-30s male product leader sits thoughtfully at a modern wooden desk in a bright home office with natural daylight, laptop open to an analytics dashboard, notebook with ideas, and coffee mug nearby.

Most A/B testing prioritization breaks because it hides the real tradeoff. We pretend we’re ranking “impact,” but we’re actually choosing how to spend scarce time under uncertainty.

Expected value fixes that. It functions as a superior prioritization framework compared to the PIE model, ICE scoring model, or PXL framework by providing a calculation for return on investment in experimentation, treating it like any other investment decision:

• There’s a possible upside (lift toward business goals).
• There’s a chance it works (probability).
• There’s a cost (time, engineering, coordination, opportunity cost).
• There’s risk (brand damage, revenue volatility, support load, pricing confusion).

This is plain decision making under uncertainty. It’s also aligned with behavioral science: humans overweight vivid stories and recent wins, and we anchor on “big ideas.” EV pushes you back toward base rates and math.

It’s especially useful in startup growth because your constraints are tighter. You can’t run ten tests to find one winner. You often get one shot per sprint.

One more reason I like EV: it keeps teams honest about what “impact” means. A 2% lift sounds small until you convert it into dollars per week. Meanwhile, a “big redesign” can look exciting and still have negative EV once you price in cost and risk.

If you can’t explain why a test is worth running in dollars, you’re not prioritizing. You’re hoping.

How I calculate expected value for A/B testing (in dollars)

!Clean, minimal high-contrast table diagram illustrating an Expected Value (EV) framework for prioritizing A/B tests like pricing, onboarding, and win-back emails, with columns for probability, lift, value, cost, risk, and net EV ranking.

Here’s the core model I use:

EV = p × lift × value − cost − risk

I keep it simple on purpose. This model excels in A/B testing and conversion rate optimization. If the model gets too detailed, nobody trusts it, and it stops being used.

Step 1: Define “value” as a real unit for expected value calculation

Pick the unit that connects to cash:

• For checkout tests: value = gross profit per order.
• For activation tests in product-led growth: value = expected gross profit per activated user (often activation-to-paid × LTV margin).
• For win-back: value = expected margin per reactivated customer.

If attribution is messy, I still choose a unit. Imperfect beats imaginary.

Step 2: Estimate lift and probability like an operator, not a pundit

I start with analytics and back-of-the-envelope math:

• What metric will move (activation, purchase, retention)?
• How many users hit that step weekly?
• What’s the plausible lift range, given past tests?

Then I set p, the probability of occurrence for the test delivering potential for improvement, not “any lift.” If your bar is +1% and you can’t detect that reliably, your p is lower than you think.

Applied AI can help here, but only as an assistant in modern AI product management. I’ll use a model to summarize similar past experiments, cluster user feedback themes, or extract patterns from session notes. I won’t let it invent probabilities. The base rate has to come from your history.

To make this concrete, here’s a lightweight example table I’d actually use in conversion rate optimization planning:

The takeaway is not the exact numbers. The point is that EV turns fuzzy debates into comparable expected profit bets.

Where the expected value framework fails (and how I guardrail it)

EV can still push you into bad calls if you ignore time, error costs, and second-order effects.

Trap 1: Chasing “lift” while ignoring error cost

If you run lots of A/B testing, false positives and false negatives will happen. Some teams celebrate a winner, ship it after threshold optimization, and then wonder why revenue didn’t move.

I like decision-theoretic thinking here, where you weigh benefits against the cost of being wrong. The research on ranking A/B tests by cost-benefit matches what I’ve seen in practice: you should care about profit, not just statistical significance.

Guardrail: I utilize a cost-benefit matrix for risk mitigation by charging a “risk tax” on tests with high downside. Pricing, trust, and anything that touches billing gets one.

Trap 2: Ignoring time-to-learn

A high-EV test that takes six weeks might lose to a medium-EV test you can run this week. Speed matters because it enables sequential decision-making that compounds. The best growth strategy is often the one that increases learning velocity without burning credibility.

Guardrail: I treat “cost” as fully loaded. Engineering time, QA, analytics instrumentation, and review cycles all count.

Trap 3: Letting the model override strategy

Sometimes you run a test because you need to learn something structural. For example, you may need to validate willingness to pay, even if short-term EV looks mediocre. That’s fine, just label it as a learning bet, not a revenue bet. I use a decision tree to map out learning versus revenue paths.

If you want a practical view on building an experimentation program that doesn’t drown in process, I generally agree with the emphasis on cadence and alignment in this A/B testing strategy guide.

Guardrail: I keep two lanes, “cash EV” and “strategic learning,” and I don’t mix them.

Trap 4: Not writing down what you learned

EV gets better only if your probabilities improve over time. That means documentation that’s easy to maintain, where you can apply sensitivity analysis to see how changes in variables affect past outcomes. Otherwise, every quarter starts from zero.

I’ve borrowed a lot from lightweight learning logs like this experiment documentation approach, because it focuses on reusable insights, not pretty decks.

My weekly decision rule (use this on your next sprint)

I don’t overthink it. Each Monday, I do this, incorporating learning from past results akin to reinforcement learning, where past winners act as an eligibility trace for future bets:

1. List 5 to 10 test candidates with a clear primary metric tied to conversion or retention.
2. Put a dollar value on the unit, even if it’s rough.
3. Assign p, expected lift, and model confidence scores from your base rates.
4. Subtract full cost and add a risk tax when downside is asymmetric.
5. Run the top Net EV test that fits your current constraints.

Then I ask one last question: if this test fails, will I still be glad we ran it? If the answer is no, the EV math is missing something. This question helps distinguish between true positives and true negatives in your experimental history.

In the end, the expected value framework is just a discipline. It keeps you from spending your scarcest resource, team attention, on the wrong bet.