Foldwren

How to give useful feedback to your web designer

How to describe problems instead of prescribing fixes, gather feedback into a single round and settle who makes the final decision.

The most useful feedback you can give a web designer describes what is wrong and why, then leaves the fix to them. "I couldn't find the phone number" will get you a better result than "make the phone number bigger and red".

Good feedback is a skill, and nobody teaches it to business owners. A few habits make the difference between a project that wraps up in two tidy rounds and one that drags through eleven versions of the homepage.

Describe the problem, not the solution

When you look at a design and something bothers you, the natural move is to jump straight to a fix. Resist it for a moment and ask yourself what the underlying problem is.

Compare these:

  • Solution: "Move the reviews up to the top." Problem: "I'm worried people won't see that we're well reviewed before they leave."
  • Solution: "Make the logo bigger." Problem: "The business name doesn't stand out enough to me."
  • Solution: "Change the green to blue." Problem: "This green feels a bit clinical for a florist."

The problem version gives your designer room to work. There might be three ways to show you are well reviewed, and moving the whole section may be the worst of them. A star rating beside the main button could do the job without pushing your services down the page.

If you do have a fix in mind, by all means share it. Just include the reason, so the designer can solve the actual issue if your suggestion turns out to cause a new one.

Be specific about what and where

Vague feedback is the hardest kind to act on. Some phrases designers hear every week:

  • "Can you make it pop?"
  • "It needs a bit more wow."
  • "I'll know it when I see it."
  • "Something's not right."

None of these are wrong to feel. They just need translating. Try to pin down three things:

  1. Where. Which page, which section. "The services section on the homepage."
  2. What you noticed. "The three boxes all look the same and my eye skips past them."
  3. What you expected. "I thought our main service would stand out more than the other two."

Mention the device as well. "On my phone the heading runs over four lines" is far more helpful than "the heading is too long", because the designer may be looking at a wide screen where it sits happily on one.

Judge the design against the goals

Here is the uncomfortable part. You are not the customer. Your favourite colour, your dislike of a certain font and your partner's opinion of the photo are all real, but none of them tells you whether the site will work.

Before you write anything, reread the brief. Then look at the design and ask:

  • Would a first time visitor understand what we do within a few seconds?
  • Is it obvious how to get in touch or book?
  • Does this feel right for the people we are trying to reach?
  • Does it answer the questions customers ask us most?

Feedback tied to those questions carries weight. "Our customers are mostly retirees, and I think this text is too small for them" is a strong point that any designer will act on. "I just don't love the font" is a weaker one, though still worth saying if it truly bothers you. You have to live with the site, after all.

Gather everything into one round

Feedback that arrives in dribs and drabs, an email on Monday, a text on Wednesday, a voice message from your business partner on Friday, costs everyone time and usually produces contradictions. One person wants the logo larger. Another wants more space at the top. Your designer can't do both and shouldn't have to referee.

A process that works:

  1. Agree a date by which everyone will have reviewed the design.
  2. Have each person look at it on both a phone and a computer.
  3. Collect all comments in one document, organised page by page.
  4. Sort out any disagreements among yourselves before sending.
  5. Mark each item as "must change" or "would be nice".
  6. Send it once.

Most design agreements include a set number of revision rounds. Three scattered emails can easily be counted as three rounds. A single considered document is one.

Settle who decides

Every project needs one person with the final say. Others can give input, and should, but one person weighs it all up and makes the call.

The situation to avoid is the late arrival. A business partner, a spouse or a board member who hasn't been involved sees the design the night before launch and has strong views. By then changes are expensive and morale takes a hit. If someone's opinion can overturn a decision, show them the work at each key stage: the early layout, the first full design and the near finished site.

A checklist before you hit send

  • Have I said what is working, as well as what isn't? Designers need to know what to keep.
  • Is each comment tied to a specific page and section?
  • Have I described the problem and the reason behind it?
  • Have I checked the design on a phone?
  • Is this one combined list from everyone who has a say?
  • Are the priorities marked?
  • Is anything on the list really a new request that wasn't in the brief? If so, flag it as one and ask what it does to the cost and timing.

Clear, consolidated, reasoned feedback is the cheapest way to improve a website project. It costs you an extra half hour per round and can save weeks.

Your order