Estimation, planning, and honest commitments

Estimates are unreliable by nature. At the start of a piece of work you know the least you ever will, the happy path is the easiest to imagine, and the hidden work often dominates the visible. The competency is therefore not producing accurate estimates; it is managing the uncertainty honestly: estimating in ranges with named assumptions, slicing work small so the error compounds less, de-risking before committing, and keeping the distinction between an estimate and a commitment sharp enough that everyone knows which they are hearing. It matters because delivery credibility is built or destroyed here. A commitment that was really an optimistic estimate, defended until the deadline and then missed, costs more than the slip: it costs the trust that would have made the next honest forecast believable. The examinations test it because the pressure to give a confident date is constant at every scope, and the defensible answer is nearly always the one that names what is not yet known.

1. An estimate is not a commitment, and both are said aloud. "Our best estimate is this; what we can commit to is that." The gap between them is the buffer against uncertainty, named rather than hidden, and naming it is what builds trust.
2. Ranges, not points. A single date at the start of uncertain work is a range wearing a costume. State the range and the assumptions that drive its width.
3. Slice small and de-risk first. Small pieces estimate more accurately and their errors compound less; a time-boxed spike on the fuzziest part narrows the range faster than any amount of planning.
4. History beats hope. How long similar work actually took is a better forecast than how long anyone hopes this will take.
5. Re-forecast the moment reality diverges, and say so. Surprises sprung at the deadline are how trust dies. Early disclosure with options — date, scope, resourcing — is the honest form of a slip.
6. Do not guess under pressure; be decisive about the process instead. Asked for a date on the spot with no estimate, commit to the date by which a credible estimate will exist, name the key unknowns, and commit to scope. Decisiveness about how the answer will be produced is not the same as inventing the answer.

Estimation is one of the better-studied problems in software engineering and in cognitive psychology, and the unit has one research-grade model among its practitioner ones.

The planning fallacy research

The finding in Daniel Kahneman and Amos Tversky, Intuitive Prediction: Biases and Corrective Procedures (1979) that people predicting the time a task will take systematically underestimate it, even when they know that similar tasks in the past overran, because they reason from the specifics of the case in front of them rather than from the distribution of similar cases. The corrective the authors propose — the outside view, forecasting from the reference class of comparable work — is the psychological basis for principle 4. The effect is robust and has been replicated across domains; it is the reason estimation is not fixed by asking people to try harder.

The cone of uncertainty practice

The observation, given its standard software form in Steve McConnell, Software Estimation: Demystifying the Black Art (2006), that estimates are least accurate at the start of work and narrow as reality is discovered. Its corollaries are the working practices of this unit: estimate in ranges, slice work small, de-risk the fuzziest parts first, and re-forecast as the cone narrows. The cone narrows only if the discovering is done; unexamined uncertainty stays wide, and the model excuses nothing about failing to re-forecast once more is known.

Cycle time and historical forecasting practice

Using how long work actually takes, measured, as the basis of forecasts rather than how long people estimate it will. The operational form of the outside view. History predicts only work that resembles the past, so novel work still needs de-risking spikes, and a cycle-time distribution is a range: quoting its average as a date reinvents the original error.

Brooks's law practice

The observation in Frederick P. Brooks Jr., The Mythical Man-Month: Essays on Software Engineering (1975) that adding people to a late software project makes it later, because the new people must be trained by the existing ones and the communication paths multiply. It is the reason "add people" is rarely the honest option when a commitment is at risk, and why the options that remain are date, scope and, occasionally, resourcing applied early rather than late. Its scope is narrower than its fame — it applies to work that cannot be partitioned — and the judgment is in telling that work from work that can.

Batch size and predictability practice

From Donald G. Reinertsen, The Principles of Product Development Flow: Second Generation Lean Product Development (2009), the argument that predictability is a property of the delivery system rather than of effort: smaller batches and limited work in progress reduce variance in delivery times more reliably than pressure does. It is the reason a team producing wildly inconsistent estimates gets engineering — smaller slices, historical data, forecast reviews — rather than exhortation.

The estimate with its assumptions

Any estimate larger than a few days is given as a range with the two or three assumptions that drive its width written beside it. When an assumption turns out wrong, the range moves and the reason is visible. An estimate whose assumptions cannot be stated is an impression.

The commitment, buffered and explained

What is promised outward is derived from the estimate with a deliberate, stated buffer, and the stakeholder is told both numbers. The commitment also states the scope it covers, the known risks, and how variance will be communicated. A commitment is a shared understanding of those four things, not a promise to hit a date no matter what.

The spike before the plan

