Designing SaaS products: 6 reasons why you need a user flow | Strafe Creative

Designing SaaS products: 6 reasons why you need a user flow

Author
Published
DesignUser ExperienceWeb Design

We cannot imagine life today without SaaS, digital products, websites and applications, and with that comes high expectations from users about how they perform. To perform as the user expects, digital applications require a huge amount of upfront work during the design process. That’s where a user flow comes in – a practical and efficient way to ensure your technology always provides a great user experience.  

In this blog, we’ll be covering the benefits and reasons why we here at Strafe, believe that creating a user flow during the SaaS design process is essential. But let’s get back to basics, what even is a user flow?

We’ve talked about wireframes and design systems in our previous posts, but a user flow comes before all of that…

What is a user flow?

A user flow is a diagram to explain how a user would click and flow around a website or application. This includes from page to page and interactions that trigger emails or processes, such as user sign-in. The user flow maps out every single journey a user could take, depending on any possible action.

Userflows that Strafe use are built showing a clear user journey between pages

Why do we create a user flow?

We create user flows to map out all the ways a user could potentially interact with a SaaS product. This helps us find out if the journey through the software, at any given moment, makes sense to the user and they end up where they want to be. 

Where does a user flow fit into SaaS the design process? 

Before we start to work on any wireframes or designs, we start with the user flow. Typically we’ll design a master user flow first and then create individual components off the back of that. 

There are three key things to consider when starting work on your user flow:

  1. Do you know your product? What is the SaaS product for? What benefits does the user get from the software? 
  2. Who is your audience? Some SaaS products offer different functionalities depending on who is using it.
  3. What is the objective of the flow? This can vary depending on who the user is and where they are in their experience with the software. For example, the onboarding process vs. the process to add new team members to an account.  

Here are six reasons why a user flow really is essential: 

1. A communication tool 

A user flow is a much easier, visual way to present the initial product design to a client. We show our user flows to clients on calls and talk them through the journey their customers will take. By using a digital user flow like this, we can make live amends and edits during meetings and finalise solutions that make sense. 

 

2. Easier to figure out what’s working or not 

By walking step by step through the user journey it’s much easier to identify what is working and what is not. If a user forgets their password, is the next step to ask them to reset it? Nuances like this can be much more difficult to find and address if the processes aren’t clear in the initial design stages 

 

3. A great starting point for future development

By producing a detailed user flow at the start of a SaaS project, you make your life easier further down the line. When new developments or features are required, the master user flow can be reviewed and new user journeys can be added in where they make logical sense, rather than squeezing in updates wherever you can.

 

 

4. Easy to check usability and pick it apart

Is the user following a journey that makes sense to them? A live user flow that can be reviewed and analysed is such a useful starting point. Test with clients, target personas and 3rd party testing teams and find out where you can make improvements. Pick it apart and then easily put it back together in an order that immediately adds value to the user. 

5. Improves efficiency of the project 

Given the user flow is the starting point of the design process, getting this part right is key – especially in a large, detailed and complex SaaS project. In our user flows we identify which sections are required in every part of the journey so we can ensure that all interactions align and flow smoothly. For example on the welcome screen of an app, which buttons and menus will be available? Noting down, the main menu, log in and sign up helps you then ensure the journey a user could take from each is clear.

With our experience on larger technology projects, at Strafe we always ensure the user can DO what they logged on to the software, to do. From inviting new team members to a SaaS plan, resetting their password or going through the onboarding process, every step of these processes needs to be planned out in detail. 

When you have such detail written down, in an easy to understand format, the rest of the design process is much easier. Going back to add in a full ‘forgotten password’ flow, once the software has already been designed and built is a lot harder! 

6. You can personalise it 

Depending on the audience that will use that particular part of the product, you can personalise the user journey they take – in particular when it comes to onboarding the user onto the product.

As designers, we think of onboarding in two ways, frictionless and friction-based.

Frictionless onboarding makes it really easy for a user to sign up, log in and get started with the product straight away – removing barriers to entry. For example, creating an account with just an email and password. Unfortunately, this means a user might not understand the full value of the product and may lose interest more quickly. 

Friction-based onboarding takes the user on a more detailed flow, asking questions about what they want to get out of the product, their role at work (if relevant) and then showing the user how to get started. Whilst some users may find this too long of a process and drop off, many will enjoy learning how to get the most of the software and understand its value early on.

For instance, take ‘Notion’, a project management software that enables users to create useful boards, notes and plans within their teams. During onboarding, Notion asks users what they will use the software for and their role, which allows them to take users through a specific flow. A marketer for example might then be shown how to create content calendars, moon boards, asset lists and how they can integrate team members for collaborative working. 

To follow up, Notion sends a series of onboarding emails showing the new user how to use the product for maximum efficiency and value. Each of these parts of the user journey will have been mapped out to ensure each possible persona understands the value of the software from the moment they start using it and therefore are more likely to stay as a long-term customer. 

Conclusion

The bottom line is, user flows are an essential part of the design process. They bring clarity, certainty and efficiency to the user experience. From simple log in pages to complex SaaS tools, a user flow will ensure your customers get the most value from your software from the moment they open it. Without a detailed user flow, you’re likely to end up with a clunky experience that users may eventually give up on later down the line.

 

We'd love to hear about your project!

Get in touch with us and see how we can help you.

Please select applicable project types:
Web ProjectUX / UI DesignBrandingSaaS Design & BuildE-commerce