How to test your design mockup with real users
The fastest way to get feedback on a design mockup is to show it to 6-8 people from your target audience for five seconds, ask what it is and what they'd do next, then have them click where they'd start a real task. Their first impressions and first clicks reveal what stakeholder critique can't.
There’s a ready-made template for this — skip to itThe method: a 15-minute mockup test in three parts
Most mockup feedback comes from the wrong people. Your designer friends critique the kerning, your stakeholders push their pet feature above the fold, and a Reddit thread tells you eleven contradictory things. None of them can answer the only question that matters: does someone who's never seen this understand it and know what to do next? Only people who match your target audience — and have no stake in the design — can tell you that.
The good news is that static mockups are one of the easiest things to test. You don't need a working product or even a clickable prototype — three short exercises (a 5-second look, a first-click task, and a side-by-side preference question) take about 15 minutes per participant, and 6-8 sessions will surface the comprehension problems that survive every internal review. One honest caveat up front: a static mockup can tell you whether people get it and where they'd go — it can't tell you whether the flow behind that click actually works. For that, test a clickable prototype next.
Decide the one question each screen must answer
"Get feedback" is not a test — it invites opinions about colors. Pin each mockup to a single question: Do people understand what this is? Do they know where to start the main task? Which of these two directions communicates better? Everything else in the study — who you recruit, what you ask — falls out of that choice.
Recruit target users, not teammates
The screener does the real work here. You want people who plausibly need the product but have never seen this design — cold eyes are the entire point. Screen out coworkers, fellow designers, and anyone you've already pitched the idea to; they can't un-know what they know, so their feedback measures politeness, not comprehension.
Run the 5-second look first
A 5-second test means showing the design for exactly five seconds, then hiding it and asking what they remember: what is this, who is it for, what stood out? Five seconds is roughly the attention a first-time visitor gives a page, so this measures your visual hierarchy honestly. Always run it first — once someone has studied the mockup, their first impression is gone for good.
Follow with a first-click task
Bring the mockup back and ask them to click (or point to) where they would start a specific real task — "you want to see pricing, where do you go?" A first-click test works because people who start in the right place usually succeed at the task, and people who start in the wrong place usually don't. Ask why they chose that spot before you reveal whether it was "right."
If you're comparing versions, ask for reasons, not votes
For a preference test — showing two or three design directions side-by-side — alternate which version participants see first, and treat the vote as the least interesting output. "Which would you trust with your billing info, and what specifically made you pick it?" gets you the reasons, and the reasons are what you can act on. A 5-3 split with clear reasoning beats an 8-0 vote with none.
Count patterns, then fix and re-show
Tally per problem, not per complaint: "6 of 8 read the headline as a developer tool" is a finding; "some people were confused" is noise. Fix the top two or three misreads, then re-run the identical test on the revised mockup — with static images the whole cycle fits inside a week.
What to measure
- First-impression recall — what they say the page is after five seconds — in their own words
- Message match — how close their description lands to the value proposition you intended
- Hierarchy hit — the first element each person mentions — is it the one you designed to lead?
- First-click accuracy — what share clicked where the real action actually lives
- Click hesitation — how long they hovered before committing — slow clicks signal guessing
- Confusion points — elements people asked about, misread, or skipped entirely
- Trust flinches — moments they questioned whether the product looks legitimate
- Preference reasons — the specific words behind each A-vs-B pick — not just the tally
- 1. You saw the design for five seconds. What is this, and who do you think it's for?— Ask before showing the design again — this is your headline and hero doing their job, or not.
- 2. What's the one thing you remember most from the page?— Whatever they name is your real visual hierarchy, regardless of what the layout intends.
- 3. If you wanted to [primary action], where would you click first? What made you pick that spot?
- 4. Was there anything on this design you didn't understand or that felt out of place?
- 5. What would you expect to happen after clicking [the main button]?— Expectation gaps here become rage-clicks after launch — cheaper to find them now.
- 6. Between these two versions — which would you trust more to [do the job], and what specifically made you choose it?
- 7. Is anything missing from this page that you'd need to see before taking that next step?
What’s in the ready-to-run study
This is the exact study Sera drafts when you paste your mockup below. Every piece is editable before launch.
Design mockups usability test
Moderated · Think-aloud · Live URL or Figma prototype
Screener
4 questions that admit target-audience members with fresh eyes and reject designers, coworkers, existing users, and professional testers.
Tasks
A timed 5-second exposure, 2 first-click tasks on your key actions, and an optional A/B preference comparison if you upload two versions.
Interview questions
7 post-task questions with probe instructions — the AI moderator digs into what each participant actually misread or hesitated on, not a generic script.
Participants & timing
N = 8 recommended — enough to see every misread twice. Sessions run 10-15 minutes; recruit-to-readout is typically under 24 hours with the Sera panel.
Try this template
See your design mockup through your users' eyes
the AI drafts your full study in ~2 minutes.
- Works with live URLs and Figma prototypes
- First 7 interviews free
- No credit card required
How it works in Sera
1 · Paste your flow
Drop in the live URL or Figma prototype. Sera reads the flow, drafts the screener, tasks, and questions, and shows you the whole study for review.
2 · Interviews run
Participants attempt the task on their own device while the AI moderator watches, listens, and probes hesitations in real time. You can sit in on any session.
3 · Readout, cited
Friction moments ranked by how many participants hit them, each linked to the exact clip. Share the readout; skeptics can click through to the evidence.
Frequently asked questions
How do I get feedback on a design mockup?
Show it to 6-8 people from your target audience: a 5-second look to test first impressions, a first-click task to test whether they know where to act, and follow-up questions about anything confusing. Feedback from teammates and design communities measures craft; feedback from target users measures whether the design works.
What is a 5-second test?
You show a design for five seconds, hide it, and ask what the person remembers — what the product is, who it's for, what stood out. Five seconds approximates a first-time visitor's initial attention, so it tests whether your headline and hierarchy communicate before anyone reads closely.
How many people do you need to test a design?
For qualitative feedback on a mockup, 6-8 target users will surface most comprehension problems, and you'll see the serious ones at least twice — which is what lets you rank them. Preference tests between versions benefit from larger numbers (15-20+) if you want a split you can lean on.
Can I test a design that isn't clickable?
Yes — 5-second, first-click, and preference tests all work on flat images. Participants point or click where they would act, and you measure whether that matches where the action lives. What a static mockup can't tell you is whether the flow behind the click works; that's a prototype test.
What's the difference between testing a mockup and testing a prototype?
A mockup test measures comprehension: do people get what this is and know where to start? A prototype test measures usability: can they actually complete the task across screens? Test mockups early when redirection is cheap, then wire the winning direction into a clickable prototype and test the flow.
Where can I get honest feedback on my design besides my team?
Design communities critique execution, and friends are too polite to be useful. The honest source is people who match your target audience and have never seen the design — recruited through a panel, a customer list, or an ad audience. Strangers with no stake in your feelings are the only reviewers who'll tell you they don't get it.
Keep reading
Find out why people abandon
your design mockup — this week.
Paste your URL, review the study Sera drafts, and watch the first interview yourself.
Your first 7 interviews are on us — no credit card required.