Presentation Tips for Design Managers: The Design Review
By Daniel Harper · Career & Business
How should a design manager present work to stakeholders? Start with the problem and what success looks like, then show the design solving it, ideally with evidence from research or testing. Ask for the specific decision you need. Stakeholders who are engaged and paying attention are moved by the quality of the argument; distracted ones react to surface details, so present when they can focus.
Design managers present work to people who will form an opinion in the first few seconds of seeing it: executives, product managers, engineers, clients. That first reaction is often about something superficial, a colour, an image, a word, and a design review can easily turn into a discussion of preferences instead of a decision about whether the design solves the problem.
How people judge what they see
The elaboration likelihood model, set out by Richard Petty and John Cacioppo, describes two ways people are persuaded. When people care about a topic and have the attention to spare, they weigh the quality of the arguments. When they are distracted or uninvested, they rely more on surface cues: who is speaking, how confident they seem, how attractive the material looks.1
A design review is often held in the worst conditions for careful judgement: a busy executive, a full agenda, ten minutes between other meetings. In those conditions, people react to surface details. The fix is partly about the presentation and partly about the timing.
Start with the problem, not the screens
Before you show any design, remind the room of the problem and what success looks like:
"New customers are abandoning sign-up at the address step. Our goal is to get completion from 61% to 75% without losing the data sales needs."
Now the design will be judged against that goal, rather than against personal taste.
Show evidence, not just pictures
A design supported by evidence is much harder to dismiss as a matter of taste: a usability test, a pilot result, research quotes, the data that showed the problem. Show the user struggling with the old version and succeeding with the new one, if you can. Evidence moves the conversation from "I don't like the green" to "does this solve the problem?"
Ask for a specific decision
Every design review should end with a decision. Say at the start what you need: approval to build, a choice between two options, agreement on a direction. Without a clear ask, reviews drift into open-ended feedback that is hard to act on.
Choose the moment
If a design decision matters, do not squeeze it into the last five minutes of a long meeting. Book time when the decision-makers can actually look at the work. A design reviewed with attention gets judged on its merits; one glanced at between other topics gets judged on its colours.
Handling feedback in the room
When a stakeholder gives feedback, ask what problem they are trying to solve. "Make the button bigger" often means "I'm worried people won't find it", and there may be a better way to solve that. Note feedback without committing to every change on the spot; say you will come back with how you have addressed it.
Presenting to engineers
Engineers judge a design by whether it can be built well, not by how it looks in a mock-up. Present to them early, before the design is finished, and show the behaviour as well as the screens: what happens on errors, on slow connections, with long names and empty states. Ask what is expensive to build and what is cheap. A design that engineering helped shape gets built the way it was intended.
Presenting research
When you present user research, lead with the two or three findings that change decisions, each with a real quote or clip. A long list of observations is easy to agree with and hard to act on.
For the interview questions that cover this role, see behavioral interview questions for design managers, and for the research on persuasion routes, the two routes to changing someone's mind.
References
- Petty, R. E., & Cacioppo, J. T. (1986). The Elaboration Likelihood Model of persuasion. Advances in Experimental Social Psychology, 19, 123–205. https://doi.org/10.1016/S0065-2601(08)60214-2