Communication
Reducing Cognitive Load in Design Reviews
How to present designs so stakeholders can evaluate rather than react
Key Insight
Stakeholders who are cognitively overloaded in design reviews fall back on subjective reactions ("I don't like it") rather than strategic evaluation ("does this serve the user's goal?"). Reducing cognitive load in presentations means presenting fewer decisions per session, providing context before showing designs, and structuring reviews around specific questions rather than open-ended reactions.
Key Points
- •Present fewer designs per session — 3-5 decisions is the limit before overload sets in
- •Set context before showing the design: user goal, constraints, what you're asking stakeholders to evaluate
- •Ask specific questions: "Does this layout support the user's primary goal?" not "What do you think?"
- •Separate critique of UI from critique of content — different cognitive modes
- •Provide design rationale proactively so stakeholders spend energy evaluating, not guessing
Guidelines
- ✓Open every review with a one-sentence problem statement: "We're solving [user need] for [audience]"
- ✓State what decisions have already been made and what's open for input — scope the review
- ✓Show context (user flow, page in context) before close-up (component detail)
- ✓When presenting options, provide a recommendation — "I prefer A because..." guides productive discussion
- ✓End with clear next steps: who decides what, by when
Want to learn this interactively?
Experience hands-on experiments and test your understanding.
🔥
Practice this topic
Active recall — strengthens long-term retention