1
00:00:00,000 --> 00:00:04,980
[MUSIC]

2
00:00:04,980 --> 00:00:08,930
We've covered a lot throughout
this course about users and goals.

3
00:00:08,930 --> 00:00:13,151
We're ready to combine the users and
their goals to make a user flow.

4
00:00:13,151 --> 00:00:17,368
User flows are the route we want users
to take from one end of the product to

5
00:00:17,368 --> 00:00:18,920
another.

6
00:00:18,920 --> 00:00:22,273
User flows aren't the only
path users can take.

7
00:00:22,273 --> 00:00:26,980
But a good user flow should provide a plan
to get users where they want to go as

8
00:00:26,980 --> 00:00:28,721
efficiently as possible.

9
00:00:28,721 --> 00:00:32,863
People in the industry sometimes use
the phrase in as few clicks as possible,

10
00:00:32,863 --> 00:00:37,860
because we don't want our users clicking
or tapping more than they have to.

11
00:00:37,860 --> 00:00:42,729
Again, it goes back to providing the best
experience possible for our users.

12
00:00:42,729 --> 00:00:46,350
This is why we're trying to give
them a good path to follow.

13
00:00:46,350 --> 00:00:48,519
The process should be intuitive.

14
00:00:48,519 --> 00:00:50,726
We don't want to make
it a complex riddle for

15
00:00:50,726 --> 00:00:53,850
our users to book a ride
to their destination.

16
00:00:53,850 --> 00:00:58,770
Also, the easier it is for them to book,
the less likely they are to quit

17
00:00:58,770 --> 00:01:03,298
the process and use a competitor's
app instead, or call a taxi.

18
00:01:03,298 --> 00:01:07,790
Like we've been saying all along, people
don't aimlessly tinker with products.

19
00:01:07,790 --> 00:01:10,793
They use them for a reason,
to achieve a goal.

20
00:01:10,793 --> 00:01:14,377
There are specific steps they should
take to reach their goals, so

21
00:01:14,377 --> 00:01:17,257
it's important to determine
what those steps are and

22
00:01:17,257 --> 00:01:20,670
make sure that those steps
are ordered logically.

23
00:01:20,670 --> 00:01:23,313
In our case,
users shouldn't be able to pay for

24
00:01:23,313 --> 00:01:26,696
their ride without specifying
where they're going first.

25
00:01:26,696 --> 00:01:28,540
That doesn't make a lot of sense.

26
00:01:28,540 --> 00:01:33,441
Instead, we should organize our product
in such a way that the steps the user

27
00:01:33,441 --> 00:01:34,750
takes makes sense.

28
00:01:34,750 --> 00:01:38,854
Users are trying to reach their goals and
expect things to be easy to find and

29
00:01:38,854 --> 00:01:40,300
ordered appropriately.

30
00:01:41,410 --> 00:01:44,114
Different users may use
the product differently, so

31
00:01:44,114 --> 00:01:45,744
take that into consideration.

32
00:01:45,744 --> 00:01:48,570
Not every user will have
the same user flow.

33
00:01:48,570 --> 00:01:52,772
Maybe there are options that the
businessman uses, like booking a ride in

34
00:01:52,772 --> 00:01:57,131
a fancier car that give him different
steps than the college students take.

35
00:01:57,131 --> 00:01:59,274
Think of it as a choose
your own adventure book,

36
00:01:59,274 --> 00:02:02,500
where you want everyone to reach
their different goals successfully.

37
00:02:03,810 --> 00:02:07,460
Unfortunately, our users aren't
all-knowing mind readers.

38
00:02:07,460 --> 00:02:11,617
They don't just automatically know what
we had in mind for them to do next.

39
00:02:11,617 --> 00:02:16,117
For that reason we need to guide our
users through the use of buttons,

40
00:02:16,117 --> 00:02:20,615
like a next button, calls to action
like book my ride, or feedback,

41
00:02:20,615 --> 00:02:23,580
the phone vibrates when
their ride pulls up.