With Userflow, you can create nearly any type of Flow to assist users. However, not every Flow is equally engaging. Below, we present essential best practices for crafting effective Flows. Be sure to check out our extensive video series on onboarding best practices.
Don’t tell, Drive action
Don’t: Build Next-Next-Next tours
A common use of product tours is to build introductory Flows that explain menu items in your UI. These kinds of tours, however, are not very engaging for your end users, as they do not prompt them to take action. Many will therefore quickly click through these Flows or dismiss them.
Do: Build action-based Flows that drive towards the “Aha!” moment
A better way to build onboarding Flows is to build action-based Flows that drive towards key Aha moments. For example, we at Userflow use our first intro Flow to guide new users through building a Flow and show how easy it is.
Be clear and concise in your text
Don’t: Assume that users know what to do
Just because you point a beacon or Tooltip to an element in your app, it is not always clear to the user that they need to click the item. So don’t assume that they know.
Do: Be clear and concise about the actions you want users to take
To ensure the user takes the action, keep the Flow step clear and concise. For example, by making a single action line with the action to take.
How to drive user action
Trigger steps based on in-app interaction to improve user engagement. When that isn’t an option, add a button or other trigger to advance the user through the Flow.
Step triggers (if this, then that)
Use Triggers to create "if this, then that" navigation rules. A trigger can perform an action based on conditions such as:
An element is present, clicked, or disabled.
A user completing an input field.
The user reaches a specific page (URL).
Action buttons
Add action buttons to your steps that drive clear next steps. When activated, an action can be specified, such as Go to step (to navigate to another step) or Start new Flow/Checklist.
By combining these elements, you ensure the user is actively participating, rather than just clicking "Next-Next-Next.”
Best practices for Flow success
Once you have defined your steps, added content, and configured transitions, you should have a basic working Flow. Building a great Flow is like guiding someone through a maze. You don't want to tell them every detail about the walls (Next-Next-Next tours); instead, you want to focus on the key turns they must take (action-based steps) to reach the prize (the "Aha moment") quickly and efficiently.
Here are five useful tips and best practices to make your Flow even better:
Customize Appearance with Themes: Change the look and feel of your modals, Flows, and checklists to make them feel native to your application. (Refer to Customizing Themes to learn more.)
Keep Flows Short and Focused: Keep your flows brief; users tend to drop off after step four, and completion rates can drop sharply if a Flow exceeds six steps.
Drive Action, Don't Just Tell: Build action-based Flows that guide users toward key "Aha moments," such as guiding them to build a key component of their application. Avoid building simple "Next-Next-Next" tours that only explain menu items.
Be Clear and Concise: Always specify the actions you want users to take at a Flow step. Do not assume users will know they need to click an item just because you point a tooltip or beacon to it.
Always Ensure Flows End Properly: Make sure Flows eventually dismiss or hide to prevent them from blocking other content (such as other Flows or checklists) from appearing. It is best practice to add a dismiss action on the final step to provide a clear call to action for completion.