-
Notifications
You must be signed in to change notification settings - Fork 0
/
qual-and-quant.html
210 lines (202 loc) · 14.2 KB
/
qual-and-quant.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta http-equiv="X-UA-Compatible" content="ie=edge">
<title>David Spencer | Qual & Quan</title>
<link rel="stylesheet" href="/css/normalize.css">
<link rel="stylesheet" href="/css/main.css">
<link href="https://fonts.googleapis.com/css?family=EB+Garamond:400,700|Roboto:300,400,700" rel="stylesheet">
<meta name="theme-color" content="#C6CCCA">
<link rel="shortcut icon" type="image/png" href="img/favicon32x32.png"/>
</head>
<body>
<nav id="nav">
<ul>
<li><a href="index.html">Home</a></li>
<li><a class="current" href="index.html#projects">Projects</a></li>
<li><a class="" href="about.html">About</a></li>
</ul>
</nav>
<header class="content-block hero">
<h1>Qualitative and Quantitative Research Informing UI</h1>
<h2>Using Analytics to Inform UX Design</h2>
<span class="tags">Analytics</span><span class="tags">Usability Testing</span><span class="tags">UI</span>
</header>
<!-- <div class="container"> -->
<main>
<div class="content-block">
<h3>Challenge</h3>
<p>A case study of the <a class="link" target="_blank" rel="nofollow" href="https://shop.googlemerchandisestore.com/">Google Merchandise Store</a> using qualitative and quantitative research to improve the e-Commerce website. The timeframe of this project was 2 weeks.
</p>
<h4><span>Software used</span></h4>
<ul>
<li>Google Analytics</li>
<li>Illustrator</li>
<li>InDesign</li>
<li>QuickTime Player (to record usability tests)</li>
</ul>
<h3>Findings</h3>
<p>After distilling data from Google Analytics and creating usability tests to confirm these observations, I discovered that the Google Merchandise Store has a lot of room for improvement. The focus of this case study is on the user flow of finding products and the check-out process, other areas of the site require attention but are outside the scope of this project.
</p>
<p>Recommended changes and Cart UI improvements to tackle checkout-out abandonment rate of 96.11% <span>[Fig. 1]</span> were realised from usability test insights.</p>
</div>
<figure class="wide-image">
<img class="responsive-h" src="img/qual-and-quan/google-merch-slide13.jpg" alt="Image of recommended UI changes to decrease check-out abandonment">
<figcaption>Fig. 1 Recommended Cart UI changes to decrease check-out abandonment.</figcaption>
</figure>
<div class="content-block">
<h3>Who are our users and how do they shop?</h3>
<p>Before creating the usability tests, I wanted to gather data to see who our users are and how do they interact with the site. Over a third of sessions are from desktop devices <span>[Fig. 2]</span>.
</p>
</div>
<figure class="wide-image">
<img class="responsive-h" src="img/qual-and-quan/google-merch-slide.jpg" alt="Pie chart showing users per device.">
<figcaption>Fig. 2 Pie chart of users per device.</figcaption>
</figure>
<div class="content-block">
<p>Considering the ratio of desktop sessions to mobile it was a little surprising to find that the majority of transactions actually come from mobile devices <span>[Fig. 3]</span>.</p>
</div>
<figure class="wide-image">
<img class="responsive-h" src="img/qual-and-quan/google-merch-slide2.jpg" alt="Stacked bar chart of transaction per time of day">
<figcaption>Fig. 3 Graph of transactions per device by time of day.</figcaption>
</figure>
<div class="content-block">
<p>I delved into this phenomenon a little further, so I looked at the sessions at each time of day and overlaid it on to the transactions <span>[Fig. 4]</span>.</p>
</div>
<figure class="wide-image">
<img class="responsive-h" src="img/qual-and-quan/google-merch-slide3.jpg" alt="Stacked bar chart of transaction per time of day with sessions overlay.">
<figcaption>Fig. 4 Overlay of sessions.</figcaption>
</figure>
<div class="content-block">
<p>Google gives everyone access to their merchandise store's analytics, but this access isn't at admin level so not all info is available. I couldn't track people across devices, so my inference is an assumption that people search on their desktops – at work – and then in their lunch break or commute they are making the purchases on their phones.</p>
<p>Another interesting finding was how virtually no-one uses the site search bar <span>[Fig. 5]</span>. This could be influenced by an unnecessary animation that hides the search bar on scroll. To see the search bar, one has to be at the very top of the page (window.pageYOffset = 0).</p>
</div>
<figure class="wide-image">
<img class="responsive-h" src="img/qual-and-quan/google-merch-slide6.jpg" alt="Pie chart of site search usage.">
<figcaption>Fig. 5 Site search usage</figcaption>
</figure>
<div class="content-block">
<p>Although an interesting insight, in the usability tests, even once the users found the search bar (taking up to 10 minutes in one case) they didn't feel compelled to use it. They wanted to see a more general view of the products when shopping, shopping by category and seeing the different styles and colours was preferred. One user stated, "To be honest with you I didn’t even notice the search box, I wouldn’t have used it for the Onesie. Maybe for the pen I would have used the search. I tend to search by category anyway."</p>
<p>The strongest performing category on the eCommerce store is Apparel <span>[Fig. 6]</span>.</p>
</div>
<figure class="wide-image">
<img class="responsive-h" src="img/qual-and-quan/google-merch-slide4.jpg" alt="Imgage of sales by category.">
<figcaption>Fig. 6 Sales by category in April 2019.</figcaption>
</figure>
<div class="content-block">
<p>An alarming statistic is the check-out abandonment rate of 96.11% <span>[Fig. 7]</span>, I offer UI solutions to this further on after insights from the usability tests.</p>
</div>
<figure class="wide-image">
<img class="responsive-h" src="img/qual-and-quan/google-merch-slide5.jpg" alt="xxx">
<figcaption>Fig. 7 Shopping drop-offs</figcaption>
</figure>
<div class="content-block">
<h3>Usability testing</h3>
<p>I conducted 3 usability tests and showed each person an image of a product to be added to the shopping cart, one at a time <span>[Fig. 8]</span>. After the 4 items were added to the cart, the users checked-out until the payment screen. The 4 tasks, adding an item to the cart, were timed.</p>
</div>
<figure class="wide-image">
<img class="responsive-h" src="img/qual-and-quan/google-merch-slide7.jpg" alt="image of the usability test products.">
<figcaption>Fig. 8 The products that were to be found and added to the cart.</figcaption>
</figure>
<div class="content-block">
<p>Task 1, find the 'YouTube Kid's Onesie White', proved to be difficult for all 3 testers... But why? <span>[Fig. 9]</span></p>
</div>
<figure class="wide-image">
<img class="responsive-h" src="img/qual-and-quan/google-merch-slide8.jpg" alt="Image of Comparative results of the time the tasks took each user.">
<figcaption>Fig. 9 Comparative results of the time the tasks took each user.</figcaption>
</figure>
<div class="content-block">
<h4>Making the user think</h4>
<p>The biggest confusion the site caused the users were the broken links at the bottom of the Home page <span>[Fig. 10]</span>. Upon seeing an image of a similar item to what they were looking for and it being titled 'View all kids Apparel', each user clicked on this. Instead of being directed to the Kids Apparel category, as expected, they were directed to the specific item pictured, 'Google Protector Onesie Navy'.</p>
</div>
<figure class="wide-image">
<img class="responsive-h" src="img/qual-and-quan/google-merch-slide9.jpg" alt="Image of broken links.">
<figcaption>Fig. 10 Broken category links go to specific product item, not category.</figcaption>
</figure>
<div class="content-block">
<p>This was true for each of the 'Shop by Category' links, causing a lot of confusion. A user said, "Ah huh, somehow I found another section, I don’t know how that worked out"</p>
<p><span>N.B. I checked back a few weeks later and the broken links were fixed, good work Google!</span></p>
<p>Unfortunately the confusion wasn't limited to the broken links. All users encountered a problem when adding apparel to the cart <span>[Fig. 11]</span>. Each time the user clicked 'Add to Cart', the choose size input was overlooked and the error modal didn't allow for size selection. The user had to close the modal and then choose the size.</p>
</div>
<figure class="wide-image">
<img class="responsive-h" src="img/qual-and-quan/google-merch-slide10.jpg" alt="Image of no size chosen error.">
<figcaption>Fig. 11 Overlooking size selection.</figcaption>
</figure>
<div class="content-block">
<p>Why did the user miss the 'Choose Size' selection? The select option isn't styled like a drop-down and the button 'Add to Cart' isn't styled like a button <span>[Fig. 12]</span>. Both these interactive elements don't have the proper affordance and increase the cognitive load on the user. Furthermore, once the user clicks on the 'Choose Size' drop-down, they are met with bizarre abbreviations for apparel sizes; SM, MD and LG. One user commented, "SM, I don’t know what that is… Small medium?".</p>
</div>
<figure class="wide-image">
<img class="responsive-h" src="img/qual-and-quan/google-merch-slide11.jpg" alt="Image of selecting size.">
<figcaption>Fig. 12 Select size confusion.</figcaption>
</figure>
<div class="content-block">
<h3>Improving the cart & check-out</h3>
<p>The current Cart <span>[Fig.13]</span> can be improved to reduce drop-offs further down the funnel.</p>
</div>
<figure class="wide-image">
<img class="responsive-h" src="img/qual-and-quan/google-merch-slide12.jpg" alt="Image of the current shopping cart.">
<figcaption>Fig. 13 The current Shopping Cart.</figcaption>
</figure>
<figure class="wide-image">
<img class="responsive-h" src="img/qual-and-quan/google-merch-slide13.jpg" alt="Image of changes to improve the cart.">
<figcaption>Fig. 14 Changes to improve the Cart.</figcaption>
</figure>
<div class="content-block">
<p>Even these simple changes <span>[Fig. 14]</span> could have a big impact on reducing abandonment and helping the user through the check-out process. None of the users that I tested noticed the 'Estimate Shipping', making the 'Estimate Shipping' look like a button (once again improper affordance) could improve check-out abandonment because users will realise they don't have to go further into the funnel to get shipping and tax pricing. This same rational can also be attributed to displaying the payment options on the cart, rather than waiting until the Payment page.</p>
</div>
<div class="content-block">
<p>Currently one must sign-in to check-out <span>[Fig. 15].</span></p>
</div>
<figure class="wide-image">
<img class="responsive-h" src="img/qual-and-quan/google-merch-slide14.jpg" alt="xxx">
<figcaption>Fig. 15 Current sign in to check-out page.</figcaption>
</figure>
<figure class="wide-image">
<img class="responsive-h" src="img/qual-and-quan/google-merch-slide15.jpg" alt="xxx">
<figcaption>Fig. 16 Proposed guest sign in option to check-out.</figcaption>
</figure>
<div class="content-block">
<p>Guest check-outs greatly reduce check-out abandonment <span>[Fig. 16]</span>.</p>
</div>
<div class="content-block">
<h3>Summary</h3>
<p>With these changes I'd expect a drop in check-out drop-offs and greater user satisfaction with the check-out process. These changes should be tracked further with Analytics concentrating on abandonment rates.</p>
<p>It was good to see that the broken category links were fixed weeks later, because this caused a lot of confusion for the user. The affordance on the 'Choose size' option and also the 'Add to cart' button really needs to be changed to reduce 'user error' (it isn't actually a user error, this is a design error). Also a content review is necessary, focusing first on the abbreviations of sizes.</p>
</div>
<div class="project-nav">
<div class="project-prev">
<a href="fomo-app.html">
<span class="direction">Previous</span>
<span class="description">#1 Gr8ti-tude: Wake up happier</span>
</a>
</div>
<div class="project-next">
<a href="design-thinking-workshop.html">
<span class="direction">Next</span>
<span class="description">#3 Design Thinking Workshop</span>
</a>
</div>
</div>
</main>
<footer>
<div>
<h5>Twitter</h5>
<a class="link" target="_blank" href="https://twitter.com/D_J_Spencer">@D_J_Spencer</a>
</div>
<div>
<h5>LinkedIn</h5>
<a class="link" target="_blank" href="https://www.linkedin.com/in/david-j-spencer/">www.linkedin.com/in/david-j-spencer</a>
</div>
<div>
<h5>Email</h5>
<a class="link" href="mailto:davidjspencer@gmail.com">davidjspencer@gmail.com</a>
</div>
<div class="">
<h6>Designed and coded by David Spencer, source code available on <a class="link" href="https://github.com/davidjspencer/portfolio">Github</a>.</h6>
</div>
</footer>
<script type="text/javascript" src="js/scroll.js"></script>
</body>
</html>