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

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

Example for: an enterprise sales rep asking for custom CSV exports for one client

  1. Direct Email Response:
    Hi Marcus,

Thanks for sharing the feedback from Acme Corp regarding custom CSV exports. I understand their finance team spends extra time reformatting monthly reports, and improving their reporting efficiency is an important goal.

Right now, our engineering team is fully committed to our Q2 priority: rebuilding the core data pipeline to eliminate dashboard latency for all customers. Taking on custom export formats would delay that launch by two weeks. Because of this trade-off, we cannot build this feature this quarter.

In the meantime, Acme can use our automated Google Sheets integration to pull the raw tables directly and apply their custom templates. I have added Acme's reporting requirements to our product backlog so we can evaluate reporting enhancements during Q3 roadmap planning.

Best,
Alex

  1. In-Person Talking Points:
  • Validate the pain: Acknowledge that manual data formatting hurts Acme's user experience.
  • Explain the trade-off: Rebuilding the pipeline benefits every customer, including Acme, and cannot absorb scope creep.
  • Offer the workaround: Walk through the Google Sheets connector as a functional stopgap today.
  1. Follow-Up Action:
    Log the request in the product feedback tracker with Acme's contract value, user pain points, and current workaround notes.
Written by AI from this prompt. Your results will vary.

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.

Keep exploring

More in Product Management
Product Management

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.