<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Elizabeth Laraki</title>
        <link>https://paragraph.com/@lillib</link>
        <description>Design Partner, Electric Capital</description>
        <lastBuildDate>Wed, 17 Jun 2026 01:55:19 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>Elizabeth Laraki</title>
            <url>https://storage.googleapis.com/papyrus_images/1622438b1a4213b5a14c915d63390b20e5a577e17fee97c58c51e83e55392bb9.png</url>
            <link>https://paragraph.com/@lillib</link>
        </image>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[Onboarding Flows]]></title>
            <link>https://paragraph.com/@lillib/onboarding-flows</link>
            <guid>53Amy6SIiTEFicCHHMZK</guid>
            <pubDate>Thu, 21 Sep 2023 23:06:51 GMT</pubDate>
            <description><![CDATA[Onboarding onto new services should be super easy. But most product teams build long, complicated flows that drop new users. I regularly coach founders on how to do this better. Here are 5 tips to create onboarding flows that actually work: — 1/ Keep it short + set expectations Clearly communicate how many steps are in your onboarding flow. Target no more than 5 steps. Common ways to show the number of steps in a flow include:Progress barsNumbered stepsStep 1 of N— 2/ Show progress Show peopl...]]></description>
            <content:encoded><![CDATA[<p>Onboarding onto new services should be super easy.</p><p>But most product teams build long, complicated flows that drop new users.</p><p>I regularly coach founders on how to do this better.</p><p>Here are 5 tips to create onboarding flows that actually work:</p><p>—</p><p><strong>1/ Keep it short + set expectations</strong></p><p>Clearly communicate how many steps are in your onboarding flow.</p><p>Target no more than 5 steps.</p><p>Common ways to show the number of steps in a flow include:</p><ul><li><p>Progress bars</p></li><li><p>Numbered steps</p></li><li><p>Step 1 of N</p></li></ul><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/735111fc22c3c11c4788a906dd71c7af5a70a99d20182ac9901a26c92e489269.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>—</p><p><strong>2/ Show progress</strong></p><p>Show people where they are in the flow.</p><p>How far have they come/How far do they have to go?</p><p>Keep it simple.</p><p>These should just orient people and keep them motivated to complete the onboarding.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/23430b7b5010eeb67e7bf9df1ec72693caf217b681fdd2a3998810bcf8bd7726.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>—</p><p><strong>3/ Provide one clear way to proceed</strong></p><p>Ask for only one action at a time.</p><p>Do not bury steps inside of steps.</p><p>Keep the ‘next’ button disabled until the action is complete.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/ebcfa6d4d54197b10ed04fef3cc6425a6c217944f1980dad9bbdee02564a5fc6.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>—</p><p><strong>4/ Provide a consistent way to exit</strong></p><p>Nobody wants to feel locked into an onboarding flow.</p><p>Front load the most important information.</p><p>Build a consistent ‘ejection seat’ for every step of the flow.</p><p>Common patterns are an X in the upper right corner or a “Skip” link.</p><p>Clearly communicate if onboarding is mandatory to interact with your product.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/29a8e2e05c1ef64686823f6596c5627554760c477f425dcee039184ca72768d4.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>—</p><p><strong>5/ Be concise</strong></p><p>Generally it’s easy to cut ~50% of text from the first versions of onboarding flows.</p><p>User attention and space are limited. Do not over-explain things like:</p><ul><li><p>Usage terms for each setting</p></li><li><p>Caveats to selections</p></li><li><p>Implications of options</p></li></ul><p>You can use things like hover states or “i” icons to help users understand trickier options.</p><p>—</p><p><em>Caveat: If you aren’t sure if you need an onboarding flow, skip it.</em></p><p>You only need an onboarding flow if your product:</p><ul><li><p>Is complex</p></li><li><p>Is a completely new paradigm</p></li><li><p>Requires specific selections before a user can meaningfully interact with your product e.g., Setting access controls for your health data, Choosing what language to learn in Duolingo.</p></li></ul><p>—</p><p>Your goal is to quickly set people up to use your app.</p><p>These 5 tips will help you design clear, concise onboarding flows that work:</p><ol><li><p>Keep it short + set expectations</p></li><li><p>Show progress</p></li><li><p>Provide one clear way to proceed</p></li><li><p>Provide a consistent way to exit</p></li><li><p>Be concise</p></li></ol><p>For more content on design for founders, follow @elizlaraki</p>]]></content:encoded>
            <author>lillib@newsletter.paragraph.com (Elizabeth Laraki)</author>
        </item>
    </channel>
</rss>