<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rivet CX on Medium]]></title>
        <description><![CDATA[Stories by Rivet CX on Medium]]></description>
        <link>https://medium.com/@rivetcx?source=rss-f56fc013caa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*olo_rifgt31jwriXCB7Ucg.jpeg</url>
            <title>Stories by Rivet CX on Medium</title>
            <link>https://medium.com/@rivetcx?source=rss-f56fc013caa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:37:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rivetcx/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Value of Digital Prototyping]]></title>
            <link>https://medium.com/@rivetcx/the-value-of-digital-prototyping-ab58d30dee5?source=rss-f56fc013caa------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab58d30dee5</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Rivet CX]]></dc:creator>
            <pubDate>Tue, 12 Jun 2018 15:31:02 GMT</pubDate>
            <atom:updated>2018-06-12T15:31:02.626Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V4EHNn7dwBcKBQ9KA-_tMw.jpeg" /></figure><p>Prototyping isn’t new. It’s always been an effective approach to significant decision-making when building physical products. So why have so many product teams skipped this critical approach when it comes to digital products?</p><p>Designing a physical product starts with creating and sharing many prototypes out of cheap materials such as blue foam, clay, or wood. This manual process allows the designer to get the form and function right. It’s human-centered and illuminating.</p><p>Holding a prototype in your hand exposes terrible ideas that just don’t fit. Sharing it uncovers features that are improbable to manufacture or fail to overcome user challenges. Tool and die costs are high. Go-to-market costs can be even higher. In the physical world, it’s clear how prototyping mitigates risk, and why product development plans account for this guiding approach.</p><p>Applying a prototyping approach to digital products affords the same benefits — risk mitigation and improved market success. Too often we see impatient business, marketing or development groups jump straight from idea to development only to get stuck with re-work because of misaligned understanding or expectations. We’ve also all seen products fail because they just weren’t usable for the end-customer.</p><p>According to a <a href="https://www.mckinsey.com/business-functions/digital-mckinsey/our-insights/delivering-large-scale-it-projects-on-time-on-budget-and-on-value">McKinsey and Oxford Uni­versity study</a> of large software projects, 66% of projects go over budget, and 33% go over schedule. They also reported that as many as 17% of projects “go so bad that they can threaten the very existence of the company.”</p><blockquote>“If a picture is worth 1000 words, a prototype is worth 1000 meetings.” — Tom &amp; David Kelley</blockquote><p>Taking the time to prototype will make both your project and product more successful. Simple prototypes can measure the success of higher-level concepts. Medium fidelity prototypes are useful for measuring optimum workflows and overall screen layout. But we’ve found that the most efficient and effective prototypes are what we call True-Fi Prototypes.</p><p>Rivet CX’s True-Fi Prototypes reduce uncertainty for stakeholders, developers, and users. A True-Fi Prototype accounts for all states, controls, and instance details. Built with real, but static, business data and content these prototypes provide a realistic simulation of the system’s most important use cases.</p><p>The benefits of providing this level of detail include:</p><ul><li>Removing the guesswork from feature development</li><li>Minimizing UI documentation</li><li>Reducing BA time to review and translate to software requirements specifications</li><li>Allowing for insightful customer testing prior to development</li><li>Providing the highest level of clarity for stakeholder approvals</li></ul><p>Your customer-centered digital product strategy deserves the best chance for a successful implementation. Keeping your teams aligned and the customer involved throughout the design and implementation process helps ensure your great ideas don’t go to waste.</p><p>Skip the developer re-work by adding a little time to build a True-Fi Prototype before development, and you gain confidence that your product will be accurately built and successful with customers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab58d30dee5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>