Coaching practices for Project Planning Bias

Describe almost anything you are working through and IX Coach finds the practices whose real-world fit is closest. For Project Planning Bias, these are the strongest matches in the current practice library.

Does this sound like the set of challenges you might be facing?

• Every time I plan something I walk through the steps in my head and it feels totally doable in the time I’ve got
• I’m putting a timeline on this project from the plan in my head, and it always feels doable
• I’m about to commit to this timeline and on paper it all looks fine, but I have a nagging feeling I’m glossing over the ways it could go sideways because admitting them now feels like talking myself out of it before I’ve even started.
• I tend to figure out my plan the same morning I’m supposed to start, in a rush to just get going
• I’m late on something, I shrug, update the calendar, and immediately forget I ever thought it’d take half as long

Practices that may help

1. Reference class forecasting
   Before estimating, look up how long similar past projects actually took — not how they felt.
   The Planning Fallacy — Why Your Estimates Are Always Wrong
2. The Planning Fallacy — Why Your Estimates Are Always Wrong
   The planning fallacy is the well-replicated tendency to underestimate completion times even when you know your past projects ran late. The fix is not to "try harder" — it is to switch from imagining the ideal future scenario to consulting your own base-rate history and similar projects.
3. Use reference class forecasting for project estimates
   Estimate how long similar projects have taken historically before estimating your specific project.
   Base-Rate Neglect: Why We Ignore the Odds
4. Run a premortem before committing
   Imagine the project has already failed and work backwards to find why.
   The Planning Fallacy — Why Your Estimates Are Always Wrong
5. Separate the planning session from the execution day
   Do your planning in a dedicated session, never on the day you intend to start.
   The Planning Fallacy — Why Your Estimates Are Always Wrong
6. Log actual vs. estimated time for every task
   Build a personal database of your own estimation errors so you can calibrate future predictions.
   The Planning Fallacy — Why Your Estimates Are Always Wrong
7. Schedule buffers as first-class commitments
   Add explicit slack time to your schedule and treat it as non-negotiable white space, not a reserve to fill.
   The Planning Fallacy — Why Your Estimates Are Always Wrong
8. Estimate conservatively and act on the conservative number
   When uncertain, use a pessimistic estimate as your working assumption — not your best guess.
   Margin of Safety
9. Run a pre-mortem from the outside-view perspective
   Imagine the project has failed — then ask which base-rate failure type caused it.
   The Outside View
10. Invoke the outside view before committing to any significant plan
    Before finalizing a plan or forecast, ask "How did similar things go?" as the first checkpoint.
    The Outside View

Describe your situation in your own words to search the complete practice library.