{"id":3394,"date":"2026-11-19T12:31:18","date_gmt":"2026-11-19T10:31:18","guid":{"rendered":"https:\/\/www.kaarne.fi\/superstore\/?p=3394"},"modified":"2026-11-19T12:31:30","modified_gmt":"2026-11-19T10:31:30","slug":"tell-the-story-of-a-prototype-without-inventing-customer-results","status":"publish","type":"post","link":"https:\/\/www.kaarne.fi\/superstore\/articles\/tell-the-story-of-a-prototype-without-inventing-customer-results\/","title":{"rendered":"Tell the Story of a Prototype Without Inventing Customer Results"},"content":{"rendered":"<p>A prototype story needs a person and a problem, but it does not need an invented success rate or a quotation from a customer who never existed. You can make the design understandable by showing the decision it helps someone approach.<\/p>\n<h2>Introduce the example\u2019s status before its plot<\/h2>\n<p>Use an opening that travels with the presentation: \u201cThis is an illustrative business and customer situation created to explain the proposed page structure.\u201d Put an appropriate label on shared material too. A disclaimer spoken once in a meeting may not reach the colleague who later receives a screenshot.<\/p>\n<p>For this fictional example, an equipment-rental company serves people organising small community events. Our illustrative customer is arranging an outdoor talk and wants to know which information to provide before asking about equipment. The characters, business and journey are invented. We are not presenting a customer case study or reporting a tested website.<\/p>\n<h2>Give the character a practical uncertainty<\/h2>\n<p>The organiser does not know whether to begin with a product list or describe the event. That uncertainty gives the prototype a useful question: can the proposed page help them prepare an intelligible enquiry? Keep the situation specific enough to explain a design choice without adding an unnecessary biography.<\/p>\n<p>Avoid fictional authority signals such as a realistic customer logo wall, a named recommendation or an impressive revenue chart. Those elements can look like evidence even when they were only added to complete a layout. If the final site will require customer proof, identify that as material to obtain and verify separately.<\/p>\n<h2>Show the choice the page makes visible<\/h2>\n<p>The demonstration could begin with event needs, then show the information requested for an enquiry: location, audience size to confirm, power availability and the intended use. These are proposed fields for discussion with the real offer owner, not claims that every rental service needs or can support this intake.<\/p>\n<p>Narrate the reason: \u201cThis arrangement asks the organiser to describe the occasion before choosing a package.\u201d Then show the alternative the design avoids, such as forcing an unfamiliar person to choose between unexplained product names. You are explaining a proposed structure, not proving that the structure will outperform another one.<\/p>\n<h2>Finish at a decision, not an invented result<\/h2>\n<p>A useful story ending is: \u201cThe organiser can now see what information this proposed enquiry asks for. We need the service team to confirm that those details support its actual response process.\u201d It ends where the next project decision begins.<\/p>\n<p>An unsupported ending would say that the organiser booked faster, increased attendance or became a delighted repeat customer. Those claims would turn a designed scenario into apparent outcome evidence. Keep any real observations separate: if a reviewer interpreted a label during a meeting, record who reviewed what and the limits of that observation. Do not promote it into a claim about customers generally.<\/p>\n<h2>Use a four-part speaking card<\/h2>\n<p>Write the scenario; the uncertainty; the proposed design choice; the decision required next. For the rental example, the last line might request confirmation of the intake questions. The card can guide a short presentation without filling every section with persuasive flourish.<\/p>\n<p>Add a separate evidence note stating what, if anything, is real and cleared for this presentation. The prototype layout may be your work, while the photography is illustrative and the service facts remain provisional. Those different statuses should stay distinguishable. A polished scene does not make each ingredient equally verified.<\/p>\n<h2>Check what survives when the story is shared<\/h2>\n<p>Before sending the deck or link, read it without your narration. Can a recipient tell that the business and customer are illustrative? Could a sample quote be mistaken for an endorsement? Does a graph suggest measured performance? Remove or relabel anything whose appearance makes a stronger claim than the material supports. The story earns its place by revealing the proposal\u2019s reasoning, with its boundaries intact.<\/p>\n<p>Label the example as illustrative and explain the choices it makes visible. Sample content should help someone understand the proposal, not masquerade as customer evidence.<\/p>\n<p>To choose the prototype\u2019s question, read <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/what-should-a-website-prototype-prove-in-a-sales-conversation\/\">the framework for a bounded sales demonstration<\/a>. When real material replaces the scenario, keep <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/replace-demo-content-without-losing-the-decisions-behind-the-layout\/\">the content-transition decisions visible<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A fictional demo can make a proposed journey understandable. Its story should explain choices, while leaving testimonials, measured results and real-client claims out.<\/p>\n","protected":false},"author":1,"featured_media":3430,"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-3394","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\/sf-02-03.webp","_links":{"self":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3394","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=3394"}],"version-history":[{"count":7,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3394\/revisions"}],"predecessor-version":[{"id":3510,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3394\/revisions\/3510"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media\/3430"}],"wp:attachment":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media?parent=3394"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/categories?post=3394"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/tags?post=3394"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}