Managing client input to improve work and maintain productive relationships.
Feedback is essential—it brings client perspective and catches blind spots. But feedback is also where projects go wrong—misunderstood comments, competing opinions, endless revisions. Handling feedback skillfully means structuring it well, interpreting it accurately, and responding constructively.
Why Feedback Is Challenging
Different Languages
Designers and clients often speak past each other:
- Designer says "balance," client hears something else
- Client says "pop," designer doesn't know what they mean
- Visual literacy varies widely
- Vocabulary differs
Subjectivity vs. Objectivity
Feedback often conflates:
- Personal preference ("I don't like blue")
- Business requirement ("Our research shows blue confuses our category")
- Aesthetic judgment ("This feels dated")
- Strategic concern ("This doesn't feel premium enough")
Competing Voices
Multiple stakeholders bring:
- Different perspectives
- Different priorities
- Different aesthetic preferences
- Political dynamics
Emotional Stakes
For clients, brand work is personal:
- It represents their business
- They'll live with it for years
- Their reputation is attached
- Stakes feel high
Structuring Feedback
Before the Presentation
Set expectations:
- Explain what feedback is useful at this stage
- Request consolidated feedback (one voice)
- Set timeline for receiving feedback
- Clarify what will happen with feedback
During the Presentation
Guide the discussion:
- Ask specific questions, not "what do you think?"
- Focus on objectives: "Does this achieve the goal of...?"
- Separate reaction from direction: "Setting aside personal preference..."
- Capture feedback in real-time
After the Presentation
Formalize the feedback:
- Send summary of what you heard
- Ask for confirmation or correction
- Request any additional input by deadline
- Confirm next steps
Feedback Questions
Instead of: "What do you think?"
Ask:
- "Does this feel aligned with the positioning we discussed?"
- "How does this compare to competitors you admire?"
- "Which direction best communicates trust to your audience?"
- "What concerns you about this approach?"
- "What would need to be true for you to move forward with this?"
Interpreting Feedback
Surface vs. Underlying
What clients say isn't always what they mean:
Surface: "Make the logo bigger" Underlying: "I'm worried about visibility and recognition"
Surface: "Can we try a different color?" Underlying: "Something doesn't feel right but I can't articulate it"
Surface: "It needs more energy" Underlying: "I expected something bolder; this feels too safe"
Ask follow-up questions to understand the underlying concern.
Feedback Categories
Categorize feedback to respond appropriately:
Objective issues:
- Factual errors
- Technical problems
- Unmet requirements Action: Fix immediately
Preference opinions:
- "I prefer serif fonts"
- "Can we try green?" Action: Explore whether there's underlying concern; offer perspective
Strategic concerns:
- "Will our audience connect with this?"
- "Does this differentiate from competitors?" Action: Take seriously; address with evidence and rationale
Unclear feedback:
- "It needs something"
- "Make it pop" Action: Clarify before acting
Red Flag Feedback
Be alert to problematic patterns:
Contradictory feedback: "Make it bolder but more subtle" Design by committee: Different stakeholders pulling in different directions Solution prescriptions: "Just make it blue with a globe" Moving targets: "Actually, what I meant was..." All negative: Nothing works, nothing is acknowledged as good
Responding to Feedback
The Response Formula
- Acknowledge: Show you heard and understood
- Clarify: Confirm understanding of underlying concern
- Respond: Explain your perspective or approach
- Propose: Suggest path forward
Receiving Constructive Feedback
When feedback is valid:
- Thank them for the input
- Acknowledge the issue
- Explain how you'll address it
- Implement thoughtfully
Receiving Difficult Feedback
When you disagree:
- Listen fully before responding
- Acknowledge their perspective
- Explain your rationale
- Offer professional recommendation
- Ultimately, respect their decision (within reason)
Educating Without Condescending
Sometimes clients need guidance:
- "That's a great instinct. Here's something to consider..."
- "I've seen that approach work in X context. For your situation..."
- "Let me show you why we went this direction..."
Share expertise generously, not defensively.
Standing Your Ground
When feedback would harm the work:
- Be clear about your concern
- Explain the consequences
- Propose alternatives
- Document your recommendation
- If overruled, execute professionally (or consider the relationship)
The "Why?"
Ask why behind requests:
- "Help me understand—what's driving that concern?"
- "What would that change accomplish?"
- "What specifically isn't working for you?"
Understanding the why lets you address the real issue.
Consolidating Feedback
The Committee Problem
Multiple stakeholders create chaos:
- Contradictory directions
- Endless revisions
- No clear decision
- Political dynamics
Solutions
Single point of contact: Request one person consolidate all feedback before sharing.
Identify the decider: Who has final say? Direct key questions there.
Surface conflicts explicitly: "I'm hearing X from person A and Y from person B. Can you help resolve?"
Document sources: Track which feedback came from whom.
When Feedback Conflicts
If stakeholders disagree:
- Acknowledge the tension
- Don't triangulate (don't let stakeholders argue through you)
- Request they align before you proceed
- Offer to facilitate discussion if appropriate
Revision Management
Setting Expectations
In the proposal/contract:
- Number of revision rounds included
- What constitutes a revision
- Timeline for providing feedback
- Cost of additional rounds
Defining "Revision"
Be clear what counts:
- "Consolidated feedback from one source"
- "Provided within 5 business days of presentation"
- "Scope consistent with original brief"
Not a revision:
- New requirements
- Additional deliverables
- Changing direction after approval
- Contradicting previous feedback
Tracking Revisions
Maintain clarity:
- Document each round of feedback received
- Track changes made in response
- Note what was requested vs. what was done
- Communicate when approaching revision limits
Additional Revision Conversations
When limits are reached:
- "We've completed the included revision rounds. I'm happy to continue refining."
- "Additional revisions are $X per round."
- "Alternatively, we can proceed with this version."
Difficult Feedback Situations
"I'll Know It When I See It"
Client can't articulate what they want:
- Provide structured choices, not open questions
- Use visual references to narrow direction
- Show extremes to identify boundaries
- Iterate with small tests
Feedback from Non-Decision-Makers
Input from people who can't approve:
- Acknowledge their perspective
- Check with actual decision-maker
- Don't implement without approval
- Document the dynamic
Changing Direction Late
Significant changes after approval:
- Reference original approval
- Explain scope/timeline impact
- Propose change order if needed
- Be clear this is a new direction, not a revision
Personal Attacks
When feedback becomes personal:
- Stay professional
- Don't engage emotionally
- Redirect to the work
- Consider whether relationship is viable
Feedback Documentation
Why Document
Records protect everyone:
- Clarifies what was agreed
- Prevents revisiting settled decisions
- Supports additional billing if needed
- Provides reference for disputes
What to Document
- Feedback received (verbatim when possible)
- Your interpretation (confirmed with client)
- Decisions made
- Changes implemented
- Who approved what
How to Document
- Meeting notes sent after discussions
- Email confirmations of decisions
- Change log in project files
- Formal sign-offs for major approvals