Resolve Conflicting Design Feedback

Made for Graphic Designers

Resolve Conflicting Design Feedback

Also useful for: people in Creative, people in Designers

35 min Intermediate Creative Graphic Designer Communicate Better Career outcome: Avoid Professional Risk

Turn clashing opinions into a brief-based recommendation, a focused decision request, and a clean record of what happens next.

Create a free account to save your progress and use this Playbook.

Use this when

You receive conflicting feedback from clients, stakeholders, or internal reviewers and need to resolve it before another revision round begins.

You'll need

  • Project context
  • Approved brief
  • Feedback received
  • Decision process
  • Project constraints
  • Feedback setting

You'll get

  • Every meaningful feedback item classified
  • Every disputed request traced to the brief
  • The central conflicts and scope changes separated
  • A recommended design direction with visible tradeoffs
  • Final approval authority confirmed or questioned
  • A focused resolution message ready to send

By the end of this playbook

You will have:

  • Every meaningful feedback item classified
  • Every disputed request traced to the brief
  • The central conflicts and scope changes separated
  • A recommended design direction with visible tradeoffs
  • Final approval authority confirmed or questioned
  • A focused resolution message ready to send

Sample

This is sample data, not your prompt. Pro unlocks this higher-stakes Playbook. On Free Playbooks you can still copy the assembled prompt into any AI.

Sample input

Project: Festival landing page, round two.
Brief: Attract first-time attendees ages 21 to 35, feel energetic and welcoming, and drive early ticket sales. Use bold type, candid photography, and a visible ticket button.
Feedback: Marketing wants a larger headline and visible ticket button. The executive sponsor wants a smaller headline and formal group photo. The events manager wants the full performer list in the hero.
Decision process: Marketing manages the project, but final authority is unclear.
Constraints: One revision remains, development starts Friday, and the hero must stay fast and readable on mobile.
Setting: Shared feedback document.

Sample assembled prompt

Core conflict: The marketing lead's request...
The executive sponsor's request introduces a...
The events manager's full performer list...
Recommendation: Keep the bold headline, candid...
Offer a tighter headline scale as...
Move the performer list below the...
Approval question: "Can the confirmed final...
I traced the requests back to...
The bold headline, candid image, and...
The formal photo and smaller headline...
I recommend keeping the approved direction,...
Please confirm the final approver and...

Part of a collection

Stop the Revision Spiral

10 playbooks

Build a practical revision system for setting scope, presenting design work, sorting feedback, tracking versions, and responding when clients keep changing direction.

Next: Revision Control Message Kit

View collection

Best next playbooks

Suggest an idea

What should we add?

Loading the suggestion form…