Key Insight
Every design decision should explicitly link to user goals, business goals, or project goals — replacing subjective preference with evidence-based rationale.
Key Points
- •Shift language from subjective ("I think...") to objective ("Based on research...")
- •Use the three-part structure: State the problem, Explain the solution, Provide evidence
- •For every decision, answer: What problem? What alternatives? Why this option? What evidence?
- •Connect every design choice to user goals, business goals, or project goals
- •Authority comes from reasoning, not title—"Here's why this solves your problem"
- •Anticipate objections and address them proactively
- •[FIGURE — Decision rationale framework] Shows: Three-column structure linking Problem → Solution → Evidence for design decisions. Teaches: Every design decision should be traceable to a problem and supported by evidence. Reproduce as: Interactive decision documentation template.
Guidelines
- ✓Start presentations with the problem, not the solution — stakeholders need to feel the pain before they appreciate the fix
- ✓Keep a decision log documenting rationale for significant choices so you can reference them later when decisions are questioned
- ✓Use comparative framing: show what happens with and without your solution, using data or realistic scenarios
- ✗Avoid design jargon with non-design audiences — say "easier to scan quickly" instead of "improved visual hierarchy through typographic scale"
- ✓Practice the one-sentence pitch: can you explain why this decision matters in a single sentence a non-designer would understand?
Want to learn this interactively?
Experience hands-on experiments and test your understanding.
🔥
Practice this topic
Active recall — strengthens long-term retention