-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
286 lines (266 loc) · 8.13 KB
/
index.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
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<meta name="robots" content="noindex">
<title>Savor Seattle Testing Options</title>
<link rel="stylesheet" href="css/reset.css">
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/sky.css">
<!-- Theme used for syntax highlighting of code -->
<link rel="stylesheet" href="lib/css/monokai.css">
<!-- Printing and PDF exports -->
<script>
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match( /print-pdf/gi ) ? 'css/print/pdf.css' : 'css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
</head>
<body>
<div class="reveal">
<div class="slides">
<section>
<section>
<h2>Issue #1</h2>
<p>
A number of people didn't seem to make use of the top navigation on desktop devices
and couldn't find the self-guided tasting passports page.
</p>
<p>
<img src="img/issue1.gif" alt="">
</p>
</section>
<section>
<h2>Potential Solution</h2>
<p>
We hypothesized that users were mistaking the links for regular text and
thought that by adding subtle indications we could overcome this issue.
</p>
<p>
<img src="img/test1-var1.gif" alt=""><br>
<img src="img/test1-var2.gif" alt=""><br>
<img src="img/test1-var3.gif" alt="">
</p>
</section>
<section>
<h2>Results</h2>
<p>
We decided this would make a simple test and ran that experiment
over the period of 1 week. Unfortunately, the results were extremely
poor and we decided to end the experiment early as a result.
</p>
<p>
<img src="img/test1-results.gif" alt="">
</p>
</section>
</section>
<section>
<section>
<h2>Issue #2</h2>
<p>
Lots of people made mention of the fact that they weren't very clear on what they
would be able to pick with regards to their tasting options.
</p>
</section>
<section>
<h2>Potential Solution</h2>
<p>This was proposed and implemented by GLG</p>
<p>
<img src="img/issue2-solution.gif" alt="">
</p>
</section>
<section>
<h2>Results</h2>
<p>
This was considered to be particularly low risk and this wasn't run in the form of
an A/B test.
</p>
<p>
However, we don't know what impact that has made as a result.
</p>
</section>
</section>
<section>
<section>
<h2>Issue #3</h2>
<p>
It took at least one person <strong>over 10 minutes</strong> to understand
that the price <strong>included food</strong>.
</p>
<p>
<img src="img/issue3-hero.gif" style="height: 80%; width: 80%;" alt="">
</p>
</section>
<section>
<h2>Potential Solution</h2>
<p>
Identify opportunities to improve the clarity around this fact,
primarially through copy updates.
</p>
</section>
<section>
<h2>Status</h2>
<p>
This has yet to be addressed thus far.
</p>
</section>
</section>
<section>
<section>
<h2>Issue #4</h2>
<p>
We saw people making heavy use of the tour finder to understand our product
offerings however, it doesn't feature a blade for any of the Tasting
Passport options. While we have some information below, nobody scrolled
that far down the page.
</p>
<p>
<img src="img/issue4-example.gif" style="height: 50%; width: 50%;" alt="">
</p>
</section>
<section>
<h2>Potential Solution</h2>
<p>
Add the tour finder table
</p>
<img src="img/issue4-solution.png" alt="">
</section>
<section>
<h2>Potential Solution</h2>
<p>
Update the tour finder
</p>
<img src="img/issue4-solution2.gif" style="height: 50%; width: 50%;" alt="">
</section>
<section>
<h2>Considerations</h2>
<ul>
<li>This was quoted as $7,500 just to update the tour finder</li>
<li>That did not include any kind of testing</li>
<li>Did not include updating the table</li>
<li>Main risk is introducting an analysis paralysis style situation</li>
</ul>
</section>
</section>
<section>
<section>
<h2>Issue #5</h2>
<p>
Pricing isn't very clear on mobile devices
</p>
<p>
<img src="img/issue5.gif" style="width: 25%;" alt="">
</p>
</section>
<section>
<h2>Potential Solution</h2>
<p>
<img src="img/issue5-solution1.gif" style="width: 40%;" alt="">
</p>
</section>
<section>
<h2>Alternative Solution</h2>
<p>
<img src="img/issue5-solution2.gif" style="width: 50%;" alt="">
</p>
</section>
</section>
<section>
<section>
<h2>Issue #6</h2>
<p>
A number of users complained about the script font we were using as it
made the pricing difficult to read.
</p>
<p>
<img src="img/issue6-pricing.png" alt="">
</p>
</section>
<section>
<h2>Potential Solution</h2>
<p>
Pick a more appropriate font and replace it across the site or
potentially just for the relevant pricing sections.
</p>
</section>
<section>
<h2>Status</h2>
<p>Yet to be addressed thus far but considered very low risk.</p>
</section>
</section>
<section>
<section>
<h2>Issue #7</h2>
<p>
Many of our testers made heavy use of the homepage slider to see our options but we
don't currently have a blade for any of our passport options.
</p>
</section>
<section>
<h2>Potential Solution</h2>
<p>
Add a blade for each of the passport options.
</p>
<p>
<img src="img/homepage-blade.jpg" alt="">
</p>
</section>
<section>
<h2>Considerations</h2>
<ul>
<li>
Current quoted price to implement this is $3,400 but we can implement
most of this already without any additional custom development work.
</li>
<li>
Example shown in previous slide was done via the CMS in 10 minutes.
</li>
<li>
Overall considered low risk to implement.
</li>
</ul>
</section>
</section>
</div>
</div>
<script src="js/reveal.js"></script>
<script>
const presenting = false;
if (presenting) {
var masterKey = '15565070618491508833';
var plugin = 'plugin/multiplex/master.js';
} else {
var secret = null;
var plugin = 'plugin/multiplex/client.js';
}
// More info https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
controls: true,
progress: true,
center: true,
hash: true,
transition: 'slide', // none/fade/slide/convex/concave/zoom
multiplex: {
// Example values. To generate your own, see the socket.io server instructions.
secret: masterKey, // null so the clients do not have control of the master presentation
id: 'f7c1582ed879a9ff', // id, obtained from socket.io server
url: 'https://reveal-js-multiplex-ccjbegmaii.now.sh' // Location of socket.io server
},
// More info https://github.com/hakimel/reveal.js#dependencies
dependencies: [
{ src: '//cdnjs.cloudflare.com/ajax/libs/socket.io/2.2.0/socket.io.js', async: true },
{ src: plugin, async: true },
{ src: 'plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/highlight/highlight.js', async: true },
{ src: 'plugin/search/search.js', async: true },
{ src: 'plugin/zoom-js/zoom.js', async: true },
{ src: 'plugin/notes/notes.js', async: true }
]
});
</script>
</body>
</html>