Roadmap Prioritizer: 90-Minute Podcast
The Roadmap Prioritizer: 90-Minute Podcast prompt helps expert Product Managers and Strategic Consultants transform feature ideas, requirements, and business goals into a structured, high-impact 90-minute roadmap podcast script.
What is the Roadmap Prioritizer: 90-Minute Podcast prompt?
Copy the prompt below into ChatGPT, Gemini, Claude or any capable LLM, replace the bracketed variables with your own values, and run it.
ROLE: You are an expert Product Manager and Strategic Consultant specializing in ruthlessly efficient roadmap prioritization and executive decision-making. Your expertise lies in balancing technical debt, user growth, and business revenue within a high-speed development environment. GOAL: Your objective is to ingest a collection of feature ideas, technical requirements, and business goals to generate a structured, high-impact 90-minute roadmap podcast script. This script will serve as an internal alignment tool, explaining the "why" behind the "what" for the upcoming quarter. CONTEXT: Information provided: - PRODUCT VISION: [PRODUCT VISION] - FEATURE LIST/BACKLOG: [FEATURE LIST] - RESOURCES/CONSTRAINTS: [RESOURCES] - TARGET KPI: [PRIMARY KPI] - TIMELINE: [QUARTER/YEAR] INSTRUCTIONS: 1. Analysis: Review [FEATURE LIST] and categorize items using the RICE (Reach, Impact, Confidence, Effort) framework or MoSCoW method. 2. Prioritization: Select the top 3-5 features that most directly influence [PRIMARY KPI] while remaining within [RESOURCES]. Defend why lower-priority items are being deferred. 3. Narrative Arc: Structure the response as a podcast script between two hosts: "The Strategist" (focused on business/market) and "The Builder" (focused on engineering/UX). 4. Content Flow: - Intro: State the [PRODUCT VISION] and the current market landscape for [TIMELINE]. - The Big Wins: Deep dive into the top 3 priorities, explaining the data-driven rationale for each. - The Hard Choices: Explicitly discuss what is NOT being built and why those trade-offs were made. - The Execution: Discuss how [RESOURCES] will be allocated to ensure delivery. - Outro: A rallying call to the team regarding the impact on the [PRIMARY KPI]. OUTPUT FORMAT: The output must be a narrative podcast script. Include speaker names and brief emotional cues (e.g., [Host A, with excitement]). Use conversational but professional language. Avoid generic corporate jargon; focus on specific outcomes related to [FEATURE LIST]. QUALITY BAR: The final script must provide a clear sense of direction and resolve potential team friction by providing logical, evidence-based justifications for every roadmap decision. It must sound like a real, high-stakes strategy session, not a list of bullet points. Ensure the transition between "The Strategist" and "The Builder" highlights the balance between innovation and technical feasibility.
What variables does the Roadmap Prioritizer: 90-Minute Podcast prompt use?
| Variable | What to put | Example |
|---|---|---|
| [PRODUCT VISION] | A concise statement of the product's long-term goal and customer value proposition. | e.g. To be the leading AI companion for creative professionals, enhancing ideation and output while reducing mental block. |
| [FEATURE LIST] | A bulleted or numbered list of proposed features, technical requirements, and backlog items. | e.g. - AI-powered article summarization - Collaborative real-time editing - Dark mode UI option - Improved API stability for integrations - Database migration to PostgreSQL |
| [RESOURCES] | Key constraints and available resources (e.g., team size, budget, time). | e.g. 10 engineers, 3 designers, 1 QA for Q3; fixed budget for cloud credits; no major holidays planned. |
| [PRIMARY KPI] | The main performance indicator that the prioritized roadmap aims to impact. | e.g. Monthly Active Users (MAU) growth by 20% |
| [TIMELINE] | The specific quarter and year for which the roadmap is being planned. | e.g. Q3 2024 |
How do I use the Roadmap Prioritizer: 90-Minute Podcast prompt?
- 1Step 1: Gather your product vision, a comprehensive list of features/backlog items, available resources/constraints, your primary KPI, and the target timeline.
- 2Step 2: Replace the bracketed placeholders in the prompt body with your specific information. Be as detailed as possible, especially for [FEATURE LIST] and [RESOURCES].
- 3Step 3: Submit the prompt to your chosen AI model (GPT-4o, Gemini Pro, or Claude Sonnet are recommended).
- 4Step 4: Review the generated podcast script. Edit for accuracy, tone, and any missing details, ensuring it genuinely reflects your unique product strategy and team context.
When should you use the Roadmap Prioritizer: 90-Minute Podcast prompt?
Quarterly Planning & Alignment
Use it to articulate the strategic rationale behind your product roadmap decisions to internal teams and stakeholders, fostering clarity and alignment.
Executive Communication
Prepare a compelling, narrative-driven presentation for leadership that defends prioritization choices and links them directly to business goals.
Team Morale & Understanding
Provide engineering, design, and marketing teams with a clear 'why' behind the 'what,' addressing potential concerns about deferred features.
Strategic Review Meetings
Structure a high-level discussion on upcoming product initiatives, ensuring all angles (business, technical, user) are covered systematically.
Onboarding New Leaders
Offer new product or engineering leaders a condensed yet comprehensive overview of current strategic priorities and historical decision-making.
What does the Roadmap Prioritizer: 90-Minute Podcast prompt output look like?
The Strategist: (Upbeat, confident) Welcome back to 'The Product Pulse,' your deeper dive into what's driving our innovation. Today, we're dissecting our Q3 2024 roadmap, aimed squarely at accelerating our Monthly Active Users by a crucial 20%, cementing our vision to be the leading AI companion for creative professionals. The Builder, great to have you here to unpack how we'll make this happen. The Builder: (Thoughtful, pragmatic) Always a pleasure, Strategist. For Q3, we’re laser-focused on three core initiatives. Our top priority is 'AI-powered Article Summarization.' This isn't just a new feature; it's about solving a fundamental pain point for our users: information overload. Engineering has projected a significant reduction in content consumption time, which directly correlates to engagement. We're dedicating 4 engineers to this, targeting a late August beta launch. The Strategist: That's a strong start. It directly aligns with our user value proposition. What’s next for significant impact? The Builder: Our second 'big win' is 'Collaborative Real-time Editing.' While it sounds like a table-stakes feature, the data shows a clear demand from our pro-tier users for team-based ideation. This project, which will take 3 engineers, is expected to increase team adoption and retention. We've optimized the backend architecture to support concurrent editing efficiently, building on the stability work from last quarter. The Strategist: Excellent. And our third priority, where are we putting our remaining muscle?
Which AI model works best with the Roadmap Prioritizer: 90-Minute Podcast prompt?
Excels at nuanced narrative generation, role-playing, and integrating complex data points into a cohesive, conversational script, handling the RICE/MoSCoW analysis robustly.
Strong in structuring detailed, multi-part outputs and maintaining a consistent tone across different speaker roles, making it ideal for the podcast format.
Proficient in generating extensive, high-quality text, following intricate instructions for content flow and quality bar, and producing professional, jargon-free explanations.
What are the pros and cons of the Roadmap Prioritizer: 90-Minute Podcast prompt?
Pros
- Generates a multi-perspective podcast script for transparent roadmap communication.
- Forces data-driven prioritization using RICE/MoSCoW analysis (even if simulated).
- Explains 'why' behind decisions, reducing potential team friction.
- Adopts professional yet conversational tone and specific roles.
- Clearly links features to business goals (KPIs) and resource allocation.
- Provides a comprehensive internal alignment tool.
Cons
- Requires substantial input for effective prioritization (e.g., realistic feature list details).
- The AI's 'analysis' of RICE/MoSCoW is simulated; human oversight is crucial.
- Output length can be significant, potentially requiring multiple iterations or larger context windows.
- May struggle to accurately simulate complex emotional cues without explicit examples.
How can you get better results from the Roadmap Prioritizer: 90-Minute Podcast prompt?
- Provide specific RICE scores or MoSCoW categorizations within the [FEATURE LIST] for more precise prioritization.
- Detail any interdependencies or specific technical challenges within [FEATURE LIST] or [RESOURCES] for a more realistic 'Builder' perspective.
- If the initial output is too generic, reiterate with examples of desired conversational style or specific product insights.
- Specify the 'vibe' of each host (e.g., 'The Strategist: Analytical but inspiring', 'The Builder: Practical and detail-oriented').
- For complex backlogs, break down the [FEATURE LIST] into smaller, themed groups to help the AI focus its analysis.
- Request a brief summary of the RICE/MoSCoW analysis before the podcast script to check the AI's understanding.
Frequently asked questions about the Roadmap Prioritizer: 90-Minute Podcast prompt
What is the Roadmap Prioritizer: 90-Minute Podcast prompt?
It's a prompt designed to help product managers and strategists create a podcast script that explains and justifies their product roadmap. It simulates a conversation between two expert hosts, covering prioritization, trade-offs, and execution.
Who is this prompt for?
This prompt is ideal for Product Managers, Product Leaders, Strategic Consultants, and anyone responsible for communicating product strategy and gaining internal alignment on quarterly or annual roadmaps.
How does the prompt handle prioritization?
It uses the RICE (Reach, Impact, Confidence, Effort) framework or MoSCoW (Must, Should, Could, Won't) method to analyze and prioritize features. The AI simulates this analysis to select and defend top priorities.
Can I customize the podcast hosts?
Yes, while the default roles are 'The Strategist' and 'The Builder,' you can describe specific characteristics or even rename them in your instructions to tailor the output to your preferences.
What if my feature list is very long?
For very long lists, consider providing a pre-filtered list or breaking it into thematic groups. The AI works best with focused inputs, though high-context models can handle larger inputs.
How can I ensure the script sounds authentic?
Provide specific details in your inputs, especially about the product, market, and team culture. You can also specify desired conversational nuances or provide examples of phrases you want used or avoided.