Decline a stakeholder feature request diplomatically
Turn down an out-of-scope feature request without burning bridges. Perfect for product managers protecting roadmap focus while maintaining strong stakeholder relationships.
You getDirect Email Response, in-Person Talking Points and follow-Up Action
Prompt
You are an experienced product manager known for clear communication and firm roadmap discipline. Help me write a polite, professional response declining a stakeholder feature request.
Rules:
- Validate their underlying business goal without committing to their proposed solution.
- Explain the trade-off clearly, citing current focus on committed quarterly goals.
- Provide an alternative path, such as an existing workaround or logging the context for future planning cycles.
- Keep the tone respectful, collaborative, and decisive.
Output format:
1. Direct Email Response: A ready-to-send draft under 150 words.
2. In-Person Talking Points: 3 bullet points for a 1-on-1 conversation.
3. Follow-Up Action: One sentence describing what documentation or tracking to update.
Here is the stakeholder request and context:Example output
Paste the stakeholder's email, message, or request notes into ChatGPT, Claude, or Gemini after the prompt text. To adjust the response, ask the model to make the tone firmer or suggest a specific alternative workflow.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Write a post-advisory board roadmap recap
Turn raw meeting notes into a crisp follow-up email that shows customer advisory board members how their feedback shaped the roadmap.
Turn a Vague Founder Request into a Scoped Problem Brief with Trade-Offs
Get a one-page brief that separates the requested feature from the real user problem, compares three options by cost and risk, and names the one question to answer before building.
Write a Stakeholder Update That Leads with Decisions, RAG Status and Risk Owners
Turns your raw product notes into a short stakeholder update: decisions needed first, red/amber/green status per initiative, and every risk with an owner and next step.
Plan a listening-first advisory board agenda
Design a collaborative, listening-oriented customer advisory board meeting agenda. Use this to ensure customer participants speak twice as much as internal product presenters.
Extract win and loss drivers from CRM notes
Turn raw CRM deal records into actionable product, pricing, and sales execution patterns. Use it to prepare roadmap reviews and board updates.
Rewrite empty state copy to accelerate user activation
Turn passive placeholder screens into clear, action-oriented entry points that guide users to their first completed task. Use it during product design and copy polish.
- Schedule phased customer communications for feature sunsetting
- Turn onboarding test notes into root causes
- Analyze customer feedback using Jobs to Be Done
- Reframe a feature request into a core user problem
- Draft Multi-Tier SaaS Product Packaging and Feature Matrix
- Stress Test Your Product Requirements Document for Edge Cases