Check project forecasts against realistic base rates

Stress-test internal projections against historical industry base rates to neutralize planning fallacy and timeline optimism.

You getReference Class Identification, inside View vs. Outside View and critical Blind Spots

Prompt

Prompt
Act as an analytical forecaster applying the outside view and reference class forecasting. Evaluate the plan I paste against historical industry base rates to counter optimism bias.

Rules:
- Identify the reference class (the broad category of similar historical projects).
- Compare stated estimates for timeline, budget, and adoption against typical historical outcomes.
- Identify specific failure modes typical of this reference class that the proposal ignores.
- Do not fabricate precise statistical studies; provide well-established historical ranges and state what data requires local verification.

Output format:
- Reference Class Identification (definition of the benchmark category)
- Inside View vs. Outside View (table with columns: Metric, Proposed Forecast, Historical Base Rate Benchmark, Variance Risk)
- Critical Blind Spots (3 typical reference-class risks omitted in the plan)
- Calibrated Baseline (revised, risk-adjusted timeline and resource estimates)

My forecast notes are below:

Example output

Example for: enterprise ERP implementation plan projecting a 6-month completion

Reference Class Identification

Reference Class: Large-scale Enterprise Resource Planning (ERP) platform migrations and core database consolidations within mid-market organizations (500–2,000 employees).

Inside View vs. Outside View
MetricProposed ForecastHistorical Base Rate BenchmarkVariance Risk
Implementation Timeline6 months14 to 21 monthsSevere: Over 70% of ERP migrations exceed initial timeline estimates by at least 100%.
Internal Resource Allocation10 hours/week per department head25 to 30 hours/week during mappingHigh: Department leads consistently underestimate data hygiene and validation workloads.
Custom Integration Budget$45,000 contingency30% to 50% of total software licensingHigh: Legacy API deprecation and schema mismatches usually double integration scope.
End-User Adoption at Launch90% compliance within 14 days40% to 60% active usage at 60 daysModerate: Resistance to workflow shifts leads to parallel spreadsheets without strict deprecation.
Critical Blind Spots
  1. Data Cleansing Backlog: The schedule assumes legacy database records are export-ready, whereas deduplication and field mapping typically consume 20-30% of total project hours.
  2. Vendor Scope Boundaries: The plan assumes vendor consultants handle connector code, but standard vendor contracts place transformation logic entirely on client engineers.
  3. Post-Go-Live Productivity Dip: Projections omit the predictable 15-25% drop in operational efficiency during the initial 30 days following system cutover.
Calibrated Baseline
  • Adjusted Timeline: 14 months to complete cutover (Phased launch: Finance in month 8, Supply Chain in month 11, Full deprecation in month 14).
  • Adjusted Financial Reserve: Increase implementation contingency from $45,000 to $130,000 to cover external systems integration and temporary operational backfill.
Written by AI from this prompt. Your results will vary.

Paste your project plan, budget proposal, or timeline targets into ChatGPT, Claude or Gemini right after the prompt. Follow up by asking: "What three early warning signals will tell us within the first month that we are trending toward the base rate rather than our optimistic plan?"

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Critical Thinking & Decisions
Critical Thinking & Decisions

Draft a calm devil's advocate brief

Create structured, non-defensive questions to stress-test popular proposals. Use this to surface blind spots in upcoming team discussions without sounding confrontational.

Critical Thinking & Decisions

Stress test a strong gut feeling

Pressure-test an instinctive business decision against hidden assumptions and worst-case realities. Use it before signing a contract or greenlighting spend.

Critical Thinking & Decisions

Stress test an optimistic project timeline

Expose hidden friction, coordination overhead, and missing buffers in your project schedule. Use it before committing to deadlines with clients or executive leadership.