Hey and welcome back.
We're going to jump right into the dos and don'ts of user flows so user flows shows the purpose of what
you're trying to create and really we shouldn't be vague at all.
So this title tells me absolutely nothing vague.
User flows and names really had the potential complexity and doesn't communicate enough information
back to the viewer.
Remember, we have to be a little more detailed when we think about these.
I do not know what is happening here.
All I know is that there is some sort of vague flow and it's going in different directions.
Maybe this could be broken.
No, I don't know what profile means.
Maybe the user is trying to get to their profile.
Maybe the user is on their profile or maybe the user is signing up.
I'm not sure.
What you should do is use descriptive names.
Maybe it's add user payment details, organize them maybe into separate flows, is the user trying to
get to the profile to edit their profile picture?
That's a separate flow.
And by naming your flows, you're really able to design from the user's perspective and you can split
goals based off of what they're trying to do.
Remember, you can create separate flows.
Don't be afraid to make as many as you want.
It really helps us break down all the different requirements we need in all the different scenarios
that may pop up.
Your flow should always go in one direction.
I mean, there's really no excuse to do something like this.
I mentioned it before about sprawling like flowcharts or site maps, but these are confusing and they
don't really do a good job of actually indicating some sort of user flow.
They may tell me all the different possibilities that the user may encounter while they're in our product
or website or whatever we're building.
But to take a look at that, that's incredibly overwhelming.
So these work as a good site map or to show the way the navigation works in your product, but don't
do it for a user.
So what we should do is the following.
Split them up into distinct flows and categorize them.
So if we zoom out just a bit, we had like three different flows broken into er broken into one or put
together as one, and over here, what we've done is even though there's like a decision tree, one
of our flows, we've actually just broken them out separately, will name them both descriptions for
each task and they'll have an end goal.
So remember, keep it simple.
Break it out.
It's OK to be a little redundant, but it's going to help you in the end.
And the last don't.
Your photos should represent a complete task.
Don't do this, you're missing a bunch of details here.
There's a bunch of useless information like click button at bottom.
I'm not sure what button means, fill out fields like what fields.
And I mean, there is just nothing left at the end.
We should have some sort of description of what that end goal is.
We need to know the details the user needs to take to complete a task and the actions.
This is what you should probably be doing at the right amount of detail, letting each step and goal
this way, anyone can read and understand your flow.
So I know that this flow is purchasing a product instantly and that can mean a lot of things.
But we can break that up into several flows so I can review a product details, I can review a product
details and use the buy now button.
And that pushes me into the next step.
I am reviewing shipping and payment information and we can even add to this review shipping and payment
information.
Confirm.
Details and make a purchase.
Let's just open this frame up just a little bit more.
And the last step is that purchase has been confirmed.
You get an order confirmation and you receive some sort of success message.
So remember at the right amount of detail and outline each step and goal.
That way, anyone can read it and understand it.
We don't want people looking at those confusing site maps with not enough information outlining each
step or each scenario.
And we don't want people to be confused.
So follow these do's and don'ts and you'll be ready to create your very own user flows.