{"id":3038,"date":"2026-11-19T11:03:45","date_gmt":"2026-11-19T09:03:45","guid":{"rendered":"https:\/\/www.kaarne.fi\/superstore\/?p=3038"},"modified":"2026-11-19T11:04:03","modified_gmt":"2026-11-19T09:04:03","slug":"the-client-says-make-it-pop-what-do-you-ask-next","status":"publish","type":"post","link":"https:\/\/www.kaarne.fi\/superstore\/articles\/the-client-says-make-it-pop-what-do-you-ask-next\/","title":{"rendered":"The Client Says \u201cMake It Pop.\u201d What Do You Ask Next?"},"content":{"rendered":"<p>The client has looked at your draft and supplied four words: \u201cMake it pop more.\u201d You can enlarge the heading, brighten the button or replace the photograph. Each would be a response. None yet tells you what problem you are trying to solve.<\/p>\n<h2>Treat the comment as an opening<\/h2>\n<p>A useful first reply is neither a defence of the design nor an immediate promise to change it. Try: \u201cCan we look at the particular part you mean?\u201d That keeps the conversation about the page rather than whether either person has good taste. The client may be reaching for visual language because the underlying concern is easier to recognise than describe.<\/p>\n<p>Consider a fictional freelancer presenting a service page for a repair business. The client says the upper section needs more impact. The freelancer is tempted to add a large red banner. Instead, she asks three questions and records the answers beside the draft.<\/p>\n<h2>Ask where the concern lives<\/h2>\n<p>\u201cWhich element or section are you looking at?\u201d Ask the client to point, identify the text or describe the location precisely enough that someone else can find it. \u201cThe page\u201d is too broad to guide a small change. \u201cThe sentence below the opening photograph\u201d is workable.<\/p>\n<p>If the comment concerns several places, separate them. A quiet service heading and a hard-to-find enquiry link may need different decisions. Record both rather than using one dramatic redesign to answer an undefined collection of concerns. Do not demand that the client propose a technical solution before you can understand the observation.<\/p>\n<h2>Ask what the reader should notice<\/h2>\n<p>\u201cWhat should someone notice or understand here first?\u201d This moves the discussion from a preferred effect to an intended priority. In the repair example, the answer is that customers should recognise that collection is available. The current heading names the business but leaves the collection service in small supporting text.<\/p>\n<p>Now the freelancer has something to examine. She can propose giving the collection information a clearer position and wording. A bigger logo would not answer the same question, even if it made the section look more striking. Keep the intended message in the note so the eventual design can be reviewed against it.<\/p>\n<h2>Ask why that priority matters here<\/h2>\n<p>\u201cWhat should the reader be able to decide or do after noticing it?\u201d The client explains that suitable customers should understand the service area before requesting collection. This adds an important boundary: making collection conspicuous without showing the area could invite the wrong expectation.<\/p>\n<p>The resulting brief is specific: make the collection option and covered area easy to find in the opening section, then point to the existing enquiry route. It does not claim that a particular colour will increase enquiries. It identifies the communication the design needs to support.<\/p>\n<h2>Read back one proposed change<\/h2>\n<p>Use a short confirmation: \u201cYou mean the opening service message. Readers need to see that collection is available within the stated area before they enquire. I\u2019ll revise that message and its emphasis, then show you that section again. Is that the issue?\u201d This gives the client a chance to correct your interpretation before you spend the next hour polishing the wrong element.<\/p>\n<p>A reusable note can contain five lines: location; current observation; intended reader understanding; proposed change; how we will review it. For the last line, ask the client to identify the collection option and area in the revised version. That is a communication check, not a prediction of sales.<\/p>\n<h2>Leave room for a real preference<\/h2>\n<p>Sometimes the answer really is a stylistic preference: the client wants a livelier visual identity. Record that honestly and agree how much of the page it affects. Your three questions need not turn every preference into a business claim. Their job is to distinguish a broad style discussion from a local problem with emphasis, wording or hierarchy.<\/p>\n<p>Before changing the design, agree which element the comment concerns and what the reader should notice. That gives you a useful brief whether feedback arrives in a call, an email or directly on the page.<\/p>\n<p>If another message appears to repeat an old request, use <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/did-the-client-ask-again-or-did-the-website-change-again\/\">the three-case comparison for recurring website feedback<\/a>. For team handoff, keep <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/resolved-is-not-the-same-as-ready-to-launch\/\">implementation and launch readiness separate<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Three questions can turn a taste comment into a reviewable design decision: locate it, explain its purpose and name the reader\u2019s next action.<\/p>\n","protected":false},"author":1,"featured_media":3074,"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":[24],"tags":[],"class_list":["post-3038","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-customer-understanding"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/www.kaarne.fi\/superstore\/wp-content\/uploads\/sites\/7\/2026\/11\/np-01-01.webp","_links":{"self":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3038","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=3038"}],"version-history":[{"count":7,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3038\/revisions"}],"predecessor-version":[{"id":3148,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3038\/revisions\/3148"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media\/3074"}],"wp:attachment":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media?parent=3038"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/categories?post=3038"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/tags?post=3038"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}