The premise
Launch decisions get made on momentum. AI can force a structured memo that lists kill criteria as prominently as the upside case.
What AI does well here
- Draft a memo with sections for upside, downside, kill criteria, and reversibility.
- Pull historical launch postmortems to populate base rates.
- Generate counterarguments to each go assertion.
What AI cannot do
- Override an executive who has already decided.
- Know which dependencies are actually fragile in production.
- Hold the team accountable to the kill criteria three weeks later.
End-of-lesson check
15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-business-AI-and-go-no-go-launch-decision-adults
Which of the following best describes the primary value AI brings to go/no-go decision memos?
- It surfaces kill criteria that stakeholders would prefer to ignore
- It makes the final launch decision on behalf of executives
- It automatically cancels launches that meet any downside scenario
- It replaces the need for human judgment in launch decisions
A properly structured AI-generated go/no-go memo should include which four sections?
- Market analysis, competitor review, risk assessment, and cost-benefit analysis
- Executive summary, financial projections, team capabilities, and timeline
- Project plan, resource allocation, stakeholder map, and success metrics
- Upside thesis, downside scenarios, explicit kill criteria with thresholds, and reversibility analysis
After writing each go-side claim in a go/no-go memo, what should AI be prompted to generate?
- A summary of executive preferences
- The strongest possible counterargument
- A supportive case study from industry leaders
- A list of alternative launch dates
Which limitation of AI in go/no-go decisions is MOST related to organizational dynamics?
- AI cannot pull historical postmortems for base rates
- AI cannot generate counterarguments to go assertions
- AI cannot generate the initial memo draft
- AI cannot override an executive who has already decided
Why are vague kill criteria like 'if adoption is poor' problematic in go/no-go memos?
- They violate regulatory requirements for launches
- They cannot be checked by AI systems
- They get rationalized away because they lack measurable thresholds
- They are too specific and limit flexibility
What does the reversibility analysis section of a go/no-go memo address?
- Whether team members can reverse their voting positions
- How easily the product launch can be undone or rolled back if it fails
- The financial reversibility of investment decisions
- Whether the launch decision can be changed after the memo is written
How can historical launch postmortems be used in AI-generated go/no-go memos?
- To predict exact future revenue outcomes
- To write the executive summary automatically
- To replace the need for kill criteria
- To populate base rates for downside scenarios
What problem does the lesson identify with momentum in launch decisions?
- Momentum ensures sufficient resources are allocated
- Momentum prevents AI from generating useful memos
- Momentum causes decisions to be made without structured analysis of risks
- Momentum leads to balanced decision-making
Which scenario represents the accountability gap in AI-generated go/no-go memos?
- The team agrees to kill criteria but ignores them three weeks later when adoption is low
- The memo lacks reversibility analysis
- AI fails to generate counterarguments
- AI generates a memo that no one reads
Why might AI-generated kill criteria miss critical production dependencies?
- AI always generates specific numerical thresholds
- AI doesn't know which dependencies are actually fragile in production
- AI cannot access production systems
- AI overestimates production risks
What is the relationship between kill criteria thresholds and rationalization?
- Only executive-approved thresholds prevent rationalization
- Specific numerical thresholds make it harder to rationalize away the criteria
- Thresholds have no impact on rationalization
- Vague thresholds make it easier to hold teams accountable
Which of the following is an appropriate use of AI in the go/no-go process?
- AI enforces kill criteria after launch
- AI drafts the memo structure including counterarguments
- AI makes the final go/no-go decision
- AI attends the executive meeting to vote
What underlying problem does the go/no-go memo process aim to solve?
- Decisions being made on momentum without structured risk analysis
- Lack of executive interest in launch decisions
- Too many launches being cancelled
- Insufficient funding for launches
What type of information should kill criteria include to enable future verification?
- Specific numbers and dates
- Qualitative descriptions of success
- General timelines without metrics
- Subjective assessments from stakeholders
What is the purpose of including explicit counterarguments in a go/no-go memo?
- To discourage teams from pursuing any launch
- To satisfy regulatory requirements
- To ensure the analysis is balanced rather than confirming existing preferences
- To replace the need for downside scenario analysis