Presenting Designs to Non-Designers
Learn how to present design work to clients and stakeholders who aren't designers. Get better feedback and faster approvals.
You’ve spent days perfecting a design. The typography is balanced. The color palette is cohesive. The layout guides the eye exactly where it should go. Then you present it to the client, and they say: “Can you make the logo bigger?”
This isn’t a client problem. It’s a communication gap. Non-designers don’t see what designers see. They don’t evaluate visual hierarchy, typographic rhythm, or negative space. They react emotionally and practically: does this look like my brand? Will my customers understand it? Do I personally like it?
Learning how to present designs to clients who aren’t designers is one of the most valuable skills you can develop. Here’s how.
Lead with the problem, not the pixels
The biggest mistake designers make in client presentations: jumping straight to the visuals. “Here’s the homepage design” puts the client in critique mode immediately. They start reacting to colors and fonts before understanding the reasoning.
Instead, start with context:
- Restate the goal. “We agreed the primary goal is to increase demo requests by 30%. Here’s how this design supports that.”
- Recap the brief. “Based on our discovery call, your audience is mid-level managers who need to make a quick decision. That shaped our approach.”
- Explain the strategy. “We put the value proposition front and center because your analytics show 60% of visitors leave within five seconds.”
When you frame the design as a solution to a problem, clients evaluate it against the goal — not personal taste. “Does this help us get more demos?” is a much more productive question than “do I like this shade of blue?”
Translate design language into plain English
Designers live in a world of kerning, leading, visual weight, and gestalt principles. Clients don’t. When you say “we used generous whitespace to create breathing room,” some clients hear “there’s a lot of blank space we’re not using.”
Reframe design decisions in terms clients care about:
| Designer language | Client language |
|---|---|
| ”We used whitespace to improve readability" | "We made sure the main message doesn’t compete with other elements" |
| "The visual hierarchy guides the eye" | "The most important information is what people see first" |
| "We maintained brand consistency" | "This looks and feels like your company at every touchpoint" |
| "The layout follows an F-pattern" | "We placed key content where people naturally look” |
You’re not dumbing things down. You’re translating expertise into the language of business outcomes, which is what clients actually need to make decisions.
Show the reasoning, not just the result
For every major design decision, briefly explain why you made it. This transforms the presentation from “do you like this?” to “here’s the thinking — does this align with your goals?”
Examples:
- “We chose this blue because it tested well for trust in your industry, and it complements your existing brand green.”
- “The CTA button is this size because it needs to be easily tappable on mobile, where 65% of your traffic comes from.”
- “We shortened the hero copy to one sentence because data shows people read less than 20% of web page text.”
You don’t need to justify every pixel. Focus on the decisions clients are most likely to question: color choices, layout structure, imagery, and calls to action.
Guide feedback with specific questions
“What do you think?” is an invitation for unfocused reactions. Non-designers don’t know what aspects to evaluate, so they fixate on whatever catches their eye first — usually something subjective.
Ask questions that direct attention to what matters:
- “Does the headline communicate your main value proposition?”
- “Does this design feel consistent with your brand identity?”
- “Is the call-to-action clear? Would your customers know what to do next?”
- “Which of these two directions better reflects the feeling you want?”
Each question should address one decision. This helps non-designers give feedback that’s actually useful, and it prevents the overwhelming “I don’t know, something just feels off” response.
For a structured approach, share a design review checklist with your reviewers before they start. It keeps their attention on the aspects you need input on.
Present options, not open canvases
Non-designers make better decisions when they’re choosing between options rather than evaluating a single design in isolation. When someone sees only one option, they compare it to the imaginary version in their head — which is impossible to compete with.
Present two to three concepts that each solve the brief differently:
- Option A: Clean and minimal, focused on the product
- Option B: Bold and energetic, focused on the brand personality
- Option C: Content-forward, focused on trust signals and social proof
Label each option with a descriptive name (not “Version 1” — that implies a ranking). Explain the strengths of each. Then ask the client which direction resonates and why.
Use an image feedback tool that supports side-by-side comparisons. When clients see options next to each other, their preferences become clearer — even when they struggle to articulate them verbally.
Anticipate the “make it pop” feedback
Every designer has heard it. “Can you make it pop?” “It needs more energy.” “I want it to feel premium.” These aren’t useless comments — they’re clients trying to express something real in language that doesn’t match design vocabulary.
When you get vague feedback, don’t dismiss it. Dig deeper:
- “Make it pop” → “Which element should stand out more? The headline, the image, or the CTA?”
- “It feels too corporate” → “Should it feel more approachable? More playful? Can you show me a brand whose tone you admire?”
- “It needs to feel premium” → “When you think premium, what brands come to mind? Apple minimal or luxury fashion editorial?”
Reference images are your best friend here. Collect three to four examples and ask the client to react. Pointing at an existing design and saying “like this but warmer” gives you more information than ten minutes of verbal description.
Use the right tools for non-designer reviewers
The tool you use for design reviews matters — especially when reviewers aren’t designers. Asking a marketing director to install Figma and navigate frames is a recipe for “I’ll just send you my thoughts in an email.”
Instead, use a review tool built for simplicity. Reviewer lets clients click a link, see the design full-screen, and leave comments directly on it. No account creation, no learning curve, no software to install.
This matters because friction kills feedback quality. When it’s easy to comment on a specific part of the design, clients give specific feedback. When it’s hard, they default to vague emails.
Separate presentation from review
One common mistake: presenting the design and asking for feedback in the same moment. Clients need time to process. Their first reaction in a live meeting is often superficial.
Instead, try a two-step approach:
- Present live (or via recorded video) — Walk through the design, explain the reasoning, answer initial questions
- Review async — Share the design via a review link and give clients 48 hours to leave detailed, visual feedback
This gives clients time to reflect, show the design to colleagues, and formulate thoughtful responses rather than blurting out initial reactions.
Better presentations, better projects
When you learn to present designs to clients effectively, everything improves. Feedback gets more actionable. Revision rounds decrease. Approvals happen faster. And clients trust your expertise more because they understand the thinking behind your decisions.
The shift is simple: stop presenting designs as art to be judged. Start presenting them as solutions to be evaluated. Frame the problem, explain your approach, guide the feedback, and make it easy for anyone to respond — regardless of their design background.
Ready to simplify your client review process? Try Reviewer and share your next design with a link that works for everyone — no design skills or signups required.
Frequently Asked Questions
How do I present a design to someone who isn't a designer?
Start by explaining the problem the design solves, not the design itself. Walk through your reasoning — why you chose certain layouts, colors, or hierarchies — in plain language. Avoid jargon like 'whitespace' or 'visual hierarchy.' Instead, say 'we left breathing room so the main message stands out.' Guide them with specific questions rather than asking 'what do you think?'
How do I get useful feedback from non-designers?
Give them structure. Ask targeted questions like 'does this communicate your main message?' or 'which version feels more aligned with your brand?' Use a visual feedback tool so they can point at what they mean instead of describing it. Non-designers give much better feedback when they can react to specific elements rather than evaluate the whole design at once.
What should I do when a client says 'I don't like it' but can't explain why?
Don't take it personally and don't get defensive. Ask follow-up questions to narrow down the issue: 'Is it the colors, the layout, or the overall mood that feels off?' Show alternative directions or reference images to help them articulate their preferences. Sometimes a side-by-side comparison reveals what they actually want without them needing to name it.
Should I present one design option or multiple to non-designer clients?
For initial concept reviews, present two to three options. This gives clients a meaningful choice and reveals their preferences through comparison. For refinement rounds, narrow to one direction based on earlier feedback. Never present more than three — too many options overwhelm non-designers and slow down decisions.
Related reading
How to Run Async Design Reviews That Work
A practical guide to running effective asynchronous design reviews. Better feedback, fewer meetings, and faster approvals for remote teams.
guidesBest Practices for Giving Visual Feedback on Designs
Learn how to give clear, actionable visual feedback that helps designers improve their work faster.
tipsHow to Collect Client Approvals Faster (5 Practical Tips)
Stop waiting weeks for client sign-off. Five practical techniques to speed up your design approval process.
guidesDesign Approval Process: A Step-by-Step Guide
Build a design approval process that gets clear sign-offs fast. Practical steps for designers and teams.
Explore more
Ready to get feedback?
Upload your first file and share a review link in seconds. Free, no signup required.
Try Reviewer free