<aside> 👋
This, and all of the blogs, give an overview of the process and steps taken for each part. I’ve included images taken from the FigJam boards where the majority of the work lives to illustrate the process.
If you would still like to see further details on each part, please view the FigJam board in full.
It can be found at the end of this page, or on this master page.
</aside>
Having identified best practice flows already, I started to draft my first set of user flows. I always find users flows to be a strange process for myself, as my finished flows once I’ve wireframed them are often very different to the diagrammatic versions. I think I I work better more visually, but even still I find benefits to doing this style of user flow. Particularly, it helps me establish what sort of flows each will be.
For example, the below flow is very functional, with a lot of logic surrounding it, to me this indicates this area of the product will have multiple screens, with lots of user interactivity.
In contrast, this area is more like an information architecture diagram, more focussed on one screen and the information a user will be able to see on it. Whereas the previous area was functional, this is more information, and that helps me when I start to wireframe as I know roughly what to expect.
Similarly, I find this process useful at uncovering hidden logic the user won’t see. For example, the questions in the onboarding about the users transport habits will set certain parameters for what features are recommended to them. I find it more useful to weed this out at this stage as it leads to less complex wireframing.
Overall this process was very useful and has set me up well for wireframing. This is an ongoing process, and I imagine I will revisit these user flows later to update or tweak them.
Full working and documentation of desk research can be found in this FigJam file.
https://www.figma.com/board/vtJFUq63t5iHbknFIcpBEB/User-Flows?node-id=0-1&t=Pc5y32dyYr6nZYd8-1