What are friction points?<\/strong><\/h2>\nA friction point is any variable that slows down customers as they use your product. Attrition<\/a> is quite common in SaaS, and can result from a plethora of friction points, from bugs in your product, unclear in-app messaging, to a terrible payment process.<\/p>\nWhat are the common friction types in the customer journey?<\/strong><\/h2>\nAll forms of friction have one thing in common: they hinder users from accomplishing goals in your product.<\/p>\n
These goals can range from setting up an account to using a feature successfully. In fact, according to our benchmarks<\/a> with SaaS companies:<\/p>\n\n- The average core feature adoption<\/a> rate is just about 24.5%<\/li>\n
- Average activation rates are 37.5%<\/li>\n
- Onboarding checklist completion rate is 19.2%<\/li>\n<\/ul>\n
This means that, out of all the users who sign up, only a fraction of them will stick with your product. That’s why understanding friction is key to improving product growth.<\/a><\/p>\nNow, broadly speaking, friction can be categorized into three types: emotional, cognitive, and interaction friction.<\/p>\n
\n- Emotional friction: <\/strong>Results from the emotions users feel when using your platform. It’s often the hardest to spot and deal with, but highly essential to keeping users engaged. Customers often experience emotional friction when completing a task on a site or app that is difficult due to bad UI\/UX. To eliminate this friction, always prioritize positive emotions (can be as simple as a warm greeting when a user logs in) and reduce stress to zero.<\/li>\n
- Cognitive friction: <\/strong>Cognitive friction occurs when users exert much mental effort to complete tasks. Situations like that make the customer’s mind freeze\/block due to too much cognitive load. A common example is empty screens where users have no idea where to start, or having too many UI elements on the same page, and so on.<\/li>\n
- Interaction friction: <\/strong>Interaction friction is every engagement with UI elements that results in something unexpected for website visitors or app users. The solution to interaction friction is to provide contextual guidance<\/a> and strive to make the UI intuitive.<\/li>\n<\/ul>\n
![\"the](\"https:\/\/blog-static.userpilot.com\/blog\/wp-content\/uploads\/2022\/12\/The-Hierarchy-of-Friction-Medium.png\")
<\/a>The hierarchy of friction.<\/figcaption><\/figure>\nHow to identify customer friction points?<\/strong><\/h2>\nYou can’t fight an enemy you don’t know. Hence, the next step is knowing how to identify friction in your product.<\/p>\n
Talk to your customer service team<\/strong><\/h3>\nCustomer service teams are constantly interacting with customers. When they’re not actively chatting with a user, they’re busy solving customer problems in some way. This makes your support <\/a>team the first point of call in uncovering user friction. They can give you customer insights that you couldn’t find anywhere else.<\/p>\nRun path or funnel reports<\/strong><\/h3>\nPath and funnel reports<\/a> let you visualize how users interact with your product step by step. It shows drop-off rates<\/a> between steps, overly branching paths where users wander, and stages where the average time to convert is unusually long.<\/p>\nFor example, if your onboarding funnel shows 60% of users completing the first step but only 15% reaching step three, that gap could mean there’s a UX problem. You can also analyze the average time between each stage (so you can catch friction even when users don’t fully drop off).<\/p>\n![\"Funnel](\"https:\/\/blog-static.userpilot.com\/blog\/wp-content\/uploads\/2026\/04\/0476928c-3142-4759-86f4-04f463572864-scaled.png\")
Funnel analysis lets you track drop-offs between key steps.<\/figcaption><\/figure>\nWatch session replays<\/strong><\/h3>\nSession replays<\/a> give you the qualitative “why” behind what the numbers show. Instead of guessing why users drop off at a particular step, you can watch their hesitation, the rage clicks, and moments of confusion. Think of repeated back-and-forth navigation, cursor hovering over non-clickable elements, and sessions ending right after encountering a specific screen or modal.<\/p>\nFor instance, if you notice users are consistently closing a modal and then immediately leaving, that modal is causing friction.<\/p>\n![\"Session](\"https:\/\/blog-static.userpilot.com\/blog\/wp-content\/uploads\/2026\/04\/43af9179-3d01-4ef8-8d09-bf451250a1f3-scaled.png\")
Watching session replays helps you address friction points.<\/figcaption><\/figure>\nConduct in-app surveys<\/strong><\/h3>\nTriggering in-app surveys<\/a> at key moments (e.g., right after onboarding or during user testing) can spot friction that analytics alone might miss. They’ll let you analyze low satisfaction scores<\/a> at specific touchpoints, repeated mentions of the same pain point, and gaps between what users say they want vs. what they’re doing.<\/p>\nFor instance, a user might rate your product a 6\/10 and mention in the follow-up that they “couldn’t figure out how to set up integrations.”<\/p>\n![\"In-app](\"https:\/\/blog-static.userpilot.com\/blog\/wp-content\/uploads\/2026\/04\/d252225f-c307-4d4a-8bb4-11bf3bd32914-scaled.png\")
Designing an in-app survey to collect valuable insights on a feature.<\/figcaption><\/figure>\nWhat are the most common friction points in the customer journey?<\/strong><\/h2>\nWhen implementing the strategies above, you’ll find that most friction points are pretty common to all SaaS companies.<\/p>\n
Here, I’ll focus on the top-most common friction points in SaaS and how to deal with them.<\/p>\n
Too many steps in the sign-up process<\/strong><\/h3>\nLong sign-up forms are boring and frustrate customers. The user is just getting started with your platform, and any hint of stress will make them assume that’s how the rest of the product is.<\/p>\n
So to minimize friction, you want to avoid new users thinking that way at all costs.<\/p>\n
How to reduce signup friction<\/strong><\/h4>\nYour signup flow<\/a> should be in the most distilled form possible.<\/p>\nHowever, some products require lengthy onboarding, meaning the sign-up process <\/a>will always be long, no matter how hard you try.<\/p>\nFor situations like that, it’s best practice to add gamification<\/a> elements like a progress bar to maintain customer interest.<\/p>\nYou can also implement AI in specific ways to automate the sign-up and setup process. Airtable, for example, embedded an AI agent directly in their onboarding flow to help users set up their first project without starting from scratch. Instead of asking users to manually configure fields, views, and templates, the AI walks them through the process conversationally, leading to a short time to value.<\/p>\n![\"Airtable](\"https:\/\/userpilot.com\/blog\/wp-content\/uploads\/2026\/04\/airtable-onboarding_b6bf50e1375865ef3a40526f09ee4b84.gif\")
<\/a>Airtable onboarding.<\/figcaption><\/figure>\nToo complex or too simple user onboarding process<\/strong><\/h3>\nThere’s a sweet spot between onboarding that overwhelms and onboarding that leaves users stranded.<\/p>\n
On the “too complex” end, you’ll find product tours<\/a> with 10+ stale steps (just click “Next” over and over) and welcome surveys<\/a> that ask 7+ questions without any of them actually influencing what happens next.<\/p>\nFor “too simple” onboarding, you’ll see empty states with no guidance, a bare dashboard with no clear first action, and barely a single welcome message<\/a> that says “Get started!” without explaining how.<\/p>\nBoth extremes create friction, and you should avoid them, too.<\/p>\n
How to improve your onboarding process<\/h4>\n
Start with an audit. Go through your own onboarding as if you’re a new user, and ask yourself these questions:<\/p>\n
\n- How many steps does it take before the user reaches their first “Aha!” moment<\/a>?<\/li>\n
- Are there any steps that don’t directly move the user toward value?<\/li>\n
- Would a user understand what to do if the product tour didn’t exist?<\/li>\n
- Are you showing features the user hasn’t asked for yet?<\/li>\n
- Does each survey question directly influence what happens next in the onboarding?<\/li>\n
- What do you do with the survey answers? Does it actually change the experience?<\/li>\n
- At what step do most users drop off?<\/li>\n
- Does the onboarding feel like it’s for the user, or for the product?<\/li>\n<\/ul>\n
Tip: <\/strong>If you have issues with doing an audit or investing time in it, feel free to hop on a free UX audit call with our team<\/a>.<\/p>\nOnce you’ve identified the gaps, here are a few practical solutions:<\/p>\n
\n- Use an onboarding checklist:<\/strong>\u00a0Checklists give users a clear path without flooding them with information. They show help only when users need it and let them progress at their own pace (enhancing customer satisfaction).<\/li>\n
- Build interactive walkthroughs instead of passive tours:<\/strong>\u00a0The difference between a product tour and an\u00a0interactive walkthrough<\/a> is that the latter forces users to take action (i.e., clicking a button, filling in a field, completing a task, etc.).\u00a0That “learning by doing” approach improves customer retention far better than reading tooltip after tooltip.<\/li>\n
- A\/B test to see what actually works:<\/strong> Test with valid data instead of guessing. For instance, one of our clients (Smoobu) used Userpilot’s A\/B testing<\/a> to test if triggering a walkthrough after sign-up would improve activation. The result was, indeed, a 17% increase in conversion rates in the French market.<\/li>\n<\/ol>\n
“I\u2019d definitely recommend Userpilot<\/a>. It allows us the flexibility to move fast, experiment, and really understand what users need. It\u2019s helped us speed up processes and create a smoother user experience.” <\/em>\u2013 Dasha Frantz, Product Designer at Smoobu<\/em><\/p><\/blockquote>\n
\n![\"Smoobu](\"https:\/\/blog-static.userpilot.com\/blog\/wp-content\/uploads\/2026\/04\/smoobu-ab-test-userpilot_222a073b0667cff67e0c47d9df8e2568_800.png\")
A\/B testing the conversion rates of different flows.<\/figcaption><\/figure>\nUsers are unable to complete their goals<\/strong><\/h3>\nCustomers sign up to use your tool with predefined goals and jobs-to-be-done <\/a>(JTBDs). Thus, one major source of friction is not being able to grasp how your product can help them.<\/p>\nThis can happen due to unclear UIs, lack of guidance, and even technical issues like bugs or server errors.<\/p>\n
How to improve goal completion<\/strong><\/h4>\nProvided the customer is a good fit, the only thing that can stop them from accomplishing their goals is the lack of in-app guidance<\/a> and knowledge in using your product.<\/p>\nHere’s how to bridge this information gap:<\/p>\n
\n- Guide users with interactive walkthroughs:<\/strong> Instead of passively reading what a feature does, walkthroughs help users learn about your product by taking action and completing real tasks.<\/li>\n
- Support users with <\/strong>mobile messaging<\/strong><\/a>:<\/strong> Use mobile in-app messaging to<\/a> offer guidance on features users might not be familiar with.<\/li>\n
- Use <\/strong>tooltips<\/strong><\/a>\/nudges: <\/strong>This UI element is excellent for providing contextual and helpful content about features that your customers need to complete their JTBD.<\/li>\n<\/ul>\n
For instance, Jiminny (a market intelligence platform) used Userpilot’s in-app flows<\/a> to guide users through new features and drive feature adoption. They found that tooltips produced a spike in engagement because they encouraged users to explore features without interrupting their workflow.<\/p>\n“Userpilot has become an important part of how we launch new features. With in-app flows, we can make sure users actually discover and try them. Tooltips in particular create an immediate spike in engagement because they encourage users to explore what’s new.” <\/em>\u2013 <\/em>Galya Dimitrova, Head of Product at Jiminny<\/em><\/p><\/blockquote>\n![\"Jiminny](\"https:\/\/blog-static.userpilot.com\/blog\/wp-content\/uploads\/2026\/04\/Jiminny-tooltip.jpg\")
Using tooltips to prevent users from feeling overwhelmed.<\/figcaption><\/figure>\nBad UX<\/strong><\/h3>\nBeyond lacking guidance or having too many obstacles inside the product, simply having a bad customer experience can cause enough friction to motivate churn.<\/p>\n
Common bad UX<\/a> examples include a cluttered UI with numerous popups, forms with text that users must delete before typing, modals<\/a> that don’t let users exit without clicking the CTA, and navigation that requires too many clicks to reach core features.<\/p>\nHow to reduce friction with UX<\/h4>\n
“Fixing” UX problems might turn more complicated without enough experience.<\/p>\n
However, if I had to simplify it, there are two powerful tips that are likely to improve any product:<\/p>\n
\n- Trigger your popups contextually:<\/strong>\u00a0Nobody likes a modal that hijacks their screen without warning. If your pop-up<\/a> appears at the wrong moment (or worse, can’t be dismissed without completing an action), you’re creating friction. Contextual triggers based on user behavior (e.g., showing a tooltip<\/a> after a user has visited a page three times without taking action) are far more effective than blanket popups.<\/li>\n<\/ul>\n
![\"Userpilot](\"https:\/\/blog-static.userpilot.com\/blog\/wp-content\/uploads\/2026\/04\/ca2afa9a-95e3-4996-97aa-ed24c3596f79-scaled.png\")
Example of a contextual pop-up that doesn’t take up the whole page and is easy to cancel.<\/figcaption><\/figure>\n\n- Always have usability top of mind:<\/strong>\u00a0Before adding any new element (whether it’s a banner, a slideout, or a notification badge), ask yourself: Does this increase users’ overall success? Or does it serve our internal priorities? If it’s the latter, reconsider.<\/li>\n<\/ul>\n
Bad customer service<\/strong><\/h3>\nAccording to Zendesk’s benchmark data<\/a>, about 73% of customers switch to a competitor when they experience poor customer service repeatedly.<\/p>\nBad customer service<\/a> manifests itself in different forms, ranging from too much wait time to customers not having their queries replied to.<\/p>\nHow to reduce customer service friction<\/h4>\n
You can try to solve this by hiring more people for the team. But that can be pretty expensive, and frankly, customers prefer to solve basic issues on their own.<\/p>\n
Self-service<\/a> support is proactive, convenient, and leaves everyone happy. So ideally, you should at least have an extensive knowledge base<\/a> with written or video tutorials, user guides, infographics, etc.<\/p>\nNow, there are many ways to deliver this kind of support, but I personally always advise our customers to implement an in-app resource center. At this point, it’s a standard practice for reducing the volume of support tickets in SaaS.<\/p>\n
Here’s how Userpilot enables self-service support:<\/p>\n
\n- Supports different types of learning materials:<\/strong>\u00a0You can add video tutorials, text articles, external links, in-app flows, and even custom JavaScript functions to your resource center.<\/li>\n
- Knowledge base integration<\/strong><\/a>:<\/strong> Connect your existing knowledge base from HubSpot, Zendesk, Salesforce, Freshdesk, Intercom, Document360, or Zoho Desk so users can search for help articles without leaving the product interface.<\/li>\n
- Search analytics:<\/strong>\u00a0Track what your users most frequently search for in the resource center. This tells you where your documentation has gaps and what topics generate the most confusion.<\/li>\n
- Advanced segmentation:<\/strong>\u00a0Show or hide specific resources depending on which segment a user belongs to. This way, they’ll only see what’s relevant to their role or use case.<\/li>\n<\/ul>\n
![\"Resource](\"https:\/\/blog-static.userpilot.com\/blog\/wp-content\/uploads\/2026\/04\/952495dd-6ff0-4ddf-9174-7c02f42a01e5-scaled.png\")
Creating a self-serve resource center to provide a seamless experience.<\/figcaption><\/figure>\nEliminating friction with Userpilot!<\/strong><\/h2>\nFriction is inevitable, but letting it go undetected is a choice.<\/p>\n
With Userpilot, you can both identify where friction lives and address it in one platform to drive user engagement. The analytics side helps you pinpoint exactly where users get stuck. While the engagement side lets you guide users past those friction points.<\/p>\n
We’re about to make it even faster. Lia (our upcoming AI Product Growth Agent) is designed to continuously analyze your product data, detect anomalies and drop-offs, and automatically create the flows (in-app messages, tours, or surveys) needed to solve the issue.<\/p>\n
![\"Userpilot](\"https:\/\/userpilot.com\/blog\/wp-content\/uploads\/2026\/04\/6c5f0844-b22f-4753-8a21-9ef0fbcfbdbf.png\")
<\/p>\n
What are the common friction types in the customer journey?<\/strong><\/h2>\nAll forms of friction have one thing in common: they hinder users from accomplishing goals in your product.<\/p>\n
These goals can range from setting up an account to using a feature successfully. In fact, according to our benchmarks<\/a> with SaaS companies:<\/p>\n\n- The average core feature adoption<\/a> rate is just about 24.5%<\/li>\n
- Average activation rates are 37.5%<\/li>\n
- Onboarding checklist completion rate is 19.2%<\/li>\n<\/ul>\n
This means that, out of all the users who sign up, only a fraction of them will stick with your product. That’s why understanding friction is key to improving product growth.<\/a><\/p>\nNow, broadly speaking, friction can be categorized into three types: emotional, cognitive, and interaction friction.<\/p>\n
\n- Emotional friction: <\/strong>Results from the emotions users feel when using your platform. It’s often the hardest to spot and deal with, but highly essential to keeping users engaged. Customers often experience emotional friction when completing a task on a site or app that is difficult due to bad UI\/UX. To eliminate this friction, always prioritize positive emotions (can be as simple as a warm greeting when a user logs in) and reduce stress to zero.<\/li>\n
- Cognitive friction: <\/strong>Cognitive friction occurs when users exert much mental effort to complete tasks. Situations like that make the customer’s mind freeze\/block due to too much cognitive load. A common example is empty screens where users have no idea where to start, or having too many UI elements on the same page, and so on.<\/li>\n
- Interaction friction: <\/strong>Interaction friction is every engagement with UI elements that results in something unexpected for website visitors or app users. The solution to interaction friction is to provide contextual guidance<\/a> and strive to make the UI intuitive.<\/li>\n<\/ul>\n
<\/a>The hierarchy of friction.<\/figcaption><\/figure>\nHow to identify customer friction points?<\/strong><\/h2>\nYou can’t fight an enemy you don’t know. Hence, the next step is knowing how to identify friction in your product.<\/p>\n
Talk to your customer service team<\/strong><\/h3>\nCustomer service teams are constantly interacting with customers. When they’re not actively chatting with a user, they’re busy solving customer problems in some way. This makes your support <\/a>team the first point of call in uncovering user friction. They can give you customer insights that you couldn’t find anywhere else.<\/p>\nRun path or funnel reports<\/strong><\/h3>\nPath and funnel reports<\/a> let you visualize how users interact with your product step by step. It shows drop-off rates<\/a> between steps, overly branching paths where users wander, and stages where the average time to convert is unusually long.<\/p>\nFor example, if your onboarding funnel shows 60% of users completing the first step but only 15% reaching step three, that gap could mean there’s a UX problem. You can also analyze the average time between each stage (so you can catch friction even when users don’t fully drop off).<\/p>\nFunnel analysis lets you track drop-offs between key steps.<\/figcaption><\/figure>\nWatch session replays<\/strong><\/h3>\nSession replays<\/a> give you the qualitative “why” behind what the numbers show. Instead of guessing why users drop off at a particular step, you can watch their hesitation, the rage clicks, and moments of confusion. Think of repeated back-and-forth navigation, cursor hovering over non-clickable elements, and sessions ending right after encountering a specific screen or modal.<\/p>\nFor instance, if you notice users are consistently closing a modal and then immediately leaving, that modal is causing friction.<\/p>\nWatching session replays helps you address friction points.<\/figcaption><\/figure>\nConduct in-app surveys<\/strong><\/h3>\nTriggering in-app surveys<\/a> at key moments (e.g., right after onboarding or during user testing) can spot friction that analytics alone might miss. They’ll let you analyze low satisfaction scores<\/a> at specific touchpoints, repeated mentions of the same pain point, and gaps between what users say they want vs. what they’re doing.<\/p>\nFor instance, a user might rate your product a 6\/10 and mention in the follow-up that they “couldn’t figure out how to set up integrations.”<\/p>\nDesigning an in-app survey to collect valuable insights on a feature.<\/figcaption><\/figure>\nWhat are the most common friction points in the customer journey?<\/strong><\/h2>\nWhen implementing the strategies above, you’ll find that most friction points are pretty common to all SaaS companies.<\/p>\n
Here, I’ll focus on the top-most common friction points in SaaS and how to deal with them.<\/p>\n
Too many steps in the sign-up process<\/strong><\/h3>\nLong sign-up forms are boring and frustrate customers. The user is just getting started with your platform, and any hint of stress will make them assume that’s how the rest of the product is.<\/p>\n
So to minimize friction, you want to avoid new users thinking that way at all costs.<\/p>\n
How to reduce signup friction<\/strong><\/h4>\nYour signup flow<\/a> should be in the most distilled form possible.<\/p>\nHowever, some products require lengthy onboarding, meaning the sign-up process <\/a>will always be long, no matter how hard you try.<\/p>\nFor situations like that, it’s best practice to add gamification<\/a> elements like a progress bar to maintain customer interest.<\/p>\nYou can also implement AI in specific ways to automate the sign-up and setup process. Airtable, for example, embedded an AI agent directly in their onboarding flow to help users set up their first project without starting from scratch. Instead of asking users to manually configure fields, views, and templates, the AI walks them through the process conversationally, leading to a short time to value.<\/p>\n<\/a>Airtable onboarding.<\/figcaption><\/figure>\nToo complex or too simple user onboarding process<\/strong><\/h3>\nThere’s a sweet spot between onboarding that overwhelms and onboarding that leaves users stranded.<\/p>\n
On the “too complex” end, you’ll find product tours<\/a> with 10+ stale steps (just click “Next” over and over) and welcome surveys<\/a> that ask 7+ questions without any of them actually influencing what happens next.<\/p>\nFor “too simple” onboarding, you’ll see empty states with no guidance, a bare dashboard with no clear first action, and barely a single welcome message<\/a> that says “Get started!” without explaining how.<\/p>\nBoth extremes create friction, and you should avoid them, too.<\/p>\n
How to improve your onboarding process<\/h4>\n
Start with an audit. Go through your own onboarding as if you’re a new user, and ask yourself these questions:<\/p>\n
\n- How many steps does it take before the user reaches their first “Aha!” moment<\/a>?<\/li>\n
- Are there any steps that don’t directly move the user toward value?<\/li>\n
- Would a user understand what to do if the product tour didn’t exist?<\/li>\n
- Are you showing features the user hasn’t asked for yet?<\/li>\n
- Does each survey question directly influence what happens next in the onboarding?<\/li>\n
- What do you do with the survey answers? Does it actually change the experience?<\/li>\n
- At what step do most users drop off?<\/li>\n
- Does the onboarding feel like it’s for the user, or for the product?<\/li>\n<\/ul>\n
Tip: <\/strong>If you have issues with doing an audit or investing time in it, feel free to hop on a free UX audit call with our team<\/a>.<\/p>\nOnce you’ve identified the gaps, here are a few practical solutions:<\/p>\n
\n- Use an onboarding checklist:<\/strong>\u00a0Checklists give users a clear path without flooding them with information. They show help only when users need it and let them progress at their own pace (enhancing customer satisfaction).<\/li>\n
- Build interactive walkthroughs instead of passive tours:<\/strong>\u00a0The difference between a product tour and an\u00a0interactive walkthrough<\/a> is that the latter forces users to take action (i.e., clicking a button, filling in a field, completing a task, etc.).\u00a0That “learning by doing” approach improves customer retention far better than reading tooltip after tooltip.<\/li>\n
- A\/B test to see what actually works:<\/strong> Test with valid data instead of guessing. For instance, one of our clients (Smoobu) used Userpilot’s A\/B testing<\/a> to test if triggering a walkthrough after sign-up would improve activation. The result was, indeed, a 17% increase in conversion rates in the French market.<\/li>\n<\/ol>\n
“I\u2019d definitely recommend Userpilot<\/a>. It allows us the flexibility to move fast, experiment, and really understand what users need. It\u2019s helped us speed up processes and create a smoother user experience.” <\/em>\u2013 Dasha Frantz, Product Designer at Smoobu<\/em><\/p><\/blockquote>\n
\nA\/B testing the conversion rates of different flows.<\/figcaption><\/figure>\nUsers are unable to complete their goals<\/strong><\/h3>\nCustomers sign up to use your tool with predefined goals and jobs-to-be-done <\/a>(JTBDs). Thus, one major source of friction is not being able to grasp how your product can help them.<\/p>\nThis can happen due to unclear UIs, lack of guidance, and even technical issues like bugs or server errors.<\/p>\n
How to improve goal completion<\/strong><\/h4>\nProvided the customer is a good fit, the only thing that can stop them from accomplishing their goals is the lack of in-app guidance<\/a> and knowledge in using your product.<\/p>\nHere’s how to bridge this information gap:<\/p>\n
\n- Guide users with interactive walkthroughs:<\/strong> Instead of passively reading what a feature does, walkthroughs help users learn about your product by taking action and completing real tasks.<\/li>\n
- Support users with <\/strong>mobile messaging<\/strong><\/a>:<\/strong> Use mobile in-app messaging to<\/a> offer guidance on features users might not be familiar with.<\/li>\n
- Use <\/strong>tooltips<\/strong><\/a>\/nudges: <\/strong>This UI element is excellent for providing contextual and helpful content about features that your customers need to complete their JTBD.<\/li>\n<\/ul>\n
For instance, Jiminny (a market intelligence platform) used Userpilot’s in-app flows<\/a> to guide users through new features and drive feature adoption. They found that tooltips produced a spike in engagement because they encouraged users to explore features without interrupting their workflow.<\/p>\n“Userpilot has become an important part of how we launch new features. With in-app flows, we can make sure users actually discover and try them. Tooltips in particular create an immediate spike in engagement because they encourage users to explore what’s new.” <\/em>\u2013 <\/em>Galya Dimitrova, Head of Product at Jiminny<\/em><\/p><\/blockquote>\nUsing tooltips to prevent users from feeling overwhelmed.<\/figcaption><\/figure>\nBad UX<\/strong><\/h3>\nBeyond lacking guidance or having too many obstacles inside the product, simply having a bad customer experience can cause enough friction to motivate churn.<\/p>\n
Common bad UX<\/a> examples include a cluttered UI with numerous popups, forms with text that users must delete before typing, modals<\/a> that don’t let users exit without clicking the CTA, and navigation that requires too many clicks to reach core features.<\/p>\nHow to reduce friction with UX<\/h4>\n
“Fixing” UX problems might turn more complicated without enough experience.<\/p>\n
However, if I had to simplify it, there are two powerful tips that are likely to improve any product:<\/p>\n
\n- Trigger your popups contextually:<\/strong>\u00a0Nobody likes a modal that hijacks their screen without warning. If your pop-up<\/a> appears at the wrong moment (or worse, can’t be dismissed without completing an action), you’re creating friction. Contextual triggers based on user behavior (e.g., showing a tooltip<\/a> after a user has visited a page three times without taking action) are far more effective than blanket popups.<\/li>\n<\/ul>\n
Example of a contextual pop-up that doesn’t take up the whole page and is easy to cancel.<\/figcaption><\/figure>\n\n- Always have usability top of mind:<\/strong>\u00a0Before adding any new element (whether it’s a banner, a slideout, or a notification badge), ask yourself: Does this increase users’ overall success? Or does it serve our internal priorities? If it’s the latter, reconsider.<\/li>\n<\/ul>\n
Bad customer service<\/strong><\/h3>\nAccording to Zendesk’s benchmark data<\/a>, about 73% of customers switch to a competitor when they experience poor customer service repeatedly.<\/p>\nBad customer service<\/a> manifests itself in different forms, ranging from too much wait time to customers not having their queries replied to.<\/p>\nHow to reduce customer service friction<\/h4>\n
You can try to solve this by hiring more people for the team. But that can be pretty expensive, and frankly, customers prefer to solve basic issues on their own.<\/p>\n
Self-service<\/a> support is proactive, convenient, and leaves everyone happy. So ideally, you should at least have an extensive knowledge base<\/a> with written or video tutorials, user guides, infographics, etc.<\/p>\nNow, there are many ways to deliver this kind of support, but I personally always advise our customers to implement an in-app resource center. At this point, it’s a standard practice for reducing the volume of support tickets in SaaS.<\/p>\n
Here’s how Userpilot enables self-service support:<\/p>\n
\n- Supports different types of learning materials:<\/strong>\u00a0You can add video tutorials, text articles, external links, in-app flows, and even custom JavaScript functions to your resource center.<\/li>\n
- Knowledge base integration<\/strong><\/a>:<\/strong> Connect your existing knowledge base from HubSpot, Zendesk, Salesforce, Freshdesk, Intercom, Document360, or Zoho Desk so users can search for help articles without leaving the product interface.<\/li>\n
- Search analytics:<\/strong>\u00a0Track what your users most frequently search for in the resource center. This tells you where your documentation has gaps and what topics generate the most confusion.<\/li>\n
- Advanced segmentation:<\/strong>\u00a0Show or hide specific resources depending on which segment a user belongs to. This way, they’ll only see what’s relevant to their role or use case.<\/li>\n<\/ul>\n
Creating a self-serve resource center to provide a seamless experience.<\/figcaption><\/figure>\nEliminating friction with Userpilot!<\/strong><\/h2>\nFriction is inevitable, but letting it go undetected is a choice.<\/p>\n
With Userpilot, you can both identify where friction lives and address it in one platform to drive user engagement. The analytics side helps you pinpoint exactly where users get stuck. While the engagement side lets you guide users past those friction points.<\/p>\n
We’re about to make it even faster. Lia (our upcoming AI Product Growth Agent) is designed to continuously analyze your product data, detect anomalies and drop-offs, and automatically create the flows (in-app messages, tours, or surveys) needed to solve the issue.<\/p>\n
<\/p>\n
- \n
- The average core feature adoption<\/a> rate is just about 24.5%<\/li>\n
- Average activation rates are 37.5%<\/li>\n
- Onboarding checklist completion rate is 19.2%<\/li>\n<\/ul>\n
This means that, out of all the users who sign up, only a fraction of them will stick with your product. That’s why understanding friction is key to improving product growth.<\/a><\/p>\n
Now, broadly speaking, friction can be categorized into three types: emotional, cognitive, and interaction friction.<\/p>\n
- \n
- Emotional friction: <\/strong>Results from the emotions users feel when using your platform. It’s often the hardest to spot and deal with, but highly essential to keeping users engaged. Customers often experience emotional friction when completing a task on a site or app that is difficult due to bad UI\/UX. To eliminate this friction, always prioritize positive emotions (can be as simple as a warm greeting when a user logs in) and reduce stress to zero.<\/li>\n
- Cognitive friction: <\/strong>Cognitive friction occurs when users exert much mental effort to complete tasks. Situations like that make the customer’s mind freeze\/block due to too much cognitive load. A common example is empty screens where users have no idea where to start, or having too many UI elements on the same page, and so on.<\/li>\n
- Interaction friction: <\/strong>Interaction friction is every engagement with UI elements that results in something unexpected for website visitors or app users. The solution to interaction friction is to provide contextual guidance<\/a> and strive to make the UI intuitive.<\/li>\n<\/ul>\n
<\/a>The hierarchy of friction.<\/figcaption><\/figure>\n How to identify customer friction points?<\/strong><\/h2>\n
You can’t fight an enemy you don’t know. Hence, the next step is knowing how to identify friction in your product.<\/p>\n
Talk to your customer service team<\/strong><\/h3>\n
Customer service teams are constantly interacting with customers. When they’re not actively chatting with a user, they’re busy solving customer problems in some way. This makes your support <\/a>team the first point of call in uncovering user friction. They can give you customer insights that you couldn’t find anywhere else.<\/p>\n
Run path or funnel reports<\/strong><\/h3>\n
Path and funnel reports<\/a> let you visualize how users interact with your product step by step. It shows drop-off rates<\/a> between steps, overly branching paths where users wander, and stages where the average time to convert is unusually long.<\/p>\n
For example, if your onboarding funnel shows 60% of users completing the first step but only 15% reaching step three, that gap could mean there’s a UX problem. You can also analyze the average time between each stage (so you can catch friction even when users don’t fully drop off).<\/p>\n
Funnel analysis lets you track drop-offs between key steps.<\/figcaption><\/figure>\n Watch session replays<\/strong><\/h3>\n
Session replays<\/a> give you the qualitative “why” behind what the numbers show. Instead of guessing why users drop off at a particular step, you can watch their hesitation, the rage clicks, and moments of confusion. Think of repeated back-and-forth navigation, cursor hovering over non-clickable elements, and sessions ending right after encountering a specific screen or modal.<\/p>\n
For instance, if you notice users are consistently closing a modal and then immediately leaving, that modal is causing friction.<\/p>\n
Watching session replays helps you address friction points.<\/figcaption><\/figure>\n Conduct in-app surveys<\/strong><\/h3>\n
Triggering in-app surveys<\/a> at key moments (e.g., right after onboarding or during user testing) can spot friction that analytics alone might miss. They’ll let you analyze low satisfaction scores<\/a> at specific touchpoints, repeated mentions of the same pain point, and gaps between what users say they want vs. what they’re doing.<\/p>\n
For instance, a user might rate your product a 6\/10 and mention in the follow-up that they “couldn’t figure out how to set up integrations.”<\/p>\n
Designing an in-app survey to collect valuable insights on a feature.<\/figcaption><\/figure>\n What are the most common friction points in the customer journey?<\/strong><\/h2>\n
When implementing the strategies above, you’ll find that most friction points are pretty common to all SaaS companies.<\/p>\n
Here, I’ll focus on the top-most common friction points in SaaS and how to deal with them.<\/p>\n
Too many steps in the sign-up process<\/strong><\/h3>\n
Long sign-up forms are boring and frustrate customers. The user is just getting started with your platform, and any hint of stress will make them assume that’s how the rest of the product is.<\/p>\n
So to minimize friction, you want to avoid new users thinking that way at all costs.<\/p>\n
How to reduce signup friction<\/strong><\/h4>\n
Your signup flow<\/a> should be in the most distilled form possible.<\/p>\n
However, some products require lengthy onboarding, meaning the sign-up process <\/a>will always be long, no matter how hard you try.<\/p>\n
For situations like that, it’s best practice to add gamification<\/a> elements like a progress bar to maintain customer interest.<\/p>\n
You can also implement AI in specific ways to automate the sign-up and setup process. Airtable, for example, embedded an AI agent directly in their onboarding flow to help users set up their first project without starting from scratch. Instead of asking users to manually configure fields, views, and templates, the AI walks them through the process conversationally, leading to a short time to value.<\/p>\n
<\/a>Airtable onboarding.<\/figcaption><\/figure>\n Too complex or too simple user onboarding process<\/strong><\/h3>\n
There’s a sweet spot between onboarding that overwhelms and onboarding that leaves users stranded.<\/p>\n
On the “too complex” end, you’ll find product tours<\/a> with 10+ stale steps (just click “Next” over and over) and welcome surveys<\/a> that ask 7+ questions without any of them actually influencing what happens next.<\/p>\n
For “too simple” onboarding, you’ll see empty states with no guidance, a bare dashboard with no clear first action, and barely a single welcome message<\/a> that says “Get started!” without explaining how.<\/p>\n
Both extremes create friction, and you should avoid them, too.<\/p>\n
How to improve your onboarding process<\/h4>\n
Start with an audit. Go through your own onboarding as if you’re a new user, and ask yourself these questions:<\/p>\n
- \n
- How many steps does it take before the user reaches their first “Aha!” moment<\/a>?<\/li>\n
- Are there any steps that don’t directly move the user toward value?<\/li>\n
- Would a user understand what to do if the product tour didn’t exist?<\/li>\n
- Are you showing features the user hasn’t asked for yet?<\/li>\n
- Does each survey question directly influence what happens next in the onboarding?<\/li>\n
- What do you do with the survey answers? Does it actually change the experience?<\/li>\n
- At what step do most users drop off?<\/li>\n
- Does the onboarding feel like it’s for the user, or for the product?<\/li>\n<\/ul>\n
Tip: <\/strong>If you have issues with doing an audit or investing time in it, feel free to hop on a free UX audit call with our team<\/a>.<\/p>\n
Once you’ve identified the gaps, here are a few practical solutions:<\/p>\n
- \n
- Use an onboarding checklist:<\/strong>\u00a0Checklists give users a clear path without flooding them with information. They show help only when users need it and let them progress at their own pace (enhancing customer satisfaction).<\/li>\n
- Build interactive walkthroughs instead of passive tours:<\/strong>\u00a0The difference between a product tour and an\u00a0interactive walkthrough<\/a> is that the latter forces users to take action (i.e., clicking a button, filling in a field, completing a task, etc.).\u00a0That “learning by doing” approach improves customer retention far better than reading tooltip after tooltip.<\/li>\n
- A\/B test to see what actually works:<\/strong> Test with valid data instead of guessing. For instance, one of our clients (Smoobu) used Userpilot’s A\/B testing<\/a> to test if triggering a walkthrough after sign-up would improve activation. The result was, indeed, a 17% increase in conversion rates in the French market.<\/li>\n<\/ol>\n
“I\u2019d definitely recommend Userpilot<\/a>. It allows us the flexibility to move fast, experiment, and really understand what users need. It\u2019s helped us speed up processes and create a smoother user experience.” <\/em>\u2013 Dasha Frantz, Product Designer at Smoobu<\/em><\/p><\/blockquote>\n
\nA\/B testing the conversion rates of different flows.<\/figcaption><\/figure>\n Users are unable to complete their goals<\/strong><\/h3>\n
Customers sign up to use your tool with predefined goals and jobs-to-be-done <\/a>(JTBDs). Thus, one major source of friction is not being able to grasp how your product can help them.<\/p>\n
This can happen due to unclear UIs, lack of guidance, and even technical issues like bugs or server errors.<\/p>\n
How to improve goal completion<\/strong><\/h4>\n
Provided the customer is a good fit, the only thing that can stop them from accomplishing their goals is the lack of in-app guidance<\/a> and knowledge in using your product.<\/p>\n
Here’s how to bridge this information gap:<\/p>\n
- \n
- Guide users with interactive walkthroughs:<\/strong> Instead of passively reading what a feature does, walkthroughs help users learn about your product by taking action and completing real tasks.<\/li>\n
- Support users with <\/strong>mobile messaging<\/strong><\/a>:<\/strong> Use mobile in-app messaging to<\/a> offer guidance on features users might not be familiar with.<\/li>\n
- Use <\/strong>tooltips<\/strong><\/a>\/nudges: <\/strong>This UI element is excellent for providing contextual and helpful content about features that your customers need to complete their JTBD.<\/li>\n<\/ul>\n
For instance, Jiminny (a market intelligence platform) used Userpilot’s in-app flows<\/a> to guide users through new features and drive feature adoption. They found that tooltips produced a spike in engagement because they encouraged users to explore features without interrupting their workflow.<\/p>\n
“Userpilot has become an important part of how we launch new features. With in-app flows, we can make sure users actually discover and try them. Tooltips in particular create an immediate spike in engagement because they encourage users to explore what’s new.” <\/em>\u2013 <\/em>Galya Dimitrova, Head of Product at Jiminny<\/em><\/p><\/blockquote>\n
Using tooltips to prevent users from feeling overwhelmed.<\/figcaption><\/figure>\n Bad UX<\/strong><\/h3>\n
Beyond lacking guidance or having too many obstacles inside the product, simply having a bad customer experience can cause enough friction to motivate churn.<\/p>\n
Common bad UX<\/a> examples include a cluttered UI with numerous popups, forms with text that users must delete before typing, modals<\/a> that don’t let users exit without clicking the CTA, and navigation that requires too many clicks to reach core features.<\/p>\n
How to reduce friction with UX<\/h4>\n
“Fixing” UX problems might turn more complicated without enough experience.<\/p>\n
However, if I had to simplify it, there are two powerful tips that are likely to improve any product:<\/p>\n
- \n
- Trigger your popups contextually:<\/strong>\u00a0Nobody likes a modal that hijacks their screen without warning. If your pop-up<\/a> appears at the wrong moment (or worse, can’t be dismissed without completing an action), you’re creating friction. Contextual triggers based on user behavior (e.g., showing a tooltip<\/a> after a user has visited a page three times without taking action) are far more effective than blanket popups.<\/li>\n<\/ul>\n
Example of a contextual pop-up that doesn’t take up the whole page and is easy to cancel.<\/figcaption><\/figure>\n - \n
- Always have usability top of mind:<\/strong>\u00a0Before adding any new element (whether it’s a banner, a slideout, or a notification badge), ask yourself: Does this increase users’ overall success? Or does it serve our internal priorities? If it’s the latter, reconsider.<\/li>\n<\/ul>\n
Bad customer service<\/strong><\/h3>\n
According to Zendesk’s benchmark data<\/a>, about 73% of customers switch to a competitor when they experience poor customer service repeatedly.<\/p>\n
Bad customer service<\/a> manifests itself in different forms, ranging from too much wait time to customers not having their queries replied to.<\/p>\n
How to reduce customer service friction<\/h4>\n
You can try to solve this by hiring more people for the team. But that can be pretty expensive, and frankly, customers prefer to solve basic issues on their own.<\/p>\n
Self-service<\/a> support is proactive, convenient, and leaves everyone happy. So ideally, you should at least have an extensive knowledge base<\/a> with written or video tutorials, user guides, infographics, etc.<\/p>\n
Now, there are many ways to deliver this kind of support, but I personally always advise our customers to implement an in-app resource center. At this point, it’s a standard practice for reducing the volume of support tickets in SaaS.<\/p>\n
Here’s how Userpilot enables self-service support:<\/p>\n
- \n
- Supports different types of learning materials:<\/strong>\u00a0You can add video tutorials, text articles, external links, in-app flows, and even custom JavaScript functions to your resource center.<\/li>\n
- Knowledge base integration<\/strong><\/a>:<\/strong> Connect your existing knowledge base from HubSpot, Zendesk, Salesforce, Freshdesk, Intercom, Document360, or Zoho Desk so users can search for help articles without leaving the product interface.<\/li>\n
- Search analytics:<\/strong>\u00a0Track what your users most frequently search for in the resource center. This tells you where your documentation has gaps and what topics generate the most confusion.<\/li>\n
- Advanced segmentation:<\/strong>\u00a0Show or hide specific resources depending on which segment a user belongs to. This way, they’ll only see what’s relevant to their role or use case.<\/li>\n<\/ul>\n
Creating a self-serve resource center to provide a seamless experience.<\/figcaption><\/figure>\n Eliminating friction with Userpilot!<\/strong><\/h2>\n
Friction is inevitable, but letting it go undetected is a choice.<\/p>\n
With Userpilot, you can both identify where friction lives and address it in one platform to drive user engagement. The analytics side helps you pinpoint exactly where users get stuck. While the engagement side lets you guide users past those friction points.<\/p>\n
We’re about to make it even faster. Lia (our upcoming AI Product Growth Agent) is designed to continuously analyze your product data, detect anomalies and drop-offs, and automatically create the flows (in-app messages, tours, or surveys) needed to solve the issue.<\/p>\n
<\/p>\n - Knowledge base integration<\/strong><\/a>:<\/strong> Connect your existing knowledge base from HubSpot, Zendesk, Salesforce, Freshdesk, Intercom, Document360, or Zoho Desk so users can search for help articles without leaving the product interface.<\/li>\n
- Supports different types of learning materials:<\/strong>\u00a0You can add video tutorials, text articles, external links, in-app flows, and even custom JavaScript functions to your resource center.<\/li>\n
- Always have usability top of mind:<\/strong>\u00a0Before adding any new element (whether it’s a banner, a slideout, or a notification badge), ask yourself: Does this increase users’ overall success? Or does it serve our internal priorities? If it’s the latter, reconsider.<\/li>\n<\/ul>\n
- Support users with <\/strong>mobile messaging<\/strong><\/a>:<\/strong> Use mobile in-app messaging to<\/a> offer guidance on features users might not be familiar with.<\/li>\n
- Build interactive walkthroughs instead of passive tours:<\/strong>\u00a0The difference between a product tour and an\u00a0interactive walkthrough<\/a> is that the latter forces users to take action (i.e., clicking a button, filling in a field, completing a task, etc.).\u00a0That “learning by doing” approach improves customer retention far better than reading tooltip after tooltip.<\/li>\n
- Cognitive friction: <\/strong>Cognitive friction occurs when users exert much mental effort to complete tasks. Situations like that make the customer’s mind freeze\/block due to too much cognitive load. A common example is empty screens where users have no idea where to start, or having too many UI elements on the same page, and so on.<\/li>\n