<?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 Lived In Content on Medium]]></title>
        <description><![CDATA[Stories by Lived In Content on Medium]]></description>
        <link>https://medium.com/@livedincontent?source=rss-13911fd90eb0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*b4csuq44Z2rIj_vyDaR_qQ.png</url>
            <title>Stories by Lived In Content on Medium</title>
            <link>https://medium.com/@livedincontent?source=rss-13911fd90eb0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:04:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@livedincontent/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[Streaks and engagement aren’t the whole story]]></title>
            <link>https://livedincontent.medium.com/anti-patterns-for-capacity-aware-exits-94925438a9e1?source=rss-13911fd90eb0------2</link>
            <guid isPermaLink="false">https://medium.com/p/94925438a9e1</guid>
            <dc:creator><![CDATA[Lived In Content]]></dc:creator>
            <pubDate>Tue, 06 Jan 2026 11:58:38 GMT</pubDate>
            <atom:updated>2026-02-21T19:09:15.666Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Adapting in real life often involves small, unremarkable decisions about capacity — leaving to-dos uncrossed, appearing to flake on a commitment, intentionally “giving up”.</blockquote><figure><img alt="A checklist with one item checked off" src="https://cdn-images-1.medium.com/max/1024/1*w3SckLqXG4dEmQJPuyTeYw.png" /></figure><p>How often are we rewarding perseverance in how we talk to one another and in how “friendly” apps are designed. Is that motivating? Is it helpful? Did it up engagement metrics?</p><figure><img alt="“Two side-by-side hand-drawn black-and-white sketches comparing design patterns. Left panel, titled ‘Ideal Pattern,’ shows a calm interface with the text ‘Taking a break?’ and two neutral buttons, ‘Save &amp; Exit’ and ‘Resume Later.’ A note says ‘You can pick up where you left off anytime.’ Below, a relaxed person sits outdoors under a sun, with handwritten annotations reading ‘Options with support,’ ‘No pressure,’ and ‘Friendly reassurance.’ Right panel, titled ‘Anti-Pattern,’ shows a tense interf" src="https://cdn-images-1.medium.com/max/1024/1*6nTkCjj-NZZddAlup7tCrQ.png" /><figcaption>A visual contrast between capacity-aware exits and coercive persistence.</figcaption></figure><p>Here are a few anti-patterns I’ve noticed and try to avoid.</p><h3>Anti-example 1: The motivational override</h3><p>A user taps “end session” halfway through.</p><p>The app responds with: <em>“You’re almost there! Want to finish strong?”</em></p><p>What this does:</p><ul><li>Overrides the user’s assessment of their capacity</li><li>Frames stopping as weakness disguised as encouragement</li><li>Introduces pressure at the exact moment regulation may be fragile</li></ul><p><strong>What’s lost:</strong> trust<br><strong>What’s gained:</strong> maybe 90 more seconds of completion data</p><h3>Anti-example 2: The silent penalty</h3><p>A user exits early. Nothing is said in the moment.</p><p>Later, they see:</p><ul><li>A broken streak</li><li>A progress bar that visibly regressed</li><li>A reminder they’re “behind” on their plan</li></ul><p>What this does:</p><ul><li>Retroactively reframes a self-protective choice as failure</li><li>Teaches the user that listening to their body has consequences</li><li>Encourages future overextension to avoid penalties</li></ul><p><strong>The message learned:</strong> finish, even when you shouldn’t</p><h3>Anti-example 3: The false choice</h3><p>On exit, the user sees:</p><ul><li>“Continue session”</li><li>“Abandon session”</li></ul><p>What this does:</p><ul><li>Collapses nuance into a binary</li><li>Forces the user to label their action as quitting</li><li>Misses the distinction between <em>stopping</em> and <em>giving up</em></li></ul><p>Capacity-aware exits avoid loaded verbs like <em>abandon</em>, <em>quit</em>, or <em>fail</em> — especially in moments of low capacity.</p><h3>Reframing the design question</h3><p>Instead of asking: <em>How do we reduce early exits?</em></p><p>Capacity-aware design asks: <em>How do we acknowledge an exit without destabilizing the user?</em></p><p>When there’s an indication of a change in plan or a loosening of standards, the question often comes up: <em>Is this coddling? Is it enabling? Does it make us soft? </em><strong>No, it’s attentiveness to reality.</strong></p><p>A capacity-aware response does three quiet things:</p><ol><li><strong>It doesn’t argue with the user’s state.</strong><br>The system accepts that capacity can drop mid-interaction without demanding justification.</li><li><strong>It preserves orientation.</strong><br>The user knows where they are, what stopping means, and how to return — without pressure.</li><li><strong>It avoids moral framing.</strong><br>No language that implies failure, falling behind, or “giving up.”</li></ol><p>💬 Leave a comment with an example of an exit flow you’ve questioned, redesigned, or wish you could change.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94925438a9e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What if stopping counted?]]></title>
            <link>https://livedincontent.medium.com/what-if-stopping-counted-0e883948671c?source=rss-13911fd90eb0------2</link>
            <guid isPermaLink="false">https://medium.com/p/0e883948671c</guid>
            <category><![CDATA[ux-writing]]></category>
            <dc:creator><![CDATA[Lived In Content]]></dc:creator>
            <pubDate>Sat, 03 Jan 2026 20:53:03 GMT</pubDate>
            <atom:updated>2026-01-03T21:18:21.377Z</atom:updated>
            <content:encoded><![CDATA[<p>Most apps are designed around continuation.</p><p>Keep going. <br>Finish the session.<br>Protect the streak.</p><p><strong>The logic of “keep going”</strong></p><p>Those mechanics work — and for good reason. They reduce decision fatigue, build momentum, and help people return.</p><p>But in health contexts, especially chronic ones, stopping isn’t always failure. Sometimes it’s regulation.</p><figure><img alt="AI-generated image of someone taking a rest. A few text-embedded notes to reiterate the goal: allowing space for self-agency and using CTAs as prompts and not directives." src="https://cdn-images-1.medium.com/max/1024/1*fuiYYshEH9ZAk5-9HxeLqw.png" /></figure><p><strong>Moments when pausing makes sense</strong></p><p>In health products, interaction is shaped as much by nervous-system state as by motivation or intent. CTAs don’t just move people forward; they signal safety, urgency, or pressure. Timing, wording, and default actions can either support regulation or add load.</p><p><strong>Regulation over completion</strong></p><p>Pausing, skipping, or stopping early often reflects self-protection rather than disengagement. When all non-completion is treated as failure, very different user states get flattened into the same outcome.</p><blockquote>What interests me is whether adaptive CTAs can preserve guidance while allowing capacity to fluctuate — <strong>without framing that variability as a problem to fix.</strong></blockquote><p>This isn’t a new idea. UX advocates and clinicians have talked about self-agency for years. What’s harder is holding onto it when you’re building something that still needs to motivate, guide, and function at scale — while interacting with real nervous systems</p><h3>When Stopping Is the Interaction</h3><p>I spend a lot of time thinking about prompts, CTAs, and the small decisions people make inside products — especially health products.</p><p>Not in the abstract. In the practical, slightly messy way that comes from working on real systems with real constraints: streaks, progress bars, drop-offs, edge cases, and all the quiet signals users send when they pause or stop.</p><blockquote>Imagine a guided breathing session designed to last five minutes.<br>At minute three, the user exits.</blockquote><blockquote>In most products, that moment is logged as a drop-off. The system assumes loss of interest, failed motivation, or friction. The next time the user opens the app, they’re nudged to “finish what you started” or reminded that they’re behind.</blockquote><blockquote>But there’s another plausible reading: three minutes was enough. The user noticed a shift, or hit a limit, or chose to stop before tipping into overwhelm. From a nervous-system perspective, that exit might be the success condition.</blockquote><p>The interaction didn’t fail. It completed — just not on the product’s timeline.</p><p>There isn’t a single pattern that solves this.</p><p>But adaptive CTAs — ones that respond to capacity rather than override it — open up a different question: not how to keep people going, but how to stay supportive when they can’t.</p><p>That’s the space I’m exploring next.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0e883948671c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>