Draft a design critique response without sounding defensive
Turn harsh or blunt stakeholder critique into a collaborative, objective reply grounded in user data and shared goals.
You getAcknowledgment, design Rationale and proposed Options
Prompt
Act as a senior product design lead. Help me respond to tough stakeholder critique without sounding defensive or emotional.
Rules:
- Validate the stakeholder concern clearly without conceding core user needs.
- Anchor every design rationale in user goals, usability principles, or project constraints.
- Offer a constructive next step, such as an A/B test, user testing plan, or a targeted alternative.
- Keep the tone professional, open, and outcome-oriented.
Output format:
- Acknowledgment: 1-2 sentences validating their perspective.
- Design Rationale: 2-3 concise bullet points explaining why the current choice was made.
- Proposed Options: Two clear paths forward to resolve the disagreement.
- Ready-to-Send Reply: A polished email or Slack message combining the above.
Here is the critique I received:Example output
Paste the stakeholder's exact comments or meeting notes after the prompt in ChatGPT, Claude, or Gemini. As a follow-up, ask the model to shorten the draft for a quick Slack reply or expand it into an agenda for a live alignment meeting.
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
Triage conflicting design feedback by user impact
Turn contradictory stakeholder notes into an objective tradeoff matrix with clear decisions. Use it when design reviews stall over opposing priorities.
Uncover business goals behind stakeholder design requests
Turn rigid feature demands into diagnostic interview questions that expose actual business constraints, metrics, and problems.
Write component deprecation notices and migration paths
Produce clear deprecation notices and step-by-step replacement guides for UI components. Use this to help product teams upgrade design systems without breaking views.
Write focused critique questions before a design review
Generate specific discussion prompts that keep reviewers focused on user flows and system usability rather than personal aesthetic taste.
Write tooltip and walkthrough onboarding copy
Turn dense feature walkthroughs into concise, progressive tooltips that users actually read and complete.
Build a five-day remote design sprint schedule
Set up a structured, timeboxed agenda for running an effective remote design sprint across distributed teams without video call fatigue.
- Plan a wireframe content hierarchy before sketching
- Turn user interview quotes into an empathy map
- Write an unmoderated usability test task script
- Audit Form Labels and Helper Text for UX Clarity
- Design a Progressive Disclosure Pattern for Complex Settings
- Structured Design Critique and Feedback Framework