When should you use it?
- You are about to raise prices, change packages or drop a service line
- A launch or hire is costly enough that a wrong call would hurt for months
- You have already written the plan and want it challenged rather than polished
Not for: Small, easily reversed choices that are cheaper to just try; Decisions that need legal, tax or financial advice from a qualified professional; Situations where you have no figures at all; the break-even step needs real numbers
What do you need, and what do you get?
You need
- A short written plan with the change, the date and who it affects
- Current figures such as client count, average revenue per client and costs
- Any customer-facing message you will need to send about it
You get
- A dated failure story with four ranked causes and an early signal to watch for each
- A break-even figure: the number of clients or sales that could walk away while the change still pays
- A list of assumptions rated high, medium or low with a test under $100 for each
- A five-point rubric and a draft message scored and revised against it
How does it work, step by step?
- Write the plan downPut the change, timing, affected customers and your current numbers into a few lines.
- Run the pre-mortemUse our prompt below so the assistant explains the failure before it judges the idea.
- Check the mathRecalculate the break-even point yourself; it is the figure most likely to drive your decision.
- Test the weakest assumptionPick the low-confidence assumption with the biggest impact and run its cheap test this week.
- Draft against the rubricHave it set the scoring points before writing the announcement, then revise until each point passes.
The prompt
Our own prompt, inspired by Shubham Vora and written to work in ChatGPT, Claude and Gemini. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
My plan: {plan}. Current numbers: {figures}. 1. Suppose it is {review_date} and this change went badly. Explain why in a short report: rank the four most likely causes and give, for each, a sign I would notice within the first month. 2. Calculate how many {customers_or_sales} I can lose after the change before total revenue falls below today's level. Show the arithmetic. 3. Name each assumption the plan relies on, rate how sure I should be (high, medium or low), and suggest one test I can run this week for less than $100. 4. For the {message_type} I must send, first set five scoring points, then draft it, score each point out of five and revise until all score five. Keep my facts separate from your guesses, and do not invent data.
Inspired by Shubham Vora: LinkedIn post: three prompts to run before any big decision. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- The model invents plausible causes. Treat the ranking as a list of questions, not a forecast.
- Break-even math is only as good as your figures. Use actual averages, not the hoped-for price.
- A rubric the model writes for itself can be easy to pass. Edit the points before it scores the draft.
- Running it once and ignoring the warnings defeats the purpose. Put the early signals in your calendar.
Our take
Most people use chat assistants to improve a plan they have already fallen for, and the assistant obliges. Vora's fix is to change the question: describe the failure first, then defend the idea. The pre-mortem itself is a well-known planning technique, but his version earns its place by pairing it with a hard number, the amount of customer loss the change can survive, which turns a vague worry into a threshold you can watch. The assumption list with cheap tests is the practical bridge between thinking and doing, and drafting a rubric before the customer email stops the assistant from grading its own work on vibes. Our cautions: the failure reasons are invented scenarios, not research, so use them to decide what to check rather than what to believe, and always redo the break-even arithmetic yourself. In our dry run with a fictional landscaping company moving 60 clients from per-visit billing to a 10% dearer annual contract, the assistant ranked upfront cost as the top risk, showed that five clients could leave before revenue dropped, and suggested a two-week pilot offer to ten clients as the cheapest test.
Where the time goes back: A twenty-minute session replaces days of second-guessing, and the break-even figure plus a few cheap tests tell you whether to go ahead before you announce anything you would have to walk back.
FAQ
Why imagine failure instead of asking for feedback?
What was his example?
Which assistant should I use?
Source and credit
Inspired by Shubham Vora. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- LinkedIn post: three prompts to run before any big decision
- Creator
- Shubham Vora
- Published on
- Original date
- Nov 4, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- ChatGPT
- AI dry run
- Nov 4, 2026: passed. Dry-run tested by our AI test agent on sample input. Ranked causes with early signals, correct break-even math (lose 5, the 6th costs money), cheap tests per assumption, rubric set before drafting and applied.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Nov 4, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.