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.

You getObjective Summary, hard Kill Triggers and warning Triggers

Prompt

Prompt
Act as a risk analyst. Help me establish concrete kill criteria before launching a project so my team avoids the sunk cost fallacy.

First, ask me 3 short numbered questions in one message:
1. What is the core objective and timeline of the initiative?
2. What primary resources (budget, headcount, or time) are committed?
3. What are the key assumptions that must prove true for success?

Wait for my answers. Once I respond, provide kill criteria following these rules:
- State measurable red lines with numbers and deadlines, not vague statements.
- Separate hard stops (mandatory shut down) from review triggers (mandatory pivot or pause).
- Specify an explicit owner responsible for pulling the plug.

Output format:
- Objective Summary (2 sentences)
- Hard Kill Triggers (3 numbered items with metric, threshold, and deadline)
- Warning Triggers (2-3 items requiring formal review)
- Off-Ramp Protocol (3 actionable wind-down steps)

Example output

Example for: launching an outbound enterprise sales pilot

Objective Summary

Validate outbound enterprise demand for our compliance automation module by securing paid pilots. The initial sprint runs for 90 days with a dedicated budget of $35,000.

Hard Kill Triggers
  1. Zero Signed Letters of Intent by Day 60: If fewer than 2 qualified enterprise prospects sign an LOI after at least 150 completed discovery calls, cancel outbound marketing spend immediately.
  2. Customer Acquisition Cost Above $18,000: If the average cost to book an audited pilot exceeds $18,000 by Day 75, halt SDR contractor agreements.
  3. Core Feature Failure Rate Exceeds 25%: If more than 1 in 4 pilot users experience fatal export errors during the first two weeks of onboarding, stop all new sales demos.
Warning Triggers
  • Response Rate Below 1.5%: If cold outreach response is under 1.5% across 1,000 contacts by Day 30, pause outreach to rewrite messaging and refine ICP criteria.
  • Sales Cycle Expansion: If average sales conversation cycles exceed 45 days without a scheduled security review, convene a mandatory go/no-go meeting with leadership.
Off-Ramp Protocol
  1. Notify contractors and software vendors 14 days prior to contract termination dates.
  2. Offer participating pilot leads a grandfathered export tool or refund their deposit within 5 business days.
  3. Document objections and technical failure logs in a single post-mortem memo before reassigning team members to core product roadmap priorities.
Written by AI from this prompt. Your results will vary.

Paste this into ChatGPT, Claude or Gemini. Answer the model's 3 questions directly with your project targets and resources. Follow up by asking: "Which of these triggers will be hardest for the team to accept emotionally, and how do we prepare for it?"

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Critical Thinking & Decisions