260701_thumb_06_프리모템.png

A Pre-Mortem Before You Start — Preview the Failure

Assume it already failed and trace the causes backward — risks, early-warning signs, preventions, and the one thing to guard first.

0 views·0 copies

Prompt text

For the {{plan}} in the input below, assume "at the set date, this failed completely" and write a pre-mortem tracing the causes backward.

Work rules:
1. First write the failure scenario as one obituary-style paragraph — vividly, what broke and how (3-4 sentences).
2. List 5-7 causes, each tagged "likelihood (H/M/L) x impact (H/M/L)" with one line of reasoning.
3. Pair each cause with one "early-warning sign" (if you see this, danger) and one "prevention you can do now".
4. Pick the single most fatal risk as "guard this first" and justify why it's #1.
5. No vague risks ("poor communication") — narrow to risks specific to this plan.

Forbidden: no generic filler risks. No fabricated probability claims (likelihood/impact as relative grades only).

Output: markdown. One intro line + a per-cause table or a likelihood-x-impact quadrant + one "where to touch first" line at the end.
Output language: Write in the user's language. This instruction must work identically in any language.
Self-contained: Finish within this reply. No external sites or extra steps.
Fallback: If the plan is short, assume the most plausible type, state it at top, and proceed.

----
Input
- {{plan}} (required): the upcoming project/decision/event, in one paragraph.
- {{timeframe}} (optional): the target date. If blank, assume "a near deadline".
AI

AI response

Recommended AI: ChatGPT, Claude, Gemini

Let's kill it on paper first, so it survives in real life.

The obituary (6 months out)

The community meetup launched, ran twice, and quietly died. The first event drew a decent crowd from one big group blast, but almost no one came back, and by month three the organizers were the only ones in the room. It didn't fail loudly — it just never built a reason to return.

Causes (likelihood x impact)

CauseL x IWhy
No repeat reason after event 1H x Hone-off content, nothing pulling people back
Over-reliance on one promo channelH x Mall signups from a single blast, no organic loop
Organizer burnoutM x H2 people doing 100% of prep
Vague target audienceM x M"anyone interested" = no one specifically

Early warnings x preventions

  • No repeat reasonwarning: week-2 signups under half of week-1. prevent: design a 3-part series so event 1 needs event 2.
  • One channelwarning: 90%+ from the same source. prevent: add a "bring one person" ask at each event.
  • Burnoutwarning: prep slipping to the night before. prevent: split roles now, hard-cap prep at 2 hrs/event.

Guard this first

The missing repeat reason (H x H). Traffic problems are fixable later; a format nobody returns to can't be rescued by more promo. Lock the "why come back" before the first invite goes out.

Related prompts