Prepare Roadmap Review Talking Points for a Board Meeting
Generates talking points for a board-level roadmap review, including narrative arcs, data points, and likely questions. Built for product leaders preparing for high-stakes quarterly board meetings.
When to use this prompt
Use this when preparing for a board-level roadmap review. You will need the current roadmap, recent metric movement, upcoming strategic bets, and any context on board members' prior concerns. The prompt structures your message around 3 narrative arcs rather than a dense feature list, because boards respond to story more than detail. It also pre-generates likely questions so you are not caught flat-footed. It is not a substitute for strategic thinking; it is a structuring tool for the thinking you have already done. If you have not decided what matters, the prompt cannot decide for you.
The Prompt
You are a VP of Product preparing talking points for a board-level roadmap review. The structure must anchor around 3 narrative arcs and anticipate likely board questions. Company stage: {{company_stage}} Quarter recap: {{quarter_recap}} Current roadmap: {{current_roadmap}} Key metrics: {{key_metrics}} Strategic bets: {{strategic_bets}} Known board concerns from last meeting: {{prior_concerns}} Produce the talking points in this structure: 1. OPENING (60 seconds) â One paragraph answering: "Where are we now?" Include 2-3 concrete numbers. End with a sentence that frames the roadmap discussion. 2. ARC 1: WHERE WE ARE â Summary of the last quarter's progress against the plan. For each major bet: stated goal, result, lesson learned. Be honest about misses. 3. ARC 2: WHAT WE ARE DOING NEXT â Next quarter's plan in 3-4 bullets. Each bullet should connect a customer problem to the work being done. Include rough resource allocation. 4. ARC 3: WHAT WE ARE BETTING ON (12-18 month view) â The 1-2 strategic bets that will define the next year. For each bet: hypothesis, evidence so far, what would prove it wrong, and what success looks like. 5. ANTICIPATED QUESTIONS â 5-7 questions the board is likely to ask, each with a 2-3 sentence draft answer. Include at least 2 hard questions ("why are you missing X" or "are we over-invested in Y"). Do not duck them. 6. THE ASK (if any) â What the board is being asked to approve or discuss. If this is informational only, state that explicitly. Tone rules: - Honest about misses. Boards lose trust fast in leaders who spin. - Specific numbers over vague trends. - Connect every feature to a customer or business outcome. - Do not end with "any questions?" â end with the specific ask or discussion point.
Example Output
OPENING: We ended Q1 at 18 percent ARR growth quarter-over-quarter with gross retention steady at 92 percent. The product surfaced two validated signals: SMB customers want faster onboarding, and mid-market customers want deeper integrations. Our Q2 roadmap is built around those two pulls. ARC 1: WHERE WE ARE - Q1 bet on rewrite of onboarding. Goal: reduce time-to-first-value from 12 to 6 days. Result: 8 days in beta, shipping to GA this week. Lesson: the remaining friction is integrations, not UX. - Q1 bet on mobile app. Goal: 10k MAUs. Result: 6k MAUs, under plan. Lesson: we under-invested in ASO and push notifications; Q2 will course-correct. - Q1 bet on AI drafting feature. Goal: validate demand. Result: 35 percent of trial users try it, 80 percent of those convert. Strong signal, expanding in Q2. ARC 2: WHAT WE ARE DOING NEXT - Ship 3 integrations mid-market customers requested (40 percent of eng). - Double down on AI drafting with a premium tier (25 percent of eng). - Fix mobile growth with redesigned ASO and push flows (20 percent of eng). - Pay down onboarding tech debt uncovered during Q1 rewrite (15 percent of eng). ARC 3: STRATEGIC BETS - Bet 1: AI drafting becomes our primary upsell path within 18 months. Hypothesis: power users will pay 3x for AI features. Evidence: 80 percent conversion from trial. What would prove it wrong: conversion under 30 percent at full funnel. Success: 20 percent of paid users on AI tier. ANTICIPATED QUESTIONS - Q: Why did mobile miss plan? A: We underestimated ASO investment and pushed launch before push notifications were ready. We have dedicated 3 engineers to the fix in Q2 and expect to hit plan by end of quarter. - Q: Are we over-invested in AI? A: Currently 25 percent of eng time. Evidence says the bet is working at the trial level; we will pull back if conversion at full funnel disappoints. THE ASK: Informational discussion, no vote required.
Recommended Tools
Google Workspace (Docs and Slides) is the standard for board materials and supports commenting from board members before the meeting. Notion projects works when the board is internal and prefers web-native docs. Aha provides roadmap views purpose-built for board-level presentation with strategic-initiative grouping. Use Aha for the visual roadmap artifacts and Docs for the narrative talking points.
Frequently Asked Questions
When should I use this prompt?
Use it 1-2 weeks before a board meeting, not the day before. The value is in preparing for the hard questions, and the 'anticipated questions' section is only useful if you have time to rehearse answers and gather supporting data. Do not use it for informal investor updates where a simpler email format is better. Reserve it for the 2-4 times a year when you are in front of your board with the full roadmap on the table. For monthly investor updates, prompt 22 (weekly exec update) scaled up is usually enough.
How do I handle hard questions about misses?
The prompt explicitly forces you to include at least 2 hard questions in the anticipated list. Use that discipline. When the board asks a hard question, the best answer is: acknowledge the miss clearly, explain the specific reason (not 'we underestimated'), describe what you learned, and commit to a specific correction with a deadline. Do not defend, do not spin, do not promise to recover lost time. Boards trust leaders who can say 'this is what happened and this is what we changed' more than leaders who avoid the question.