1
00:00:00,940 --> 00:00:02,050
Hey and welcome back.

2
00:00:02,680 --> 00:00:09,430
We're going to jump right into the dos and don'ts of user flows so user flows shows the purpose of what

3
00:00:09,430 --> 00:00:14,630
you're trying to create and really we shouldn't be vague at all.

4
00:00:14,650 --> 00:00:18,670
So this title tells me absolutely nothing vague.

5
00:00:18,670 --> 00:00:24,520
User flows and names really had the potential complexity and doesn't communicate enough information

6
00:00:24,520 --> 00:00:25,360
back to the viewer.

7
00:00:25,660 --> 00:00:29,500
Remember, we have to be a little more detailed when we think about these.

8
00:00:29,510 --> 00:00:32,000
I do not know what is happening here.

9
00:00:32,320 --> 00:00:37,680
All I know is that there is some sort of vague flow and it's going in different directions.

10
00:00:37,690 --> 00:00:38,650
Maybe this could be broken.

11
00:00:38,650 --> 00:00:41,200
No, I don't know what profile means.

12
00:00:41,200 --> 00:00:43,510
Maybe the user is trying to get to their profile.

13
00:00:44,110 --> 00:00:49,120
Maybe the user is on their profile or maybe the user is signing up.

14
00:00:49,120 --> 00:00:49,990
I'm not sure.

15
00:00:50,950 --> 00:00:55,150
What you should do is use descriptive names.

16
00:00:56,460 --> 00:01:02,550
Maybe it's add user payment details, organize them maybe into separate flows, is the user trying to

17
00:01:02,550 --> 00:01:05,170
get to the profile to edit their profile picture?

18
00:01:05,370 --> 00:01:06,380
That's a separate flow.

19
00:01:06,870 --> 00:01:11,610
And by naming your flows, you're really able to design from the user's perspective and you can split

20
00:01:11,610 --> 00:01:14,630
goals based off of what they're trying to do.

21
00:01:15,180 --> 00:01:17,160
Remember, you can create separate flows.

22
00:01:17,190 --> 00:01:19,140
Don't be afraid to make as many as you want.

23
00:01:19,170 --> 00:01:24,210
It really helps us break down all the different requirements we need in all the different scenarios

24
00:01:24,210 --> 00:01:25,380
that may pop up.

25
00:01:26,100 --> 00:01:28,180
Your flow should always go in one direction.

26
00:01:28,890 --> 00:01:31,620
I mean, there's really no excuse to do something like this.

27
00:01:32,540 --> 00:01:39,560
I mentioned it before about sprawling like flowcharts or site maps, but these are confusing and they

28
00:01:39,560 --> 00:01:43,820
don't really do a good job of actually indicating some sort of user flow.

29
00:01:44,120 --> 00:01:50,180
They may tell me all the different possibilities that the user may encounter while they're in our product

30
00:01:50,180 --> 00:01:52,000
or website or whatever we're building.

31
00:01:52,280 --> 00:01:55,470
But to take a look at that, that's incredibly overwhelming.

32
00:01:55,790 --> 00:02:01,970
So these work as a good site map or to show the way the navigation works in your product, but don't

33
00:02:01,970 --> 00:02:02,780
do it for a user.

34
00:02:02,810 --> 00:02:06,470
So what we should do is the following.

35
00:02:07,620 --> 00:02:10,680
Split them up into distinct flows and categorize them.

36
00:02:11,850 --> 00:02:18,030
So if we zoom out just a bit, we had like three different flows broken into er broken into one or put

37
00:02:18,030 --> 00:02:23,250
together as one, and over here, what we've done is even though there's like a decision tree, one

38
00:02:23,250 --> 00:02:28,830
of our flows, we've actually just broken them out separately, will name them both descriptions for

39
00:02:28,830 --> 00:02:31,460
each task and they'll have an end goal.

40
00:02:31,860 --> 00:02:34,270
So remember, keep it simple.

41
00:02:34,290 --> 00:02:35,230
Break it out.

42
00:02:35,550 --> 00:02:39,380
It's OK to be a little redundant, but it's going to help you in the end.

43
00:02:39,720 --> 00:02:40,890
And the last don't.

44
00:02:41,940 --> 00:02:44,550
Your photos should represent a complete task.

45
00:02:45,060 --> 00:02:48,520
Don't do this, you're missing a bunch of details here.

46
00:02:49,170 --> 00:02:53,960
There's a bunch of useless information like click button at bottom.

47
00:02:53,970 --> 00:02:58,470
I'm not sure what button means, fill out fields like what fields.

48
00:02:58,470 --> 00:03:01,370
And I mean, there is just nothing left at the end.

49
00:03:02,220 --> 00:03:05,310
We should have some sort of description of what that end goal is.

50
00:03:05,730 --> 00:03:11,070
We need to know the details the user needs to take to complete a task and the actions.

51
00:03:12,730 --> 00:03:18,130
This is what you should probably be doing at the right amount of detail, letting each step and goal

52
00:03:18,460 --> 00:03:21,040
this way, anyone can read and understand your flow.

53
00:03:21,140 --> 00:03:26,110
So I know that this flow is purchasing a product instantly and that can mean a lot of things.

54
00:03:26,110 --> 00:03:32,890
But we can break that up into several flows so I can review a product details, I can review a product

55
00:03:32,890 --> 00:03:34,930
details and use the buy now button.

56
00:03:35,590 --> 00:03:37,830
And that pushes me into the next step.

57
00:03:38,800 --> 00:03:46,090
I am reviewing shipping and payment information and we can even add to this review shipping and payment

58
00:03:46,090 --> 00:03:47,050
information.

59
00:03:49,040 --> 00:03:49,940
Confirm.

60
00:03:51,440 --> 00:03:55,040
Details and make a purchase.

61
00:03:58,290 --> 00:04:01,280
Let's just open this frame up just a little bit more.

62
00:04:05,690 --> 00:04:08,730
And the last step is that purchase has been confirmed.

63
00:04:08,750 --> 00:04:12,670
You get an order confirmation and you receive some sort of success message.

64
00:04:13,370 --> 00:04:18,020
So remember at the right amount of detail and outline each step and goal.

65
00:04:18,350 --> 00:04:22,290
That way, anyone can read it and understand it.

66
00:04:22,610 --> 00:04:27,020
We don't want people looking at those confusing site maps with not enough information outlining each

67
00:04:27,020 --> 00:04:28,760
step or each scenario.

68
00:04:29,030 --> 00:04:31,450
And we don't want people to be confused.

69
00:04:31,580 --> 00:04:37,040
So follow these do's and don'ts and you'll be ready to create your very own user flows.