Before committing to work with a wide range, a time-boxed investigation of the fuzziest part, with a defined question and a fixed end. Its output is a narrower range, or the discovery that the work is not what it seemed. Spending a week to learn that a quarter's estimate was wrong by a factor of two is the best week of the quarter.

Forecast reviews

At a fixed cadence, the team compares its forecasts to its actuals and asks why they differed. Chronic over-commitment and chronic sandbagging get the same treatment, because both are forecasts that carry no information: recalibrate against historical data. The team that delivers exactly to plan every quarter with no misses is more likely sandbagging than excelling.

The early slip conversation

The week a commitment becomes doubtful, the stakeholder hears it, with the cause and the options: move the date, reduce the scope, or add resourcing where it will actually help. The conversation happens while choices still exist. A slip disclosed late converts a delivery problem into a trust problem.

At team scope the object is the team's forecast and its commitment, and the manager states ranges, buffers deliberately, and re-forecasts openly. At organisational scope the object becomes commitments that depend on several teams, where uncertainty must be aggregated honestly rather than best cases added up, and the truthfulness of rolled-up status becomes the thing to manage; forecast calibration across teams is a system to run, not a speech to give. At executive scope the object is the organisation's planning cadence and the credibility of its commitments to the business and the board — staged commitments with checkpoints, credibility repaired through smaller verifiable deliveries in sequence rather than bolder promises, and the flagship date-versus-quality call made on total cost over time. The pattern is in How Judgment Scales; the reporting system that carries status upward is treated in DE-4 Managing scope, risk, and dependencies across workstreams.

• Gives ranges with named assumptions and separates the estimate from the commitment. team
• Buffers the commitment deliberately and says so. team
• Slices work small and de-risks the fuzziest part with a time-boxed spike before committing. team
• Re-forecasts early and openly when reality diverges, with options. team
• Declines to give a date on the spot with no estimate, and says what it would take to give one.
• Failure mode — treating an estimate as a promise. team
• Failure mode — silent padding, so that nobody knows what the number means. team
• Failure mode — committing to the optimistic number to dodge a hard conversation. team
• Failure mode — going quiet as the timeline slips. team
• Defines a department commitment as scope, known risks and a variance protocol, and guards that definition under pressure. org
• Aggregates uncertainty across several teams honestly rather than adding up best cases. org
• Treats chronic over-commitment and chronic sandbagging as the same calibration failure and recalibrates both against history. org
• Improves predictability through batch size and work-in-progress limits rather than pressure. org
• Failure mode — letting a commitment mean "guaranteed date". org
• Failure mode — guessing under executive pressure and calling it decisiveness. org
• Failure mode — praising the sandbagger's streak. org
• Failure mode — demanding better estimates without changing how work is sliced or measured. org
• Gives the board a staged commitment: near-term milestones firm, later phases as ranges that tighten at named checkpoints, unknowns stated plainly. exec
• Rebuilds credibility after repeated misses by diagnosing the systemic cause and delivering smaller, verifiable commitments in sequence, not by promising bigger. exec
• Discloses a major miss early with options, while choices still exist. exec
• Makes the flagship date-versus-quality call on total cost over time, decides explicitly, and communicates the reasoning. exec
• Reads execution health as whether the organisation reliably converts commitments into delivered outcomes, not as activity. exec
• Failure mode — giving the board false precision because it asked for a date. exec
• Failure mode — re-promising bigger after each miss. exec
• Failure mode — sitting on a known miss until it is undeniable. exec
• Failure mode — holding a date by shipping something that will fail at scale. exec

Honesty versus confidence. Stakeholders want a date and read a range as evasion; a point estimate reads as confidence and is usually wrong. The resolution is to be confident about the process — the checkpoints, the spikes, the date by which the range narrows — while being honest about the number.

Buffer versus credibility. A commitment buffered too little is missed; one buffered too much looks like sandbagging and, when always hit, is. The named buffer is the resolution: the stakeholder sees both numbers and the reason for the gap.

Slicing versus coherence. Small pieces estimate well and can lose sight of the whole; large pieces keep the shape of the work and estimate badly. The judgment is to slice for estimation while planning for the outcome, and to keep the two views visibly connected.

Early disclosure versus premature alarm. A slip disclosed the moment it is possible spreads alarm about risks that may not materialise; one disclosed the moment it is certain is too late for options. The rule is to disclose when the probability crosses the threshold at which the stakeholder would want to act, and to say that it is a probability.

Date versus quality. Holding a launch date by cutting quality and slipping it to hold quality are both real options with real costs. The judgment is made on total cost over time, not this quarter's optics, and the failure the examinations present most often is the launch that ships to a date and fails at scale.

