1
00:00:00,930 --> 00:00:04,940
Let's look at all the steps we
need to include in the process.

2
00:00:04,940 --> 00:00:08,060
For a ride sharing app,
we have three different goals.

3
00:00:08,060 --> 00:00:12,110
To get to the airport quickly,
to get home as cheaply as possible, and

4
00:00:12,110 --> 00:00:15,410
the third goal, for
the third group you worked through.

5
00:00:15,410 --> 00:00:18,140
We also have things they
all have in common.

6
00:00:18,140 --> 00:00:20,980
They all have a starting point and
a destination.

7
00:00:20,980 --> 00:00:23,030
They all have to pay for their trip.

8
00:00:23,030 --> 00:00:26,640
We need to determine the best order for
all of this.

9
00:00:26,640 --> 00:00:29,790
For now, let's focus on the business man,
and we'll go back and

10
00:00:29,790 --> 00:00:31,050
look at the other groups in a minute.

11
00:00:32,080 --> 00:00:35,920
The business man has his goal,
to get to the airport quickly.

12
00:00:35,920 --> 00:00:39,140
But what does he need to
do in our app to get there?

13
00:00:39,140 --> 00:00:43,640
Let's make a stack of cards with all
the screens or pages that he needs to use.

14
00:00:44,880 --> 00:00:49,130
We may decide that our app could let
us schedule rides for the future, so

15
00:00:49,130 --> 00:00:52,030
this businessman doesn't
have to wait around.

16
00:00:52,030 --> 00:00:54,110
That sounds like a great feature, but

17
00:00:54,110 --> 00:00:57,220
is it something that actually plan for
the app?

18
00:00:57,220 --> 00:01:00,630
Sometimes we may find features
that you want to explore or

19
00:01:00,630 --> 00:01:04,150
implement when you're working on
some user experience document.

20
00:01:04,150 --> 00:01:08,360
After all, you're finding ways to
make the lives of your users easier.

21
00:01:08,360 --> 00:01:11,710
However, it's important to check
either with your projects team,

22
00:01:11,710 --> 00:01:14,740
if you're on one, or
with your own constraints

23
00:01:14,740 --> 00:01:18,720
to make sure that these features can be
implemented within the project's timeline.

24
00:01:20,450 --> 00:01:21,990
We need a destination,

25
00:01:21,990 --> 00:01:24,950
the driver won't know where to
take the passengers otherwise.

26
00:01:26,030 --> 00:01:28,890
Which also means we need
a pickup location, so

27
00:01:28,890 --> 00:01:31,450
the driver knows where
to meet the passenger.

28
00:01:31,450 --> 00:01:33,580
This should probably default
to the current location.

29
00:01:35,680 --> 00:01:40,070
We might want to follow up with
a survey about how his ride was.

30
00:01:40,070 --> 00:01:42,850
That way we can make rides better for
our future passengers.

31
00:01:42,850 --> 00:01:45,990
After making it through
security at the airport,

32
00:01:45,990 --> 00:01:49,210
our timely businessman will be waiting for
his flight.

33
00:01:49,210 --> 00:01:53,960
So he in particular may decide to rate
the driver when he's no longer in a rush.

34
00:01:55,260 --> 00:01:59,000
Additionally, we should ask if
he wants to tip his driver.

35
00:02:00,620 --> 00:02:04,010
We need a way for the businessman
to select the payment for his ride.

36
00:02:04,010 --> 00:02:08,364
For him specifically, we should be able to
choose between multiple payment options.

37
00:02:08,364 --> 00:02:12,317
He may have a company card as well as
a personal card within the app, so

38
00:02:12,317 --> 00:02:16,860
that's yet another step we need
to take into consideration.

39
00:02:16,860 --> 00:02:20,630
We may want to know how many people
are riding with the businessman, or

40
00:02:20,630 --> 00:02:23,440
at least allow him to choose
the number of seats in a vehicle.

41
00:02:24,850 --> 00:02:28,630
Is there a premium option
available with luxury cars?

42
00:02:28,630 --> 00:02:31,440
If so, let's find a place
to build that option in.

43
00:02:32,710 --> 00:02:37,259
The app should probably alert him
when his ride is getting close, or

44
00:02:37,259 --> 00:02:40,566
if the driver is running
late because of traffic.

45
00:02:40,566 --> 00:02:44,470
He is looking to book a ride
which is an obvious step, but

46
00:02:44,470 --> 00:02:46,390
it may be easy to overlook.

47
00:02:46,390 --> 00:02:49,617
We need on-boarding, or
the process of creating an account and

48
00:02:49,617 --> 00:02:52,310
setting up the app for first-time users.

49
00:02:52,310 --> 00:02:55,360
Since this isn't a repeated part
of the businessman's journey,

50
00:02:55,360 --> 00:02:58,130
we're going to leave those
details out of our user flow.

51
00:02:58,130 --> 00:03:00,920
However, if you're up for
an extra challenge, and for

52
00:03:00,920 --> 00:03:03,990
some more practice,
you can create a list of the pages and

