BusinessStaff pick2 fill-in fields

The Pre-Mortem

Imagine the project already failed, then turn that story into ranked risks, warning signs and one cheap test.

Shared by Jonah KimOctober 29, 20262K copies

Live preview

1,977 copies

It is {{date six months from now}}. Our project, {{project name}}, has failed.

Here's what the project is:
{{two or three sentences: goal, team, timeline, budget}}

1. Write a short, believable story (under 200 words) of how it failed,
   as told by someone on the team.
2. List the eight most likely causes of failure. For each, rate
   likelihood (1-5) and damage (1-5), and sort by likelihood x damage.
3. For the top three, give one early warning sign we'd see in the
   next 30 days.
4. Suggest the single cheapest test we could run this week to reduce
   the top risk.

Be specific to our situation. No generic risks like "poor communication"
unless you can say exactly how it would show up.

Ask Ideabro with this

Suggested model

Any LLM

Works with most modern chat models. Results improve when you give it more context than you think it needs.

Get more out of it

Add real numbers: price, audience size, costs. Vague in, vague out.
Ask it to argue against its own recommendation.
End with “What should I do in the next 48 hours?”

Make it yours

Improved this prompt? Share your version — editors review every submission and credit the author.

Related prompts

More business

BusinessClaude

Customer Interview Synthesiser

Turn a pile of interview notes into patterns, quotes and decisions, without inventing insights.

Here are notes from {{number}} customer interviews about {{product or problem}}:

"""
{{interview notes, separated by ---}}
"""

1. List the recurring problems, with how many interviews mentioned each.
2. For each problem, include one verbatim quote, marked with which interview it's from.
3. Note any contradictions between interviewees.
4. Separate what people DID (behaviour) from what they SAID they'd do (opinion).
5. Suggest three decisions these interviews support, and one decision they
   clearly do NOT support yet.

Only use what's in the notes. If a pattern appears in just one interview,
label it "single mention".

3 fill-in fields: Number, Product or problem, Interview notes, separated by

1.1K copies

BusinessAny LLM

One-Page Decision Memo

Turn a messy decision into a one-page memo with options, trade-offs and a clear recommendation.

I need to make a decision: {{decision}}.
Deadline: {{when}}. Who's affected: {{people or teams}}.

Here's my messy thinking so far:
{{brain dump}}

Write a one-page decision memo with these sections:
- The decision in one sentence
- Options (two to four), each with cost, upside, downside and reversibility
- What we know vs. what we're guessing
- Recommendation, with the main reason in one sentence
- What would make us change our minds
- Next step, owner and date

Write in plain language for someone who has two minutes. If my brain dump
is missing something essential to decide, list it at the top as "Open questions".

4 fill-in fields: Decision, When, People or teams…

842 copies

BusinessAny LLM

Pricing Page Stress Test

Read your pricing like a confused customer, a bargain hunter and your finance team would.

Here is the draft pricing for {{product}}, which {{one-line description}}:

"""
{{pricing tiers, limits and prices}}
"""

Our main customer is {{customer}} and our biggest cost per user is {{cost driver}}.

Read it three times, as three different people:
1. A first-time visitor who has 20 seconds. What do they think they're buying?
   What confuses them?
2. A power user trying to get maximum value for minimum money. How would
   they game this?
3. Our finance lead. Which customer could cost us more than they pay?

Then:
- Rewrite the tier names and one-line descriptions to be clearer.
- Suggest one change that protects our margins without punishing normal users.

5 fill-in fields: Product, One line description, Pricing tiers, limits and prices…

701 copies