Turn a chaotic debate into decision options

Synthesize messy meeting transcripts or heated Slack arguments into neutral, structured trade-off options for executive sign-off.

You getCore Dilemma, decision Options Matrix and trade-off Comparison

Prompt

Prompt
Act as a neutral executive decision facilitator. Analyze the discussion notes below and structure the debate into distinct decision pathways.

Rules:
- Neutralize emotional language, accusations, and conversational tangents.
- Frame the conflict as 2 to 3 distinct, viable options.
- For each option, clearly present pros, cons, unstated risks, and required commitments.
- State what evidence or metric would prove each option was the correct choice.

Output format:
1. Core Dilemma (1 sentence stating the root trade-off)
2. Decision Options Matrix (for each option: Name, Description, Pros, Cons, Hidden Risks, Reversibility: Low/Med/High)
3. Trade-off Comparison (table: Option | Cost | Speed to Deliver | Strategic Risk)
4. Recommended Next Step (a concrete proposal on how to reach consensus or run a spike)

My meeting notes are below:

Example output

Example for: engineering debate on rewriting the analytics pipeline vs. patching legacy software

  1. Core Dilemma
    Choose between short-term stability with ongoing maintenance debt or a multi-quarter rewrite that risks shipping roadmap delays.
  2. Decision Options Matrix
    Option A: Incremental Refactor of Legacy Pipeline
  • Description: Patch existing database queries, optimize indexes, and add alerting while keeping the core monolith intact.
  • Pros: Fast implementation (3 weeks); zero disruption to Q3 product deliverables.
  • Cons: Does not solve query latency caps above 10,000 concurrent events.
  • Hidden Risks: Staff burnout from maintaining brittle, undocumented legacy code.
  • Reversibility: High

Option B: Dedicated Green-Field Service Rewrite

  • Description: Build a modern event-streaming service in parallel over the next 4 months.
  • Pros: Scales linearly for 3 years; reduces monthly infrastructure spend by 35%.
  • Cons: Pulls two senior engineers off all customer-facing feature development.
  • Hidden Risks: Timeline slippage during dual-run data reconciliation.
  • Reversibility: Low
  1. Trade-off Comparison
OptionCostSpeed to DeliverStrategic Risk
A: Incremental RefactorLow engineering cost, high cloud spend3 weeksHits architectural wall in 6 months
B: Full Service RewriteHigh engineering cost, low cloud spend16 weeksDelays core product launch timeline
  1. Recommended Next Step
    Run a 5-day technical spike on Option A to see if index caching meets minimum latency SLAs for Q4. If it passes, defer Option B to next year's budget cycle.
Written by AI from this prompt. Your results will vary.

Paste your messy meeting notes, debate transcripts, or multi-person discussion into ChatGPT, Claude or Gemini. You can follow up by asking the model to evaluate the options using a one-way vs. two-way door framework.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Meetings & Notes