Resolve conflicting roadmaps with trade-off framing

Evaluate competing roadmap priorities across departments using a structured trade-off framework that identifies compromises and executive escalation paths.

You getConflict Diagnosis, comparison Matrix and recommended Path and Rationale

Prompt

Prompt
Act as an executive product strategist. Analyze the conflicting priorities and roadmap proposals pasted below between competing teams, and construct an objective trade-off evaluation.

Rules:
- Identify root causes of conflict (e.g., shared dependencies, opposing KPI incentives, resource constraints).
- Propose three realistic sequencing options: Favor Team A, Favor Team B, and a Hybrid compromise.
- Evaluate each option across revenue impact, technical debt risk, and time-to-market.

Output format:
- Conflict Diagnosis (summary of competing incentives)
- Comparison Matrix (table comparing the 3 sequencing options across Impact, Risk, Effort, and Trade-offs)
- Recommended Path and Rationale (clear recommendation with mitigations)
- Executive Escalation Brief (5-sentence briefing note for leadership if teams remain deadlocked)

Here are the conflicting roadmaps and constraints:

Example output

Example for: Growth Team wants self-serve checkout vs Platform Team wants database sharding

Conflict Diagnosis

The Growth Team is incentivized on Q3 new customer conversion and wants instant checkout enhancements. The Platform Team is incentivized on system uptime and must complete database sharding before anticipated Black Friday traffic spikes. The conflict stems from shared senior backend engineer capacity.

Comparison Matrix
OptionRevenue ImpactTech Debt RiskEffortCore Trade-off
1. Prioritize GrowthHigh short-term ($400k ARR)Critical; risks multi-hour outages in Q46 weeksGains top-line sales but endangers Black Friday stability.
2. Prioritize PlatformNeutral short-termLow; establishes scalable cluster8 weeksSecures stability but forfeits Q3 conversion target.
3. Hybrid SequencingModerate ($220k ARR)Managed; core sharding delivered7 weeksGrowth builds client-side UX; platform completes sharding backend first.
Recommended Path and Rationale

Adopt Option 3 (Hybrid Sequencing). Have Growth decouple the checkout redesign from database writes by using hosted Stripe components for six weeks. This protects 80% of Platform's sharding timeline while capturing immediate checkout funnel improvements.

Executive Escalation Brief

Growth and Platform are currently deadlocked over backend capacity for Q3. Growth's checkout overhaul projects $400k ARR, while Platform's sharding prevents critical failure during Q4 peak volume. Delaying Platform completely introduces unacceptable operational risk during our highest-grossing period. We recommend a phased hybrid model that frees Growth to build frontend improvements while preserving backend capacity for sharding. If leadership requires an absolute priority, we request an explicit trade-off approval between Q3 conversion and Q4 stability.

Written by AI from this prompt. Your results will vary.

Paste the competing team proposals, goals, and constraints directly after the prompt in ChatGPT or Claude. Ask the model to revise the criteria if company-wide OKRs prioritize cost savings over delivery speed.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Leadership & Management