Next Move: How to Formulate a 'Next Bet' and Ensure Its Verifiability
A detailed guide on formulating a 'Next Bet'—the single next verifiable move that should result from the Iterate phase, with clear hypotheses, bets, and expected signals.
Next Move: How to Formulate a 'Next Bet' and Ensure Its Verifiability
The Iterate phase is when the team turns findings from Evaluate into the next step. But this is precisely where a trap lies: Iterate can easily turn into a chaotic list of "improvements" that disperses focus and doesn't guarantee learning.
To avoid this, the PTOS methodology uses the concept of "One Next Move" (Next Bet).
Fundamental Principle
An iteration is the next verifiable decision, not "more work."
You are not making a "list of improvements for the quarter," but one next bet that has a clear goal and a cost of error.
What is a 'Next Bet'?
A Next Bet is the minimal change that, according to your hypothesis, can significantly shift user behavior. It always has three components:
1. Hypothesis: What should become true in user behavior (not in their opinion).
- Example: "If we simplify the report form to one click, the percentage of users creating a report in their first session will increase."
2. Bet: The minimal change that can confirm or refute the hypothesis.
- Example: "We are not redesigning the entire editor, but only adding a 'Create Standard Report' button and observing its
adoption."
3. Expected Signal: What exactly we will see in the data (or in qualitative feedback) within a defined time window to make a decision.
- Example: "Within 14 days, we expect more than 20% of new users to use this button, and it will not lead to an increase in support requests."
Honesty Rule: An Iteration Must Have a Chance to "Die"
If your "next bet" cannot fail because the success criteria are vague ("it will get better," "usability will improve"), then it's not a Next Bet. It's "eternal work" that will consume resources without yielding measurable results.
Clear Success/Fail/Grey thresholds, defined before the start, are a mandatory condition.
Why Only One Next Move?
Focusing on one bet is critically important:
- Signal Clarity: If you make three changes simultaneously, you will never know which one worked (or broke everything).
- Learning Speed: Small, focused bets allow for faster cycles through the
Product Loopand quicker learning. - Focus Protection: This forces the team to choose what's most important, rather than spreading themselves thin on "cosmetic" improvements.
Connection to the Stop-doing list
Every Next Bet must be accompanied by a Stop-doing list—a list of things the team stops doing.
- "We stop supporting the old, complex flow."
- "We stop promising clients a feature we've abandoned."
- "We stop looking at noisy metrics that distract us."
The Stop-doing list frees up resources and mental energy for the new bet.
Conclusion
Stop thinking of Iterate as "tweaking." Think of it as a series of conscious, verifiable bets.
Bad iteration: "Let's improve the report interface."
Good iteration (Next Bet): "Our hypothesis is that users don't create reports due to complexity. Our bet is to add a 'one-click report' button. We will consider it successful if the signal (conversion to report creation) increases by 15% in 2 weeks without an increase in support load."
This approach transforms chaos into a managed process and ensures that each iteration makes your product not just "different," but truly "better."