A senior manager who leads four teams is in a leadership meeting when a vice-president asks them, on the spot, to commit the group to a launch date for an initiative that was scoped in a slide deck a week ago. No team has estimated it. The vice-president wants a date for a customer conversation that afternoon and says, in front of the room, that a good leader should be able to give one.

The two easy answers are a guess and a refusal. A guess, delivered confidently, becomes the commitment the moment it leaves the room, and it will be defended against evidence for the next quarter. A refusal — "we can't commit without estimating" — is true and reads as unhelpful, and leaves the vice-president with nothing to say to the customer.

The senior manager is decisive about the process rather than the number. They say that the initiative has not been estimated and that a date given now would be a guess dressed as a plan; that they will have a credible estimate, as a range with its drivers, by the end of the following week; and that they can commit today to the scope of the first phase, which is well enough understood to start. They name the two unknowns that will drive the width of the range — a dependency on a platform team and a data migration nobody has sized — and say what the group will do in the coming week to narrow both. For the customer conversation, they offer the vice-president a sentence that is true: the first phase is committed and starts now, and the full timeline will be set within two weeks.

Behind the answer is a plan. The four teams run a one-week spike on the migration and a scoping conversation with the platform team; the estimate that comes back is a range with three assumptions attached; the commitment offered to the vice-president is buffered against it, states the scope it covers and the risks, and says how variance will be communicated. The vice-president gets a date within two weeks, and it is one that carries information.

What the senior manager does not do is treat the pressure in the room as a reason to invent a number. The cost of the honest answer is a moment of discomfort in a meeting. The cost of the other answer is a quarter of defending a date nobody believed, and a launch that either slips or ships broken.

• DE-1 Prioritisation under constraint — the sequencing a commitment is made against, and the trade-offs that move when it slips.
• DE-4 Managing scope, risk, and dependencies across workstreams — the dependencies and risks that widen a range, and the status reporting that carries a slip upward.
• SV-2 Communicating and partnering across functions — explaining a range and its drivers to a stakeholder who wants a date.
• CC-5 Values, integrity, and ethical judgment under pressure — declining to shade a forecast under pressure, and absorbing the cost of declining.
• DE-5 Designing how work flows — batch size and flow as the system properties that make forecasts believable.

1. What is the difference between an estimate and a commitment, and why say both aloud?
   Answer

   The estimate is the best forecast; the commitment is what is promised outward, deliberately buffered. Saying both names the buffer, so nobody mistakes one for the other, and the visible gap is what builds trust.
2. Why is a single date at the start of uncertain work "a range wearing a costume"?
   Answer

   Because at the start you know the least you ever will and the range is at its widest; a point estimate hides that width rather than removing it. State the range and the assumptions that drive it.
3. A vice-president asks you on the spot to commit your group to a date for unestimated work. What is the credible response? org
   Answer

   Commit to a date by which a credible estimate will exist, name the key unknowns and what will narrow them, and commit to the scope that is understood. Decisive about the process, honest about the number.
4. One team consistently over-commits and misses; another quietly sandbags and always hits. Why are these the same problem, and what fixes both? org
   Answer

   Both produce forecasts that carry no information. Both are fixed by recalibrating against historical data — smaller slices, cycle-time distributions, forecast reviews — not by a speech for one and congratulations for the other.
5. Why does adding people to late work usually make it later, and what does that leave as options?
   Answer

   New people must be trained by the existing ones and communication paths multiply, so the work slows before it speeds up. What remains is date, scope, or resourcing applied early enough to help, disclosed while choices still exist.
6. What makes a staged commitment more credible to a board than a single date, and what does repeated re-promising cost? exec
   Answer

   Near-term milestones committed firmly, later phases as ranges that tighten at named checkpoints, unknowns stated plainly: it is the only forecast a sophisticated audience should believe. Re-promising bigger after each miss spends the credibility that would have made the next honest forecast believable.
7. The flagship launch can hold its date by cutting quality or slip it. What is the basis for the call? exec
   Answer

   Total cost over time, not this quarter's optics: a launch that fails at scale costs more than a slip. Decide explicitly and communicate the reasoning.

• Daniel Kahneman and Amos Tversky, Intuitive Prediction: Biases and Corrective Procedures (1979) — the planning fallacy and the outside view.
• Steve McConnell, Software Estimation: Demystifying the Black Art (2006) — the cone of uncertainty; ranges and slicing.
• Frederick P. Brooks Jr., The Mythical Man-Month: Essays on Software Engineering (1975) — adding people to late work.
• Donald G. Reinertsen, The Principles of Product Development Flow: Second Generation Lean Product Development (2009) — batch size and variance; predictability as a system property.