One of the clearest signs that a product organization is losing discipline is the size of its backlog.
Leaders often treat a deep backlog as evidence of strategic depth. In practice, it is usually the opposite. It is a storage unit for ideas the team is unlikely to act on, a source of false certainty, and a subtle way to avoid making hard prioritization decisions.
That is why I like the three sprint rule: only maintain a real, actively managed commitment window for the next three sprints. Everything beyond that should be lightweight context, not treated as planned work.
Why Three Sprints Works
Three sprints is long enough to build something real and short enough to stay honest.
Within that window, teams can align design, research, engineering, QA, messaging, and customer expectations around a common delivery rhythm. Outside that window, the value of detailed planning drops quickly because customer signal changes, markets move, dependencies shift, and yesterday's priorities stop being relevant.
The practical advantages are straightforward:
- customer feedback gets incorporated before the team hardens weak assumptions,
- backlog sprawl becomes harder to justify,
- sunk-cost bias is reduced because less speculative work gets over-groomed,
- and morale improves because the team is working against a believable horizon.
What This Looks Like in Practice
The rule is not just "plan less." It is a way of structuring execution.
The first discipline is to keep the real backlog focused on the next three sprints only. Beyond that, future ideas can sit in an idea bank, but they should not consume the team's detailed planning energy.
The second discipline is scope. Major features should be shaped so the MVP can land inside that three-sprint window. If the work is too large to do that, then the team is probably carrying too much complexity into the first cut.
The third discipline is stage design. In a healthy cadence, the first sprint in the window is often where design leads and engineering resolves research spikes. The second sprint lays foundations and gets the basic value path working. The third sprint tightens, tests, and prepares the feature for actual customer use.
That pattern will vary by team, but the operating principle is the same: the window should produce usable progress, not abstract momentum.
Why This Matters to Operators and Boards
For product leaders, the three sprint rule is a delivery discipline. For operators and investors, it is also a diagnostic.
If a team cannot explain what is truly committed in the next six weeks, it is usually signaling one of three problems:
- priorities are unstable,
- the roadmap is carrying too much fiction,
- or the operating cadence is weaker than leadership thinks.
Short commitment windows do not make teams less strategic. They make them more credible. Strategy lives in how choices get updated as reality changes, not in how many future tickets fit on a board.
The Simpler Test
If an item has been sitting in the backlog for months without moving meaningfully closer to execution, it is probably not a priority. Archive it. Remove it. Let the backlog represent real intent instead of accumulated guilt.
That is the value of the rule. It creates focus, preserves adaptability, and gives the team a cadence they can actually believe.