-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathprojectOne.html
More file actions
595 lines (395 loc) · 24 KB
/
projectOne.html
File metadata and controls
595 lines (395 loc) · 24 KB
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
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
<!--USE ON EACH PAGE !!START!! -->
<!DOCTYPE html>
<html>
<head>
<title>Patrick H. Thomas | Portfolio</title>
<link rel="apple-touch-icon" sizes="180x180" href="images/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="images/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="images/favicon-16x16.png">
<link rel="manifest" href="images/site.webmanifest">
</head>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="stylesheet" type="text/css" href="main.css">
<link href="https://fonts.googleapis.com/css2?family=Raleway:wght@400;700&display=swap" rel="stylesheet">
<link href="https://fonts.googleapis.com/css2?family=Roboto+Slab:wght@400;700&display=swap" rel="stylesheet">
<link href="https://fonts.googleapis.com/css2?family=Josefin+Sans:ital,wght@0,200;0,400;0,600;0,700;1,400&family=Yeseva+One&display=swap" rel="stylesheet">
<link href="https://fonts.googleapis.com/css2?family=Montserrat:ital,wght@0,100;0,400;0,500;0,600;0,700;1,400&display=swap" rel="stylesheet">
<script src="https://kit.fontawesome.com/8b6e4ed6e1.js" crossorigin="anonymous"></script>
<body>
<header class="header">
<div class="header-row">
<!--logo-->
<span class="header-logo">
<img class="staticImage" src="images/colorlogo.svg">
</span>
<nav class="navLinkLayout">
<a class="navLink" href="index.html">HOME</a>
<!--<a class="navLinkProjects" onclick="smoothScroll(document.getElementById('projectOne'))">PROJECTS</a>-->
<a class="navLink" href="about.html">ABOUT</a>
</nav>
</div>
</header>
<!--USE ON EACH PAGE !!END!! -->
<main class="projectOneContent" id="projectOneContent">
<div class="projectOneHeroContainer">
<div class="projectOneHero">
<img class="staticImage" id="coopHeroImg" src="images/projectOne/hero.svg">
<div class="projectOneHeroText">
<h1>Coop</h1>
<p>When it comes to the creative process, an uninterrupted workflow can mean the difference between a stroke of inspiration and starting at a blank page. Coop wants to provide an online platform that allows teams to remotely create, share, and collaborate on projects without having to lose momentum. In addition to conducting research and developing the designs necessary to implement this task, I was happy to be able to craft an identity that accurately reflects the vision of the stakeholders and users alike.</p><br>
</div>
<div class="listLeft">
<h2>Role</h2>
<li>UX UI Design</li>
<li>Visual Design</li>
<li>Branding and Identity</li>
<br>
<h2>Tools</h2>
<li>Pen & Paper</li>
<li>Sketch, InVision</li>
<li>Adobe Illustrator</li>
</div>
<div class="listRight">
<h2>Deliverables</h2>
<li>User Research</li>
<li>Competitive Analysis</li>
<li>User Flows</li>
<li>Logo</li>
<li>Branding & Styleguide</li>
<li>Wireframes</li>
<li>High Fidelity Mockups</li>
<li>Prototype</li>
<li>Usability Testing</li>
</div>
</div>
</div>
<section class="projectOneSectionOne">
<div class="introContainer">
<div class="staticContainer">
<div class="coopText1">
<h2>Problem</h2>
<p>Services that are intended to facilitate remote work often cater to a homogenized user pool and often leave a large portion of users with a cluttered interface and extraneous features. Additionally, certain demographics that require a prioritization of collaboration, social connection, and iteration control are overlooked.</p>
</div>
<div class="coopText2">
<h2>Solution</h2>
<p>We developed an application that caters to the creative industry workforce, which we discovered is a widely overlooked demographic in this market. What emerged after iterating and testing our designs is an application that prioritizes features that assist creative workflow and social interaction without hindering a wider user pool from engaging in the baseline file storage and sharing capabilities. </p>
</div>
<img class="staticImage" id="solution" alt="Three views of the app on an android phone"src="images/projectOne/solution.svg">
</div>
<div class="firstButton">
<a class="activeButton" href="https://invis.io/U4YN0WEVQ5J">View Mobile Prototype</a>
</div>
<div class="firstButton">
<a class="activeButton" href="https://invis.io/68YULJ13JE2">View Desktop Prototype</a>
</div>
</div>
</section>
<section class="projectOneSectionTwo">
<div class="discoveryContainer">
<div class="staticContainer">
<div class="coopText3">
<h1>the discovery phase</h1>
<p>At the outset it was understood that the intention was to introduce a new application to the remote file storage and sharing market. Otherwise, it was too early to begin shaping the end product. We still needed to research the market and survey potential users to discover the identity and desires of our target audience.</p>
<br>
<p>I deployed an initial survey to determine the most frequently used remote storage and file sharing apps, then started with a comprehensive SWOT analysis of each of them. I then diagrammed user flows for each application, detailing three key actions: onboarding, saving an item, and organizing items. This helped to distinguish consistent or unique elements that exist in the competition’s user flows, and made helped me form an understanding of the nuances that set each apart.</p>
<p>I was starting to form a better understanding of the competition, but I still needed to deploy another more extensive round of user surveys in order to nail down a clearer picture of our power user, and what features will dominate our minimum viable product.</p>
</div>
<img class="staticImage" id="swot" src="images/projectOne/swot.png">
<div class="row2">
<div class="coopText4">
<h3>analyzing the data</h3>
<br>
<p>- 77% expressed the importance of remote collaboration
<br><br>
- 55% deemed social connectivity features a necessity
<br><br>
- 95% of those who reported working in a creative industry (photographers, illustrators, novelists, etc.) expressed the need for an easier way to collaborate remotely.
<br><br>
- All agreed features that are must-haves include multi-media file uploading, easy organization, streamlined sharing, as well as the ability to create text documents </p>
<br>
</div>
<!--CAROUSEL-->
<div class="carouselContainer1">
<div class="carousel1">
<div class="slide" onclick="smoothScroll(document.getElementById('slide2'))">
<img src="images/projectOne/study1.jpg">
</div>
<div class="slide" id="slide2">
<img src="images/projectOne/study2.jpg">
</div>
<div class="slide">
<img src="images/projectOne/study3.jpg">
</div>
</div>
</div>
</div>
<div class="coopText5">
<p>It was made clear that users who rely heavily and specifically on file organization and text editing features are generally happy with the products they’re currently using. In tandem with my prior market research, it appeared as if our competitors have a stronghold on office and professional use. Dissatisfied users generally wished that collaboration features were more prevalent. These users reported having jobs in marketing, illustration, and design, meaning our competitors don’t have a firm grip on a creative audience. After reviewing this user study, I was able to determine the best path forward was to position the product as a storage hub that makes collaboration on remote creative projects more convenient and accessible. The key features revolving around real-time collaboration, and social connectivity.</p>
</div>
<div class="row3">
<div class="coopText6">
<h3>getting to know the user</h3>
<p>The previously conducted research gave me a solid foundation to identify user personas. Each persona acts as a compilation of the motivations, frustrations, and goals discovered from the potential users surveyed previously, and from their ideation forward they will act as a summation of who will ultimately be engaging with the application.</p>
<br>
</div>
<!--CAROUSEL-->
<div class="carouselContainer2">
<div class="carousel2">
<div class="slide">
<img src="images/projectOne/persona1.jpg">
</div>
<div class="slide">
<img src="images/projectOne/persona2.jpg">
</div>
<div class="slide">
<img src="images/projectOne/persona3.jpg">
</div>
</div>
</div>
</div>
<!--CAROUSEL-->
<div class="row4">
<div class="coopText7">
<p>With the defined users in mind, I was able to brainstorm and prioritize specific functionality that the application will provide. Keeping a an eye on the aforementioned data streamlined this process and helped to avoid blindspots while avoid superfluous features. </p>
<br>
</div>
<!--CAROUSEL-->
<div class="carouselContainer3">
<div class="carousel3">
<div class="slide">
<img src="images/projectOne/story1.jpg">
</div>
<div class="slide">
<img src="images/projectOne/story2.jpg">
</div>
</div>
</div>
</div>
<!--CAROUSEL-->
<div class="coopText8">
<p>With this I had everything I needed to construct educated user flow diagrams for the most high priority features.</p>
<br>
</div>
<!--CAROUSEL-->
<div class="carouselContainer3">
<div class="carousel3">
<div class="slide">
<img src="images/projectOne/flow1.jpg">
</div>
<div class="slide">
<img src="images/projectOne/flow2.jpg">
</div>
<div class="slide">
<img src="images/projectOne/flow3.jpg">
</div>
<div class="slide">
<img src="images/projectOne/flow4.jpg">
</div>
<div class="slide">
<img src="images/projectOne/flow5.jpg">
</div>
<div class="slide">
<img src="images/projectOne/flow6.jpg">
</div>
</div>
</div>
<!--CAROUSEL-->
</div>
</div>
</section>
<section class="projectOneSectionThree">
<div class="designContainer">
<div class="staticContainer">
<div class="row5">
<div class="coopText9">
<h1>the design</h1>
<p>Now it was time to use all the knowledge gained in the discovery proccess to hash out how to apply the identified features to a material design. I began by sketching out wireframe iterations by hand.<br><br>
I then replicated those sketches in Sketch and assembled the first clickable prototype with InVision. Click the button below to see the first prototype.</p><br>
</div>
<img class="staticImage" id="sketches"src="images/projectOne/sketches.jpg">
</div>
<div class="firstButton">
<a class="activeButton" href="https://invis.io/QVY6MEVDETG">Go to Wireframe Prototype</a>
</div>
<img class="staticImage" id="wireframes" src="images/projectOne/wireframe1.png">
<!--BUTTON-->
<div class="row10">
<div class="coopText9">
<br>
<h3>usability testing</h3>
<p>Before going any further, it was important to put these early iterations in front of some test subjects. The primary focus for these initial tests was to ensure that the structure, logic of the flow patterns, and information architecture were translating well to the user, and if they weren’t, use the opportunity to properly identify the problem and develop solutions based on user feedback. </p><br> <br><p>The first round of usability testing was showing that the previous effort poured establishling the foundation for the design proved effective, but more importantly I was able to identify a few immensely important components of the design that needed to corrected. A few of the testers experienced enough confusion with the onboarding process to warrant an audit of the current flow pattern. With their feedback I was able to identify the pain points and provide a more descriptive but less overbearing onboarding approach.</p>
<br>
</div>
<!--CAROUSEL-->
<div class="carouselContainer4">
<div class="carousel4">
<div class="slide">
<img src="images/projectOne/onboard1.jpg">
</div>
<div class="slide">
<img src="images/projectOne/onboard2.jpg">
</div>
</div>
</div>
</div>
</div>
<!--CAROUSEL-->
<div class="staticContainer">
<div class="row6">
<div class="coopText9">
<p>Other functions that I was able to successfully rework as a result of user feedback revealed themseles on the main hub of the platform. The ability to organize materials was initially confined to a right-click function, which in retrospect defied the heirarchy of the previously established user stories. The testers’ experience reminded me of that fact, and I implemented an easier way to simply create a new organizational subfolder.</p>
</div>
<br>
<div class="carouselContainer4">
<div class="carousel4">
<div class="slide">
<img src="images/projectOne/hub1.jpg">
</div>
<div class="slide">
<img src="images/projectOne/hub2.jpg">
</div>
</div>
</div>
</div>
</div>
<div class="staticContainer">
<p>Additionally, this created a good opportunity to create a more prominent “Add Content” button, establishing a clearer solution to one of the most important functions of the product.</p>
<p>Upon passing a second round of usablity testing, I was feeling confident that this early iteration of the design was meeting the functionality and usablity of the minimum viable product.</p>
</div>
</div>
</section>
<section class="projectOneSectionOne">
<div class="discoveryContainer">
<div class="staticContainer">
<h1>branding & identity</h1>
<p>Acting as the sole designer on this project, it was also my duty to create and properly implement the branding for this new product. At this point, all I had to work with was the understanding of how the product is intended to function, and who the target audience is. </p><br>
<div class="row6">
<div class="coopText9">
<h3>Establishing the foundation</h3>
<p>At a bare minumum, Coop was to function as a remote, collaborative storage platform, so it was warranted to conduct some brief research into how similar products are branded. The goal was to learn how I could implement some of the common successful elements while also establishing a distinct brand that speaks to our target audience.After that I committed to sketching and moodboarding until a solid theme was established, from which the specific branding elements could emerge</p>
</div>
<br>
<div class="carouselContainer4">
<div class="carousel4">
<div class="slide">
<img src="images/projectOne/mood1.jpg">
</div>
<div class="slide">
<img src="images/projectOne/mood2.jpg">
</div>
<div class="slide">
<img src="images/projectOne/mood3.jpg">
</div>
<div class="slide">
<img src="images/projectOne/mood4.jpg">
</div>
</div>
</div>
</div>
<!--CAROUSEL-->
<div class="staticContainer">
<div class="row6">
<div class="coopText1">
<h3>Typography</h3>
<!--FONT FAMILY RALEWAY-->
<p class="raleway">Primary: RalewayRaleway displays as a strong and simple primary font. The geometric design and low contrast promote readiablity, while the medium-high x-height lends an expressive element.</p>
<p class="robotoSlab">Complementary: Roboto SlabRoboto Slab serves as an appropriate complement to Raleway with similar x-height and openness but with added serifs.</p>
</div>
<div class="coopText2">
<h3>color</h3>
<p>The colors I picked were chosen based on the previous moodboards, and were picked with the intention to be used sparingly across the platform. A complementary pallete gives the ability to draw attention to important functional aspects while maintaining conservative use of heavy fill colors.</p>
<img class="staticImage" id="colorImage" src="images/projectOne/color.png">
</div>
</div>
<h3>Compiling the style guide</h3>
<p>All of these brand decisions funnelled into a comprehensive style guide to aid in the iminent build out of a high fidelity prototype and any future changes to the design.</p><br>
<!--MODAL WINDOW-->
<!-- Trigger/Open The Modal -->
<div class="firstButton">
<a class="activeButton" id="styleGuideButton">See the Style Guide</a>
</div>
<!-- The Modal -->
<div id="myModal" class="styleGuideWindow">
<!-- Modal content -->
<div class="modal-content">
<span class="close">✕</span>
<img class="modalImg" src="images/projectOne/styleguide.jpg">
</div>
</div>
<!--MODAL WINDOW-->
<!--BUTTON-->
</div>
</div>
</section>
<section class="projectOneSectionTwo">
<div class="aboutContainer">
<div class="staticContainer">
<div class="row6">
<h2>High Fidelity Iterations</h2>
<br><br>
<h3>Leveraging the style guide</h3>
<p>The style guide was put to work immediately as an atlas for layering the branding aspects over the wireframes.</p><br>
<p>Key elements as well as whole page layouts were then paired with their alternatively styled counterparts and put in front of an audience for a series of preference tests. When the results established a pattern, I made revisions to reflect the feedback.</p><br>
<img class="staticImage" id="preferenceImg" src="images/projectOne/preference.png">
<div class="row6">
<div class="coopText9">
<h3>High Fidelity Prototype</h3>
<p>Feeling almost ready to apply the finishing touches on this project, I transformed the new mock-ups into another clickable prototype through InVision. I then turned to another pool of testers to give more feedback. With the vast majority of the structural and functional kinks worked out, I was given feeback that primarily focused on the aesthetic portion of the design. I also wanted to ensure that any implementation of the branding wasn’t impeding on the previously refined functional qualities. </p><br>
<h3>Final Refinements</h3>
<p>Adjusting to the feedback from this round of prototype testing was the last step in finalizing the Coop prototype and wrapping up this project.</p><br><br>
<div class="firstButton">
<a class="activeButton" href="https://invis.io/U4YN0WEVQ5J">Go to Mobile Prototype</a>
</div>
<div class="firstButton">
<a class="activeButton" href="https://invis.io/68YULJ13JE2">Go to Desktop Prototype</a>
</div>
</div>
<div class="bottomImgContainer">
<img class="staticImage" id="coopBottomImg" src="images/projectOne/hifi2.png"></div>
</div>
<!--BUTTON-->
</div>
</div>
</section>
<section class="projectOneSectionThree">
<div class="aboutContainer">
<div class="whyContainer">
<h2>Conclusion</h2>
<p>There are well established products that offer remote collaboration and content storage, but through this project I was able to create a brand and functional platform that caters to a user pool that this market typically doesn’t account for.With giants like Google Drive occupying the scene, it’s difficult to imagine establishing a design system that outweighs the competition. However, I was surprised to find my own user flows that proved easier to use in usability tests.That said, the competition dominating this market is generally feature-rich to an extent I wasn’t able to reach. While the minimum viable product was certainly delivered, given more time, I would have supplied Coop users with the ability to create spreadsheets, collaborate over video, or complete other more complex tasks.</p><br>
<h3 class="backToTop" onclick="smoothScroll(document.getElementById('projectOneContent'))">Back to the top</h3>
</div>
</div>
</section>
</main>
<!--USE ON EACH PAGE !!START!! -->
<footer class="footer">
<h3>I appreciate your time</h3>
<p>You can find me elsewhere on the internet or shoot me an email through any of the links below. Take care.</p>
<nav class="link-list">
<span class="footer-icon">
<a href="https://www.linkedin.com/in/patrick-thomas-b2234b191?lipi=urn%3Ali%3Apage%3Ad_flagship3_profile_view_base_contact_details%3BYj7z2P%2BjS1u%2BI99TvKcRhg%3D%3D">
<i class="fab fa-linkedin-in"></i>
</a>
</span>
<span class="footer-icon">
<a href="https://github.com/patrickhthomas">
<i class="fab fa-github"></i>
</a>
</span>
<span class="footer-icon">
<a href="https://www.instagram.com/monstersintherapy/">
<i class="fab fa-instagram"></i>
</a>
</span>
<span class="footer-icon">
<a href="mailto: patrick@sendhelp.biz">
<i class="fal fa-paper-plane"></i>
</a>
</span>
</nav>
<img class="staticImage" src="images/colorlogo.svg">
</footer>
<script src="main.js"></script>
</body>
</html>
<!--USE ON EACH PAGE !!END!! -->