Form questions
Design feedback questions for a mockup review
Ask 8 to 12 per mockup and show it before asking anything. Never skip the first impression in the person's words, what they would click first, and whether the main message is clear. Those three show whether the design communicates on its own, before anyone explains it.
Design feedback questions should ask what a person noticed and understood, not whether they like the colours, because those answers can be acted on. These twenty one questions start with a first impression taken before anything else is asked, then test clarity, hierarchy and what people would click, and end with a preference between options.
The questions
First look
In a few words, what is this page for?Long textRequired
Ask straight after a five second look, before any other question shapes the answer.
What did you notice first?Short text
What is your first impression of the design?Long text
Clarity
How clear is the main message?Single choiceRequired
A five point scale from very unclear to very clear.
Where would you click first to do the main task?Short textRequired
Name the task, for example book a class. Compare answers with the intended button.
Is anything confusing or missing?Long text
Which words, if any, did you not understand?Short text
Hierarchy and readability
How would you rate each of these?Rating grid
Rows: visual hierarchy, contrast and readability, spacing, consistency with the brand. Columns poor to excellent.
Is the text easy to read on this screen size?Single choice
Does anything feel too crowded or too empty?Long text
Does the design feel trustworthy?Single choice
Useful for checkout, sign up and payment screens.
Comparing options
Which version do you prefer?Single choice
Only when two or more options are shown side by side or one after the other.
Why that one?Long text
Which version makes the main task easiest?Single choice
Often a different answer from the preference, and the more useful one.
Accessibility and context
Do you use any accessibility settings or tools?Multiple choice
Larger text, screen reader, high contrast, none. Lets you check the design with the people it most affects.
Which device would you usually use for this?Single choice
Would this design make you more or less likely to use the product?Single choice
What one change would improve it most?Long text
Your roleDropdown
For internal reviews: designer, developer, marketing, leadership, customer.
May the team follow up?Single choice
Anything else?Long text
Which questions to make required
Three are required: what the page is for, how clear the main message is, and where they would click first. These test whether the design works without explanation, which is the main question in any mockup review. Preference and rating questions are optional, because liking a design and being able to use it are different things.
- In a few words, what is this page for?
- How clear is the main message?
- Where would you click first to do the main task?
The form built from these questions
A static copy of the finished form, from its own example page.
Three ways to change this bank
For a logo or brand identity, replace the click question with what kind of business the person thinks it represents and which words describe it. For a printed flyer or poster, ask what they remember after looking away and whether they could find the date and price. For an internal design critique among colleagues, keep the clarity and hierarchy questions and add what problem the design is solving, so feedback is judged against the brief rather than taste. In every version, show the design at the size it will really be seen, on a phone if it is for phones, because clarity and contrast change with the screen.
Questions people ask
How do you get useful design feedback?
Ask people what they see and what they would do, not whether they like it. Show the design before asking anything, ask for a first impression in their own words, and give them a task such as finding where to book. Feedback that describes behaviour can be fixed; feedback about taste rarely can.
What is a five second test?
A quick method where a person looks at a design for about five seconds, then answers what it was for and what they remember. It checks whether the main message and purpose come through immediately. The first question in this bank is built for it, which is why it comes before anything else.
Should design feedback come from colleagues or customers?
Both, for different reasons. Colleagues can check the design against the brief and brand. Customers show whether it works for the people it is for. Keep the two sets of answers separate, because colleagues know too much to judge clarity the way a newcomer does.
How do you compare two design options fairly?
Show them in a different order to different people, ask the same questions about each, and ask which makes the main task easiest as well as which is preferred. Preference alone tends to favour the more familiar or more decorated option, not the more usable one.
Should accessibility be part of design feedback?
Yes. Contrast, text size and clear wording decide whether some people can use the design at all. The W3C accessibility guidelines set testable criteria for contrast and text. Asking whether reviewers use accessibility tools also helps you include the people most affected.
Can people upload screenshots with their comments?
In a form, a file upload question accepts images or PDFs, so a reviewer can mark up a screenshot and attach it. For design reviews with many comments, a shared design tool is better, and the form can collect the overall answers and ratings alongside it.
Build this form in about a minute
The button opens the form generator with this form already described. Change the wording to match your own, generate, then edit any field.
Create a form with OneCraftOther question banks
Usability testing questions before, during and after each task
Usability testing questions come in three kinds: a screener before the session, short questions after each task, and wrap up questions at the end. These twenty two are written for a moderator to fill in as the session runs, so every participant is asked the same things in the same order.
App feedback questions to ask before the store prompt
App feedback questions asked inside the app catch problems while the user can still be helped, before they become a one star review. These twenty two questions cover the overall rating, what people use the app for, crashes and speed, what is missing and the device, so a bug report and a feature request never land in the same box.
Pricing survey questions including the Van Westendorp four
Pricing survey questions ask what people spend now, what they would consider too cheap and too expensive, which plan they would choose and which features they would pay for. These twenty questions centre on the four Van Westendorp price sensitivity questions, asked in a fixed order after people know what the product does.
On writing the questions themselves, read How to write a feedback form. For everything the builder can do, see the form maker. Step by step: Create a conversational form with AI, then View, export and manage your responses.
Written and checked by the OneCraft team. Last checked .