Skip to content

Hofstadter’s Law and Estimates: Plan Duration Using Actual Work

Summary

Learn to interpret Hofstadter’s law without a fixed multiplier, estimate work and waiting separately, test unknown tasks, and improve plans using actual work.

Published

Estimate Duration with Actual Effort and Waiting Time

Hofstadter’s law is an observation that tasks take longer than expected even after allowing for that tendency. It supplies a caution rather than a fixed overrun formula.

Estimate active work and waiting separately, using comparable completed work and current differences.

Use the Observation without a Universal Multiplier

Atlassian discusses Hofstadter’s law as a warning about work exceeding expectations. (Atlassian: Engineering planning and Hofstadter’s law) Avoid turning it into a universal multiplier.

For unfamiliar work, test an unknown operation to learn its duration.

Include Work, Review Waits, and Revisions

Two hours of drafting with review on the next day does not mean same-day completion. Mark submission and review separately.

Choose schedule allowance against actual variation and the effect of delay.

Use Estimate Differences in Future Plans

Record effort, waits, and revisions to identify overrun causes. Repeated waiting calls for revised review ownership or timing.

Keep public intake periods aligned with delivery capacity.

For the related decision, read Set deadlines using effort and waiting.

SpreadSite is a no-code website builder that lets you create, publish, and update a website from Google Sheets using ready-made templates.

To publish a website communicating feasible delivery and intake dates, give SpreadSite a try!

Build a website with SpreadSite →

Frequently asked questions

Q: Does the law provide a formula?

A: It is a caution about estimates rather than a fixed overrun calculation.

Q: Is active effort enough for scheduling?

A: Include review waits and revision time.

Q: How should unfamiliar work be estimated?

A: Test unknown operations and record actual duration.

Q: What should be recorded after an overrun?

A: Effort, waits, revisions, and specific causes.

Sources

Build a website with Google Sheets using SpreadSite