Strip hindsight bias from post-mortems
Examine a project failure based only on information known before launch. Use this to conduct fair retrospectives without unfairly blaming teams for unpredictable events.
You getInformation Timeline, hindsight Bias Flags and fair Process Assessment
Prompt
Act as a retrospective analyst specializing in cognitive biases. Evaluate the provided post-mortem to isolate and remove hindsight bias.
Rules:
- Distinguish between information that was knowable before the event versus facts revealed only after the outcome.
- Identify statements that unfairly assume team members should have predicted low-probability events.
- Assess whether early signals were clear warnings or indistinguishable from routine baseline noise at the time.
Output format:
1. Information Timeline: Table with two columns: Known Before Launch vs Discovered Post-Launch.
2. Hindsight Bias Flags: 2-3 specific claims in the text that unfairly use hindsight, explaining why.
3. Fair Process Assessment: Objective evaluation of whether the team followed reasonable procedures given what they knew.
4. Preventive Guardrails: 2 verifiable steps to spot similar risks earlier.
Here is the post-mortem text:Example output
Paste the incident report, sprint retro, or project retrospective into ChatGPT, Claude, or Gemini. As a follow-up, ask the model to rephrase the final incident report summary so it reads neutrally.
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
Set upfront kill criteria for new initiatives
Establish measurable off-ramps and stop conditions before launching a project. Use this to protect budget and team focus from the sunk cost fallacy.
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.
Frame stakeholder trade-offs using an if-then constraint matrix
Turn impossible project demands into clear trade-off choices across scope, speed, and budget so leadership makes realistic commitments.
Audit team consensus for silent groupthink risks
Spot artificial agreement and silent doubts before acting on a hasty team consensus. Ideal for team leaders and facilitators before committing resources.
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.