Progressive disclosure examples – quick summary<\/h2>\n\n- Progressive disclosure is a design pattern<\/a> that gradually reveals information depending on the user’s need.<\/li>\n
- The benefits of progressive disclosure are to improve customer experiences<\/a> for new users, simplify the user interface<\/a>, create a better understanding of initial and secondary features, and reduce the learning curve<\/a>.<\/li>\n
- Some examples of progressive disclosure are:<\/li>\n
- Empty states<\/a> help to prompt a user to take action.<\/li>\n
- You can use a sign-up flow<\/a> to guide users through a few core features before giving them full access to the product.<\/li>\n
- Favor multiple screens over one page to reduce the user’s cognitive load. You can use progress bars<\/a> to show different actions.<\/li>\n
- Use multi-layer menus to keep the user interface clean by showing only the essentials. But still giving access to important features of your product.<\/li>\n
- Interactive guides<\/a> and step-by-step guides<\/a> can lead users to learn in little incremental steps to prevent any feelings of overwhelm.<\/li>\n
- Checklists<\/a> help users adopt features making them a great progressive disclosure technique.<\/li>\n
- You can use tooltips<\/a> to display additional information and highlight a feature without overloading the UI.<\/li>\n
- Grouping and categorizing content in resource centers<\/a> help users find the information they need more easily.<\/li>\n
- Segmenting users<\/a> with similar jobs to be done<\/a> helps to use different progressive disclosure strategies based on their needs.<\/li>\n
- For new user onboarding<\/a>, give them only the options<\/a> to learn core and secondary features so you can show only the information that will increase user adoption.<\/li>\n
- Use multiple secondary displays to show step-by-step options for focusing the user’s attention.<\/li>\n
- Want a great way of managing your progressive disclosure techniques? Userpilot can assist with your product. Get a Userpilot demo.<\/a><\/li>\n<\/ul>\n
What is progressive disclosure?<\/h2>\n
Progressive disclosure is a design pattern that gradually exposes users to information over multiple screens. It aims to prevent overwhelm as users progress through your product.<\/p>\n
Benefits of progressive disclosure<\/h2>\n
For many reasons, progressive disclosure is a great design process to implement in your product user interfaces.<\/p>\n
Here are some of them:<\/p>\n
\n- Improve the customer experience for novice users<\/strong> – Learning a new product can be overwhelming, especially if there are a number of core features that users can use. Progressive disclosure can help slow down this learning and ultimately improve the first-time experience<\/a> with new users.<\/li>\n
- Cleaner user interface<\/strong> – Progressive disclosure follows simple principles suggested by interaction designers<\/a> to adopt cleaner interfaces<\/a> that only reveal the information a user needs.<\/li>\n
- A better understanding of core and secondary features<\/strong> – Progressive disclosure can help to isolate your primary or secondary features.<\/li>\n
- Reduce the learning curve<\/strong> – Teaching your user how to use your product through small steps using progressive disclosure can help reduce the learning curve<\/a>.<\/li>\n
- Less error prone<\/strong> – It will also help them be less error prone because of their increased knowledge of your product.<\/li>\n<\/ul>\n
Examples of progressive disclosure used in SaaS<\/h2>\n
Examples are a great way to get inspiration on how to use progressive disclosure in your SaaS. Here are five ways to help create a better experience for your users.<\/p>\n
Empty states that prompt action<\/h3>\n
An empty state is the technical design term<\/a> for a screen inside your product that is almost completely blank. Empty states occur most commonly when users have just signed up<\/a> to a new platform, or when there is some kind of error message.<\/p>\nRather than leaving it blank<\/a>, which could confuse users and potentially lead them away from your SaaS, use empty states to prompt action.<\/p>\nCrowdfire makes good use of its blank state<\/a> by showing the next step a user should take by selecting topics of interest.<\/p>\n![\"A](\"https:\/\/images.storychief.com\/account_6827\/crowdfire-empty-state-progressive-disclosure-examples_192bebe3f8cc3b7a295ba6498c62c571_800.png\")
<\/picture>Crowdfire\u2019s empty state example.<\/figcaption><\/figure>\nA sign-up flow that walks users through getting started<\/h3>\n
A sign-up flow<\/a> can also collect needed data, so when users enter the app, the interface matches their goals.<\/p>\nA sign-up flow helps walk the user through using the app and configure any settings needed, rather than throwing a user head first into your SaaS without a clue how they can do anything.<\/p>\n
Asana is a classic example of a great sign-up flow which makes for a good progressive disclosure.<\/p>\n![\"A](\"https:\/\/images.storychief.com\/account_6827\/asana-signup-progressive-disclosure-examples_c03c9433d5f0eb8f75f5b7b1f09c00c4_800.jpg\")
<\/picture>Asana\u2019s sign-up flow.<\/figcaption><\/figure>\nMultiple screens vs a one-page overload<\/h3>\n
Cramping everything your users need on one screen can overwhelm them. A better approach is to split things up over multiple screens. These reductions of options on one screen helps to reduce the user’s cognitive load.<\/p>\n
You can use multi-screens with progress bars to show different actions. It could be for your sign-up flows or when configuring any advanced settings.<\/p>\n
Userpilot uses a secondary screen when you set up a checklist. Users can reveal different screens by selecting different buttons, making multiple options manageable.<\/p>\n![\"A](\"https:\/\/d37oebn0w9ir6a.cloudfront.net\/account_6827\/userpilot-checklist-progressive-disclosure_6c10920485d379d248e9ed3f849d81a5.gif\")
<\/picture>Userpilot<\/a>\u2019s multi-screen options.<\/figcaption><\/figure>\nMulti-layer menus<\/h3>\n
Multi-layer menus can help you with progressive disclosure. It helps to reduce the number of things on the user interface so users can focus on what they are doing with as few distractions as possible.<\/p>\n
The dropdown menu shows the essentials with simple buttons that, when clicked, reveal the next level of options for a user.<\/p>\n
Loom uses this as part of its progressive disclosure strategy. When you want to edit your video, you interact with a widget.<\/p>\n![\"A](\"https:\/\/images.storychief.com\/account_6827\/loom-video-options_d49262b3ec84b7c019270d49dcb54443_800.jpg\")
<\/picture>A multi-layer menu example from Loom.<\/figcaption><\/figure>\nThe widget then shows the product’s core features, so the more advanced options are progressively disclosed. But are a click away when a user needs them.<\/p>\n![\"A](\"https:\/\/images.storychief.com\/account_6827\/loom-edit-options_a15c8aeec93b1bc7a8ff0e6a4d8ac1e6_800.jpg\")
<\/picture>Loom\u2019s widget shows advanced settings.<\/figcaption><\/figure>\nStep-by-step interactive guides and wizards<\/h3>\n
Another example of progressive disclosure is using step-by-step interactive guides<\/a> and wizards<\/a>.<\/p>\nYou can also hide or blur part of the options you’re showing a user to focus their attention on the most important details.<\/p>\n
Userpilot uses this technique for part of its Hubspot integration configuration. It uses short guiding messages while hiding secondary steps to prevent users from feeling overwhelmed when completing the setup.<\/p>\n![\"A](\"https:\/\/images.storychief.com\/account_6827\/userpilot-integration-hubspot-progressive-disclosure_39950345078b950c8725c2d62c7460c6_800.jpg\")
<\/picture>Userpilot<\/a>\u2019s use of blurring to draw the user’s attention.<\/figcaption><\/figure>\nHow to apply progressive disclosure in your onboarding process to drive product adoption?<\/h2>\n
Progressive disclosure is a great technique to help you drive product adoption in your onboarding process. Here are three ways you can achieve this.<\/p>\n
Use checklists for progressive guidance<\/h3>\n
Checklists are a great way for simplifying complexity progressive disclosure. They can break down features to help them get started without any overwhelm.<\/p>\n
During the onboarding<\/a>, you can use a checklist<\/a> where each point will open a new screen and guide them through your core features. Moreover, showing users one step at a time will help increase user adoption.<\/p>\n![\"A](\"https:\/\/images.storychief.com\/account_6827\/userpilot-checklist-progressive-disclosure_eb81cb740eacb9526ff21d505c5c2740_800.jpg\")
<\/picture>An example of a checklist in Userpilot.<\/figcaption><\/figure>\nUse tooltips as part of interaction design<\/h3>\n
Tooltips<\/a> are an essential tool for progressive disclosure. As part of the onboarding, you can trigger them for new users to show them around your SaaS.<\/p>\nYou can use tooltips to showcase any of your SaaS features and provide additional information without overloading the UI with tons of information.<\/p>\n![\"A](\"https:\/\/images.storychief.com\/account_6827\/userpilot-tooltip-progressive-disclosure_f0d637f6611b8546a12f6612b49f955f_800.jpg\")
<\/picture>An example of how Userpilot uses tooltips.<\/figcaption><\/figure>\nCategorize and group content in resource centers<\/h3>\n
A knowledge base<\/a> is where you store resources for a user and where they can get answers themselves on how to get the most out of the product.<\/p>\nOne of the concerns with a resource center is that if you have a complex SaaS, they could be hundreds of articles for them to get their heads around. As part of progressive disclosure, you want to make accessing this information as easy as possible.<\/p>\n
One of the best practices of resource centers is categorizing and grouping content together. It lets users only be a handful of clicks away from accessing the information they need, making things simple.<\/p>\n![\"An](\"https:\/\/d37oebn0w9ir6a.cloudfront.net\/account_6827\/resource-center-modules-progressive-disclosure_e4bedc3826c64e3967bbc0da580b6933.gif\")
<\/picture>See how Userpilot<\/a> groups and categorizes its resource center.<\/figcaption><\/figure>\nA side benefit of a resource center<\/a> is it can help reduce customer support tickets, as users can self-serve answers.<\/p>\nBest practices when implementing a progressive disclosure strategy<\/h2>\n
It’s clear now that progressive disclosure is a good way of making things simple for users when going through your SaaS. To ensure that you succeed in implementing your progressive disclosure strategy, here are some best practices you should follow.<\/p>\n
Segment users with similar JTBDs<\/h3>\n
Each user has their own goals they want to complete with your product. Knowing what goals they want to complete will help you with your progressive disclosure strategy.<\/p>\n
One way to ensure you are dealing with each user’s needs is by segmenting them<\/a>. Segmenting your users by their jobs to be done<\/a> (which you can learn more about via in-app surveys) lets you use a different progressive disclosure strategy for each segment.<\/p>\nThere is no point showing advanced settings to a new user when they’ve only just joined your SaaS. Each job to be done can have different core features.<\/p>\n
With segmentation<\/a>, you can make sure that you are gradually letting new users discover new features when they are ready for them. And you can even customize the information in a resource center based on their goals to reduce confusion.<\/p>\n![\"A](\"https:\/\/images.storychief.com\/account_6827\/user-segmentation-jtbd-progressive-disclosure_32ab6f616490628d199ff224261e8930_800.jpg\")
<\/picture>Userpilot<\/a>\u2019s user segmentation options.<\/figcaption><\/figure>\nPrioritize core and secondary features<\/h3>\n
Some SaaS products can be complex and have a range of features. Introducing them all at once can really stop new users in their tracks.<\/p>\n
A best practice of progressive disclosure is limiting the options presented to a user during onboarding<\/a>. Progressive disclosure defers advanced or not often-used features, so you can limit to only show users the core and secondary features.<\/p>\nIn the example below, Userpilot shows three choices<\/a> when beginning a flow for an in-app experience, so it’s clearer to a user what they should do next.<\/p>\n![\"A](\"https:\/\/images.storychief.com\/account_6827\/userpilot-create-flow-progressive-disclosure_08d9aec73d9a01871e4eb32b9adaaf4c_800.jpg\")
<\/picture>Userpilot\u2019s<\/a> show uses the core and secondary features as options.<\/figcaption><\/figure>\nOnce the user has chosen one of the options, you can show them the available choices of only that feature. In the Userpilot examples, if the user chooses a flow, they are presented with the option to use modal, slideouts, tooltips, and driven actions.<\/p>\n![\"A](\"https:\/\/images.storychief.com\/account_6827\/userpilot-user-onboarding-ui-patterns-dashboard_3448047f960128905f5c5b9d7745cf39_800.jpg\")
<\/picture>An example of Userpilot<\/a> flows.<\/figcaption><\/figure>\nLimiting what you show users based on what they decided helps users to progress in using your onboarding<\/a> rather than making them think about what they should do next from a long list of options.<\/p>\nCreate effective onboarding flows with branched experiences<\/h3>\n
Rather than showing a generic onboarding flow, which may not be relevant to a user and might be super long, you should offer branched experiences.<\/p>\n
You can do this by showing multiple screens that have step-by-step options. When users select a certain response, it takes them down a path relevant to whatever they choose.<\/p>\n
ConvertKit does this in their sign-up flow.<\/p>\n![\"A](\"https:\/\/images.storychief.com\/account_6827\/convertkit-welcome-page-minimum-viable-onboarding_694630792108e7b756a2618a8e89a260_800.jpg\")
<\/picture>The questions asked by ConvertKit direct users in the right direction.<\/figcaption><\/figure>\nThey ask a user where they are joining from. And depending on what they choose, a different screen is shown to them.<\/p>\n![\"A](\"https:\/\/images.storychief.com\/account_6827\/convertkit-user-adoption-personalized-customer-experience_7a6b70dc3df7bdfd1a9a416cc4d5285b_800.jpg\")
<\/picture>Convertkit sign-up flow.<\/figcaption><\/figure>\nSet goals to see how new users use the product<\/h3>\n
Setting goals<\/a> can help you with your progressive disclosure strategy. You can set micro or macro goals<\/a> that will match your different segment’s goals so you can see how your users engage and adopt features.<\/p>\n![\"A](\"https:\/\/images.storychief.com\/account_6827\/userpilot-goals-progressive-disclosure_5b836623aa0ad39f58cb29640af43514_800.jpg\")
<\/picture>Userpilot\u2019s goal-setting feature.<\/figcaption><\/figure>\nThese goals will help you see if users haven’t discovered or adopted any features. You can identify any friction with granular event tracking by being able to spot patterns in usage.<\/p>\n
With this analytical data<\/a>, you can segment and show them tutorials or highlight unused features with tooltips.<\/p>\n![\"A](\"https:\/\/images.storychief.com\/account_6827\/features-events-userpilot-analytics_a4579055c6dbcc3b7c870627c11e903b_800.png\")
<\/picture>Userpilot<\/a>\u2019s analytics.<\/figcaption><\/figure>\nPrototype and A\/B test for improvements based on feedback<\/h3>\n
Testing your progressive disclosure strategy and getting feedback can show you how well they work.<\/p>\n
You can create simple prototypes<\/a> for your ideas and A\/B test<\/a> them for user usability. You can ask the user to submit a friction log so you can spot any friction points and how you can make improvements.<\/p>\n![\"A](\"https:\/\/images.storychief.com\/account_6827\/friction-log-recruit-users-userpilot_931656b0558c85bd9f010cd588046fe2_800.png\")
<\/picture>A friction log example from Userpilot.<\/figcaption><\/figure>\nYou can also use experience surveys<\/a> to collect feedback on your prototypes to get further information on how to improve.<\/p>\n![\"A](\"https:\/\/images.storychief.com\/account_6827\/in-app-surveys-good-survey_b959d4fc4ee3c90f81a7f51c4d79cc13_800.png\")
<\/picture>Userpilot<\/a>\u2019s in-app survey.<\/figcaption><\/figure>\nConclusion<\/h2>\n
Progressive disclosure will help you make your SaaS more consumable for users by giving them bite-size information to stop them from getting overwhelmed. And these progressive disclosure examples will help to improve your user’s experience.<\/p>\n
Userpilot is a great tool to get you started with a progressive disclosure strategy. It can help you segment your users, organize your resource centers, and create interactive walkthroughs, all key for progressive disclosure.<\/p>\n
Plus, with Userpilot’s native mobile SDK<\/a>, you can also onboard and engage mobile app users by creating personalized messaging, push notifications, and surveys.<\/span><\/p>\n
What is progressive disclosure?<\/h2>\n
Progressive disclosure is a design pattern that gradually exposes users to information over multiple screens. It aims to prevent overwhelm as users progress through your product.<\/p>\n
Benefits of progressive disclosure<\/h2>\n
For many reasons, progressive disclosure is a great design process to implement in your product user interfaces.<\/p>\n
Here are some of them:<\/p>\n
- \n
- Improve the customer experience for novice users<\/strong> – Learning a new product can be overwhelming, especially if there are a number of core features that users can use. Progressive disclosure can help slow down this learning and ultimately improve the first-time experience<\/a> with new users.<\/li>\n
- Cleaner user interface<\/strong> – Progressive disclosure follows simple principles suggested by interaction designers<\/a> to adopt cleaner interfaces<\/a> that only reveal the information a user needs.<\/li>\n
- A better understanding of core and secondary features<\/strong> – Progressive disclosure can help to isolate your primary or secondary features.<\/li>\n
- Reduce the learning curve<\/strong> – Teaching your user how to use your product through small steps using progressive disclosure can help reduce the learning curve<\/a>.<\/li>\n
- Less error prone<\/strong> – It will also help them be less error prone because of their increased knowledge of your product.<\/li>\n<\/ul>\n
Examples of progressive disclosure used in SaaS<\/h2>\n
Examples are a great way to get inspiration on how to use progressive disclosure in your SaaS. Here are five ways to help create a better experience for your users.<\/p>\n
Empty states that prompt action<\/h3>\n
An empty state is the technical design term<\/a> for a screen inside your product that is almost completely blank. Empty states occur most commonly when users have just signed up<\/a> to a new platform, or when there is some kind of error message.<\/p>\n
Rather than leaving it blank<\/a>, which could confuse users and potentially lead them away from your SaaS, use empty states to prompt action.<\/p>\n
Crowdfire makes good use of its blank state<\/a> by showing the next step a user should take by selecting topics of interest.<\/p>\n
<\/picture>Crowdfire\u2019s empty state example.<\/figcaption><\/figure>\n A sign-up flow that walks users through getting started<\/h3>\n
A sign-up flow<\/a> can also collect needed data, so when users enter the app, the interface matches their goals.<\/p>\n
A sign-up flow helps walk the user through using the app and configure any settings needed, rather than throwing a user head first into your SaaS without a clue how they can do anything.<\/p>\n
Asana is a classic example of a great sign-up flow which makes for a good progressive disclosure.<\/p>\n
<\/picture>Asana\u2019s sign-up flow.<\/figcaption><\/figure>\n Multiple screens vs a one-page overload<\/h3>\n
Cramping everything your users need on one screen can overwhelm them. A better approach is to split things up over multiple screens. These reductions of options on one screen helps to reduce the user’s cognitive load.<\/p>\n
You can use multi-screens with progress bars to show different actions. It could be for your sign-up flows or when configuring any advanced settings.<\/p>\n
Userpilot uses a secondary screen when you set up a checklist. Users can reveal different screens by selecting different buttons, making multiple options manageable.<\/p>\n
<\/picture>Userpilot<\/a>\u2019s multi-screen options.<\/figcaption><\/figure>\n Multi-layer menus<\/h3>\n
Multi-layer menus can help you with progressive disclosure. It helps to reduce the number of things on the user interface so users can focus on what they are doing with as few distractions as possible.<\/p>\n
The dropdown menu shows the essentials with simple buttons that, when clicked, reveal the next level of options for a user.<\/p>\n
Loom uses this as part of its progressive disclosure strategy. When you want to edit your video, you interact with a widget.<\/p>\n
<\/picture>A multi-layer menu example from Loom.<\/figcaption><\/figure>\n The widget then shows the product’s core features, so the more advanced options are progressively disclosed. But are a click away when a user needs them.<\/p>\n
<\/picture>Loom\u2019s widget shows advanced settings.<\/figcaption><\/figure>\n Step-by-step interactive guides and wizards<\/h3>\n
Another example of progressive disclosure is using step-by-step interactive guides<\/a> and wizards<\/a>.<\/p>\n
You can also hide or blur part of the options you’re showing a user to focus their attention on the most important details.<\/p>\n
Userpilot uses this technique for part of its Hubspot integration configuration. It uses short guiding messages while hiding secondary steps to prevent users from feeling overwhelmed when completing the setup.<\/p>\n
<\/picture>Userpilot<\/a>\u2019s use of blurring to draw the user’s attention.<\/figcaption><\/figure>\n How to apply progressive disclosure in your onboarding process to drive product adoption?<\/h2>\n
Progressive disclosure is a great technique to help you drive product adoption in your onboarding process. Here are three ways you can achieve this.<\/p>\n
Use checklists for progressive guidance<\/h3>\n
Checklists are a great way for simplifying complexity progressive disclosure. They can break down features to help them get started without any overwhelm.<\/p>\n
During the onboarding<\/a>, you can use a checklist<\/a> where each point will open a new screen and guide them through your core features. Moreover, showing users one step at a time will help increase user adoption.<\/p>\n
<\/picture>An example of a checklist in Userpilot.<\/figcaption><\/figure>\n Use tooltips as part of interaction design<\/h3>\n
Tooltips<\/a> are an essential tool for progressive disclosure. As part of the onboarding, you can trigger them for new users to show them around your SaaS.<\/p>\n
You can use tooltips to showcase any of your SaaS features and provide additional information without overloading the UI with tons of information.<\/p>\n
<\/picture>An example of how Userpilot uses tooltips.<\/figcaption><\/figure>\n Categorize and group content in resource centers<\/h3>\n
A knowledge base<\/a> is where you store resources for a user and where they can get answers themselves on how to get the most out of the product.<\/p>\n
One of the concerns with a resource center is that if you have a complex SaaS, they could be hundreds of articles for them to get their heads around. As part of progressive disclosure, you want to make accessing this information as easy as possible.<\/p>\n
One of the best practices of resource centers is categorizing and grouping content together. It lets users only be a handful of clicks away from accessing the information they need, making things simple.<\/p>\n
<\/picture>See how Userpilot<\/a> groups and categorizes its resource center.<\/figcaption><\/figure>\n A side benefit of a resource center<\/a> is it can help reduce customer support tickets, as users can self-serve answers.<\/p>\n
Best practices when implementing a progressive disclosure strategy<\/h2>\n
It’s clear now that progressive disclosure is a good way of making things simple for users when going through your SaaS. To ensure that you succeed in implementing your progressive disclosure strategy, here are some best practices you should follow.<\/p>\n
Segment users with similar JTBDs<\/h3>\n
Each user has their own goals they want to complete with your product. Knowing what goals they want to complete will help you with your progressive disclosure strategy.<\/p>\n
One way to ensure you are dealing with each user’s needs is by segmenting them<\/a>. Segmenting your users by their jobs to be done<\/a> (which you can learn more about via in-app surveys) lets you use a different progressive disclosure strategy for each segment.<\/p>\n
There is no point showing advanced settings to a new user when they’ve only just joined your SaaS. Each job to be done can have different core features.<\/p>\n
With segmentation<\/a>, you can make sure that you are gradually letting new users discover new features when they are ready for them. And you can even customize the information in a resource center based on their goals to reduce confusion.<\/p>\n
<\/picture>Userpilot<\/a>\u2019s user segmentation options.<\/figcaption><\/figure>\n Prioritize core and secondary features<\/h3>\n
Some SaaS products can be complex and have a range of features. Introducing them all at once can really stop new users in their tracks.<\/p>\n
A best practice of progressive disclosure is limiting the options presented to a user during onboarding<\/a>. Progressive disclosure defers advanced or not often-used features, so you can limit to only show users the core and secondary features.<\/p>\n
In the example below, Userpilot shows three choices<\/a> when beginning a flow for an in-app experience, so it’s clearer to a user what they should do next.<\/p>\n
<\/picture>Userpilot\u2019s<\/a> show uses the core and secondary features as options.<\/figcaption><\/figure>\n Once the user has chosen one of the options, you can show them the available choices of only that feature. In the Userpilot examples, if the user chooses a flow, they are presented with the option to use modal, slideouts, tooltips, and driven actions.<\/p>\n
<\/picture>An example of Userpilot<\/a> flows.<\/figcaption><\/figure>\n Limiting what you show users based on what they decided helps users to progress in using your onboarding<\/a> rather than making them think about what they should do next from a long list of options.<\/p>\n
Create effective onboarding flows with branched experiences<\/h3>\n
Rather than showing a generic onboarding flow, which may not be relevant to a user and might be super long, you should offer branched experiences.<\/p>\n
You can do this by showing multiple screens that have step-by-step options. When users select a certain response, it takes them down a path relevant to whatever they choose.<\/p>\n
ConvertKit does this in their sign-up flow.<\/p>\n
<\/picture>The questions asked by ConvertKit direct users in the right direction.<\/figcaption><\/figure>\n They ask a user where they are joining from. And depending on what they choose, a different screen is shown to them.<\/p>\n
<\/picture>Convertkit sign-up flow.<\/figcaption><\/figure>\n Set goals to see how new users use the product<\/h3>\n
Setting goals<\/a> can help you with your progressive disclosure strategy. You can set micro or macro goals<\/a> that will match your different segment’s goals so you can see how your users engage and adopt features.<\/p>\n
<\/picture>Userpilot\u2019s goal-setting feature.<\/figcaption><\/figure>\n These goals will help you see if users haven’t discovered or adopted any features. You can identify any friction with granular event tracking by being able to spot patterns in usage.<\/p>\n
With this analytical data<\/a>, you can segment and show them tutorials or highlight unused features with tooltips.<\/p>\n
<\/picture>Userpilot<\/a>\u2019s analytics.<\/figcaption><\/figure>\n Prototype and A\/B test for improvements based on feedback<\/h3>\n
Testing your progressive disclosure strategy and getting feedback can show you how well they work.<\/p>\n
You can create simple prototypes<\/a> for your ideas and A\/B test<\/a> them for user usability. You can ask the user to submit a friction log so you can spot any friction points and how you can make improvements.<\/p>\n
<\/picture>A friction log example from Userpilot.<\/figcaption><\/figure>\n You can also use experience surveys<\/a> to collect feedback on your prototypes to get further information on how to improve.<\/p>\n
<\/picture>Userpilot<\/a>\u2019s in-app survey.<\/figcaption><\/figure>\n Conclusion<\/h2>\n
Progressive disclosure will help you make your SaaS more consumable for users by giving them bite-size information to stop them from getting overwhelmed. And these progressive disclosure examples will help to improve your user’s experience.<\/p>\n
Userpilot is a great tool to get you started with a progressive disclosure strategy. It can help you segment your users, organize your resource centers, and create interactive walkthroughs, all key for progressive disclosure.<\/p>\n
Plus, with Userpilot’s native mobile SDK<\/a>, you can also onboard and engage mobile app users by creating personalized messaging, push notifications, and surveys.<\/span><\/p>\n
- Cleaner user interface<\/strong> – Progressive disclosure follows simple principles suggested by interaction designers<\/a> to adopt cleaner interfaces<\/a> that only reveal the information a user needs.<\/li>\n
![\"A](\"https:\/\/images.storychief.com\/account_6827\/crowdfire-empty-state-progressive-disclosure-examples_192bebe3f8cc3b7a295ba6498c62c571_800.png){kind=spacer}
<\/picture>![\"A](\"https:\/\/images.storychief.com\/account_6827\/asana-signup-progressive-disclosure-examples_c03c9433d5f0eb8f75f5b7b1f09c00c4_800.jpg)
<\/picture>![\"A](\"https:\/\/d37oebn0w9ir6a.cloudfront.net\/account_6827\/userpilot-checklist-progressive-disclosure_6c10920485d379d248e9ed3f849d81a5.gif)
<\/picture>![\"A](\"https:\/\/images.storychief.com\/account_6827\/loom-video-options_d49262b3ec84b7c019270d49dcb54443_800.jpg)
<\/picture>![\"A](\"https:\/\/images.storychief.com\/account_6827\/loom-edit-options_a15c8aeec93b1bc7a8ff0e6a4d8ac1e6_800.jpg)
<\/picture>![\"A](\"https:\/\/images.storychief.com\/account_6827\/userpilot-integration-hubspot-progressive-disclosure_39950345078b950c8725c2d62c7460c6_800.jpg)
<\/picture>![\"A](\"https:\/\/images.storychief.com\/account_6827\/userpilot-checklist-progressive-disclosure_eb81cb740eacb9526ff21d505c5c2740_800.jpg)
<\/picture>![\"A](\"https:\/\/images.storychief.com\/account_6827\/userpilot-tooltip-progressive-disclosure_f0d637f6611b8546a12f6612b49f955f_800.jpg)
<\/picture>![\"An](\"https:\/\/d37oebn0w9ir6a.cloudfront.net\/account_6827\/resource-center-modules-progressive-disclosure_e4bedc3826c64e3967bbc0da580b6933.gif)
<\/picture>![\"A](\"https:\/\/images.storychief.com\/account_6827\/user-segmentation-jtbd-progressive-disclosure_32ab6f616490628d199ff224261e8930_800.jpg)
<\/picture>![\"A](\"https:\/\/images.storychief.com\/account_6827\/userpilot-create-flow-progressive-disclosure_08d9aec73d9a01871e4eb32b9adaaf4c_800.jpg)
<\/picture>![\"A](\"https:\/\/images.storychief.com\/account_6827\/userpilot-user-onboarding-ui-patterns-dashboard_3448047f960128905f5c5b9d7745cf39_800.jpg)
<\/picture>![\"A](\"https:\/\/images.storychief.com\/account_6827\/convertkit-welcome-page-minimum-viable-onboarding_694630792108e7b756a2618a8e89a260_800.jpg)
<\/picture>![\"A](\"https:\/\/images.storychief.com\/account_6827\/convertkit-user-adoption-personalized-customer-experience_7a6b70dc3df7bdfd1a9a416cc4d5285b_800.jpg)
<\/picture>![\"A](\"https:\/\/images.storychief.com\/account_6827\/userpilot-goals-progressive-disclosure_5b836623aa0ad39f58cb29640af43514_800.jpg)
<\/picture>![\"A](\"https:\/\/images.storychief.com\/account_6827\/features-events-userpilot-analytics_a4579055c6dbcc3b7c870627c11e903b_800.png)
<\/picture>![\"A](\"https:\/\/images.storychief.com\/account_6827\/friction-log-recruit-users-userpilot_931656b0558c85bd9f010cd588046fe2_800.png)
<\/picture>![\"A](\"https:\/\/images.storychief.com\/account_6827\/in-app-surveys-good-survey_b959d4fc4ee3c90f81a7f51c4d79cc13_800.png)
<\/picture>