I'm trying to show different user paths in a deliverable. I want to create a user flow but I'm finding this difficult as the user can click on many different buttons on each page to get to the final destination.
For example: from the landing page, a user can click on support button, login button, or dashboard button (which are all on the same page) to get to the end of the flow.
Does anyone know a way around this? Maybe by specifying which button they're clicking within the page?
Use labels on or near your connector lines to show which action the user is choosing. This example from How to Improve App Settings shows diverging paths based on system responses, and those labels could also be used to show user responses through clicks without making thumbnails that are too detailed.
If you imagine how this information would be documented or implemented in a prototyping tool like Adobe XD or MarvelApp, what you would be doing is associating a hotspot or an action with a page by drawing an arrow between the two. That's just one way of doing this but obviously it depends on how many buttons you have and how many pages it is going to.
With visualisation there is always a trade-off between the completeness of information at one glance (i.e. how much you need to drill in to get all the details) versus how easy it is to understand the information. If you can provide an example of how complex or how much information you have to capture, it will be easier to work out the best way to show it within the space you have to work with.