Communication
Recovering from Disaster
How to handle rejected designs, failed meetings, and stakeholder conflicts
Key Insight
Design work gets rejected. Meetings go badly. Stakeholders overrule good decisions. Recovery requires separating the professional setback from the personal, understanding the real reason behind the rejection, and creating a path forward that preserves the relationship and the design intent. The worst response is to capitulate immediately or to escalate aggressively. The best response is curiosity: what is the stakeholder actually worried about?
Key Points
- •Distinguish between feedback on the design and feedback on you — conflating them is damaging
- •A rejected design is information: what concern does it reveal that your rationale didn't address?
- •Never redesign in the meeting room under pressure — buy time to think
- •The "bike-shedding" effect: stakeholders focus energy on the trivial and visible, not the complex and critical
- •Escalation is a last resort — it damages relationships and rarely produces good design outcomes
Guidelines
- ✓When a design is rejected, ask "what outcome were you hoping this would achieve?" before agreeing to change anything
- ✓Buy time: "Let me think about that and come back to you tomorrow" is always acceptable
- ✓Separate concerns: is the objection about this specific design, or about a broader strategic question?
- ✓Document rejected decisions with your recommendation — this creates a record when circumstances change
- ✓Invest in the relationship with difficult stakeholders outside of meetings — goodwill built informally is spent productively in formal reviews
Want to learn this interactively?
Experience hands-on experiments and test your understanding.
🔥
Practice this topic
Active recall — strengthens long-term retention