Imagine opening a website layout and pausing at the service section. Something feels off, but you can’t tell whether it’s the colors, the order, or the way the information is presented. You start typing a comment, delete it, and wonder whether “I don’t love this part” is helpful enough.
It’s a perfectly reasonable starting point. You don’t need design vocabulary to contribute. The next step is to give that first impression a little context: where you’re getting stuck, what you expected, and why the difference matters.
I use Figma every day to create website layouts and prototypes at Jollity Studios. As a designer, I can explore ways to address a concern. Your knowledge of the business and its audience gives me the context to do that.
Start With What the Page Needs to Do
Before evaluating individual details, put the page’s main job into a sentence. For example: “This page should help someone choose a service and schedule an appointment.”
That gives you something concrete to review. Can a visitor tell the services apart? Is it clear how to book an appointment? Does the page explain what happens next?
A page can look appealing while leaving those questions unanswered. If the layout doesn’t help visitors choose the right service, that’s worth raising even if you like the overall style. Relating that concern to the page’s purpose gives me a specific problem to work through.
I recommend keeping that one-sentence goal nearby as you review. It helps connect a reaction like “This feels too busy” to a specific concern, such as too many competing choices before the booking link.
Point to the Specific Moment of Confusion
“The page is confusing” gives me a concern to investigate. “In the service comparison, I can’t tell whether the consultation is included in both options” gives me a place to start.
Try naming the page, section, and thing you’re trying to understand. You can use ordinary descriptions: “the first paragraph under the heading” or “the button beside the pricing information” is enough.
If you’re reviewing in Figma, placing a comment by the relevant element helps keep your observation connected to its location. You don’t need to turn the comment into a design brief.
Still unsure what’s bothering you? Describe where you hesitated or what you expected to find. “I reached this section and wasn’t sure what to read next” is useful feedback, even without a diagnosis. I can ask a follow-up question or suggest possibilities from there.
Explain the Reason Behind the Request
You’re welcome to suggest a solution. If you think a button should be larger, say so. Adding the reason helps me evaluate whether size, placement, wording, or another change would address the underlying concern.
Here are three hypothetical examples:
Making booking easier to find
- Less context: “Make the booking button bigger.”
- More context: “Booking is the main action on this page, but my attention goes to the newsletter signup first. Could the appointment option stand out more?”
Clarifying the brand’s tone
- Less context: “Make it feel more professional.”
- More context: “The playful headings feel more casual than the guidance we’re offering. Could the page feel approachable while conveying care and reliability?”
Helping someone find information
- Less context: “Move this section up.”
- More context: “Visitors need to confirm that we serve their area before booking. Could that information be easier to find near the appointment details?”
Each expanded comment identifies something the design should accomplish. That leaves room to discuss options while keeping your concern at the center of the decision.
Bring What You Know About Your Customers
You have information that a layout alone can’t provide: the questions people ask before buying, the differences they struggle to understand, and the concerns that make them hesitate.
Suppose prospective customers regularly ask whether they need a consultation before choosing a service. Sharing that question gives me a reason to make the answer easy to find. Without that context, I might not know how much attention it deserves.
Be clear about what you know and what you’re assuming. “Our sales team regularly gets this question” carries different information than “I wonder whether a first-time visitor would ask this.” Both can contribute to the discussion.
Personal preferences have a place, too. You can say, “I prefer a warmer color palette.” If there’s also a brand guideline or audience concern behind that preference, share it. Separating those reasons helps me understand what to explore and what needs to stay consistent.
Bring Your Team's Feedback Together
If several people are reviewing, I recommend comparing notes before passing along the combined feedback. That gives your team a chance to explain different priorities and identify decisions that still need discussion.
One person might want a shorter page, while another wants more service detail. The useful next question is which details visitors need to make a choice. Your team doesn’t have to settle on the design solution, but clarifying that need gives me a better basis for proposing one.
Flag business requirements and identify which concerns matter most. Separate those from ideas you’d like to explore. If opinions still differ, explain the priorities behind each view so I can consider them when proposing options.
Include what works, too. “The service comparison makes the options easy to understand; please preserve that clarity” helps guide revisions as much as a request for change.
Use a Simple Starting Sentence
For your next review, try this:
“On [page or section], I’m having trouble with [specific issue]. This matters because [user or business goal].”
You don’t have to use it for every comment. It’s there for the moments when you know something needs attention but aren’t sure how to explain it.
You bring knowledge of your business and customers; I bring design skills to help turn that knowledge into a workable page. Start with the section where you hesitated and tell me what made you pause.
