Instantly Improve Product Roadmap Communication with These ChatGPT Prompts
Communicating roadmap changes is critical but time-consuming. Use these expert-crafted ChatGPT prompts to draft clear, concise, and empathetic updates for stakeholders, from engineering teams to executives. Save hours and ensure everyone is aligned on your product's direction.
Generate an exciting internal announcement for a new feature launch, ensuring team alignment and motivation.
Draft an internal announcement for the upcoming launch of our new feature: '[Feature Name]'. The target audience is the entire company. The goal is to inform, generate excitement, and acknowledge the teams involved. Key points to include: what the feature is, the customer problem it solves, the target launch date '[Date]', and a shout-out to the '[Engineering Team Name]' and '[Design Team Name]' teams. Keep the tone celebratory and concise.
Executive Summary: Strategic Roadmap Pivot
Create a high-level summary for leadership, clearly explaining a significant strategic shift in product direction.
Write a one-paragraph executive summary explaining a strategic pivot in our product roadmap. We are shifting focus from '[Old Initiative]' to '[New Initiative]'. Explain the 'why' behind this decision, referencing key data points like '[e.g., recent user feedback, market trend analysis, competitive pressure]'. Emphasize the expected positive impact on our primary business goal of '[e.g., increasing user retention, entering a new market segment]'. The tone should be confident and strategic.
Communicate Project Delay to Stakeholders
Craft a transparent and reassuring message to stakeholders, explaining a project delay without causing panic.
Draft an email to stakeholders announcing a delay for the '[Project Name]' project. The original launch was '[Original Date]', and the new estimated launch is '[New Date]'. Clearly state the primary reason for the delay: '[e.g., unexpected technical complexity, resource reallocation to a higher priority issue]'. Reassure them that '[e.g., quality remains our top priority, we are adding resources to mitigate further delays]'. Outline the immediate next steps we are taking. Maintain a professional and accountable tone.
Justify Technical Debt for Business Leaders
Generate a non-technical explanation and analogy for business stakeholders, justifying the prioritization of technical debt work.
Explain the importance of prioritizing work on technical debt in the next quarter. Use an analogy to help non-technical stakeholders understand the concept. For example, compare it to '[e.g., performing maintenance on a factory machine to prevent a bigger breakdown]'. Connect this work directly to business value, such as '[e.g., increasing future development speed, improving system stability, reducing bugs]'. The goal is to get buy-in for allocating '[X]% of capacity' to this initiative.
Customer-Facing Feature Release Update
Write a user-friendly blog post or update, announcing a recently shipped feature with a focus on customer benefits.
Write a short, engaging 'What's New' update for our customers about the release of '[Feature Name]'. Focus on the benefits, not just the functionality. Start with the problem it solves for them. Use bullet points to highlight 2-3 key improvements. Include a call-to-action, like '[e.g., 'Try it out now!' or 'Learn more in our help center']'. The tone should be friendly and customer-centric.
Sales Enablement: Upcoming Roadmap Features
Equip the sales team with concise talking points about upcoming features, designed to build excitement without over-promising.
Create a list of 3-5 talking points for the sales team about our upcoming Q3 roadmap theme: '[Roadmap Theme, e.g., 'AI-Powered Automation']'. For each point, describe a key feature like '[Feature 1 Name]', the customer pain point it addresses, and a concise benefit statement. Frame these as 'coming soon' to help them build excitement without over-promising on specific dates. Include a 'What NOT to say' section to avoid miscommunication.
FAQ: Controversial Feature Deprecation
Proactively prepare clear and empathetic answers for frequently asked questions about a controversial feature deprecation.
Generate a list of Frequently Asked Questions (FAQs) regarding our decision to deprecate the '[Old Feature Name]' on '[Date]'. Address the following questions: Why are you removing it? What should I use instead? What will happen to my data associated with this feature? Will I get a refund/credit? I still need this feature, what can I do? Provide clear, empathetic, and direct answers for our support team to use.
Slack: Urgent Priority Shift Notification
Draft a quick, clear Slack message for the engineering team, communicating an immediate priority shift for the current sprint.
Draft a Slack message for the #engineering channel about a priority shift. We need to pause work on '[Paused Task/Story]' to immediately address '[Urgent Task/Story]' due to '[Reason, e.g., a critical customer bug, a new competitive threat]'. Acknowledge the disruption and state that I will be updating the Jira board accordingly. Offer to sync with anyone who has questions. The tone should be direct and respectful of their focus.
Investor Update: Roadmap Progress Summary
Summarize roadmap achievements and future plans concisely for an investor newsletter or board update.
Write a section for our quarterly investor update summarizing product roadmap progress. Cover three key areas: 1) What we shipped last quarter ('[Feature A]', '[Feature B]') and the initial impact ('[Metric, e.g., 10% increase in engagement]'). 2) What we're building now ('[Current Initiative]'). 3) A high-level look at what's next ('[Future Theme]') and how it aligns with our company's strategic goals. Keep it concise, data-driven, and forward-looking.
Decline Feature Request Respectfully
Craft a respectful but firm response to a stakeholder, declining a feature request that doesn't align with the current roadmap.
Draft a response to a stakeholder who has requested '[Feature Request]'. While we appreciate the suggestion, it doesn't align with our current strategic focus on '[Current Strategy, e.g., improving core workflow performance]'. Acknowledge the value of their idea and explain that we have to make tough choices to best serve the majority of our users. Mention that we've logged their feedback for future consideration. The tone should be empathetic but firm.
Quarterly Roadmap Presentation Outline
Generate a structured outline for a comprehensive quarterly roadmap presentation to the entire company.
Create an outline for a 30-minute all-hands presentation on the upcoming quarterly product roadmap. The structure should include: 1) Recap of last quarter's successes (with key metrics). 2) The overarching theme/goal for this quarter. 3) A breakdown of the 3-4 key initiatives or epics. 4) For each initiative, explain the 'why' (customer problem) and the 'what' (the solution). 5) How this work connects to company-level OKRs. 6) Time for Q&A.
Translate Tech Update for Marketing Team
Rewrite a technical update from engineering into a clear, benefit-focused message suitable for the marketing team.
Translate the following technical update into a simple, benefit-oriented summary for the marketing team. Technical Update: 'We've finished the backend refactor of the authentication service, moving from a monolithic to a microservices architecture. This will reduce latency and improve scalability.' The summary should focus on the customer and business impact, such as faster login times and a more reliable platform, which they can use in their messaging.
Announce New Product Discovery Initiative
Inform product, design, and engineering teams about a new discovery initiative, outlining its goals and how to participate.
Draft a communication to the product, design, and engineering teams about a new discovery process we're starting for '[Problem Space, e.g., user onboarding]'. Explain the goal of this discovery phase and the key questions we want to answer. Outline the planned activities, such as '[e.g., customer interviews, prototype testing, data analysis]'. Clearly state how team members can contribute or follow along.
Pre-Mortem Brainstorming for Launch Risks
Generate a prompt to facilitate a pre-mortem session, identifying potential failure points for a major upcoming feature launch.
Act as a facilitator for a project pre-mortem. Our goal is to identify potential risks for the upcoming launch of '[Project Name]'. Start with the premise: 'Imagine it's six months from now, and the launch has failed spectacularly. What went wrong?' Generate a list of 10 potential failure points across different categories: technical, marketing, user adoption, and competitive response. This will help us brainstorm risks.
Customer Support Briefing: Upcoming Product Change
Prepare the customer support team with a concise briefing document for an upcoming product change that may generate inquiries.
Create a one-page briefing document for the Customer Support team about the upcoming change to '[Feature/Policy]'. Include: 1) A simple 'What is changing?' section. 2) 'When is it happening?'. 3) 'Why are we making this change?'. 4) A list of 3-5 anticipated customer questions with approved answers. 5) The official escalation path for issues product/engineering needs to see.
Request Company-Wide Roadmap Input
Craft a company-wide message inviting ideas and suggestions for the next roadmap planning cycle, aligned with a strategic theme.
Draft a company-wide message inviting input for our upcoming '[e.g., H2 2024]' roadmap planning. Explain that we are focusing on the strategic theme of '[Strategic Theme]'. Ask for ideas and suggestions that align with this theme. Provide a clear deadline for submissions and a link to the submission form or tool (e.g., a specific Slack channel, Aha! ideas portal, or Google Form).
Define Feature's 'Why': JTBD & Problem Statement
Write a concise 'Jobs to be Done' (JTBD) user story and a clear problem statement for a feature, enhancing development team understanding.
Write a 'Jobs to be Done' (JTBD) style user story and a clear problem statement for the feature '[Feature Name]'. The user is a '[User Persona]'. The core problem is '[Problem Description]'. The JTBD format should be: 'When [situation], I want to [motivation], so I can [expected outcome].' This will help the development team understand the user context and purpose behind the feature.
Communicate Feature Scope Reduction
Explain to the project team the strategic decision to reduce a feature's scope for an initial release, maintaining clarity and alignment.
Draft a message for the project team explaining the decision to reduce the scope of '[Feature Name]' for its v1 launch. We are deferring '[Specific Functionality]' to a later release. The reason for this is to '[e.g., hit our critical launch window, de-risk the release by focusing on the core value prop, respond to early user feedback]'. Reiterate that the core problem is still being solved and frame this as a smart, iterative approach.
Public Roadmap Update: Now, Next, Later
Write a customer-facing update for a public roadmap page, effectively using the 'Now, Next, Later' framework.
Write an update for our public roadmap page. Structure the update using three categories: Now (In Progress), Next (Coming Soon), and Later (Under Consideration). Under 'Now', list '[Feature A]' and '[Feature B]'. Under 'Next', list '[Feature C]' and '[Feature D]'. Under 'Later', list '[Idea E]' and '[Idea F]'. For each item, write a one-sentence, user-friendly description of the value it will provide.
A/B Test Internal Communication Plan
Outline a communication plan for an upcoming A/B test, ensuring all key internal stakeholders are informed and prepared.
Create a mini-communication plan for an A/B test on the '[Feature, e.g., checkout page]'. Identify the key internal stakeholders who need to be informed (e.g., Customer Support, Engineering, Marketing). For each stakeholder group, specify what they need to know, when they need to know it, and the best channel to use (e.g., Slack, email). The goal is to ensure internal teams are not surprised by user reports.
Synthesize User Feedback for Roadmap Decisions
Analyze raw user feedback, summarizing it into distinct themes to inform and prioritize roadmap decisions.
I have the following raw user feedback from interviews and support tickets: '[Paste 5-10 pieces of raw feedback here]'. Analyze this feedback and summarize it into 3-5 distinct themes. For each theme, provide a representative user quote and suggest a potential product opportunity or problem to solve. This will help me prioritize what to work on next.
Proactive Partner Comms: Breaking API Changes
Draft a clear, proactive email to technical partners, detailing upcoming breaking changes to an API and required actions.
Draft a technical partner announcement about a breaking change in our API. The change affects the '[Specific Endpoint]'. The change will go live on '[Date]'. Clearly explain what is changing, why it's necessary ('[e.g., to improve security and performance]'), and what action partners need to take. Link to the updated API documentation and provide a clear contact point for support. The tone must be clear, direct, and helpful.
Draft a company-wide email sharing key success metrics and celebrating the positive impact of a recent feature launch.
Write a company-wide email celebrating the successful launch of '[Feature Name]'. Share 2-3 key success metrics since its launch '[X weeks/months]' ago. For example: '[Metric 1: e.g., 25% adoption rate]', '[Metric 2: e.g., Reduced support tickets by 15%]', '[Metric 3: e.g., Positive customer quote]'. Thank the entire team for their hard work and connect this success back to our company goals.
Roadmap Kickoff Meeting Agenda (Dev Team)
Create a detailed 1-hour agenda for a quarterly roadmap kickoff meeting, aligning the development team on the 'why' and key initiatives.
Generate a meeting agenda for a 1-hour quarterly roadmap kickoff with the engineering and design team. The goal is to align everyone on the 'why' behind the work. Include time slots for: (1) Welcome & Goal of the Meeting, (2) Quick Review of Last Quarter's Impact, (3) Presenting the New Quarter's Theme and OKRs, (4) Deep Dive into the 2-3 Key Epics, (5) Open Q&A and Discussion, (6) Next Steps. For each agenda item, add a brief description.
Reframe Feature 'No' to 'Not Yet'
Transform a hard 'no' on a feature request into a 'not yet', preserving a positive relationship with the stakeholder.
Rewrite this response from a 'no' to a 'not yet'. Original response: 'We will not be building the custom reporting feature this year.' The stakeholder is '[Stakeholder Role, e.g., Head of Sales]'. The new response should acknowledge the importance of their request, explain that our current focus is on '[Current Priority, e.g., platform stability]', and frame their request as something we are keen to explore in a future planning cycle once the current priorities are addressed.
Turn these prompts into a reusable workspace
Save your favourite prompts once, reuse them with Alt+P, keep a live Table of Contents of long chats, and export conversations when you're done.
