-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathneedsanalysis.html
320 lines (276 loc) · 25.6 KB
/
needsanalysis.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
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
<!DOCTYPE HTML>
<!--
Phantom by HTML5 UP
html5up.net | @ajlkn
Free for personal and commercial use under the CCA 3.0 license (html5up.net/license)
-->
<html>
<head>
<title>Needs Analysis</title>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<!--[if lte IE 8]><script src="assets/js/ie/html5shiv.js"></script><![endif]-->
<link rel="stylesheet" href="assets/css/main.css" />
<!--[if lte IE 9]><link rel="stylesheet" href="assets/css/ie9.css" /><![endif]-->
<!--[if lte IE 8]><link rel="stylesheet" href="assets/css/ie8.css" /><![endif]-->
</head>
<body>
<!-- Wrapper -->
<div id="wrapper">
<!-- Header -->
<header id="header">
<div class="inner">
<!-- Logo -->
<a href="index.html" class="logo">
<span class="symbol"><img src="images/logo.svg" alt="" /></span><span class="title">Wedding Planning</span>
</a>
<!-- Nav -->
<nav>
<ul>
<li><a href="#menu">Menu</a></li>
</ul>
</nav>
</div>
</header>
<!-- Menu -->
<nav id="menu">
<h2>Menu</h2>
<ul>
<li><a href="index.html">Home</a></li>
<li><a href="projectbrief.html">Project Brief </a></li>
<li><a href="consentnarrative.html"> Consent Narrative</a></li>
<li><a href="inspo.html">Inspirational Designs</a></li>
<li><a href="needsanalysis.html">Needs Analysis</a></li>
<li><a href="designdevelopment.html">Design Development</a></li>
<li><a href="heuristicevaluation.html">Heuristic Evaluation</a></li>
<li><a href="designrefinement.html">Design Refinement</a></li>
<li><a href="formalusabilitytestdesign.html">Formal Usability Test Design</a></li>
<li><a href="finalrefinement.html">Final Refinement</a></li>
</ul>
</nav>
<!-- Main -->
<div id="main">
<div class="inner">
<h1>Needs Analysis</h1>
<h2>What problem are you proposing to solve?</h2>
<p>
A person’s wedding day is the beginning of their life with their significant other. They get to wear fancy clothes, walk down the aisle, eat fancy cake, and at the end of the day, leave as a married couple. Perhaps for their honeymoon? People spend months, even years planning every intricate detail of this one day, detailing when things are going to get delivered and providing continuous entertainment for their guests. Planning the wedding day details is currently stressful because there are so many pieces to set up and dependencies out of the bridal party’s control. The options are hire an expensive day-of planner, have a stressed bride, have a stressed bridal party, or have things go perfectly (rarely). We propose to solve problems that arise on the day of the wedding by increasing communication between the bride and the people setting up, and alert the bridal party of tasks they should complete when they need to be done, in a manner that is not overwhelming. If we can mitigate the issues that arise on the day of the wedding, couples can have a smooth day without needing to hire an expensive day-of planner, brides will feel less overwhelmed, and each wedding attendant will know where to be at all times. Our solution could increase communication amongst all wedding participants, which would reduce the likelihood for problems to arise, and result in a graceful wedding day.
</p>
<h2>Who matters?</h2>
<p>
The bride and the groom are the most important people. Their wedding day is for them to officially start their new lives as a married unit with a new title and celebrate with their closest family and friends.
</p>
<p>
The bride and groom families are second tier because, according to our users, they are the ones that check on details and coordinate the setup when the bride or groom cannot.
</p>
<p>
The wedding depends on their hired caterers and vendors. The caterers provide goods necessary to the wedding such as cake, food, drinks, flowers, and more. Without these goods, parts of the wedding would be empty, causing unhappiness. Therefore, the location of these caterers is utterly important to the bride.
</p>
<p>
Finally, the rest of the wedding party and guests matter because the bride and groom invited them to celebrate their big day. They are emotionally connected to the bride and groom.
</p>
<h2>How do your prospective users think about this problem/activity?</h2>
<p>
For most people, the day of the wedding is about as stressful as it can get. After months (or years) of planning this one event, planners not only need to get ready for their own big day, but also make sure everything is going smoothly for the guests, all the food is arriving on time, the venue looks as it should, and all of the people are exactly where they are supposed to be. For some brides and grooms, the idea of all of this coordination and organization is so overwhelming that they hire a day-of coordinator, who comes in and deals with the majority of these logistics so the couple can enjoy their day together. However, not every couple has this luxury, and most couples who don’t resign themselves to the idea of “whatever will happen will happen” so that if something does go wrong on their big day, they are mentally prepared to ignore it and charge ahead. On top of all the stressful coordination that has to happen on the day of the wedding, weddings themselves draw out lots of emotions (good and sometimes bad) for the couple, their families, and their friends. It is often a huge turning point in the couple’s life together, and all that emotion coupled with the logistics of the day often has the couple feeling rather drained by the end of it. Oftentimes, the couple is so busy at their own wedding that they don’t even have time to enjoy the food that they so painstakingly chose for the day. Overall, most people look forward to their big day and are excited about what will come after it in their married life, but actually getting through that day can be extremely stressful for the couple and many of the people closest to them.
</p>
<h2>What requirements must your solution satisfy?</h2>
<ul>
<li>
The solution must reduce wedding stress on the day of the wedding, not increase it by adding a difficult learning curve.
</li>
<li>
The solution must be highly customizable so that each user has a positive experience. Many of the people we’ve spoken to have problems with the pre-laid templates and checklists because they don’t have the option to add things that are more relevant to them and remove the ones that don’t apply.
</li>
<li>
The solution must replace the need for a day-of coordinator.
</li>
<li>
The solution must be something that can be set-up before the day of the wedding, so that the day-of is as little stress as possible.
</li>
<li>
The solution must not be too invasive. Too many notifications or reminders on the day of the wedding could stress the couple out more than they would have been initially.
</li>
<li>
The solution must improve communications between the couple and anyone else helping them with day-of coordination.
</li>
</ul>
<h2>What will the impact of a successful solution be?</h2>
<p>
If our solution is successful, couples will be less stressed on the day of the wedding and will have more time to appreciate their big day. For different people, this may mean different things. For some, this might mean that they have more time to spend with family that they may not normally get to see or have a more relaxing morning getting ready instead of organizing centerpieces for later in the evening. We are also hoping that this solution will help people who are helping the couple on the day of. Oftentimes, close family and friends who are heavily involved in the planning process spend a lot of time on the day-of helping the couple coordinate all of the arrivals. We hope our solution will not only make this day easier on them, but also provide a more direct line of communication so that the couple and anyone else helping to coordinate feels more confident in the timeline of the day and that they each have the most up to date information.
</p>
<h2>Development of Personas</h2>
<p>
To help synthesize our interactions with users so far, we’ve developed 4 personas that distill some of the key qualities/personalities we’ve noticed so far.
</p>
<span class="image main"><img src="images/analneeds/personas.png"></span>
<div class="box alt">
<div class="row uniform">
<div class="3u">
<span class="image fit"><img src="images/analneeds/sarah.jpg" alt="" /></span>
</div>
<div class="3u">
<span class="image fit"><img src="images/analneeds/judy.jpg" alt="" /></span>
</div>
<div class="3u">
<span class="image fit"><img src="images/analneeds/john.jpg" alt="" /></span>
</div>
<div class="3u$">
<span class="image fit"><img src="images/analneeds/rebecca.jpg" alt="" /></span>
</div>
</div>
</div>
<ul><h3>Sarah</h3>
<li>Super organized, has been planning wedding for a while</li>
<li>Started planning her wedding over a year in advance</li>
<li>Gets a lot of info/help from people she knows who have gotten married recently</li>
<li>Has to balance wanting to be in creative control vs. accepting help from people around her</li>
<li>Has a ‘whatever will happen, will happen’ attitude towards day-of scheduling and management</li>
</ul>
<ul><h3>Judy</h3>
<li>Sarah’s mom, very kind, supportive and empathetic</li>
<li>Worried about finances, but also wants to make sure her Sarah has a happy, fulfilling wedding</li>
<li>Wants to be able to share information that she researches for her daughter more easily, both for day of and in general</li>
<li>Has taken on a lot of responsibilities and tasks for managing the day of the event, wants Sarah to feel at ease that she’ll handle it all </li>
</ul>
<ul><h3>John</h3>
<li>Chill and laid-back businessman with some experience in planning events and managing people</li>
<li>Doesn’t feel compelled to be part of the researching process - comes in after the research has been done and helps make the final decision</li>
<li>Not very stressed about the details of the wedding, more concerned with just being married and supporting his partner</li>
<li>Doesn’t have a lot of responsibilities the day of the wedding, but really wants to make sure his partner is as little stressed as possible</li>
</ul>
<ul><h3>Rebecca</h3>
<li>Rebecca is rather nonchalant about the entire process</li>
<li>Wants to maintain creative control over the wedding to see her vision come through and balance her aesthetic with her partner’s</li>
<li>Good at planning, and so isn’t particularly concerned about making it all come together</li>
<li>Hasn’t started planning her wedding yet, even though the event is less than a year away</li>
</ul>
<h2>Why is “day-of planning” important to our users?</h2>
<h3>Timeline</h3>
<span class="image main"><img src="images/analneeds/timeline.jpg"> </span>
<p>
We created a timeline of all the major “to-do” items that a wedding planner would have to do in order to plan a traditional wedding. One of the key insights we gained from creating this design artifact was 16% of the events needed to happen the day of the wedding (ex: setting up the cake, checking to make sure the music is ready).
</p>
<p>
It was difficult for our team to prioritize the tasks during the “day of.” There were several hypothetical situations where we imagined that a certain item that needed to arrive the day of was time restricted by time and the availability of people (ex: The florists could only arrive at 11 am because they have to make other flower deliveries in the morning). We also considered that because of these restrictions some events could happen at once (ex: The flowers and the band come at once). As a result, the “to do” items are scattered throughout the day and each wedding schedule will look vastly different, but requires a lot of planning ahead of time and a deep understanding of knowing exactly where and when people need to be.
</p>
<p>
Despite having a lot of “to do” items on the day of the wedding, there are still several items we left out. From the users we spoke to, several mentioned that they either delegated or planned on delegating certain “day of’” tasks to family or friends as a way to mitigate the chaos. Because this is such a case by case situation, we did not want to add another post it note (ex: Message Cynthia to confirm she picked up the flowers or ask Arjun to usher in guest) but one of aspects our group talked about is how there is a strong need for communication during “the day of” events.
</p>
<h3>Day-of Schedule</h3>
<p>
One of the users we talked to, Cassi, had a plethora of rich information regarding the intricacies of laying out the day-of schedule for her wedding. As a particularly organized bride, Cassi created a minute-by-minute playbook for all of the details of her wedding. She felt this gave her a greater level of control over the process, and put her mind at ease that she, and everyone involved in helping out, could sync up on what was supposed to be happening at any given time.
</p>
<span class="image right"><img src="images/analneeds/CassiSchedule.png"></span>
<p>
Months in advance, Cassi had already developed a schedule with this level of detail, and planned on going over it and distributing it among the many people in charge of making the wedding run smoothly. A quick analysis of this schedule reveals some key insights:
</p>
<ol>
<li>At pretty much any given part of the day, there are many interdependent moving parts that need to be coordinated</li>
<li>There are lots of stakeholders involved at different points of the day, and everyone needs to stay on top of the schedule and know where they’re supposed to be when</li>
<li>Once this document is printed and distributed, it’s fully static and last-minute changes would induce stress and unneeded complications</li>
</ol>
<p>
We (and the users we’ve talked to) firmly believe that the day of the wedding should be an enjoyable, stress-free experience focused on spending time with friends and family and celebrating the beginning of a new life together with your partner. In Cassi’s case, creating a granular schedule as above achieves some components of stress alleviation, BUT (1) Cassi is extraordinarily organized, and not all couples create such schedules in advance and (2) Even this system has drawbacks.
</p>
<p>
So what? Why is this important? Every user we’ve talked to has demonstrated varying levels of stress about the mechanics of planning and executing the day-of schedule for their wedding. While some personalities are more able to deal with the uncertainties of coordinating and puppeteering a complex event (and are accordingly less prone to breakdowns when problems inevitably arise), others are quick to lose tempers and chill, as vendors fail to show on time, the schedule shifts, and their control over making every detail perfect fades.
</p>
<p>
For both ends of the spectrum, there’s an immense opportunity to do some preventative care and patch a lot of potential sources for stress before it becomes a defining characteristic of the day. That’s where we come in.
</p>
<h3>Engagement Design Insights</h3>
<p>
In one of our engagements with a user, the user mentioned that the problem with several of our inspirational designs that attempted to simplify the entire process of wedding planning is the giant checklist format. These checklists stressed the user out just by looking at them and were too static and non-customizable, focusing on details that the user did not care about in regards to their own wedding.
</p>
<p>
During the engagement, the user designed an interface that they wish they could use instead of the hundreds-of-items-long checklist which would only show them a single task at a time and encourage them, whenever they have free time, to make headway on this task. In choosing which area of wedding planning to focus on developing a solution for, we ended up choosing day-of planning because we felt that we could provide the most impact to our users in this space and because we found it to be a really interesting interface design problem.
</p>
<p>
We are not proposing a solution to the day-of planning interface but rather, we realized that we could apply the design the user quickly sketched out during the engagement to our day-of planning problem to help us start framing some use cases. Below are mockups of the user’s particular design geared towards day-of planning.
</p>
<span class="image right"><img src="images/analneeds/mockup.png"></span>
<p>
Already, we can start to see some value this sort of interface would provide for the user, who is trying to enjoy the day of their wedding while also having to juggle the responsibilities that come with planning the event. This type of interface increases visibility to the planners (the bride and the groom) of what needs to be addressed by them and what doesn’t. Simultaneously, if we allow other people in the wedding party (such as the parents) to see the same screens as the planners and potentially handle/help out with situations that arise on the day of the wedding, we effectively also have a task distribution tool. For example, if the florist is late but the bride is getting dressed, a member of the wedding party could use this interface and notice that they can contact the florist and plan accordingly.
</p>
<p>
This system of distributed day-of coordination allows the user to focus their attention and energy on what matters during their big day. A lot of the users we have talked to point out that the planning of the wedding isn’t really what excites them and maybe isn’t even really for them as much as it is for their guests and family. Our users are more excited about starting their married lives together and so our value proposition is in minimizing and distributing the amount of stress the bride and the groom have to experience on the day of their wedding while doing our best to ensure everything still goes according to plan.
</p>
<h2>Effort Chart</h2>
<table>
<tr>
<th></th>
<th>Annabel</th>
<th>Christina</th>
<th>Zoher</th>
<th>Casey</th>
<th>Patrick</th>
<th>Total</th>
</tr>
<tr>
<td><strong>Project Brief</strong></td>
<td>20</td>
<td>20</td>
<td>20</td>
<td>20</td>
<td>20</td>
<td><strong>100</strong></td>
</tr>
<tr>
<td><strong>Needs Analysis</strong></td>
<td>20</td>
<td>20</td>
<td>20</td>
<td>20</td>
<td>20</td>
<td><strong>100</strong></td>
</tr>
</table>
</div>
</div>
<!-- Footer -->
<footer id="footer">
<div class="inner">
<!-- <section>
<h2>Get in touch</h2>
<form method="post" action="#">
<div class="field half first">
<input type="text" name="name" id="name" placeholder="Name" />
</div>
<div class="field half">
<input type="email" name="email" id="email" placeholder="Email" />
</div>
<div class="field">
<textarea name="message" id="message" placeholder="Message"></textarea>
</div>
<ul class="actions">
<li><input type="submit" value="Send" class="special" /></li>
</ul>
</form>
</section>
<section>
<h2>Follow</h2>
<ul class="icons">
<li><a href="#" class="icon style2 fa-twitter"><span class="label">Twitter</span></a></li>
<li><a href="#" class="icon style2 fa-facebook"><span class="label">Facebook</span></a></li>
<li><a href="#" class="icon style2 fa-instagram"><span class="label">Instagram</span></a></li>
<li><a href="#" class="icon style2 fa-dribbble"><span class="label">Dribbble</span></a></li>
<li><a href="#" class="icon style2 fa-github"><span class="label">GitHub</span></a></li>
<li><a href="#" class="icon style2 fa-500px"><span class="label">500px</span></a></li>
<li><a href="#" class="icon style2 fa-phone"><span class="label">Phone</span></a></li>
<li><a href="#" class="icon style2 fa-envelope-o"><span class="label">Email</span></a></li>
</ul>
</section> -->
<ul class="copyright">
<li>© Untitled. All rights reserved</li><li>Design: <a href="http://html5up.net">HTML5 UP</a></li>
</ul>
</div>
</footer>
</div>
<!-- Scripts -->
<script src="assets/js/jquery.min.js"></script>
<script src="assets/js/skel.min.js"></script>
<script src="assets/js/util.js"></script>
<!--[if lte IE 8]><script src="assets/js/ie/respond.min.js"></script><![endif]-->
<script src="assets/js/main.js"></script>
</body>
</html>