How to give useful feedback on your website V1
V1 confirms the design direction before detailed production begins. Focused feedback on visual tone, hierarchy, layout and calls to action gives V2 a clear foundation.
V1 is a viewable design direction, not the final detailed website. It exists because most people can respond to something concrete more effectively than they can describe a design from a blank page. Your task is not to proofread every sentence yet. It is to decide whether this is the right foundation for V2.
The four questions V1 should answer
1. Does the visual character feel like this business? Look at the color, type, image treatment and overall tone. You do not need design terms. “This feels too formal for our shop” is useful feedback.
2. Is the most important information given the right priority? A customer should understand what you do and what action to take. If company history dominates while the services are difficult to find, explain that effect.
3. Does the main layout support the customer’s path? Check the order of major sections and the relationship between pages. Detailed text and final images can still change in V2; the structure they will live in is the important decision now.
4. Are the primary calls to action right? The direction should make the intended next step clear: call, open LINE, submit an enquiry, request a booking, or choose another agreed action.
Good and bad feedback, side by side
| Unhelpful | Helpful |
|---|---|
| “I don’t like the homepage.” | “The homepage starts with our history — customers usually ask about services first. Can services become the first priority?” |
| “Make it pop more.” | “The section headings don’t stand out — I scrolled past the prices without noticing them.” |
| “Something feels off.” | “The photos are right but the opening text sounds too formal for our shop — we talk to customers much more casually.” |
| “Change the about page.” | “The about page is fine, but it doesn’t mention we’ve been here 15 years — that’s our biggest trust point.” |
The pattern: helpful feedback names what you saw, where, and what effect it had on you as a reader. It never needs design vocabulary. “I scrolled past it” or “this sounds unlike us” are precise, professional observations — you are the expert on your business and your customers, and that’s exactly the expertise the feedback needs.
Describe the reaction, not the design solution
“I don’t like it” is a valid reaction, but it does not yet reveal what should be protected or changed. A short explanation gives the team something concrete to work from.
You don’t have to know what you want instead. You only have to describe the reaction: what you looked at, and what it made you feel or do. “This photo makes us look bigger than we are.” “I read the first paragraph twice and still wasn’t sure what we do.” Every sentence of that shape is actionable, even when it contains no solution.
Two more habits help: react as a stranger first — read the direction once pretending you know nothing, and note where you would hesitate — and say what is right, not only what is wrong. “This section is exactly the tone I want” protects good decisions as V2 becomes more detailed.
What belongs in V2 review instead
Once V1 is approved, V2 adds the real service information, copy, images, responsive details and in-scope forms or integrations. Detailed factual corrections, missing content, form behavior and final page-by-page checks belong primarily in that review.
If V2 reveals that a factual correction requires a small layout adjustment, say so. If the request changes the approved visual direction or adds a new store, portal, payment flow or other major capability, identify it openly as a possible scope change so it can be evaluated separately.
When you don’t need much feedback at all
Sometimes the direction is simply right. If the visual tone, hierarchy, layout and main actions work, approve it and let detailed production begin. There is no benefit in inventing objections to make a review feel substantial. If a concern is difficult to put into words, a short walkthrough with the team is often enough to identify the underlying issue.
This article explains AlphaBlue’s current V1 direction review. Other providers may use “V1” to mean a different kind of deliverable, so confirm the stage definition before reviewing.