<?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 Jill T on Medium]]></title>
        <description><![CDATA[Stories by Jill T on Medium]]></description>
        <link>https://medium.com/@jill.tipton?source=rss-5c45561bddd0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*8-PmbiWPTriVkClk</url>
            <title>Stories by Jill T on Medium</title>
            <link>https://medium.com/@jill.tipton?source=rss-5c45561bddd0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:29:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jill.tipton/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[How to build 0–1 exploratory products]]></title>
            <link>https://medium.com/alan/how-to-build-0-1-exploratory-products-225ee4015673?source=rss-5c45561bddd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/225ee4015673</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Jill T]]></dc:creator>
            <pubDate>Thu, 08 Aug 2024 09:43:43 GMT</pubDate>
            <atom:updated>2024-08-08T09:56:02.536Z</atom:updated>
            <content:encoded><![CDATA[<p>A year and half ago, Alan decided to build a back pain solution. At the time, our overall objective was hazy: all we knew was that <strong>back pain came up incessantly when we spoke to customers</strong> and public health data showed the same — ⅔ of the French population had back pain just last year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ho0KU_Y0LnFIp-D5Q0CVfQ.png" /></figure><p>12 months later, Alan now provides a back pain offer that includes 60 exercises, teleconsultation, chat with a physical therapist, and light gamification. In the past month alone:</p><ul><li>1800 members started the back pain program</li><li>And have shared some outstanding feedback like, “<em>The exercises are better than what I had at the physical therapist’s office” </em>and “<em>I no longer feel pain in my lower back when I lift my 18-month-old daughter from her crib.</em>”</li></ul><p>But the road to get there wasn’t easy. We worked within <a href="https://www.linkedin.com/posts/thmsrolf_%3F%3F%3F%3F%3F%3F%3F-%3F%3F-%3F%3F%3F%3F%3F%3F-%3F%3F%3F-activity-7168913661850279936-PYg5/?utm_source=share&amp;utm_medium=member_desktop">Alan’s Explore/Expand framework</a>, spending several months in the exploratory phase to find product market fit and then a big scaling phase to ship and launch to 500,000 members.</p><h3>Success on an exploratory product</h3><p>The challenge was daunting: how to encourage members to make progress on a physical health problem over several weeks entirely inside a digital app? Below are our team’s tips for tackling an exploratory topic with verve.</p><h4>💖 MVPs (minimum viable product) are overrated; be bold on vision!</h4><p>MVPs can be too tame. Without an ambitious vision driving you, you lose steam fast. We asked ourselves, “What’s the coolest thing we could build — something we’d be excited to share with the world and personally love to use?” If you’re not excited about it, users won’t be either.</p><h4>👷 But while you’re bold on vision, be scrappy with execution</h4><p>We incessantly asked, “What’s the fastest way to get this in the app so we can learn?” For example, we wanted to test a big idea: teleconsultation. Instead of overthinking it, we shipped it in only one sprint by using shortcuts like Calendly and Google Meet.</p><h4>👊 Focus more than you think you need to</h4><p>Drastically limit:</p><ul><li><em>Your scope.</em> Originally, the crew was also building a mental health program. We stopped to go all-in on back pain</li><li><em>Your team size.</em> 4–5 people max can go very far, very fast. It means less time finding alignment</li><li><em>Your objectives.</em> The crew had an adoption goal and a satisfaction goal. We dropped one to avoid tackling two tough goals simultaneously</li><li><em>Your features.</em> As soon as it’s clear something isn’t working, kill it and be proud of your feature graveyard. Don’t get stuck in an endless iteration loop; look for the next big thing.</li></ul><h4>🐶 Use your product constantly</h4><p>In the past 4 months, our PM took the back pain program entry survey 96 times. Doing so helps you call problems out asap and fix them just as fast.</p><h4>💀 If you’re doing it right, you should be having fun!</h4><p>Despite many depressing usage graphs that initially looked like this 📉, we laughed a lot! Our mindset was to be pessimistic/realistic about individual iterations but optimistic about long-term success because we knew we had the right vision and the right team. The team must <em>love</em> working together; you can’t ride the rollercoaster without it!</p><h3>Enter the scaling phase</h3><p>Once we were assured we had a product worth launching widely, we completely adjusted our way of working. Whereas before speedy and creative iterations were the key to success, now we needed a longer-term plan to ship to more than half a million members. A few things we learned:</p><h4>☘️ Define super sharp ownership</h4><p>While the 0–1 phase is more of a zigzag that requires a lean team to wear many hats to make progress on a problem, the 1–10 phase is like a train moving full steam ahead that must arrive at the next station no matter what.</p><p>At the beginning of the Expand Phase, the PM created a Google Sheet defining for each topic:</p><ul><li>what questions needed to be answered</li><li>the LOCI (Lead, Owner, Contributors, Informed)</li><li>the deadline</li></ul><p>We checked on this sheet every week to call out risks in our delivery.</p><h4>☁️ Test with soft launches</h4><p>That said, just because we were scaling didn’t mean we could no longer test iteratively! One important thing was reflecting deeply on the question: what is the ideal journey of a user discovering our product?</p><p>We adapted button copy, email messaging, and even broader in-app flows to ensure that members were learning about our back pain solution in a way that made them most likely to use it as intended.</p><h4>🍏 Come up for air with moments for member delight</h4><p>Our exploratory team loved the 0–1 phase and found ourselves a bit discouraged in the scaling tunnel. To remedy this, we allowed for mini-moments of delight where we’d take a couple of days to add a killer animation or rework a flow.</p><p>Balancing in this way can help team members bring more energy to the scaling phase.</p><h3>And now what? Do we move to Run Mode?</h3><p>Normally Alan’s framework has product initiatives moving from Explore to Expand and then to Run — aka we let the feature sit and only invest to fix bugs.</p><p>But <strong>our ambition for back pain has grown as we’ve worked on it</strong>. To fully embody our role as a health partner for our members, we want to verticalize healthcare.</p><p>So the next big challenge is to return to Explore Mode and determine how we can build on top of our existing back pain offer to <strong>prevent visits to osteopaths and physical therapists that could be addressed with our own solutions</strong>.</p><p>It’s another big challenge that requires changing members’ mental models and habits, but one that we’re excited to tackle!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=225ee4015673" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alan/how-to-build-0-1-exploratory-products-225ee4015673">How to build 0–1 exploratory products</a> was originally published in <a href="https://medium.com/alan">Alan Product and Technical Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>