Effort Shock and Reward Shock

Two Shocks

Most project failures, looked at carefully, trace back to one of two miscalibrations.

Effort shock: the project turned out to require much more effort than expected. The work was harder, took longer, demanded more coordination, generated more problems than the estimate anticipated.

Reward shock: the project was completed successfully, but the reward - the satisfaction, the recognition, the downstream benefit - was much less than expected. The thing that made the project seem worth doing turned out to be less valuable than it appeared from the outside.

Effort shock and reward shock pull in opposite directions but produce similar outcomes: projects that are abandoned before completion, or completed but not pursued, or pursued with declining energy that degrades quality.

Effort Shock

Effort shock is the more studied of the two. The planning fallacy - the systematic tendency to underestimate how long and how much things take - has been well documented since the 1970s. Projects are almost always more costly than the estimate and almost always take longer than planned.

The causes are structural. Planning focuses on the plan itself rather than on the ways the plan will differ from reality. The most optimistic plausible scenario is used as the base case rather than a historical average. Potential problems are identified and then not incorporated into the plan at full weight.

The remedy is also structural: planning from historical base rates rather than from the inside view, explicitly budgeting for problems, treating the optimistic scenario as an upper bound rather than an expectation.

But even with good structural remedies, some effort shock is irreducible. Real projects encounter real surprises. Building in a contingency budget for surprises (typically 30-50% of the naive estimate) is better than pretending the surprises won't come.

Reward Shock

Reward shock is less studied and in some ways more insidious. It is not about misjudging how hard something will be to do - it is about misjudging how much the done thing will be worth.

We evaluate anticipated rewards from the outside, before experience has informed the valuation. The thing looks more appealing than it will feel from the inside, partly because we imagine the best version of the outcome rather than the average version, and partly because we do not anticipate the adaptation - the way that having the thing changes our evaluation of it.

The promotion that was supposed to feel vindicating feels like more responsibility. The finished book that was supposed to feel like a monument feels like the past. The achieved goal that was supposed to change things often changes them less than expected.

Reward shock produces motivation failure in the middle of projects - not because the project is going badly but because the anticipated reward is being reassessed downward as the reality of what it would provide becomes clearer.

Managing Both

Managing effort shock: plan from base rates, build in contingency, update the estimate as the project proceeds rather than anchoring to the original.

Managing reward shock: before starting a project, try to genuinely imagine what having the outcome would actually feel like - the average experience, not the best version. Talk to people who have done similar projects. What was it actually like when they finished? What did they feel? How long did the reward last?

Neither shock is fully avoidable. Projects genuinely are unpredictable, and rewards genuinely are harder to anticipate than costs. The goal is not perfect prediction but honest calibration - starting projects with a realistic picture of both what they will require and what they will produce, so that the shocks, when they come, are smaller and the decisions made in response to them are better.