Prompt Library
Instantly Draft Clear Product Roadmap Communications with ChatGPT
Communicating roadmap updates is critical but time-consuming. Use these expert ChatGPT prompts to instantly draft clear, concise, and empathetic announcements for stakeholders, engineering teams, and customers. Save hours and ensure everyone is aligned on what's next.
Add ChatBoost to ChromeSave these prompts into ChatBoost and reuse them with Alt+P.
Prompt Library (27)
27 PromptsFree
Generate High-Level Roadmap Announcement Email
Generate a concise, high-level announcement for an upcoming quarter's product roadmap to share with the entire company.
Generate a concise company-wide email announcing the product roadmap for the upcoming quarter, [Q# YYYY]. The key themes are: 1. [Theme 1: e.g., 'User Onboarding Overhaul'], 2. [Theme 2: e.g., 'Performance & Scalability'], and 3. [Theme 3: e.g., 'AI-Powered Insights']. For each theme, briefly explain the 'why' behind it and the expected customer value. Keep the tone optimistic and forward-looking.
Compose Stakeholder Update for Feature Delay
Compose a clear and empathetic message to inform stakeholders about a delay in a key feature release.
Draft a professional update for key stakeholders (executives, sales, marketing) regarding the delay for the feature '[Feature Name]'. The original release date was [Original Date], and the new target is [New Date]. Explain the reason for the delay ([e.g., 'unforeseen technical complexity in integrating with a third-party API']) and outline the mitigation plan ([e.g., 'we've allocated two additional senior engineers to the project']). Reassure them about our commitment to quality.
Build Case for New Strategic Initiative
Generate a compelling narrative to justify the addition of a major new initiative to the product roadmap.
Generate a compelling justification document for adding the new strategic initiative '[Initiative Name]' to the [Roadmap Period, e.g., 'H2 2024'] roadmap. Include the following sections: 1. Problem Statement (what customer/business problem does this solve?), 2. Proposed Solution (a high-level overview), 3. Business Impact (e.g., 'projected to increase user retention by 15%'), 4. Market Opportunity (reference [Competitor A] or [Market Trend]), and 5. High-Level Resource Ask.
Explain Feature Reprioritization to Team
Compose a memo explaining why one feature has been prioritized over another, focusing on the strategic reasoning.
Compose an internal memo for the product and engineering teams explaining a roadmap reprioritization. We are moving '[Feature A]' ahead of '[Feature B]'. Explain that this decision is based on [e.g., 'recent customer feedback from our top 10 enterprise accounts and a new competitive threat']. Acknowledge the hard work already done on [Feature B] and clarify that it is now slated for [New Quarter/Timeline].
Write Customer-Facing Roadmap Teaser
Generate a snippet for a public blog post teasing upcoming features and themes from the roadmap.
Compose a friendly and exciting blog post section titled 'What's on the Horizon?' for our customers. Tease three upcoming features or improvements from our roadmap: 1. [Feature 1 Name and brief benefit], 2. [Feature 2 Name and brief benefit], 3. [Improvement Area, e.g., 'a major performance boost for large datasets']. Avoid specific dates, using phrases like 'in the coming months' or 'later this year'. The tone should be customer-centric and build anticipation.
Build Internal FAQ for Roadmap Shifts
Create a list of frequently asked questions and answers to proactively address team concerns about roadmap shifts.
A significant change has been made to our product roadmap: [Describe the change, e.g., 'we are pausing the development of the mobile app to focus on core web platform features']. Generate an internal FAQ document for employees to address potential questions. Include questions like: 'Why was this change made?', 'What does this mean for the mobile team?', 'Will we ever build the mobile app?', 'How does this affect our company goals?', and 'Where can I ask more questions?'. Provide clear, transparent answers for each.
Communicate Feature Scope Reduction to Team
Communicate a decision to reduce a feature's scope for an MVP release, framing it as a positive strategic choice.
Compose a Slack message for the engineering team about the feature '[Feature Name]'. We've decided to reduce its scope for the initial release by removing [Specific functionality]. Frame this as a strategic decision to '[e.g., get the core value into customers' hands faster and gather real-world feedback].' Emphasize that the removed functionality is now planned for a V2 fast-follow release. Thank the team for their adaptability.
Develop Sales Talking Points for Roadmap
Create a set of clear, concise talking points for the sales team to use when discussing the future roadmap with prospects.
Generate a 'safe-harbor' list of talking points for the sales team about our upcoming product roadmap. For each of the following initiatives, provide a customer-benefit-oriented one-liner they can share with prospects. Initiatives: 1. [Initiative A], 2. [Initiative B], 3. [Initiative C]. Include a clear disclaimer at the top that roadmaps are subject to change and these are not commitments.
Draft Customer Email for Feature Deprecation
Compose a sensitive and helpful email to customers announcing that a feature will be deprecated and removed.
Compose a sensitive and helpful email to all users announcing the deprecation of the '[Feature Name]' feature, effective [Date of Removal]. Start by acknowledging the feature's past utility. Explain clearly why it's being removed ([e.g., 'low usage and high maintenance cost, preventing us from building new, more valuable features']). Offer a workaround or alternative solution ([e.g., 'You can achieve a similar outcome by using our new reporting dashboard']). Provide a link to a support article with more details.
Structure Roadmap All-Hands Presentation Script
Outline a script for a 15-minute presentation at a company all-hands meeting to walk through the next quarter's roadmap.
Generate a presentation script outline for a [Duration, e.g., '15-minute'] company all-hands segment on the [Quarter, e.g., 'Q3'] product roadmap. The structure should be: 1. (2 min) Intro: Briefly recap last quarter's wins. 2. (3 min) Our North Star: Reiterate our main product goal for the year. 3. (8 min) Q3 Themes: Detail the 3 key themes ([Theme 1], [Theme 2], [Theme 3]), explaining the 'why' and customer impact for each. 4. (2 min) Q&A Prep: Suggest 2-3 likely questions and draft concise answers.
Respond to Customer Feature Request Status
Draft a polite and transparent response to a customer asking why their requested feature is not on the public roadmap.
A customer has asked why their feature request, '[Requested Feature]', is not on our roadmap. Draft a thoughtful and empathetic reply. Acknowledge their great idea and thank them for the feedback. Explain our prioritization process briefly (e.g., 'we focus on initiatives that solve the most common problems for the broadest set of users'). While we can't commit to building it now, confirm that their feedback is logged and will be considered in future planning cycles.
Compose Kick-off Email for New Roadmap Theme
Compose an email to kick off a new major development theme, inspiring the cross-functional team.
Draft an internal kick-off email for a new roadmap theme: '[Theme Name]'. The audience is the dedicated cross-functional team (product, design, engineering, marketing). The email should: 1. State the mission and vision for this theme. 2. Define the key problem we are solving for the user. 3. List the high-level success metrics (e.g., 'increase feature adoption by 20%'). 4. Announce the date/time for the official kick-off meeting. The tone should be motivational and create a sense of shared purpose.
Explain Tech Debt Initiative to Non-Tech Stakeholders
Justify a roadmap initiative focused on paying down technical debt to non-technical stakeholders.
Explain a new roadmap item, 'Platform Modernization Initiative', to non-technical stakeholders. Avoid jargon. Use an analogy, like 'upgrading the foundation of our house so we can build new rooms faster and more safely in the future.' Explain the business benefits: 1. Increased development velocity for future features. 2. Improved site reliability and performance. 3. Enhanced security. State the expected duration is [e.g., 'one full development cycle'].
Create In-App Notification for New Feature
Compose a concise and compelling in-app notification to announce a newly launched feature from the roadmap.
Compose concise and compelling copy for an in-app notification announcing our new feature, '[Feature Name]'. Include a catchy headline (e.g., 'Introducing [Feature Name]!'), a one-sentence benefit-driven description (e.g., 'Now you can automatically sync your calendar in seconds.'), and a clear call-to-action button (e.g., 'Try it Now' or 'Learn More'). Keep the total character count under 150.
Generate Engineering-Focused Roadmap Summary
Create a technical-focused summary of the quarterly roadmap for the engineering department.
Summarize the [Quarter, e.g., 'Q4'] product roadmap for the engineering team. Focus on the technical implications and known challenges. For each of the three main epics ([Epic 1], [Epic 2], [Epic 3]), briefly describe the user story, but then elaborate on the expected technical scope, potential dependencies on other teams or services, and any known risks we need to de-risk early.
Develop Marketing Brief for Feature Launch
Draft a brief for the marketing team about a feature coming off the roadmap and into a launch cycle.
Compose a marketing brief for the upcoming launch of '[Feature Name]', which is currently in the final stages of development. Include: 1. Target Audience: [e.g., 'Power users in enterprise accounts']. 2. Key Benefit: [e.g., 'Saves an average of 3 hours per week on manual reporting']. 3. Top 3 Talking Points: [List three concise points]. 4. Suggested Launch Tier: [e.g., 'Major announcement with blog post and webinar']. 5. Target Launch Date: [Date].
Report Feature Scope Increase to Leadership
Communicate to leadership that a feature's scope has increased and explain the impact on the timeline.
Draft an update for the leadership team regarding '[Feature Name]', communicating a critical requirement discovered during development that necessitates an increase in scope. This will impact the timeline, pushing the release from [Old Date] to [New Date]. Explain why this is necessary for the feature's success and the risk of not doing it. Reiterate the value proposition of the feature with the added scope.
Compose 'Year in Review, Year Ahead' Summary
Generate a summary of last year's roadmap achievements and a high-level look at next year's strategic direction.
Generate a 'Year in Review, Year Ahead' blog post section. For the 'Year in Review', list our top [Number] most impactful feature releases from last year's roadmap and the value they delivered. For the 'Year Ahead', introduce our high-level strategic theme for the new year, which is '[e.g., 'Deepening Integration and Automation']', and give a sneak peek at one or two initiatives that support this theme. Keep the tone celebratory and visionary.
Share Post-Launch Learnings & Results
Draft an internal update after a major roadmap item has launched, sharing results and learnings.
Compose an internal announcement sharing the results of the '[Feature Name]' launch, which was a key [Roadmap Period, e.g., 'Q1'] roadmap item. Share key success metrics ([e.g., '25% adoption rate in the first month, exceeding our 15% goal']). Also, share one key learning ([e.g., 'We learned that our onboarding for this feature needs to be more interactive']). Thank all the teams involved for their hard work.
Justify 'Fast Follow' Release Strategy
Explain to stakeholders why a feature is being released with a minimal scope, to be followed by rapid enhancements.
Create a short explanation for stakeholders on our 'fast follow' release strategy for '[Feature Name]'. Explain that we are launching a core MVP to [e.g., 'validate our primary hypothesis and capture market timing']. Immediately following this, our roadmap includes two 'fast follow' releases in the subsequent sprints to add [Enhancement A] and [Enhancement B]. This approach reduces risk and allows us to build based on real user data.
Request Roadmap Input from Stakeholders
Draft a message to internal teams or customers asking for input for the next roadmap planning cycle.
Compose an email to [Target Audience: e.g., 'our customer advisory board' or 'all internal employees'] to solicit input for our [Roadmap Period, e.g., 'H2 2024'] roadmap planning. Explain that we are gathering ideas and feedback to shape our future priorities. Ask them to submit their top challenges or feature ideas via [Method: e.g., 'this Google Form' or 'our #feedback Slack channel'] by [Date]. Thank them for helping build a better product.
Explain Persona Shift in Roadmap Focus
Explain a roadmap shift that de-prioritizes features for one user persona to focus on another.
Write an internal strategy update explaining a shift in our product roadmap's focus. For the next [Number] quarters, we will be prioritizing features for the '[New Target Persona, e.g., 'Enterprise Admin']' over the '[Old Persona, e.g., 'Individual Contributor']'. Justify this shift based on [Business Reason, e.g., 'our company's strategic move upmarket and higher LTV of enterprise accounts']. Acknowledge this is a change and explain how we will continue to support our existing [Old Persona] users.
Create Public Roadmap Disclaimer Statement
Generate a clear and friendly 'safe harbor' statement to include on a public-facing roadmap page.
Generate a clear and friendly 'safe harbor' or disclaimer statement for our public roadmap page. It should be friendly but legally sound. Explain that the roadmap represents our current product direction but is not a commitment. State that priorities can change based on customer feedback and market conditions, and that the timing of releases is subject to change. Encourage readers to check back for the latest updates.
Summarize Roadmap Changes for Executives
Create a one-paragraph executive summary of recent, significant changes to the product roadmap for a board update.
Compose a single-paragraph executive summary of recent, significant changes to the product roadmap for a board of directors update. The key changes are: 1. The '[Project Alpha]' launch has been accelerated due to competitive pressure. 2. The '[Project Beta]' has been postponed to Q4 to allocate resources to Alpha. 3. A new discovery track for '[New Tech, e.g., Generative AI]' has been added. Frame these changes as decisive actions to capitalize on market opportunities and mitigate risks.
Onboard New Hire to Product Roadmap
Generate a concise welcome message for a new hire, providing them with an overview and links to the current product roadmap.
Draft a concise welcome message for a new team member, [New Hire Name], to be posted in our team channel. The message should briefly introduce them and then provide a quick orientation to our product roadmap. Include links to: 1. Our high-level public roadmap. 2. Our detailed internal roadmap in [Tool, e.g., Jira or Asana]. 3. The strategy document that outlines our goals for the year. Encourage them to ask any questions.
Convert Roadmap Initiative to User Story
Convert a high-level roadmap initiative into a clear, actionable user story format for the development team.
Translate the following high-level roadmap initiative: '[Initiative: e.g., Improve team collaboration]' into a standard user story format for the development backlog. The format should be: 'As a [User Persona], I want to [Action], so that I can [Benefit].' Also, add a few potential acceptance criteria to clarify the scope. For example: 'As a project manager, I want to tag my teammates in comments, so that I can notify them of updates directly.'
Announce New Roadmap Discovery Track
Inform the team about a new 'discovery' track on the roadmap dedicated to exploring a new technology or problem space.
Draft an internal announcement about adding a new 'Discovery Track' to our product roadmap for [Quarter, e.g., 'Q3'] dedicated to researching '[Problem Space or Technology, e.g., how AI can automate customer support tickets]'. Clarify that this is not a commitment to build, but an investment in research and prototyping to validate the opportunity. Name the lead PM and Designer for this track and explain how other team members can contribute ideas.
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.
Add ChatBoost to Chrome — It's free