Use this concept as a question to test the decision, not as a label for a person.
Open →Decision situation
Project estimation
Estimate time and effort with an outside view instead of relying only on the current plan.
Signals to notice
Reasons to slow down and check.
- The estimate starts from one target date.
- Comparable completed work is not being used.
- The plan assumes dependencies will behave normally.
Questions before action
Make the missing evidence visible.
- What happened in comparable completed work?
- What range is supported by the reference class?
- Which assumptions would move the estimate toward either end?
Relevant lenses
Concepts that may help you test the reasoning.
Practical moves
Do something different, not only notice a label.
Use outcomes from comparable completed cases before refining an inside-view plan.
Open →Create a reference point before seeing a strong external number or recommendation.
Open →Preserve what was known, expected and uncertain before the outcome changes memory.
Open →Skill to develop
Forecasting
You can produce forecasts that are easier to challenge, compare and learn from later.
Practice this situation
Choose a useful first move.
A sponsor says the migration should finish in twelve weeks. The delivery team then estimates each work package while that date remains visible.
Skill: ForecastingOpen scenario →A team has a detailed task plan for a data migration. It predicts 40 days, but nobody has checked how long similar migrations actually took.
Skill: ForecastingOpen scenario →The previous project missed its date by six months. Managers now double every estimate, even though most comparable projects had much smaller delays.
Skill: ForecastingOpen scenario →