<?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 Stéphanie Prugne on Medium]]></title>
        <description><![CDATA[Stories by Stéphanie Prugne on Medium]]></description>
        <link>https://medium.com/@stephanieprugne_68112?source=rss-845782c7c57------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*OeptKoMBWaGxOReU</url>
            <title>Stories by Stéphanie Prugne on Medium</title>
            <link>https://medium.com/@stephanieprugne_68112?source=rss-845782c7c57------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:25:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@stephanieprugne_68112/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 3 versions approach: How I design features to unlock creativity and strategy]]></title>
            <link>https://medium.com/design-bootcamp/the-3-versions-approach-how-i-design-features-to-unlock-creativity-and-strategy-b8ef2ad8c5da?source=rss-845782c7c57------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8ef2ad8c5da</guid>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Stéphanie Prugne]]></dc:creator>
            <pubDate>Fri, 17 Oct 2025 11:11:19 GMT</pubDate>
            <atom:updated>2025-10-17T11:11:19.360Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why exploring multiple design paths leads to better ideas, clearer decisions, and more innovative solutions</h4><figure><img alt="Description: A hand places a wooden cube on top of a staircase-like structure made of stacked wooden blocks, representing growth, progress, or step-by-step building. Object: Wooden cube and staircase-like structure of blocks Action: A hand places the cube on top Context: Symbolizing growth, progress, or gradual building" src="https://cdn-images-1.medium.com/max/1024/1*0KntlGhmL615X5Z2kajTbQ.jpeg" /><figcaption>Image from <a href="https://unsplash.com/photos/a-person-placing-a-piece-of-wood-into-a-pyramid-vsLbaIdhwaU">Unsplash</a></figcaption></figure><p>We’ve all been there. When a new feature is requested, it’s tempting to jump straight into designing exactly what was asked. After all, the goal is to ship fast and meet expectations.</p><p>But in my experience as a product designer, sticking to the first request often misses opportunities for both the user and the business. This challenge is even more pronounced in startup contexts, where speed is everything and many team members may not have deep product design experience. Founders, engineers, or PMs will often suggest solutions that are functional but narrow. That’s where design expertise makes the difference: not only delivering what’s asked for, but also expanding the team’s vision, <a href="https://medium.com/nyc-design/reframing-the-problem-200f6c966dfc">reframing problems</a>, and surfacing new possibilities they might never have imagined.</p><p>To explore the full potential of every feature and help teams discover better outcomes, I always design <strong>three</strong> <strong>versions</strong>. This transforms the conversation from <em>‘</em><strong><em>Can we build this?’</em></strong> to <em>‘</em><strong><em>What’s the best way to solve this problem?’ <br></em></strong>The key is making sure each version is based on user research; otherwise even the most creative design risks missing what users actually need.</p><p>It’s worth noting that this approach isn’t necessary for every small tweak or minor update. When speed and simplicity matter most, a single version is often enough. I reserve the<strong> 3 versions approach</strong> for features with significant impact, higher uncertainty, or where reducing risk is especially important. It also helps build trust within the team by inviting them into the reflection process and showing that their ideas can evolve into stronger, more thoughtful solutions.</p><h3>Version 1 : The requested feature</h3><p>The first version is simple: it’s the baseline.</p><p>This version answers the question: <strong><em>“What does the user actually need right now?”</em></strong></p><p>It ensures that the core requirements are met, deadlines are respected, and the user gets the minimum viable solution.</p><p><strong>Example</strong>: If a PM requests a search filter, version 1 delivers exactly that: users can filter by category and sort results.</p><p>✅ <strong>Purpose</strong>: meet expectations efficiently without overcomplicating.</p><h3>Version 2 : The thoughtful version</h3><p>Next comes the version that goes a step further.</p><p>I analyze the impact on workflows, UX, and long-term product strategy. This version anticipates friction points, improves usability, and often uncovers subtle opportunities the first version misses.</p><p><strong>Example</strong>: In the search filter scenario, I might add smart inputs based on user behavior or predictive suggestions that reduce clicks and streamline the workflow.</p><p>✅ <strong>Purpose</strong>: show strategic thinking and spark meaningful discussions with the team.</p><h3>Version 3 : The “Out of the box” version</h3><p>The third version is where creativity shines.</p><p>It challenges assumptions, explores innovative approaches, and gives the team a glimpse of what’s possible beyond the immediate request.</p><p><strong>Example</strong>: Instead of a traditional filter panel, I might propose an AI-driven recommendation engine that predicts what the user wants before they even search.</p><p>✅ <strong>Purpose</strong>: unlock innovation, encourage the company to think bigger, and reveal new opportunities that weren’t obvious at first glance.</p><h3>Why this approach matters</h3><p>The real power of the <strong>3 versions approach</strong> is how it changes the conversation. When the team sees three different takes side by side, they start thinking differently, much like the mindset shift described in <a href="https://neilturneruxm.medium.com/why-you-should-always-review-multiple-designs-113761099ee6">Why You Should Always Review Multiple Designs.</a></p><p>Here’s what usually happens:</p><ul><li>Encourages critical thinking and creativity</li><li>Allows teams to compare options strategically</li><li>Ensures alignment with long-term business goals</li><li>Keeps the user experience at the center while exploring innovation</li></ul><p>Instead of rushing into execution, the team is suddenly debating strategy and that’s where the best solutions emerge.</p><h3>Final thoughts</h3><p>Th<strong>e 3 versions approach </strong>isn’t just about giving options. It’s about encouraging the team to think differently and uncover solutions that may have been invisible at first.</p><p>I’ve found that this method sparks richer discussions, smarter trade-offs, and sometimes leads to completely unexpected breakthroughs.</p><p><strong>How do you approach feature design in your team?<br>Have you experimented with multiple versions before committing to one?</strong></p><p>I’d love to hear your experiences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8ef2ad8c5da" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-3-versions-approach-how-i-design-features-to-unlock-creativity-and-strategy-b8ef2ad8c5da">The 3 versions approach: How I design features to unlock creativity and strategy</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>