The Estimation Lie: Why Every Deadline Is a Guess

There is a number that appears on every project and is believed by almost no one: the estimate. The estimate is the promise of the future, the number that the team produces, the number that the manager defends, the number that the customer expects. And the estimate is, almost always, a guess wearing a costume. The costume is the precision: the date, the hour, the confidence, the plan. The reality is the uncertainty: the unknown, the hidden, the discovered, the surprising. The estimation lie is not the lie of the people, it is the lie of the process: the process that pretends the guess is a fact.

The lie is not the problem, the pretending is. The guess is the honest starting point: the team that knows what it knows, what it does not know, and how unsure it is, has the real information. The pretending is the corruption: the guess that is dressed as the fact, the uncertainty that is hidden, the risk that is buried. The project is then managed against the false number, and the false number is the foundation of the false plan. The plan fails, the team is blamed, the estimate is distrusted, and the cycle repeats. The cycle is the estimation lie, and the breaking of the cycle is the skill.

1. The Estimate Is Not a Promise

The first correction is the category: the estimate is not a promise. The promise is the commitment, the statement of what will happen, the basis of the contract. The estimate is the prediction, the statement of what is likely, the basis of the planning. The confusion of the categories is the root of the lie: the estimate that is treated as the promise becomes the false commitment, and the false commitment is the trap. The team that promises the estimate is the team that is doomed, because the estimate was never a promise.

The correction is the language: the estimate is expressed with the uncertainty, the range, the confidence. The team that says the work is between two and four weeks, with the confidence of eighty percent, is the team that is telling the truth. The team that says the work is three weeks, exactly, is the team that is guessing. The truthful language is the foundation: the range, the confidence, the reasoning. The language is the difference between the guess that is hidden and the guess that is honest.

2. The Units of the Guess

The estimate has the units, and the units are the second correction. The estimate in the hours is the false precision: the hour suggests the accuracy that the work cannot have. The estimate in the size, the complexity, the uncertainty, is the honest precision: the size is the comparison, the complexity is the judgment, the uncertainty is the admission. The units of the guess are the choice, and the choice is the honesty.

The estimation in the sizes is the practice of the teams that estimate well: the small, the medium, the large, the unknown. The sizes are the buckets, and the buckets are the admission that the work is not measurable in the exact units. The sizes are compared to the known work, and the comparison is the calibration: the team that estimates the size of the new work against the size of the old work is the team that learns its own accuracy. The learning is the loop, and the loop is the improvement of the guessing.

3. The Uncertainty Is the Content

The uncertainty is not the failure of the estimate, it is the content of it. The unknown is the information: the part of the work that is not yet understood, the dependency that is not yet known, the requirement that is not yet clear. The uncertainty is the real subject of the planning, and the planning that ignores it is the planning that is blind. The estimate that does not mention the uncertainty is the estimate that hides the risk, and the hidden risk is the risk that lands.

The honest estimate names the uncertainty: the assumption that is made, the unknown that is pending, the risk that is carried. The naming is the visibility, and the visibility is the management: the risk that is named can be watched, and the watched risk can be retired. The uncertainty is the inventory of the future work, and the inventory is the plan: the plan that includes the exploration, the prototyping, the learning, is the plan that matches the reality of the creative work. The uncertainty is the content, and the content is the plan.

4. The Cone of Uncertainty

The estimates have the shape, and the shape is the cone. The cone of uncertainty is the funnel of the project: the estimate at the beginning is the wide end, the guess that is broad and vague; the estimate at the end is the narrow end, the guess that is precise because the work is done. The cone is the natural shape of the knowledge: the early project knows little, the late project knows much, and the estimate should reflect the knowing. The cone is the antidote to the false precision of the early date.

The cone also explains the failures: the estimate that is made early and treated as the promise is the estimate that is guaranteed to be wrong, because the early estimate is the wide guess. The project that is managed against the early number is the project that is managed against the wrong number. The correction is the re-estimation: the estimate that is revised as the knowledge grows, the plan that is updated with the learning. The re-estimation is the honesty, and the honesty is the survival.

5. The Anchoring Effect

The estimates are distorted by the psychology, and the psychology is the anchoring. The anchor is the first number: the customer's budget, the manager's hope, the previous project's date. The anchor pulls the estimate toward it, and the pull is the distortion: the team that knows the number is the team that estimates toward the number. The anchoring is the unconscious, and the unconscious is the enemy of the honest estimate.

The defense against the anchor is the process: the estimate that is built from the work, not from the number; the estimate that is built by the people who will do the work; the estimate that is built without the knowledge of the anchor. The defense is the structure: the estimate that is decomposed, bottom-up, from the actual tasks, is the estimate that is anchored in the work. The process is the protection, and the protection is the accuracy: the team that estimates from the work is the team that estimates the work, not the hope.

6. The Comparison Is the Best Tool

The best tool for the estimation is the comparison, and the comparison is the memory. The team that has done the similar work before is the team that can estimate the similar work again: the past is the best predictor, and the predictor is the memory. The comparison is the calibration: the project that took six weeks last time is the project that will take about six weeks this time, with the adjustments. The comparison is the honesty of the history, and the history is the evidence.

The comparison requires the record, and the record is the discipline: the estimates that are saved, the actuals that are measured, the variance that is studied. The record is the team's own data, and the data is the improvement: the team that knows its own bias, its own overconfidence, its own patterns, is the team that corrects them. The comparison is the loop of the learning, and the loop is the compounding: the team that estimates and measures and corrects is the team that estimates better every time. The comparison is the best tool, and the tool is the history.

7. The Commitment Is Separate

The estimate is not the promise, but the commitment is real: the commitment is the agreement that is made with the knowledge of the estimate. The commitment is the separate conversation: the team says what is likely, the stakeholders say what is needed, and the agreement is the meeting in the middle: the scope that is cut, the date that is moved, the quality that is chosen, the risk that is accepted. The commitment is the decision, and the decision is the adult conversation that the estimate enables.

The commitment also includes the contingency: the buffer that is the honest acknowledgment of the uncertainty, the slack that is the admission that the estimates are guesses. The contingency is not the padding, it is the reality: the project without the contingency is the project that has the hidden buffer anyway, just unacknowledged and unmanaged. The commitment is the management of the uncertainty, and the management is the difference between the project that surprises and the project that is prepared. The commitment is separate, and the separation is the clarity.

8. The Honest Guess Is the Trust

The final reframe is the trust: the honest guess is the foundation of the trust, and the trust is the relationship. The team that says the range, names the uncertainty, revises the estimate, and explains the reasoning is the team that is believed. The team that says the false precise number is the team that is doubted, even when it is right. The honesty is the currency, and the currency is the credibility: the credibility that is built by the honest guesses is the credibility that survives the wrong guesses.

The estimation is the practice of the truth: the guess that is labeled as the guess, the uncertainty that is named, the range that is honest, the revision that is timely. The practice is the culture, and the culture is the difference between the team that is blamed for the missed dates and the team that is trusted through them. The estimate is the guess, and the guess is the information. Stop pretending. Name the range. Show the uncertainty. Revise with the learning. The honest guess is the trust, and the trust is the project's real foundation. The lie is the pretending, and the truth is the guessing, out loud, with the humility of the uncertain. That is the estimation that works.

Tags

#management #productivity