{"id":3047,"date":"2026-11-19T11:03:53","date_gmt":"2026-11-19T09:03:53","guid":{"rendered":"https:\/\/www.kaarne.fi\/superstore\/?p=3047"},"modified":"2026-11-19T11:07:20","modified_gmt":"2026-11-19T09:07:20","slug":"a-client-comment-is-a-clue-not-yet-a-design-instruction","status":"publish","type":"post","link":"https:\/\/www.kaarne.fi\/superstore\/articles\/a-client-comment-is-a-clue-not-yet-a-design-instruction\/","title":{"rendered":"A Client Comment Is a Clue, Not Yet a Design Instruction"},"content":{"rendered":"<p>\u201cMake the enquiry button bigger\u201d 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.<\/p>\n<h2>Separate the evidence from the proposed response<\/h2>\n<p>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\u2019s judgement. It makes their knowledge usable in the design decision.<\/p>\n<p>In this fictional example, a training provider reviews a course page and says, \u201cThe booking button is too small; people will miss it. Put a large red button at the top.\u201d 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.<\/p>\n<h2>Use a three-column interpretation note<\/h2>\n<h3>The reviewer did not notice the booking action while reading the course introduction<\/h3>\n<ul>\n<li><strong>Interpretation or concern:<\/strong> The next step may be difficult to find at that point<\/li>\n<li><strong>Proposed solution:<\/strong> Increase the button\u2019s size and move it above the introduction<\/li>\n<\/ul>\n<h3>The eligibility note appears after the booking action<\/h3>\n<ul>\n<li><strong>Interpretation or concern:<\/strong> People may act before recognising whether the course fits<\/li>\n<li><strong>Proposed solution:<\/strong> Move the eligibility note closer to the action<\/li>\n<\/ul>\n<h3>The button says \u201cContinue\u201d<\/h3>\n<ul>\n<li><strong>Interpretation or concern:<\/strong> The next screen may be unclear<\/li>\n<li><strong>Proposed solution:<\/strong> Try a label that names the next step<\/li>\n<\/ul>\n<p>The table deliberately uses cautious language for predicted visitor behaviour. One reviewer\u2019s 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.<\/p>\n<h2>Ask about the moment that prompted the comment<\/h2>\n<p>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?<\/p>\n<p>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\u2019s proposed treatment is one candidate; their underlying goal deserves to remain visible while you consider alternatives.<\/p>\n<h2>Write a decision that preserves the client\u2019s goal<\/h2>\n<p>A useful working brief might read: \u201cAfter understanding the course and eligibility, the reader should be able to identify how to check available dates. Review the action\u2019s position, prominence and wording together.\u201d This keeps the client\u2019s concern about discoverability without deciding prematurely that size alone is the answer.<\/p>\n<p>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.<\/p>\n<h2>Return to the comment when reviewing the revision<\/h2>\n<p>Ask whether the revised page addresses the agreed concern. The review question is no longer simply \u201cIs the button large enough?\u201d It is whether the next step is understandable at the intended point in the reading journey, while the relevant course information remains available.<\/p>\n<p>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.<\/p>\n<p>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\u2019s responsibility is to turn that conversation into an intelligible decision.<\/p>\n<p>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.<\/p>\n<h2>A useful next step<\/h2>\n<p>For the next decision, read <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/the-client-says-make-it-pop-what-do-you-ask-next\/\">The Client Says \u201cMake It Pop.\u201d What Do You Ask Next?<\/a> and <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/the-developer-needs-more-than-the-button-on-the-right\/\">The Developer Needs More Than \u201cthe Button on the Right\u201d<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Separate a client design comment into observation, interpretation and proposed solution. Use a three-column note to preserve the goal behind the request.<\/p>\n","protected":false},"author":1,"featured_media":3083,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_hide_featured_image":false,"_jetpack_featured_image_duplicate_dismissed":0,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[23],"tags":[],"class_list":["post-3047","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-product-messaging"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/www.kaarne.fi\/superstore\/wp-content\/uploads\/sites\/7\/2026\/11\/np-05-01.webp","_links":{"self":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3047","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/comments?post=3047"}],"version-history":[{"count":10,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3047\/revisions"}],"predecessor-version":[{"id":3208,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3047\/revisions\/3208"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media\/3083"}],"wp:attachment":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media?parent=3047"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/categories?post=3047"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/tags?post=3047"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}