Skip to content
Kaarne Superstore⌕
Marketing & Messaging

A Client Comment Is a Clue, Not Yet a Design Instruction

Separate a client design comment into observation, interpretation and proposed solution. Use a three-column note to preserve the goal behind the request.

A designer examines a speech bubble separated into layers showing an eye, a question mark and a proposed paint stroke.

“Make the enquiry button bigger” is a proposed design change. It may be a useful one. Before implementing it, find the observation and business concern underneath the request, so the finished change addresses the reason the client spoke up.

Separate the evidence from the proposed response

A comment often compresses three different things: something the reviewer noticed, their explanation for it, and an idea for fixing it. Unpacking those parts does not dismiss the client’s judgement. It makes their knowledge usable in the design decision.

In this fictional example, a training provider reviews a course page and says, “The booking button is too small; people will miss it. Put a large red button at the top.” No visitor study has been conducted. The statement contains a visible design concern, a prediction about visitors and a suggested treatment. Those should not become one unquestioned fact.

Use a three-column interpretation note

The reviewer did not notice the booking action while reading the course introduction

  • Interpretation or concern: The next step may be difficult to find at that point
  • Proposed solution: Increase the button’s size and move it above the introduction

The eligibility note appears after the booking action

  • Interpretation or concern: People may act before recognising whether the course fits
  • Proposed solution: Move the eligibility note closer to the action

The button says “Continue”

  • Interpretation or concern: The next screen may be unclear
  • Proposed solution: Try a label that names the next step

The table deliberately uses cautious language for predicted visitor behaviour. One reviewer’s experience is useful input, but it does not establish how all visitors behave. Keep the original comment beside the note so your interpretation can be challenged or corrected.

Ask about the moment that prompted the comment

Invite the client to describe what they were trying to do when they noticed the problem. In the example, ask them to show the point where they expected to find the next step. Did they want to book immediately, check dates first or understand who the course was for?

That detail can change the design brief. A larger button might increase prominence while leaving its destination unclear. A moved button might separate the action from information the buyer needs. The client’s proposed treatment is one candidate; their underlying goal deserves to remain visible while you consider alternatives.

Write a decision that preserves the client’s goal

A useful working brief might read: “After understanding the course and eligibility, the reader should be able to identify how to check available dates. Review the action’s position, prominence and wording together.” This keeps the client’s concern about discoverability without deciding prematurely that size alone is the answer.

Then propose a small number of treatments with reasons. For example, one option could place a clearly labelled action beside the eligibility summary. Another could retain the present position with a more informative label. Explain the trade-off in the actual page context. Do not claim either option will improve bookings without evidence.

Return to the comment when reviewing the revision

Ask whether the revised page addresses the agreed concern. The review question is no longer simply “Is the button large enough?” It is whether the next step is understandable at the intended point in the reading journey, while the relevant course information remains available.

Record what was chosen, why it fits the brief and any question left open. If the client still prefers their first treatment, you now have a concrete basis for discussing it. If the team needs visitor evidence, describe that as a separate evaluation task rather than presenting a design conversation as a test result.

This note is about interpreting one design comment. It should not become a blanket rule that clients must supply research before raising a concern. Their observations begin a useful conversation; the designer’s responsibility is to turn that conversation into an intelligible decision.

Capture the visible issue before committing to the suggested fix. A comment attached to the relevant element can provide context while the design decision is still being considered.

A useful next step

For the next decision, read The Client Says “Make It Pop.” What Do You Ask Next? and The Developer Needs More Than “the Button on the Right”.

0

Discussion 0

What did this article make you think about?

Join the conversation

Your email address will not be published. Required fields are marked *

Saved articles

Saved in this browser.