Talking to people about your designs might seem like a basic skill, but it can be difficult to do well. In many cases, how you communicate with stakeholders, clients, and other nondesigners may be more important than the designs themselves. Because if you can't get their support, your work will never see the light of day—no matter how good it is. As AI now enables anyone to generate designs, articulating design decisions to gain trust is more essential than ever. This practical guide focuses on principles, tactics, and actionable methods for presenting your designs. Whether you design apps, websites, or products, you'll learn how to get support from people who have influence over the project with the goal of creating the best user experience.
AI Reading Assistant
Whole-book reading guide from stratified index samples; jump to passages in the text
Tip the Site
Support this siteYour recognition and a small knowledge-service contribution help keep this technical work open source.Scan the WeChat Pay or Alipay code below. Logged-in and guest visitors can both tip.
WeChat Pay
Alipay
Open WeChat or Alipay and scan. No login required.
AI guide
# Articulating Design Decisions (Third Edition) — Reading Guide
## 【One-Line Pitch】
A practical playbook for designers who need to win stakeholder support by communicating design choices clearly and persuasively—essential reading for UX/UI designers, product designers, and design leaders navigating the age of AI-generated design.
## 【Book Arc】
- **Opening (~0%–16%)**: Establishes the core premise that communication is the real job of a designer, using the "Big Important Meeting" anecdote to show how presenting designs often outweighs creating them. Introduces the problem of subjective design, "too many cooks," and the CEO button phenomenon.
- **Early (~16%–32%)**: Diagnoses why stakeholder disagreements happen—defensiveness, design-by-committee, and the HiPPO effect—and reframes these as communication failures rather than design failures. Introduces the idea that most stakeholder concerns stem from misunderstanding.
- **Early (~32%–42%)**: Makes the case that "good communicators win," detailing how articulating decisions imparts intelligence, demonstrates intentionality, expresses confidence, and shows respect—the four pillars of building trust with stakeholders.
- **Middle (~42%–53%)**: Shifts to what makes a design successful, arguing that designs succeed or fail in conversations, not in isolation. Introduces the problem-solving foundation: a design is only good if it solves a problem, usually for the business.
- **Middle (~53%–58%)**: Addresses the "awareness gap"—designers often can't explain their own intuition-driven decisions. Introduces the practice of documenting thought processes, with concrete problem-solution tables as examples, and notes how AI-generated designs require similar justification.
## 【Key Takeaways】
- **Communication is the job, not a soft skill** (Early): The time spent communicating designs often exceeds the time spent creating them, and the most articulate person usually wins. This reframes stakeholder management as core design work, not an optional extra.
- **Design is subjective, but explanations can be objective** (Early): All design involves aesthetic judgment, but in a business context, "I liked it" won't hold up. The fix is anchoring decisions to measurable problems and solutions rather than personal preference.
- **Stakeholders aren't the enemy—miscommunication is** (Early): Most stakeholder pushback comes from misunderstanding, not malice. Reframing the relationship positively (avoiding "swoop and poop" thinking) opens the door to productive dialogue.
- **Four qualities make articulation persuasive** (Early): Being articulate imparts intelligence, demonstrates intentionality, expresses confidence, and shows respect—each builds trust and makes stakeholders more likely to support your work.
- **The awareness gap is your biggest blind spot** (Middle): Much of your design thinking comes from experience and intuition, making it hard to explain. You must consciously surface why you made each decision before you can defend it.
- **Document your thought process in problem-solution pairs** (Middle): Writing down the problem and proposed solutions makes unconscious thinking tangible and defensible. This documentation also serves as input for AI tools to evaluate alternatives or identify gaps.
- **AI-generated designs need the same justification as human ones** (Middle): AI decisions come from pattern recognition in training data, just as intuition comes from experience. You may need to ask AI to explain its reasoning the same way stakeholders expect from you.
## 【Reading Tips】
- **Deep-read the Opening chapters (0%–32%)** for the mindset shift: the "CEO button" concept and the reframing of stakeholders as misunderstood collaborators are foundational to everything that follows.
- **Skim the interview question sections** ("What makes a good design good?") if you're already experienced—the core insight is that problem-solving, not aesthetics, is the defensible foundation.
- **Pay special attention to the problem-solution documentation examples (~53%–58%)**: these tables are the practical template you'll want to adapt for your own workflow.
- **Note that this is an Early Release edition**—chapters 3 and 7 (design principles and common solution descriptions) are referenced but not yet available in these excerpts, so expect the final book to expand significantly on the practical tactics.
- **Take away the four qualities framework** (intelligence, intentionality, confidence, respect) as a mental checklist before any stakeholder meeting.
## 【Coverage Limits】
This guide covers the available excerpts (roughly the first half of the book). The full book promises additional chapters on design principles, common solution descriptions, and stakeholder psychology that are not yet available in this Early Release sample.
##
Page 3
related trade dress are trademarks of O’Reilly Media, Inc. The views expressed in this work are those of the author and do not represent the publisher’s view...
y’ll say we are the experts and then frequently overrule us. It can be incredibly discouraging and confusing, but the problem may not lie entirely with them....
that it doesn’t have to be this way. It’s possible to avoid the disruption and compromise that happens so frequently in organizational design through better ...
trying to solve problems for the business by accomplishing a goal or improving a metric. But, if we’re also practicing user-centered design, we must make our...
antity or other information On tap, the button changes to a quantity with an initial value of 1. User can increment quantity as needed. Remove secondary “Add...
t page by being automatically logged in. This should reduce confusion and increase conversion. When researchers are in the field, they need quick access to t...
ing support from everyone, it changes how you approach your daily work and improves your ability to get things done. Support vs. Approval I’m also intentiona...
ability to be thoughtful about a problem and articulate any solution is more important than your ability to design the perfect solution every time. When othe...
Support this siteYour recognition and a small knowledge-service contribution help keep this technical work open source.
Scan the WeChat Pay or Alipay code below. Logged-in and guest visitors can both tip.
WeChat PayAlipay
Open WeChat or Alipay and scan. No login required.
Loading comments...
Reply to Comment
Edit Comment