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
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
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.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
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.
Expose unstated assumptions in a business plan
Stress-test projects and commercial plans by uncovering implicit dependencies, fragile beliefs, and hidden points of failure.
Run a realistic project pre-mortem analysis
Spot overlooked failure modes and blind spots before launching a project. Best used during planning stages to build concrete safeguards.
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.
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.
Detect scope creep hidden in quick requests
Flag hidden architectural, operational, and delivery risks concealed inside seemingly harmless, small project additions.