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

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

Example for: critique saying the checkout button is too subtle and needs to be bright red

Acknowledgment
Thanks for flagging the visibility of the primary action on the checkout screen. Ensuring users instantly understand how to complete their purchase is our shared priority.

Design Rationale

  • We chose deep navy to maintain clear visual hierarchy with the primary brand palette and avoid warning-state confusion, since red is reserved for form validation errors.
  • The button meets WCAG AAA contrast guidelines against the white background and occupies full width on mobile viewports for tap target accessibility.
  • The current layout directs attention downward sequentially without competing against the order summary totals.

Proposed Options

  1. Increase button height from 48px to 56px and bold the label text to increase visual weight while keeping the brand palette intact.
  2. Run a 5-second preference and click test on UsabilityHub comparing the navy action against an accent-colored variant to verify time-to-click.

Ready-to-Send Reply
Hi team, thanks for the feedback on the checkout button styling. I agree that making the primary action unmissable is critical for conversion. We avoided red because our design system reserves it for error alerts, and our navy button currently meets AAA contrast standards. To increase prominence without causing error confusion, I suggest we increase the button height to 56px and run a quick 5-second click test against an accent variant this afternoon. I will share those results before we finalize the build.

Written by AI from this prompt. Your results will vary.

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.

Keep exploring

More in Design