Estimates VS finishing
Many teams try to become predictable by getting better at estimates. Another approach is to become predictable by getting better at finishing.
This page compares the two approaches as trade-offs — not as a debate. The goal is to help you choose what improves clarity and outcomes in your environment.
If you already have an account: sign in.
Approach A: predict by estimating
Estimating tries to create predictability by forecasting effort and timelines up front. It can be useful when work is repeatable and uncertainty is low.
- Optimizes for: upfront alignment, planning around dates, reporting.
- Costs: time spent forecasting, negotiation pressure, and false certainty when uncertainty is high.
- Failure mode: teams spend energy defending numbers instead of reducing uncertainty and finishing.
Approach B: predict by finishing
Finishing tries to create predictability by strengthening the system that moves work to done: clear outcomes, small slices, low WIP, visible ownership, and fast feedback.
- Optimizes for: flow, adaptability, reliable progress signals.
- Costs: requires discipline around WIP, clarity, and decision-making.
- Failure mode: if work stays large and ambiguous, “finish more” becomes pressure instead of clarity.
What “predictable” actually means
In practice, predictability is the ability to answer “what will finish next?” with confidence. That confidence comes from finish rate, clarity, and low WIP — not from better guesses.
If you need a single metric: measure how often work moves to done and how long items stay stuck in progress. That tells you more than estimate accuracy.
A simple decision guide
Leaning on estimates helps when…
- the work is repeatable and uncertainty is low
- you must plan around fixed dates/contracts
- stakeholders require forecast-based reporting
Leaning on finishing helps when…
- uncertainty is high and priorities change
- you want calm planning and fewer ceremonies
- you want progress to be visible through done
If you want predictability through finishing
- Make “done” unambiguous. Define outcomes and acceptance.
- Reduce parallel work. Lower WIP makes finishing possible.
- Slice smaller. Reduce scope until work can finish.
- Use ownership. Make the finish line someone’s responsibility.
- Keep ideas separate. Protect active work from constant churn.
Related: Finish work, Work in progress, No estimates.