Skip to content
GanttPal
Log in Get started

Bias in Estimation: Planning Fallacy, Framing, and Ranges

Estimating is difficult because time, price, and scope are often uncertain at the same time. In this Time Limit episode, Jacob Bodnar, VP of Operations at Maestro, discusses cognitive bias in project management with Brett Harned, with particular attention to how bias changes estimates. The episode runs 33 minutes and 36 seconds.

Why estimates drift optimistic

People often expect their own tasks to finish faster than they realistically will, while viewing other people's work more pessimistically. That imbalance is useful to recognize rather than treat as a personal failing. A project manager can provide a counterweight when a specialist's view is shaped by familiarity with their own work. The team can also act as a check and balance: estimators surface assumptions, while others question scope, risks, and missing details before a number becomes a commitment.

Framing, anchoring, and honest scoping

Language matters before estimating begins. Describing work as easy or straightforward encourages optimism and can make careful estimation look like overcomplication. Framing and anchoring can pull the result toward the first impression rather than the evidence. Use neutral language, ask what is known and unknown, and separate the definition of the project from the effort required to deliver it. The discussion also covers the team's 'sins of scoping' as a practical way to keep estimators honest.

A practical estimating checklist

A useful estimating checklist is: break any item over about ten days into smaller parts; estimate each part as a range; document the unknowns behind a wide range; estimate conservatively for the resources actually available; and revisit the estimate at milestones. This approach avoids treating an early figure, produced near the wide end of the cone of uncertainty, as if it were settled. Ranges also make uncertainty visible instead of hiding it inside a single confident number.

Preparing for a number needed tomorrow

An expedited estimate should be prepared before urgency arrives. Decide in advance who estimates, what scope information is required, which assumptions are acceptable, and how unknowns will be recorded. When a client needs a number by tomorrow, that process allows a conservative answer based on available resources rather than a rushed guess presented as certainty.

Frequently asked questions

What is the planning fallacy in project estimation?

It describes the tendency to expect your own work to take less time than it actually will, while judging other people's work more pessimistically. A project manager's different perspective can therefore help balance a specialist's estimate.

Why does framing work as easy distort an estimate?

Calling work easy or straightforward can push estimators toward optimism and undervalue the effort involved. Neutral wording keeps attention on scope, unknowns, and the resources actually available.

How should large estimates be structured?

Break larger work into smaller parts, express each part as a range, and treat a wide range as a signal to document what is still unknown. Revisit the estimate at milestones instead of relying on an early figure made when uncertainty was highest.

What should you prepare before a client needs a number tomorrow?

Define the expedited process in advance, estimate conservatively for the resources you actually have, and make clear which assumptions and unknowns remain unresolved.