By the end of this lesson you can
- Explain design decisions clearly to different audiences.
- Structure rationale around problems, evidence and trade-offs.
- Present work with confidence and handle challenges.
The idea
Designers spend a lot of time explaining their work. Strong rationale turns opinions into reasoned decisions others can support.
A simple structure
- Problem: what users or the business were struggling with.
- Goal: what success looks like.
- Evidence: research, data, standards or best practice.
- Options considered: what else you explored.
- Decision and trade-offs: what you chose and what you gave up.
- Next steps: how you will validate or measure it.
Adapting to audiences
- Executives: outcomes, risks and decisions needed, in a few minutes.
- Product managers: goals, priorities and trade-offs.
- Engineers: behaviour, constraints and edge cases.
- Designers: craft details and system consistency.
Handling challenges
Treat questions as curiosity, not attack. Acknowledge valid points, explain your reasoning, and be willing to change your mind when new evidence appears. "I don't know, but I'll find out" is a strong answer.
Why it matters in real projects
Good designs get rejected when they are explained poorly, and weaker designs get approved when they are explained well. Clear rationale builds trust, shortens debates and helps teams make better decisions. It is one of the most important skills in interviews and for career progression.
A realistic example
A designer presents a new navigation for a hospital booking app. A senior stakeholder asks, "Why did you remove the hamburger menu? Everyone uses those."
The designer explains: "In testing, four of five patients didn't find appointments behind the menu. We moved the four most used sections to a visible bottom bar, which tested well, and kept less used items in a 'More' tab. The trade-off is less room for new sections, which we'll review quarterly." The stakeholder agrees to proceed.
Step by step
Write the problem
State the user and business problem in one sentence.
Gather evidence
List research, data and standards that support your decision.
Show options
Include two or three alternatives you considered.
State trade-offs
Be clear about what you gave up.
Tailor
Adjust the depth for your audience.
Rehearse challenges
Prepare answers to likely questions.
Common mistakes
Mistake "I just think it looks better."
Instead Link decisions to problems and evidence.
Mistake Hiding trade-offs.
Instead State them openly.
Mistake Getting defensive.
Instead Treat questions as curiosity and stay open.
Check your understanding
Choose an answer, then check it. There is an explanation either way.
Practice exercise
Exercise · about 45 min
Rationale presentation
Prepare a five-minute rationale for one design decision.
Steps
- Use the six-part structure.
- Prepare versions for an executive and an engineer.
- List three likely challenges and your answers.
- Present to a peer and ask them to challenge you.
Deliverable
Two short rationale versions and a challenge list.
Self-assessment
Tick each item when it is true of your exercise. Be honest; this is for you.
4 items
Summary
- Structure rationale as problem, goal, evidence, options, decision and next steps.
- Tailor depth to the audience.
- Be open about trade-offs.
- Treat challenges as curiosity.
Further reading
Third-party sources, chosen for reliability. They open in a new tab.
- Design rationale (opens in a new tab)Interaction Design Foundation
- Stakeholder interviews (opens in a new tab)Nielsen Norman Group
Your notes
Marking complete updates your course and roadmap progress.