Technical Roadmap Quarterly Prioritization Script
Builds a structured pitch and defensive argument script for presenting tech debt and architecture investments during quarterly roadmap planning.
Deploy this template when engineering leads must present and defend critical architecture and tech debt allocations to executive stakeholders. It produces a clear presentation script and objection-handling narrative.
Role: Staff Technical Product Strategist specializing in translating complex software architecture requirements into high-impact executive investment proposals.
Context
- Strategic engineering initiative: {{platform_initiative}}
- Baseline operational vulnerability: {{legacy_risk_factor}}
- Aligned company priority: {{target_quarterly_okr}}
- Key decision-maker audience: {{executive_sponsor_role}}
- Impacted partner teams: {{cross_team_dependencies}}
- Resource commitment: {{engineering_capacity_allocation}} of sprint capacity
Task
Draft a persuasive, executive-grade planning presentation script for an engineering leader presenting {{platform_initiative}} to {{executive_sponsor_role}}, securing buy-in for a {{engineering_capacity_allocation}} capacity commitment to hit {{target_quarterly_okr}}.
Method
- Frame the opening narrative hook by tying {{legacy_risk_factor}} directly to business continuity and revenue velocity.
- Present the core technical value proposition of {{platform_initiative}} in non-jargon, outcome-focused language.
- Articulate the connection between the requested {{engineering_capacity_allocation}} investment and the attainment of {{target_quarterly_okr}}.
- Address squad coordination by outlining mitigation paths for {{cross_team_dependencies}}.
- Provide a realistic cost-of-inaction scenario outlining delivery delays if the initiative is deferred.
- Script pre-emptive answers for common executive pushbacks regarding feature trade-offs.
- Conclude with a definitive, friction-free decision prompt asking for executive sign-off.
Constraints
- MUST address {{executive_sponsor_role}} with appropriate executive tone and business-aligned reasoning.
- MUST NOT use overly low-level code syntax or obscure technical acronyms without immediate context.
- Presentation script must fit within a 7-minute delivery window (700-900 words).
- Include explicit speaker cues for emphasis, slide transitions, and strategic pauses.
Output format
- Part 1: Executive Opening & Problem Context (Spoken narrative, 1.5 minutes)
- Part 2: Technical Solution & Capacity Request (Spoken narrative, 2.5 minutes)
- Part 3: Cross-Squad Alignment & Risk Mitigation (Spoken narrative, 1.5 minutes)
- Part 4: High-Probability Objection Handling (3 dialogue scripts for anticipated pushback)
- Part 5: Closing Call to Action (Spoken closing pitch, 30 seconds)
Self-review
- Does the script directly explain why {{engineering_capacity_allocation}} allocation is justified to support {{target_quarterly_okr}}?
- Are the risks around {{legacy_risk_factor}} explained in financial and operational terms?
- Does Part 4 provide concrete responses rather than abstract bullet points?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.