Synopsis.
Name
The Planning Fallacy. You lay the task out, step by step, and you estimate how long it will take: you picture the work going as planned, each part taking about what it should, and you reach a date that feels honestly arrived at ... and you promise it. And the date is too soon, not because you were careless but because you built it from this task's own plan, the single run where nothing in particular goes wrong, and something in particular always does: never the same thing twice, so no plan can name it, but something, every time. So the estimate is beaten by a reality it left out by construction, and the task that was to be done by Friday is done, like the one before it and the one before that, late.
Arc
The bend is this: the more carefully you build the estimate from the task in front of you, the more surely it comes out too low, and the record that would correct it is the one thing the care sets aside. It runs on two views of the same task. The inside view builds the estimate from the specifics: the plan, its steps, the scenario where each goes about as it should. It is vivid, it is particular, it is the thing you actually know, and it is the best case, because a plan is a path through the work and the path it draws is the one where the work goes well. The outside view asks a duller question: tasks like this one, how long did they take? That record exists, and it runs long, every time, and it would price the estimate right ... but it is set aside as not applicable, because this task is known in a detail the others are not, and the detail is exactly the inside view that misleads. The reason the inside view runs low is that the plan omits the unforeseen by construction. Not one large predictable risk, which a good planner would price, but the ordinary swarm of small surprises: the dependency that slips, the review that bounces, the person out sick, the requirement that was always going to change. Each is unpredictable on its own, so no plan names it; together they are as certain as anything in the work, so every plan is beaten by them. None of it is error or sloth. Laying the task out is the job, the plan is the best knowledge there is, the estimate is sincerely meant, and no one can forecast which particular surprise will come. And where the low number also wins the approval, the money, the go-ahead, optimism is joined by incentive, and the estimate is shaded lower still, believed and pitched at once, so the two drivers pull the same way and the number that goes out is the one no reality will meet. Estimate from the record instead of the plan, forecast the task by the class of tasks it belongs to, and the number comes right: but the outside view delivers a figure no one wants to hear, feels like refusing to use what you know about this very task, needs a reference class and the honesty to count yourself into it, and pressed too far it pads the estimate until the work expands to fill it, which is the symmetric waste on the other side of the fault.
Stakes
Whether an estimate ever prices the reality instead of the plan. Every plot but the last moves the same way: toward the inside view, vivid and particular and honestly the best case, and away from the outside view, dull and unwelcome and right. The production cannot make the plan price the unforeseen, because the plan is the run where nothing in particular goes wrong and the unforeseen is precisely the thing no plan can name in advance. It can only show that no one blundered, that laying out the task is the work and the plan the best knowledge there is and each surprise genuinely unforecastable, and that the one move that sets the date right, forecasting the task from the class it belongs to rather than the story of itself, delivers a number nobody wants, gives up what is truly special about this case, and pressed too hard pads the work until it swells to fill the room, with no plan able to mark which surprise will be the one that comes.
Estate
khai-misfits: the house that holds this production and answers for the whole run.