53
00:03:03,990 --> 00:03:08,960
steps you think our businessman would
need to create an account on our app.

54
00:03:08,960 --> 00:03:12,750
For example, he may need a username,
a form of payment, and

55
00:03:12,750 --> 00:03:15,790
address that's set as home, or email.

56
00:03:15,790 --> 00:03:17,490
But that's just the beginning.

57
00:03:17,490 --> 00:03:20,730
Feel free to dream up what you
think he may need to do before he's

58
00:03:20,730 --> 00:03:21,640
able to use the app.

59
00:03:22,900 --> 00:03:24,480
Now that we have these cards,

60
00:03:24,480 --> 00:03:27,410
let's put them to use by doing
a hard sorting excercise.

61
00:03:28,600 --> 00:03:31,950
We can better visualize the different
steps in the process, and

62
00:03:31,950 --> 00:03:33,690
arrange them until they
make the most sense.

63
00:03:34,790 --> 00:03:38,920
People usually do card sorting exercises
for determining where content lives

64
00:03:38,920 --> 00:03:42,960
on a site, so they group them in
clusters with similar content.

65
00:03:42,960 --> 00:03:45,770
For example, mission statement, policies,

66
00:03:45,770 --> 00:03:51,090
company directory, and job opportunities,
could all fall under the about us heading.

67
00:03:51,090 --> 00:03:55,970
For our purposes, we'll be using the cards
like parts on a timeline, where we

68
00:03:55,970 --> 00:03:59,330
look at different steps and decide
the order that makes the most sense.

69
00:04:00,700 --> 00:04:01,300
Got it?

70
00:04:01,300 --> 00:04:02,680
Let's go.

71
00:04:02,680 --> 00:04:05,800
Our users would need to go through
an on-boarding process, but

72
00:04:05,800 --> 00:04:08,440
the businessman should've
done that already.

73
00:04:08,440 --> 00:04:12,640
Our first step for booking a ride
is to get the pick up location.

74
00:04:12,640 --> 00:04:15,968
Pickup location should default
to his current location.

75
00:04:15,968 --> 00:04:20,701
Next, he should select the destination,
either by typing it in, or

76
00:04:20,701 --> 00:04:21,934
by using the map.

77
00:04:21,934 --> 00:04:25,393
Then, the app should present to
him with his vehicle choices,

78
00:04:25,393 --> 00:04:29,000
including number of seats and
luxury upgrades.

79
00:04:29,000 --> 00:04:32,250
We'll also need to give him
a price estimate at this point.

80
00:04:32,250 --> 00:04:35,420
The app could give him a price
estimate with his vehicle choice,

81
00:04:35,420 --> 00:04:37,610
to minimize any back and forth.

82
00:04:37,610 --> 00:04:40,760
Maybe he needs to keep the trip
within a certain budget.

83
00:04:40,760 --> 00:04:44,210
Finally, he can choose to book now or
schedule for later.

84
00:04:44,210 --> 00:04:46,640
When he indicates that
he wants to schedule for

85
00:04:46,640 --> 00:04:50,300
later, he can then set
his idea arrival time.

86
00:04:50,300 --> 00:04:53,900
Let's say he wants to arrive at 3:45PM.

87
00:04:53,900 --> 00:04:58,030
If there are changes based on the time,
like a higher fare at night or

88
00:04:58,030 --> 00:05:02,220
early in the morning, the app will
inform him of the change in price.

89
00:05:02,220 --> 00:05:05,990
The app will tell him if there aren't any
luxury vehicles scheduled to drive at that

90
00:05:05,990 --> 00:05:09,710
time, in which case he can
book with an average car.

91
00:05:09,710 --> 00:05:10,600
Wait a minute.

92
00:05:10,600 --> 00:05:14,830
This sounds like we may have to
repeat the steps of choosing a car,

93
00:05:14,830 --> 00:05:16,950
which doesn't sound very efficient.

94
00:05:16,950 --> 00:05:21,480
To keep things in as few clicks as
possible, maybe we should move the option

95
00:05:21,480 --> 00:05:26,100
to book now, or schedule for later,
up to the front of the line.

96
00:05:26,100 --> 00:05:29,850
Now we can given the vehicle options
with price estimates all at once.

97
00:05:31,340 --> 00:05:35,077
Once he has selected the vehicle
option with price estimates,

98
00:05:35,077 --> 00:05:38,401
he should confirm his payment method and
book the ride.

99
00:05:38,401 --> 00:05:42,691
The app will let him know the time
that he should expect to be picked up,

100
00:05:42,691 --> 00:05:45,468
factoring in predicted
traffic in the area.

101
00:05:45,468 --> 00:05:48,270
The app will also alert him
when his driver is nearby.

102
00:05:49,570 --> 00:05:51,910
After he has been dropped
off at the airport,

103
00:05:51,910 --> 00:05:55,110
his payment method should be charged,
and an email receipt sent.

104
00:05:56,220 --> 00:06:00,480
The app should prompt him to rate his
driver and his passenger experience.

105
00:06:00,480 --> 00:06:02,790
And finally, tip if he enjoyed his ride.