<?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 Kenneth Erickson on Medium]]></title>
        <description><![CDATA[Stories by Kenneth Erickson on Medium]]></description>
        <link>https://medium.com/@kenneth.erickson?source=rss-b9fc80c7ed7f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*RBKlcjOLfFQ-nb9Kyg3XMw.jpeg</url>
            <title>Stories by Kenneth Erickson on Medium</title>
            <link>https://medium.com/@kenneth.erickson?source=rss-b9fc80c7ed7f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:08:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kenneth.erickson/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[Finding the MVE in your MVP]]></title>
            <link>https://medium.com/@kenneth.erickson/finding-the-mve-in-your-mvp-b310f13f52bf?source=rss-b9fc80c7ed7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b310f13f52bf</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[experience-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Kenneth Erickson]]></dc:creator>
            <pubDate>Thu, 20 Jun 2019 04:01:14 GMT</pubDate>
            <atom:updated>2019-06-20T05:45:30.236Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rYqxGE8b5_lxlvF4OoE_AA.jpeg" /></figure><p>Defining a Minimum Viable Product is a tried and trusted method of scoping your build if you need to develop and test your solution as rapidly as possible. However, when time and resources are limited, it can often become a lonely fight for designers to make the case to your project team to adequately prioritise features that uplift the user experience.</p><p>Pressures of budget and timelines can see these features start to slip down the backlog, in favour of having something — anything — in the field and relatively operational.</p><p>Although rapidly pushing features into the market is a major driver for most delivery teams and their stakeholders, focusing wholly on the product can create a pattern that eventually falls short of the wider experience that the MVP was first established to enable. So often, due to the nature of managing product roadmaps and change management within large organisations, the imperative to deliver on initiatives defined largely by products and features can result in design and technical debt that becomes difficult to justify resolving.</p><p>Wholly product-centric approaches can carry the risk of losing sight of your solution’s impact across the customer value chain, and compromise the overall strategic vision and customer experience. Additionally, prioritising only the delivery of functionality-first MVPs can potentially prevent teams from being able to adapt their strategic vision, tethered to a string of siloed product releases that carry a measure of design debt that may be difficult to revisit without significant investment.</p><p><strong>“If it doesn’t work, there won’t be any users to worry about.”</strong></p><p>The MVP is, by nature, principally concerned with the success of itself. It is still an excellent means of accelerating the learning experience and testing our assumptions, proving our product concepts and gathering real-world data, allowing us to learn quickly and adapt. With an MVP, proving the functional validity of the feature-set is a higher priority than ensuring an optimal user experience.</p><p>In practice, the concept of an MVP and an MVE are quite close. Both account for scoping the minimum criteria — in features, in function, and in user experience. They both seek to prioritise the features that will achieve the most valuable outcomes, versus the resources available, with the key difference being in the nature of those priorities and whose needs the product is trying to satisfy:</p><ul><li>The user’s, by ensuring each stage of their interaction with your product meets their needs and expectations?</li><li>Or the business’s, by proving that their product design is viable from a technical perspective, providing dev-ops and designers with insights that will help them iterate future versions.</li></ul><p>Whether MVP or MVE, the hope is that your product should account for the best ‘expected’ outcome you can achieve, aligning as much as possible to your user’s needs whilst contributing directly to your overall strategic objectives — which for most businesses will hopefully have their customer’s satisfaction at the centre.</p><p>With an MVP, where the initial product’s experience may be less than ideal, you can build upon this feature-set by pursuing an MVE design that accounts for the inevitable pain-points and, where possible, incorporate means to mitigate or lessen these issues and manage your users’ expectations. <br>This sort of due diligence to the user’s experience, in the context (and in support) of the design and delivery of your MVP, is what ensures your minimum, viable experience.</p><p>By keeping a concept of the baseline user experience front of mind throughout your earliest product iterations, you can help build essential elements into your MVP’s design that accommodates a sufficient level functionality, without compromising the user’s experience.<br>If we cannot deliver the ideal experience with the resources available, we can at least do what we can to mitigate the impacts, by identifying potential pain-points within our user flows and ideating simple, human-centred methods of addressing them.</p><p>The greatest risk of delivering a less-than-ideal experience within the MVP is how that compromised experience can become encoded in users’ memories. <br>In reality, your users have little or no concern for your product or it’s validity from a business perspective; they care for their own needs and any outcome that meets their expectations. The relationship with the product is conditional on how well it eases the user through its workings, and how satisfying the outcomes of those interactions were. Meeting these expectations is as vital as validating the technical functionality of your design.</p><p><strong>Defining the MVE</strong></p><p>By the time you’re scoping your solution, your team should have a fairly good understanding of what your users are trying to achieve. By interrogating your users’ objectives, we can start to extrapolate a minimal viable experience by building a view of what they might expect when interacting with your product.</p><p>Effectively the MVE is an experience that meets every step of the desired user flow, providing sufficient features to enable the entire flow with minimum impact to the user — how you achieve this behind the scenes is less important to the user, as long as they aren’t inhibited in any significant way.</p><p>For example, if your design entails enabling a user to search for a service, book it, pay for it, and then receive a summary and confirmation of their transaction, then it’s insufficient if the solution simply supports the discovery and purchase of the service. If a confirmation isn’t delivered, then the flow is broken and the experience is compromised.</p><p>For product teams, there are a number of practical ways to approach incorporating an agreed upon, minimum viable experience into your product designs. An approach I enjoy is to use a slightly expanded version of feature mapping.</p><p><strong>1. Map your features</strong></p><p>A technique common to lean, inception style design work, Feature Mapping is a fairly straightforward method of quickly scoping your MVP, by outlining the functional features that are required to fulfill each stage of the user flow.</p><p>Against each stage of your potential user flow (or journey map, or service blueprint), list each activity a user or the solution will need to undertake to achieve their goal or have a need met. <br>For each activity, map the features that would be required to fulfill that activity — this can include things such as UI elements, system triggers, and events, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7ZQUxJi1GDxU6lyi" /><figcaption>Begin by mapping your features against each stage of the user flow.</figcaption></figure><p><strong>2. Map your experience requirements</strong></p><p>For each of these features, consider what would be required for those elements to deliver on the user’s objectives. In your Feature Map, ideate and add notes around the desired experience against each relevant feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hpldejti5TuZCB1j" /><figcaption>Against each feature, ideate the desired experience elements &amp; behaviours.</figcaption></figure><p>For example, are there things the user needs to have ready before they complete a certain step in your process? If so, do you believe they have been adequately informed in previous steps, and do they understand why these things are needed? What feedback would the user like to see within the UI to help them with this?</p><p>When mapping the user flows, or better yet, the user’s journey, you can overlay the user’s objectives within the journey to identify the key moments of impact for your user, and interrogate where they may have questions before or after completing these steps. Ask yourself what you would consider being the success criteria for each objective, and investigate where in the flow this criteria may be met.</p><p>The same goes for any potential pain points. Analise where in the flow users may become confused or have questions — or most critically, where your MVP may be lacking in features to meet their expectations — and workshop ways to mitigate the pain points that cannot be prevented within your MVP.</p><ul><li>Examples of this include designing messaging that sets a user’s expectations around a particular interaction, directing users to alternate services in clearly defined scenarios. Use your modeling of their objectives to anticipate and meet their expectations at every stage of the flow.</li><li>In the absence of dynamic features that provide efficiencies to the user, experiment with lower effort solutions such as content to help mitigate possible confusion and service your desired MVE.</li></ul><p><strong>3. Refine your feature map</strong></p><p>Now that you’ve mapped specific ideas around the desired user experience, you have a chance to revisit your feature list and iterate. You may find that some ideas that surfaced in the experience layer may necessitate a new feature at a certain stage in your journey. Additionally, new elements or ideas may make previously mapped features redundant, as you may have addressed this requirement earlier in your flow (ideally at a stage better suited to the user’s needs).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pnaX2fSO1Jk3ZSYk" /><figcaption>Refine your feature map, adding new or removing features to support your desired experience.</figcaption></figure><p>Some questions you can ask yourself when revisiting the feature map may include:</p><ul><li>Are the customer’s objectives being met be each stage or the flow, with the features outlined? Are there any redundancies or unnecessary repetition?</li><li>Are there customer objectives with no corresponding feature? If so, there is a risk of not delivering on minimum experience requirements. Either investigate what features can be introduced or expanded to reduce this impact, or look at alternative ways (such as content) to manage the expectations that are not being met due to the absence of this feature.</li><li>Are there features without a corresponding objective? For instance, features that do not add clear value to the user’s experience. Interrogate what this feature enables. Can this feature be replaced by one that does?</li></ul><p><strong>4. Define your MVE scope</strong></p><p>With your features refined, you should now have a fairly robust outline of your solution that adequately aligns your product’s feasible functionality with the desired user experience. From here you can begin the difficult process of prioritising your stories in line with your initial budget and delivery constraints. <br>However, by having now mapped each element of your solution against the desired user experience, you should be able to more accurately prioritise features that will provide sufficient functionality, whilst having also ensured that each element directly contributes to the user’s objectives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hvoZ4awKT0rlv-EY" /><figcaption>Lastly, prioritise your refined feature set to inform your initial MVE backlog.</figcaption></figure><p><strong>5. Learn from the MVE</strong></p><p>Once your product has been released, it’s time to re-enter your design cycle and begin discovery on how they MVE is performing, not just from a technical perspective, but also for how your customers are reacting to it.</p><ul><li>Monitor and track the MVE as you would the MVP. Are your users’ objectives being met? Are there new behaviours or pain points that have been discovered now your product is out in the wild? Add this learning as a layer within your showcases to speak to the material CX value being delivered by this work, in addition to the foundational, technical capabilities that are being built and validated.</li><li>Your insights will now contribute to further research and discovery for future interactions, allowing you to identify areas of focus that will refine and improve the overall experience.</li></ul><p><strong>Just the start.</strong></p><p>As interchangeable as these terms have a habit of becoming, the concepts are symbiotic and enable teams to deliver on business and user requirements in a balanced fashion.</p><p>As the MVP is a method of prioritising features and stories to deliver value as soon as possible with the resources available, so too is the MVE a design tool to help prioritise and uplift these features. By aligning both of these concepts, you can do your best to ensure that the earliest iterations of your minimum viable product are also delivering on your minimum viable experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b310f13f52bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>