<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ed Williams on Medium]]></title>
        <description><![CDATA[Stories by Ed Williams on Medium]]></description>
        <link>https://medium.com/@ed.williams.design?source=rss-f02c73e5ed74------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*VJaqx9ZU-2X8aiSpfAaPpA.png</url>
            <title>Stories by Ed Williams on Medium</title>
            <link>https://medium.com/@ed.williams.design?source=rss-f02c73e5ed74------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:24:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ed.williams.design/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Case Study: Mindful UX]]></title>
            <link>https://medium.com/@ed.williams.design/case-study-mindful-ux-db4f577e4a6f?source=rss-f02c73e5ed74------2</link>
            <guid isPermaLink="false">https://medium.com/p/db4f577e4a6f</guid>
            <category><![CDATA[art]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[mindfulness]]></category>
            <category><![CDATA[meditation]]></category>
            <dc:creator><![CDATA[Ed Williams]]></dc:creator>
            <pubDate>Mon, 07 Feb 2022 16:13:23 GMT</pubDate>
            <atom:updated>2022-02-15T10:59:51.858Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/875/1*nFJaJYqb473LPqToeQVQwA.png" /></figure><h4>Can a good user experience help with mindfulness and meditation?</h4><h3>Introduction</h3><h4>Brief</h4><p><a href="https://www.hereglobalrelief.org/"><strong><em>HERE Global</em></strong></a><strong><em> </em></strong>is a movement offering people a new way to meditate. The <em>HERE </em>mobile app combines meditation practice with interactive exercises to help people create mindful pauses in their day and to improve their overall emotional and mental wellbeing.</p><p>The app offers game-like exercises that incorporate interactions such as staring, breathing and finger movement to help stimulate the brain and calm the mind. The current exercises have been developed through extensive neuro-scientific research — for example, breathing slowly with the expanding and contracting circle pictured in Fig.1 helps the user to switch off their “flight or fight” mode and tells their brain that everything is okay. Furthermore, staring at the glowing circle helps to relax the eyes and promote subconscious activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XX3SJEa_HGPXsF2GKK2Dqw.png" /><figcaption>Fig.1: The HERE app’s existing breathing</figcaption></figure><p><em>HERE Global </em>are in the midst of redesigning their mobile app in time for a large corporate rollout later in 2022. My team of three were tasked with designing, prototyping and testing brand new interactive exercises which were aesthetically congruent with the ongoing app redesign. Within our three week timeframe, extensive UX research would need to take place to determine user wants and needs from such exercises, and with our findings I would get to lead the development of a scalable visual art style that could be applied to each new exercise through the use of vector assets and curated colour palettes. But before we go too far into that, let’s talk a bit about the requirements.</p><h4>Requirements</h4><p>There were a number of requirements we needed to consider for these exercises, which included the following:</p><ul><li>Incorporate a combination of interactive components such as breathing, humming and staring.</li><li>Maintain a visual way of guiding the user’s breathing.</li><li>Have an animation and art style that’s consistent and synonymous with <em>HERE</em>.</li><li>Include an intuitive feedback loop.</li><li>And, last but not least, the exercises should be fun.</li></ul><p>Of the above, I think as a team we agreed that the main opportunity and biggest challenge here would be creating exercises that engage the necessary interactions. We wanted to be careful not to turn these exercises into ‘games’, as that would be outside of our scope and skillset.</p><h3>User Research</h3><p>Having understood and digested the brief, the team was ready to collect the data that could backup our design choices. To begin, we wanted to hear directly from prospective users of such an app.</p><h4>Interviews</h4><p>We conducted 12 user interviews over Zoom. We chose this method because we wanted the opportunity to probe and ask follow-up questions to maximise the richness of our data. We focused our questions around the following areas:</p><ul><li>The users’ typical stress triggers.</li><li>How they switch-off and de-stress.</li><li>Their experience with interactive exercises and games.</li><li>How they visualise “tranquillity” and “calm”.</li></ul><p>Unsurprisingly, work-related issues is the main cause of stress for all users, followed by issues related to family members or friends, and lastly unhealthy lifestyle habits such as excessive eating or drinking, which is both a trigger of and response to stress.</p><p>To de-stress, 25% of users said they’d opt for something stimulating or active like exercise or learning something, and 75% said they would do something more passive and calming such as watching TV, scrolling on social media, and listening to music. This told us we should prioritise designing interactive experiences that have more calming (rather than stimulating) properties.</p><blockquote>“I watch TV because it’s passive, and requires zero energy. It really feels like I am doing nothing.”</blockquote><p>When it comes to users’ experience with interactive exercises and games, the theme of escapism came out really strong. Users like to use games to remove themselves from reality and immerse themselves in a different world (however briefly) to decompress.</p><p>Most interestingly, and perhaps unsurprisingly, all users described scenes of nature when we asked them to visualise “tranquillity” and to recall memories of being at peace. For example, walking in a forest, listening to the sound of crashing waves, etc..</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T6tDP9VDq8uQi8kADA0xnQ.png" /><figcaption>What users could expect to see when testing the original HERE app</figcaption></figure><h4>User Testing: Round 1</h4><p>In addition to the interviews, we also asked some of the users to test out the current exercises on the <em>HERE </em>app. We did this (despite the fact that the exercises will soon be replaced in the new version of the app) because we wanted to find out what we should avoid in our new designs and what we can incorporate so we don’t have to reinvent the wheel. Here are some of our key constructive findings:</p><ul><li><strong>Unclear Instructions</strong>: Many of the users failed to pick up on the explanation on the starting screen shown here and simply clicked through to start the exercise. Without context of the exercises and their benefits, users lost interest relatively quickly and were left wondering what they were supposed to get out of the interactions.</li><li><strong>Distracting Audio</strong>: 80% of the users found the default music and narration to be very distracting. There is actually an option to change the audio on the starting screen, but the option is only available for a few seconds before the exercises start, so users often miss the opportunity to do so.</li><li><strong>Gamification</strong>: One of the exercises is a shape sorting “game” and the shapes are counted in the bottom corners if sorted correctly to either side. Some users found this “gamification” aspect engaging — especially those with a competitive streak — whilst others found it distracting and conversely stressed them out because they were worried about the consequences of sorting a shape incorrectly, or they thought they had to meet a certain target that they are not aware of.</li><li><strong>Exercise Duration</strong>: Because there is no clear duration indication, users were confused about how long they were meant to do the exercise for.</li></ul><h4>Competitive Analysis</h4><p>We wanted to explore what was already available on the market, and identify any gaps or potential room for improvement in existing alternatives to the <em>HERE </em>app. To start this research, we created a <a href="https://en.wikipedia.org/wiki/Decisional_balance_sheet"><strong>Pluses &amp; Deltas</strong></a> analysis on the meditation subscription service <em>Headspace</em>, the daily planner and habit-builder <em>Fabulous</em>, and lastly, a 2014 mobile puzzle game created by a team of UX designers called <em>Monument Valley</em>. Through this research we discovered the following:</p><ul><li><strong>Onboarding</strong>: A clear and personal onboarding process (alongside tutorials) go a long way in making users (especially first time users) feel safe and well taken care of, like the one found within the <em>Fabulous</em> app.</li><li><strong>Audio Feedback</strong>: Using ambient sounds to create an atmosphere and give users audio feedback really helps to enhance the overall immersive experience, as demonstrated by <em>Monument Valley</em> where the animation gives a very subtle but satisfying click sound when you move certain parts of the level around.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t18Wn0jtGsklX3KCUAlJYA.png" /><figcaption>From left to right: Headspace, Fabulous, Monument Valley</figcaption></figure><h4>Conclusions</h4><p>Taking all of the user and market research findings into consideration, we came up with the following recommendations to take forward to ideation stage:</p><ul><li>Exercises should be nature-inspired, visually soothing and immersive.</li><li>They should include small design details that delight the user.</li><li>The benefits and duration of each exercise needs to be explained clearly upfront.</li><li>Each exercise needs a clear and simple tutorial to manage users’ expectation.</li><li>Any music or narration should be unobtrusive and fitting of the exercise.</li></ul><h3>Definition</h3><h4>Persona</h4><p>To help refine our findings thus far, we created a <strong>User Persona</strong> to concentrate our research through the focal point of an imaginary prospective user of the <em>HERE Global </em>app.</p><p>Meet Jerry, a 29 year old Sales Manager at a large tech company. He exhibits the following traits (inspired by our researched data):</p><ul><li>He is always very stressed at work due to demanding sales targets, and exhibits an almost non-existent work-life balance.</li><li>He regularly plays immersive video games or endlessly scrolls on social media to escape from the pains of reality.</li><li>He has dabbled in traditional forms of meditation before, but it hasn’t really worked very well for him. He’s keen to find a similar, but perhaps more accessible way to help him de-stress.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pqFlAOIkFPAVJYiJ2_rQSw.png" /><figcaption>A summary of our user persona, Jerry</figcaption></figure><h4>Problem Statement</h4><p>By honing in on a user, we were finally able to narrow down our users’ problem into a single statement:</p><blockquote>Jerry needs a way to reduce stress in his day so that he can improve his focus and mental wellbeing whilst learning new mindfulness habits.</blockquote><h4>Ideation</h4><p>Having reached a focused definition of the problem via the above problem statement, we felt confident to move onto the design phase of the <a href="https://en.wikipedia.org/wiki/Double_Diamond_(design_process_model)"><strong>Double Diamond</strong></a> process. This began with a design studio involving the client, where we came up with more than 50 ideas for the interactive designs. The client enjoyed being a part of the process, and appreciated the opportunity to get hands on with sketching and having their ideas included. From there, we took a vote to narrow the designs down to 12 strong contenders. We then created mini-storyboards for each one to see how the exercises would flow and whether there is visual synergy between each design. After this, the 12 designs were then further whittled down to 5.</p><p>At the client’s request, these designs were picked due to their complexity compared to some of the other ideas, so we felt a bigger need to wireframe and user test them at this stage. This complexity may have conceptually been the difference between an expanding and contracting orb that’s easy to imagine, versus a detailed nature setting which may have needed further prototyping to help the client visualise the end product. It’s also worth noting that three humming exercises were chosen because it’s a new interactive element that the app had not implemented before, so it was important for us to come up with a viable option for <em>HERE </em>to consider.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DKrow_Rp__7kXB2jtgu1tg.png" /><figcaption>A collage of ideas created during our Design Studio with the client</figcaption></figure><h3>Prototyping</h3><p>Having settled on our 5 favourite ideas with the help of the client, we were ready to bring these sketches to life by creating some initial prototypes.</p><h4>Mid-Fidelity</h4><p>We created short, mid-fidelity prototypes for each exercise to give users an impression of the functionality, pace, look and feel of the exercises. These were created within <em>Figma</em>, and used <em>Figma</em>’s own <a href="https://www.youtube.com/watch?v=6Id4INKEwb8"><strong>Smart Animate</strong></a> feature and prototyping tools to emulate a sense of interactivity.</p><h4>User Testing: Round 2</h4><p>We tested the mid-fidelity exercises on 7 users over <em>Zoom </em>and asked them to provide both quantitative feedback — in the form of a ‘1 out of 10’ user rating and an emoji rating, as well as qualitative feedback around their general likes and dislikes, the pace of breathing cues, and their interpretation of the onboarding tutorials. We primarily wanted to understand if:</p><ul><li>Users can interact with each prototype as intended.</li><li>What they liked or would change about the interactions and design.</li><li>Whether they find the tutorials sufficiently clear and helpful.</li><li>Whether they understand and can feel the benefits of the exercises.</li></ul><p>After conducting the user testing, we collated our feedback and drew up the following recommendations when it came to developing high-fidelity iterations of our 5 prototypes:</p><ul><li>Standardise visual design of all exercises so they look more coherent</li><li>Include consistent tutorial copy at the start of each exercise</li><li>Avoid using complex jargons when explaining the purpose and benefits of each exercise</li><li>Remove objects or animations that don’t fit in “naturally” to avoid distracting users</li><li>Slow down the breathing pace of a couple of the exercises</li><li>Include more user-centric and nuanced range of emotions for the feedback loop</li></ul><blockquote>“I liked it when my actions mirrored, or had relevance to, the exercises.”</blockquote><p>We implemented all of the above recommendations in our final iterations (which are discussed in more detail at the end of this case study), but the one point for improvement that required deep consideration was regarding the visual standardisation across all exercises. Therefore this is what we prioritised next.</p><h3>Design</h3><h4>Design System</h4><p>Picking up on the point about visual coherency, we knew it was a high priority to standardise the aesthetics across all of our exercises. This process entailed three primary considerations:</p><ul><li>The ongoing <em>HERE </em>app redesign.</li><li>The colour palettes in use across each exercise.</li><li>And the overall art style to unify the final aesthetic.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vm5Awcwn_pZLD1GTW6FrKA.png" /><figcaption>The ongoing HERE app redesign, with revised colour palettes</figcaption></figure><h4>The Redesign</h4><p>Looking first at the ongoing <em>HERE </em>app redesign, we had to consider a design process in flux as the redesign currently being worked on hasn’t yet been finalised. Despite this, we received verbal confirmation from the client that these soft sunset/sunrise gradients would form the backbone of the new app’s visual design. This provided an inspiring springboard into assessing the colour schemes and palettes that we could apply to our exercises.</p><h4>Art Style</h4><p>Deciding upon colour palettes was informed in conjunction with deciding upon the art style. Our client had helpfully created a moodboard of ideas that we could use as a point of reference. This included art styles such as:</p><ul><li>Geometric art</li><li>Vector landscape art</li><li>Polygon art</li></ul><p>From reviewing this we agreed that either the vector landscape art or the polygon art would be the wise choices to consider due to ease of application (bearing in mind the limitations of <em>Figma</em>, as well as our own illustration skills).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7_y0PDbSzwk_ANpay-HWUQ.png" /><figcaption>A moodboard of art styles we considered for the final designs</figcaption></figure><h4>Colour Palette</h4><p>Being able to isolate a handful of reference points helped us to analyse the consistencies between these art styles, and identify what they held in common. They appear to be tri-colour, with typically two complementary pastel gradients converging in on a champagne/magnolia hue which acts as a visual motif throughout the existing <em>HERE </em>app, as well as in many of the examples of vector art we’d been studying.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SNEO4epDRB6w5yauSD84Nw.png" /><figcaption>A colour analysis of art styles we’d taken inspiration from</figcaption></figure><p>In trying to replicate this formula, we created one unique colour palette per exercise which we were able to retrofit into each of our prototypes. This was a significant step in creating a visual coherency and standardisation across all exercises whilst allowing each exercise to adopt its own visual identity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u5CPDYdDGyzPqd1U-1Daag.png" /><figcaption>Each unique colour palette applied to its respective interactive exercise’s art style</figcaption></figure><h4>Vector Assets</h4><p>Lastly came finalising the art style that each exercise would use. In the interest of time, we’d chosen the vector art style to unify each exercise. In analysing the art style, we identified the following qualities:</p><ul><li>Hard edges (often either rounded or jagged) lending themselves to a clean and simplistic design.</li><li>Linear gradients to allude to depth perception.</li></ul><p>Full utilisation of these qualities would require the creation of several bespoke assets which could replace some of the stock placeholder assets deployed in our mid-fidelity prototypes. Take for example this earth asset (pictured in Fig.2) which was found using Google Images — fine for demonstrating an impression at mid-fidelity, but impossible to customise and cater to a high-fidelity art style. Building a new vector asset from scratch allowed for a scalable image resolution as well as a gradient colour scheme that could be tweaked at every single frame of the exercise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vAP84wjKtyvpidZAkNW61g.png" /><figcaption>From left to right: A placeholder PNG of Earth, found with Google Images and used during our mid-fidelity testing; an early vector image created using Figma’s pen tool; the same vector image with our colour palettes applied</figcaption></figure><p>The creation of these assets was done using the pen tool in Figma, and the end-result was a small ecosystem of cohering vector assets that we could use to easily decorate any scene or stage within the exercises.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6CaspF0UlcU8nhx8Muk0Pg.png" /><figcaption>Our art style ecosystem</figcaption></figure><h3>Conclusion</h3><h4>End Result</h4><p>By the end of our 3-week sprint, we had accumulated 5 unique animated and interactive exercises to assist with meditation and mindfulness. They were as follows:</p><p><strong><em>Perspective Building</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yoo5zW9pxHoc1w6Lul6uPA.png" /></figure><ul><li><strong>Description</strong>: For every inhale and exhale the user takes, the perspective of the scene zooms out one notch — beginning on a boat stranded at sea, travelling through to the Earth’s atmosphere, and eventually resting at a panoramic view of the entire known universe.</li><li><strong>Interactions</strong>: Breathing, staring, eye movement.</li><li><strong>Benefits</strong>: Breathing stimulates the parasympathetic nervous system, staring induces eye relaxation that promotes subconscious activity, and travelling text prompts yield saccadic eye movements.</li></ul><p><strong><em>Humming Mountains</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f5Op9vZKUkY8YDUSVkxeew.png" /></figure><ul><li><strong>Description</strong>: As the user hums, the scene slowly awakens and breathes into life — starting out as a slumbering view of desolate snowy mountains, but culminating in a vibrant display of flora and volcanic activity.</li><li><strong>Interactions</strong>: Breathing, humming, staring.</li><li><strong>Benefits</strong>: Breathing stimulates the parasympathetic nervous system, humming prompts the vagus nerve and relaxation response, and staring induces eye relaxation that promotes subconscious activity.</li></ul><p><strong><em>Humming Bee</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w-1o6KWn3cTd3Tout8zjZQ.png" /></figure><ul><li><strong>Description</strong>: The user hums to emulate the buzzing of a bee as it flies from flower to flower, pollinating as it goes.</li><li><strong>Interactions</strong>: Breathing, humming, staring.</li><li><strong>Benefits</strong>: Breathing stimulates the parasympathetic nervous system, humming prompts the vagus nerve and relaxation response, and staring induces eye relaxation that promotes subconscious activity.</li></ul><p><strong><em>Humming Waves</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8vMfGqETebTk-eOr4VLN-g.png" /></figure><ul><li><strong>Description</strong>: A user’s hum causes a mesmerising ripple upon the water.</li><li><strong>Interactions</strong>: Breathing, humming, staring.</li><li><strong>Benefits</strong>: Breathing stimulates the parasympathetic nervous system, humming prompts the vagus nerve and relaxation response, and staring induces eye relaxation that promotes subconscious activity.</li></ul><p><strong><em>Nature Jigsaw</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jSFfQe6D1skJgh1fqHUXsA.png" /></figure><ul><li><strong>Description</strong>: By engaging their thumbs, the user twists and turns an autumn leaf until it fits the contours of a uniquely-shaped border, triggering an oddly satisfying animation to encase the leaf and present a brand new jigsaw.</li><li><strong>Interactions</strong>: Alternating finger gestures, staring.</li><li><strong>Benefits</strong>: Moving thumbs across the body midline promotes cross hemispheric brain communication, and staring induces eye relaxation that promotes subconscious activity.</li></ul><h4>Next Steps</h4><p>Given the interactivity and animation limitations of Figma, I’m not sure there is much more value that a UX Designer could add to these existing exercises, before requiring to be handed over to experienced animators and (potentially) game designers for further finessing and development.</p><p>With more time, I’m sure our next priority would be to develop another five more exercises in the style of the ones already created, whilst incorporating more variety into the interactions and benefits.</p><h4><strong>Key Learnings</strong></h4><p>After the 3-week sprint, my team was able to produce 5 impressionable animated prototypes which were grounded in exhaustive user research. The client was very happy, and was able to take away from the sprint a universally applicable art style that can be used at multiple fidelities, as well as a handful of interactive exercises which can be further explored and developed at the client’s discretion.</p><p>My key learning from this sprint was regarding project pacing, and ensuring that the scope of the project was well defined through effective and transparent communication with the client. This was how we were able to meet so many of the project requirements in such a short timeframe.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db4f577e4a6f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: A Deep Dive Into UI]]></title>
            <link>https://medium.com/@ed.williams.design/case-study-a-deep-dive-into-ui-fd9448d2b5bf?source=rss-f02c73e5ed74------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd9448d2b5bf</guid>
            <category><![CDATA[tourism]]></category>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[experience]]></category>
            <dc:creator><![CDATA[Ed Williams]]></dc:creator>
            <pubDate>Mon, 07 Feb 2022 10:57:38 GMT</pubDate>
            <atom:updated>2022-02-07T10:57:38.502Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/875/1*ogpiUFkAwLH66HEFq6ss2A.png" /></figure><h4>Transforming an archive into an experience with the user interface</h4><h3>Introduction</h3><h4>The Brief</h4><p>This project was a one-week solo sprint to take an existing website belonging to a non-profit organisation and give it a <strong>User Interface</strong> re-skin, uplift and (if necessary) rebrand that could apply to and fit across three different device viewports.</p><p>I’d chosen to take on a website called <a href="http://www.irishwrecksonline.net/"><em>Irish Wrecks Online</em></a>. They operate an online database of every known wreck surrounding the Irish coastline. Without wanting to equivocate too much; one glance at this website and it isn’t hard to tell that its UI hasn’t received much attention over the last 25 years since its establishment in 1997. It was time to bring this website into the 21st century.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EtnJNI9Ps8ZytaF1XZa0UA.png" /><figcaption>The current Irish Wrecks Online website</figcaption></figure><h4>Process</h4><p>Unlike some of my more recent projects, due to time constraints and the nature of the work, this project didn’t rely as much on the Double Diamond design process —however that’s not to say that no research took place. As part of this work I undertook various introspective exercises to help me narrow down and define a decisive ‘look and feel’ for this website redesign. These included a <strong>brand personality scale</strong>, a <strong>functionality compass</strong>, and a <strong>glossary of relevant terms</strong> and adjectives which could pertain to the new theme.</p><p>On the more ‘objective’ side of research I conducted a comparative analysis; deconstructing both lateral ‘competitors’ to Irish Wrecks Online, as well as adjacent, ‘nautical-themed’ sites and experiences. These included the <a href="https://rnli.org/"><em>Royal National Lifeboat Institution</em></a> (RNLI) website, the <a href="https://www.ireland.com/en-gb/"><em>Ireland Tourism</em></a> site, <a href="https://www.tenbyboattrips.co.uk/"><em>Tenby Boat Trips</em></a>, and the <a href="https://www.ikonpass.com/"><em>IKON</em></a> snow-sports resort pass homepage (a returning competitor that featured in my last project).</p><p>Whilst some of these comparisons gave me an insight into how to theme my redesign, what I could infer from sites like <em>IKON</em> and <em>Ireland Tourism</em> was a way to <strong>sell an experience</strong>. The focus on ‘experience’ would become central to this project’s design philosophy going forward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KOziRUqBCmWPuLPh0h6oDg.png" /><figcaption>The IKON website.</figcaption></figure><h3>Design</h3><h4>Moodboard</h4><p>With a few abstract ideas now fuelling the preliminary stages of the design process, it was time to draw inspiration directly from some appropriate visuals. Knowing that I wanted to turn <em>Irish Wrecks Online</em> (which, for all intents and purposes, is a database/archiving website) into something echoing a tourism/adventure experience, I wanted to look primarily towards iconism and imagery from <strong>pop-culture</strong>. This would include anything from movies and television, to music and video games.</p><p>I reviewed colour schemes and palettes from the likes of Guillerm Del Toro’s <a href="https://en.wikipedia.org/wiki/The_Shape_of_Water"><em>The Shape Of Water</em></a> and Wes Anderson’s <a href="https://en.wikipedia.org/wiki/The_Life_Aquatic_with_Steve_Zissou"><em>The Life Aquatic With Steve Zissou</em></a>; both of which blended marigold yellows (synonymous with various nautical paraphenalia such as sou’wester hats and mackintosh overalls) which popped against the backdrop of a deepening turquoise gradient (synonymous with the depths of the ocean).</p><p>The thrill (or, perhaps, fear) of the unknown is unsurprisingly prevalent in many maritime-themed medias. I considered delving into the eldritch themes of <a href="https://en.wikipedia.org/wiki/Lovecraftian_horror">Lovecraftian horror</a>, or perhaps the bleak mystery surrounding seafaring ghost stories such as 2019&#39;s <a href="https://en.wikipedia.org/wiki/The_Lighthouse_(2019_film)"><em>The Lighthouse</em></a> (starring Robert Pattinson and Willem Dafoe), or <a href="https://en.wikipedia.org/wiki/Return_of_the_Obra_Dinn"><em>The Return Of The Obra Dinn</em></a> (a 2018 puzzle-based video game, inspired in turn by the real events of the <a href="https://en.wikipedia.org/wiki/Mary_Celeste">Mary Celeste</a>). Enticing as these may be, I felt like their influence over the redesign should be limited, as this site is intended for audiences of all dispositions — not <em>just</em> for those susceptible to mystery, horror and general eeriness.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hy5dADxy6Lwc-yjxwC9cXA.png" /><figcaption>My moodboard, organised as a gradient collage (from left to right; deep blues and greens to burning pinks and oranges)</figcaption></figure><h4>Collages</h4><p>Gathering together a sizable collection of seagoing stock photography from <a href="https://unsplash.com/">Unsplash</a> and a handful of matching typographies, I began to mix and match various fonts, phrases, colours and images to help get an early sense of the textures that might appear on the site’s redesign.</p><p>This practice helped me to hone in on my final design system; deciding on a typography, colour palette, and overall aesthetic — the next step was to create a components library and begin prototyping.</p><h3>Prototyping</h3><h4>Concept</h4><p>Through the use of references found on my <strong>moodboard</strong>, the <strong>collages</strong> I’d begun creating, and the lingering desire to create an <strong>experience</strong> out of the new <em>Irish Wrecks Online</em> website, I’d finally resolved to basing the website redesign on a particular concept:</p><blockquote>As the user scrolls down the homepage, the imagery shifts and changes to emulate the sensation of a diver submerging deeper underwater.</blockquote><p>This could be achieved through the use of repeating site sections acting as a buffer for any appropriate stock imagery (which could denote the sense of a diver going deeper underwater).</p><h4>Components Library</h4><p>As I knew I’d need to make my designs scalable for multiple device viewports (small, medium, large; phone, tablet, desktop — respectively), as well as wanting to reinforce efficient prototyping best practices across my design, I sought to create repeatable site sections through the use of <em>Figma</em>’s <a href="https://www.youtube.com/watch?v=k74IrUNaJVk"><strong>Components</strong></a> feature.</p><p>I then built each of my components using Figma’s <a href="https://www.youtube.com/watch?v=TyaGpGDFczw"><strong>Auto-Layout</strong></a> feature, which meant that no matter the context in which I placed my component, I was always able to keep the formatting and layout of the section the same across viewports.</p><p>Whilst this process is mildly time-consuming when you first start building your prototype’s <strong>Components Library</strong>, you will eventually save yourself hours of time later down the line if you need to retroactively amend any colours, fonts, dimensions, etc., or if you need to repeat a section multiple times throughout your prototype. This foundational work enabled me to effectively drag and drop sections as I saw fit, with little to no further effort required to achieve my desired results.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FNMnfPk23UOo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DNMnfPk23UOo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FNMnfPk23UOo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/adbb1de9938263d6d4ccb04f4ea15891/href">https://medium.com/media/adbb1de9938263d6d4ccb04f4ea15891/href</a></iframe><h4>Animations</h4><p>One expectation I had to repeatedly juggle during this sprint was how high-fidelity I would eventually be able to make the prototype look. As I had imagined the effect of diving deeper underwater being bolstered by a <a href="https://en.wikipedia.org/wiki/Parallax_scrolling"><strong>parallax scrolling effect</strong></a>, it was something I was really keen to implement, but ultimately it was more of a ‘nice-to-have’ and my top priority was developing a <a href="https://en.wikipedia.org/wiki/Minimum_viable_product"><strong>minimum viable product</strong></a> that could be used to demonstrate the broad strokes of the redesign.</p><p>Fortunately, due to the aforementioned time-saving measures taken with my Components Library, I had enough time leftover at the end of the sprint to implement the intended parallax effect in a final high-fidelity prototype. This was achieved using Figma’s <a href="https://www.youtube.com/watch?v=6Id4INKEwb8"><strong>Smart Animate</strong></a> feature. The end result was a homepage that dynamically shifts to strengthen the illusion of diving deeper underwater.</p><h4>Next Steps</h4><p>Whilst I achieved more than I was expecting to on this project, given more time I would revise some of the UX choices that may have been overlooked in favour of the site’s UI overhaul. This would likely involve more time spent revising the site’s information architecture, and prioritising certain content based on its relevancy to the original <em>Irish Wrecks Online</em> mission statement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JoH5caFrX9QVcwCqFaolYg.png" /><figcaption>My final prototype, as displayed on multiple device viewports</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd9448d2b5bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Designing For DICE]]></title>
            <link>https://medium.com/@ed.williams.design/case-study-designing-for-dice-8d442968cab6?source=rss-f02c73e5ed74------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d442968cab6</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[music]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[discoverability]]></category>
            <dc:creator><![CDATA[Ed Williams]]></dc:creator>
            <pubDate>Sun, 06 Feb 2022 14:56:30 GMT</pubDate>
            <atom:updated>2022-02-06T14:56:30.932Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/875/1*toIGGenvwdCrZoC1xJQIkQ.png" /></figure><h4>Growing artist discoverability via a subscription service.</h4><h3>Introduction</h3><h4>The Brief</h4><p>This was a group concept UI/UX project oriented around designing and developing a hypothetical subscription service for the event ticketing platform, <strong>DICE</strong>.</p><p>DICE is a ticketing service that connects fans to live events. Fans using the DICE app can search, browse and buy tickets for upcoming live shows, gigs, concerts, club nights, festivals, and cultural events which have been curated by an editorial team. Tickets are purchased within the app and exist on the user’s smartphone as a QR code which also includes the date, time and location of the event. Events within the app can be found and <strong>discovered</strong> by linking the app with the user’s Spotify account.</p><p>Discoverability was a crucial detail for the project, as the brief required us to re-examine how a user can discover new artists via the DICE app in order to drive business to emergent acts and artists. We were to assume that DICE were planning to build a subscription service, which would enable users to discover and attend new live shows tailored to their likes and location.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-mIcwwWvFrQiwthK.png" /><figcaption>The DICE app in its current form.</figcaption></figure><h4>Methodology</h4><p>We relied on the Double Diamond design process model to structure and pace our workflow. This model primarily encompasses research and design, but it really helped us to stay within a predetermined scope on the project, and ensure we weren’t missing out on any key stages of our project’s deliverables.</p><p>The process model itself breaks itself down into 4 key stages:</p><ul><li><strong>Discover</strong>: During this stage we undertake User Research which helps to expand our knowledge, and correct any assumptions we might have about the client’s brief.</li><li><strong>Define</strong>: This is the part of the project where we begin to narrow down our findings in order to address a well-defined issue.</li><li><strong>Develop</strong>: Here we brainstorm ideas in an effort to solve the client’s problem, and hopefully hit upon an idea that the team likes and wants to proceed with.</li><li><strong>Deliver</strong>: Finally, in this stage we bring together the culmination of our iterated Mid- to Hi-Fidelity Prototypes in order to ensure that we’re in a good place to deliver a viable solution to the client.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0n-Bwnt2uxnKQvBY8CTabQ.png" /><figcaption>A diagram representation of the Double Diamond process model.</figcaption></figure><h4>Project Planning</h4><p>Once we’d structured the project, we had some work to do to establish some planning parameters, best practises and responsibilities. Throughout the course of the project, we’d migrated between a few different methods, but ultimately we focused on the following methods:</p><ul><li><strong>Daily Calendar</strong>: A calendar helped us to pace and place each individual task and deliverable for the project, but it didn’t let us check in on the status of an individual task. This is where the Kanban Board came in.</li><li><strong>Kanban Board</strong>: The Kanban Board allowed us to organise tasks by their status, and in the end this became our primary mode of organisation.</li></ul><p>Tasks were split up amongst the team at the start of the project, but as the scope developed and evolved, we could re-task and reprioritise on an ad-hoc basis. Upon completion of the project, my involvement had extended to user interviews, competitive research, user journey, information architecture, problem definition, ideation, wireframes, prototyping (UI) and user testing.</p><h3>User Research</h3><h4>Steps</h4><p>Whilst we undertook several processes to obtain our user research (including comparative research, personas, user journey flows), the methods we found to be most insightful were user interviews and competitive analysis.</p><p><strong>User Interviews</strong> were a great way to identify the key trends present in the topics of <strong>live events</strong> and <strong>subscription services</strong>. The most prominent of which were:</p><ul><li><strong>Discoverability</strong>: How do people find the events they want to attend? How can we take advantage of these methods and apply them within a subscription service?</li><li><strong>Incentives</strong>: What value can a subscription service provide its users? Why should people <em>want</em> to pay for such a service?</li><li><strong>Coronavirus Concerns</strong>: What safety measures can be put into place to ensure event-goers feel safe in a post-coronavirus world?</li></ul><p>Our <strong>Competitive Research</strong> helped us to identify different approaches to offering value for money from a subscription service. The competitors we identified were:</p><ul><li><strong>Jukely</strong>: Jukely is the most direct competitor to this hypothetical subscription service. It, too, is a subscription service which offers benefits/discounts/bonuses via a virtual currency which can also be used to buy and trade tickets.</li><li><strong>Spotify</strong>: Whilst Spotify is a subscription service, it doesn’t offer any additional value to its customers with regards to event-going — where it does excel is with its discoverability functions.</li><li><strong>IKON Pass</strong>: Of all three competitors, this service is perhaps the most lateral choice for comparison. It functions as an ‘unlimited access’ pass for snow sports at select ski resorts loacated around the Americas.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/665/0*qTs_mhx3kuBVT7pK.png" /><figcaption>The Jukely app.</figcaption></figure><h4>Insights</h4><p>Upon gathering our research, we felt like we needed to narrow down our insights before we began to ideate.</p><p>From our user interviews and affinity mapping, we learned that coronavirus concerns were at the forefront of people’s thoughts regarding attending events — but there was some concerns amongst the group that these insights were driven by leading questions which asked specifically about the impact of coronavirus. For the avoidance of doubt (as well as stifling the scope of the project), we chose to disregard this insight in favour of more relevant trends such as incentives and discoverability.</p><p>From our competitive research, we really liked the virtual currency and ‘gamification’ approach that Jukely had taken in its business model (even if we were less impressed with the app itself). Spotify has a rich and detailed algorithm for making pinpoint-accurate recommendations to its users for local events, however, it doesn’t embellish these recommendations with any kind of incentives for its users (as per the brief of this project). And lastly, IKON had lots of great ideas for providing value for money to its subscribers, such as food and beverage discounts, friends and family benefits, and multiple subscription plans catering to different consumer needs.</p><h3>Design</h3><h4>Ideation</h4><p>Ideation took the form of contributions via a Crazy 8s design sprint — the process of producing 8 ideas or sketches in an 8-minute time limit. From there we voted on our favourite sketches, and through repeating the same process we were able to decide on a <strong>‘How Might We’ Statement</strong> and <strong>Problem Statement</strong> to represent the specific issue that our DICE subscription service was going to solve.</p><p>The ideas that floated to the top typically involved emphasis on artist discoverability via the <strong>incentive of virtual currency</strong>. After much iteration, we agreed on the following subscription model:</p><ol><li>One subscription would grant the user access to one free event per month (chosen from a list of events by emergent artisits curated by a DICE editorial team).</li><li>Attending the event would lead to the user earning a number of virtual currency points corresponding to how ‘emergent’ the artist was.</li><li>These points could then be spent on an online store that would entitle the user to discounts on merchendise, food and drink, priority access, etc.</li></ol><p>We felt like this model served the requirement to promote artist discoverability, whilst also giving the user value for money through earned discounts and benefits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eVzAxN72l68YUi9GKuckXg.png" /><figcaption>Heat maps from our mid-fidelity user testing.</figcaption></figure><h4>Prototyping &amp; User Testing</h4><p>Our prototypes were made in <strong>Figma</strong>, and began at the low-fidelity stage, eventually culmintating in high-fidelity prototypes after receiving some user feedback via <strong>User Testing</strong>. Large efforts were made to closely align our service with DICE’s existing branding and design systems, which meant matching typography, colour schemes and imagery across all prototypes.</p><p>User Testing was conducted via <a href="https://app.maze.co/"><strong>Maze</strong></a>, and initially collected data from 10 different participants. The main focus was on the accessibility of the onboarding process, and the ease of selecting an event to attend.</p><p>Initial feedback was (predictably) less than desirable, as we prioritised making fewer design decisions early on in order to gauge feedback through usability testing which would in turn <strong>shape our design patterns</strong> going forward. Results showed that the average success rate was 22.2%, with a matching give-up rate. Polling users for feedback, the intuitiveness rating was 66%, and users spent (on average) 111 seconds attempting to complete the tests.</p><p>Iterating on test feedback, and implementing the changes in our high-fidelity prototypes, we ran our tests again and achieved <strong>considerably improved results</strong>. Our success rate was up by 66.7%, for a total of 88.9%. Our give-up rate was totally eliminated with 0% of users giving up. Likewise, intuitiveness was up to 100%, and lastly, the average time was cut down by 83.8%, with users spending (on average) 18 seconds to complete the task.</p><h3>Conclusion</h3><h4>The Final Product</h4><p>Based on the results of our final round of user testing, and (in general) of the progress made during our 2-week sprint, we were all pleased with our final prototypes, and believed that they succeeded in meeting the criteria of the brief whilst seamlessly integrating a new service within DICE’s existing offering. With this in mind, certain ideas would require further development and ideation, but I believe what we were able to produce meets the requirements for a minimum viable product.</p><p>In terms of our <strong>next steps</strong>, I believe we would like to implement some outstanding feedback from our usability tests (such as some UI improvements for visibility), but also further develop the virtual currency idea. For example, a prototype implementation of the virtual store (inclusive of discounts and benefits) would help to hammer home the concepts at play within the subscription model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GLIxqN5XZzyxl7fiak1jog.png" /><figcaption>Our final prototype.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d442968cab6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Creating a ‘Small Shop Feel’ for e-Commerce]]></title>
            <link>https://medium.com/@ed.williams.design/case-study-creating-a-small-shop-feel-for-e-commerce-16adfae191b3?source=rss-f02c73e5ed74------2</link>
            <guid isPermaLink="false">https://medium.com/p/16adfae191b3</guid>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ecommerce-website-design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Ed Williams]]></dc:creator>
            <pubDate>Mon, 15 Nov 2021 08:42:38 GMT</pubDate>
            <atom:updated>2022-02-06T15:09:48.099Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*grlH6PsvfOrZZTQAEJcznw.png" /></figure><h4>How could a local independent bookstore rely on the User Experience to grow their online client base?</h4><h4>The Brief</h4><p>This was a solo UX project that tasked me with designing an e-Commerce website for a small independent bookstore.</p><p>The fictional bookstore, named ‘Prose &amp; Poetry’, have been pitched as being Highgate’s neighbourhood bookstore since 2010. I identified their core values as being diverse, community-oriented, reasonably priced, and personable. This last core value would prove to be the focus of this particular project.</p><h4>Process</h4><p>For this project, I relied on the <a href="https://en.wikipedia.org/wiki/Double_Diamond_(design_process_model)"><strong>Double Diamond</strong></a> methodology to help me structure my research, findings, and design. This breaks down the project into 4 key stages of process:</p><ul><li><strong>Discover</strong>, where we undertake our user research.</li><li><strong>Define</strong>, where narrow down our findings in order to address a specific issue.</li><li><strong>Develop</strong>, where we spitfire ideas until we hit something we like.</li><li><strong>Deliver</strong>, where we finally present a solution using mid- to high-fidelity prototypes.</li></ul><p>A crucial stage for me was the focus point in between Define and Develop, where I finally narrowed down the scope of my project into something useful for the client.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0n-Bwnt2uxnKQvBY8CTabQ.png" /><figcaption>A diagram representation of the Double Diamond process model</figcaption></figure><h4>Competitive Analysis</h4><p>I focused my Competitive Analysis on three different businesses: two larger companies in <em>Waterstones</em> and <em>Blackwell’s</em>, and one smaller (more independent) store in <em>Daunt Books</em>. I performed the analysis using three different test:</p><ul><li><strong>Task Analysis</strong>, where we compare the number of steps it takes to complete a predetermined task.</li><li><strong>Feature Inventory</strong>, where we take a count of the number of features each website.</li><li><strong>Plus/Delta</strong>, which is a simple pros versus cons list created for each website.</li></ul><p>From the outset of conducting this research, I was unsurprised to find that <em>Waterstones</em> came out on top in every single category, and (in turn) <em>Daunt Books</em> came last.</p><p>For example, during my <strong>Task Analysis</strong>, I wasn’t even able to complete the task I’d set myself by using the <em>Daunt Books</em> website (<em>the task</em>: to purchase a classic science-fiction novel from all three websites).</p><p>Furthermore, <em>Waterstones</em> had by-far the most feature rich front page of any of the three sites, with <em>Blackwell’s</em> falling closely behind in second place during all three tests.</p><p>I summarised my findings by concluding that I found <em>Daunt Books</em> to have the most pleasant of the three websites (in terms of its minimalist and quaint visual design), but equally the least usable. <em>Waterstones</em>, by contrast, sometimes felt a little overloaded with its content, however it was by far the website best equipped to handle e-Commerce. If I could achieve the best of both worlds for designing the new <em>Prose &amp; Poetry </em>website, then I feel like the project may be successful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H3sIThbJgy7cxVOVeWCIwA.png" /><figcaption><strong>Feature Inventory</strong>: Number of features; <strong>Task Analysis</strong>: Number of steps to complete task; <strong>Plus/Delta</strong>: Net total of positives versus negatives</figcaption></figure><h4>User Research</h4><p>I began my User Research by jotting down all of my assumptions. For me, this is a really important and natural starting point when attempting to derive questions for going into my <strong>Discussion Guide</strong> (which I use to conduct User Interviews). Without them, I get quite overwhelmed with trying to pull questions out of thin air.</p><p>Once my Discussion Guide was complete, I began my User Interviews. I interviewed four people in total, and asked a broad range of questions covering preferences for both buying and reading books, as well as a few qualifying questions regarding their online shopping habits. In assembling my Affinity Map to collate the data collected, I identified eight different core trends:</p><ul><li><strong>Buying Habits</strong>: This included data on preferences such as online versus in-store, hardback versus paperback, first-hand versus second-hand, etc. This was the largest of the 8 categories.</li><li><strong>Wishlists</strong>: This concerned how people like to track the books they want to buy in the near future. Most people track their wishlists offline using native ‘notes’ apps on their phone. One user used an Amazon Wishlist to track their books.</li><li><strong>Navigation</strong>: This was regarding how people typically navigate a bookstore, whether that’s physically in-store, or via online e-Commerce sites.</li><li><strong>Community</strong>: This revolved around data for how people like to talk and communicate about books, as well as how they like to discover new ones.</li><li><strong>Places</strong>: Geographically, where do people most like to read? All four interviewees said their bedroom, with a few mentioning in parks (weather permitting).</li><li><strong>Delivery</strong>: What are people’s expectations with regards to free versus paid, or one-day versus standard delivery?</li><li><strong>Genre Preferences</strong>: What genre of books do people most like to read? Three out of four people remarked that they prefer Non-Fiction to Fiction.</li><li><strong>Book Covers</strong>: Do people really judge a book by its cover? Apparently at least two out of four people do.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZPVHvvHJi4AYchBpIHJUew.png" /></figure><h4>The Definition Phase</h4><p>I believe my biggest challenge during this project was refining my user research and defining a concise <strong>problem</strong>. I had lots of data to draw on, but in terms of picking the ‘right’ data to inform my design process, I felt like I was making arbitrary and uninformed decisions.</p><p>I knew something didn’t feel right or natural, but what I didn’t realise at the time was that I wasn’t cross-referencing my data with the client’s issue.</p><p>This resulted in me creating a <strong>Persona</strong> which didn’t necessarily reflect the kind of clientele that ‘Prose &amp; Poetry’ are typically catering to. That is to say, that I found it hard to extract the customer issue and consolidate it with the client issue.</p><p>This leads me onto the creation of my Persona. I created a Highgate-residing Software Engineer named Anthony in an effort to amalgamate my four interviewees. My first draft of the Persona had Anthony as a typical Amazon user — in other words, the kind of person who would never shop at <em>Prose &amp; Poetry </em>in the first place. I needed to realise that a shop like <em>Prose &amp; Poetry</em> were not trying to steal Amazon’s marketshare, but instead retain and develop their own marketshare in an online space.</p><p>To help put myself into the shoes of the customer, I created a <strong>User Journey</strong>, and in doing so, I was finally able to define a <strong>Problem Statement</strong> which honoured the personability of <em>Prose &amp; Poetry</em>. From this point on, the thrust of my project had shifted, and I really began to focus on nailing down that ‘small shop’ feel in an e-Commerce setting.</p><blockquote>Our customers need an accessible online shopping experience that captures the feel of shopping locally, so that they can seamlessly transition from in-store shopping to online shopping because they do not like to support non-independents (such as Amazon and Waterstones).</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OOPzmoyWleITfsWeH0KuHg.png" /><figcaption>The steps I needed to take and review in order to finally reach my Problem Statement</figcaption></figure><h4>The Design Phase</h4><p>My design phase began by trying to map out the new website’s navigation. Using open and closed <strong>Card Sorting</strong>, I was able to crowd-source a consensus on what an intuitive site navigation looks like, and this formed the basis of my site map and user flow diagrams. These diagrams, in turn, informed my initial sketches.</p><p>I began my designs with three <strong>Sketches</strong> of three of the website’s key screens. These sketches, whilst rough and intended to be ephemeral in their purpose, have actually formed the basis of the final prototype.</p><p>I then moved on to designing the <strong>LoFi Wireframes</strong>. Knowing this stage can often be an enormous time sink, I tried quite consciously to reduce the scope of these wireframes.</p><p>Despite this, somewhat frustratingly, I completely forgot to prototype the entirety of the Checkout user flow (which was a mistake made earlier on in the process), so my naive intentions were punished by having to cram these in at the last minute.</p><p>Lastly, with the <strong>Interactive Prototype</strong> in place, I began to create <strong>Colour Schemes</strong> for the prototypes and change the <strong>Typography</strong> of the designs. I think this lifted the prototypes from being LoFi to somewhere in the MidFi range.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ddYj1mCWOyttyBguVSqwA.png" /></figure><h4>The Finished Prototype</h4><p>My finished prototype makes use of a navy, pink, and ochre colour scheme. I sort of regret the pink, although I should qualify that it used to be a more muted shade until it failed the <strong>Colour Contrast Accessibility Testing</strong> when used in conjunction with navy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9WTT3it08xppWxFHFCEfTw.png" /><figcaption>The Home Screen</figcaption></figure><p>The fonts I picked were the an extra bold Serif font called <em>Spectral</em> for the headers, and a Sans Serif font called <em>Poppins</em> for the body and subheaders. The choice to use a Serif font for the headers was largely due to their association with print, and by extension, books. Similar (more classic) Serif fonts (such as <em>Times New Roman</em>) are synonymous with print, but I wanted something a bit more contemporary — which I think <em>Spectral</em> captured well. <em>Poppins</em> was chosen primarily for its readability, but when written in all capitals I think it evokes a sleek and minimalist look which again improves the modernity of the website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SVSsbgt24AV8rhNQnCWnJA.png" /><figcaption>The Search Results</figcaption></figure><p>All in all, I think the final design captures the quaint, ‘coffee shop’, minimalism of a competitor such as <em>Daunt Books</em>, but hopefully considers some additional functionalities that belong to larger book competitors such as <em>Waterstones </em>and <em>Blackwell’s</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L5R7RHJiRMLqaIsRudYnWw.png" /><figcaption>The Product Listing</figcaption></figure><h4>Next Steps</h4><p>In terms of my next steps, one thing which I’ve hardly covered in this Case Study is <strong>User Testing</strong>. I conducted User Testing twice during this process:</p><ol><li>I conducted several User Tests based on my initial Sketches, which yielded useful and valuable feedback that I was able to implement in time for developing my LoFi Wireframes.</li><li>I also conducted a User Test on my Interactive LoFi Prototype. I appreciate that this isn’t enough, so I would like to conduct more. Furthermore, this test yielded extremely useful feedback, which I would really like to go back and iterate on in future designs.</li></ol><p>To summarise, more user testing would take top priority, amongst further iterations of the final desing. This would be in an effort to take the Mid-Fidelity Prototype to High-Fidelity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16adfae191b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Anti-Procrastination via the User Experience]]></title>
            <link>https://medium.com/@ed.williams.design/case-study-anti-procrastination-via-the-user-experience-483c71fb9e83?source=rss-f02c73e5ed74------2</link>
            <guid isPermaLink="false">https://medium.com/p/483c71fb9e83</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[procrastination]]></category>
            <category><![CDATA[habits]]></category>
            <category><![CDATA[sleep]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Ed Williams]]></dc:creator>
            <pubDate>Sun, 07 Nov 2021 22:37:23 GMT</pubDate>
            <atom:updated>2021-11-07T22:37:23.030Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZACep_7oTI92GBgHAb0JUg.jpeg" /></figure><h4>A solo UX Design project focusing on improving the lifestyle habits surrounding sleep and time management.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/347/1*DCmYRPM0rJn0nhpVsIwRFQ.png" /></figure><h3>The Brief</h3><p>I needed to create a mobile application to help counteract a phenomenon known as <a href="https://www.sleepfoundation.org/sleep-hygiene/revenge-bedtime-procrastination"><strong>Revenge Bedtime Procrastination</strong></a>. This is a form of sleep deprivation, which according to <em>sleepfoundation.org</em>, describes a “decision to sacrifice sleep for leisure time that is driven by a daily schedule lacking in free time”.</p><blockquote>“For people in high-stress jobs that take up the bulk of their day, revenge bedtime procrastination is a way to find a few hours of entertainment even though it results in insufficient sleep.”</blockquote><blockquote>— sleepfoundation.org</blockquote><h3>The Plan</h3><p>This project focused on 4 key phases:</p><ul><li><strong>Empathise</strong></li><li><strong>Define</strong></li><li><strong>Prototype</strong></li><li><strong>Test</strong></li></ul><h3>Empathise</h3><p>This stage is about understanding the user. It includes conducting interviews, drawing user flows, and creating personas based upon user research.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wQxOjvQ30_nLTMvKq9kJpA.png" /><figcaption>A Journey Map helps to chart the user’s emotions throughout each stage of the problem they face</figcaption></figure><h4>User Research</h4><p>Revenge Bedtime Procrastination was a familiar feeling, and I was able to empathise with the problem having attempted to correct a less-than ideal sleeping pattern of my own. I was able to form some assumptions about the experience, and from that point began creating a discussion guide for use in user interviews.</p><p>I conducted my first <strong>User Interview</strong> with the person who proposed the idea for the project. As I knew they had experienced the issue firsthand, they felt like a good candidate for confirming or rejecting a lot of my initial assumptions about the problem.</p><p>I made a <strong>Persona</strong> based on this person in order to try and identify some core traits which may inform my research. My key take-away from building the persona was understanding the crucial balance between familial commitments and hobbies/passions for many people.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7YEGUE_v9DzHOdOGpVwXUw.png" /><figcaption>My Persona helped me to understand the target audience of my application</figcaption></figure><p>Upon completing the interview, I created an <strong>Affinity Map</strong> in order to formalise the trends that emerged from the answers I collated. These were as follows:</p><ul><li><strong>Sleep Schedule</strong>: This trend included factors such as bedtime, number of hours of sleep reached, regularity of sleep, etc.</li><li><strong>Wellbeing</strong>: This trend included factors such as priorities regarding self-care and how people like to compartmentalise their chores and hobbies.</li><li><strong>Procrastination</strong>: This trend included all habits which pertain to how we procrastinate during the evening times.</li><li><strong>Flexible Scheduling</strong>: This trend included people’s requirements (or lack thereof) regarding the ability to keep their free time flexible and varied.</li><li><strong>Wind-Down Routine</strong>: This trend included the specific part of the evening routine that immediately precedes bedtime (i.e. brushing teeth, getting changed, reading a book, etc.).</li></ul><p>From there, I created a retrospective <strong>Journey Map</strong> of the user’s experience in order to identify their primary frustrations, and two iterated <strong>User Flow</strong> charts detailing potential solutions to the problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NRGlXESeQAkmlNTeCGBvEw.png" /><figcaption>The 5 trends as they appeared on my Affinity Map</figcaption></figure><h3>Define</h3><p>At this stage, I began to draw conclusions about the research I’d gathered and ideate potential solutions to the problem.</p><h4>The Problem</h4><p>Based on the user research I had conducted, I drafted the following <strong>Problem Statement</strong>:</p><blockquote>As someone who suffers from Revenge Bedtime Procrastination, I want to add more structure to my day so that I can feel more productive in the evening and therefore procrastinate less before bedtime.</blockquote><p>However, I identified a slight issue with this statement… I’d unknowingly included an assumed possible solution within the problem — that being adding more structure to one’s day in order to prevent procrastination later down the line. Therefore, a revision of the problem was required. This was my second attempt:</p><blockquote>As someone who suffers from Revenge Bedtime Procrastination, I want to procrastinate less before bedtime so that I can improve my sleeping habits and feel happier.</blockquote><p>This felt like a more natural statement, and would open up more possibilities for defining a solution.</p><h4>Ideation</h4><p>I began ideating for potential solutions with the use of <strong><em>How Might We</em> Prompts</strong>. I tried to establish one prompt per trend that emerged from the Affinity Mapping exercise. Whilst I feel like this helped me to strictly define relevant statements regarding the issue, I do wonder if it was needlessly limiting to conceive of the statements in this way. In the end, my <em>How Might We</em> statements were as follows:</p><ul><li>How might we ensure that a user feels compelled to stick to their sleep schedule? [<strong>Sleep Schedule</strong>]</li><li>How might we give the user reassurance that they have had a fulfilling evening? [<strong>Wellbeing</strong>]</li><li>How might we effectively track/record the wind-down routine? [<strong>Wind-Down Routine</strong>]</li><li>How might we discourage the user from procrastinating before sleep? [<strong>Procrastination</strong>]</li><li>How might we enforce a routine that’s flexible and not annoying? [<strong>Flexible Scheduling</strong>]</li></ul><p>It was this final statement which I took to use as the prompt for my <strong>Crazy 8</strong> exercise. In 8 minutes, I brainstormed 8 different potential solutions for the question of ‘<em>how might we enforce a routine that’s flexible and not annoying?</em>’. My ideas ranged from fairly standard practice for scheduling applications (i.e. alarms, notifications, etc.) to more original ideas which were perhaps more ineffective.</p><p>With that said, it was through this exercise that I had the idea to use ‘poppable’ floating bubbles to represent tasks which could be completed — I deemed this to be a potential alternative to the frequently used ‘todo list’ layout which is popularised by many scheduling applications.</p><p>Whilst I see nothing wrong with this layout, in terms of giving the user more freedom and flexibility to manage their free time, I did wonder if removing the ‘linearity’ of a todo list would aid in this pursuit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xIjukJePu2I3C9YRqIhhMw.jpeg" /><figcaption>Crazy 8 in action</figcaption></figure><h4>Sketches</h4><p>With some ideas in mind, I finally put pen to paper and <strong>sketched</strong> out some of the principle screens that would comprise my application. I found this exercise largely successful, however going forward I would find it more efficient to design each screen directly into <a href="https://www.figma.com/"><em>Figma</em></a>, which I was using as my prototyping software of choice for this project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lD1t7Low9SwcB3xNgxYriw.png" /><figcaption>My initial sketches imported into Figma</figcaption></figure><h3>Prototype</h3><p>The prototyping phase is where a functional interactive prototype of the application is built.</p><h4>Interactive Prototypes</h4><p>This was the longest stage of the project. I wanted to ensure that my interactive prototype had a relatively exhaustive user flow in time for being placed in the hands of the testers. Perhaps if I’d spent a longer time defining a suitable flow specifically for the purposes of testing, I might’ve been able to save myself some time by not prototyping aspects of the application which my test users (in practice) never even got to see.</p><p>All in all, I was pleased that I managed to prototype most of the application, even just for my own benefit of seeing the full flow of the app (and not necessarily for the benefit of my test users).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/813/1*QXq_2jsyacY0ug6Fkt5GVw.png" /><figcaption>A small fragment of my overall wireframe prototype depicting the ‘bubbles’ and activity timers</figcaption></figure><h3>Test</h3><p>The interactive prototype of the application is finally placed into the hands of potential users. The user is observed operating the prototype and notes and feedback on the solution are recorded.</p><h4>Test Guide</h4><p>For my <strong>Test Plan</strong>, I designed the following:</p><ul><li><strong>The Goal</strong>: <em>What is the purpose of this test?</em> I.e. “I’m trying to gain some usability feedback on my application to help structure people’s evening and consequently avoid pre-bedtime procrastination”.</li><li><strong>Metrics</strong>: <em>Expectations with which to measure the success or failure of the test.</em> I.e. “User should be able to plan their evening by making no more than one mistake”.</li><li><strong>Script</strong>: <em>A short scripted segment to begin the test, with which the purpose is to inform and reassure the tester of the honest nature of the test.</em></li><li><strong>Screening Questions</strong>: <em>A handful of questions to begin the test with, just to have some idea of the kind of person being tested.</em> I.e. “Do you find yourself procrastinating in the evening?”.</li><li><strong>Tasks</strong>: <em>The predefined user flows that are used to prompt the testers to experience with a short question or challenge.</em> I.e. “Could you please imagine that you are at the start of your evening, and you are trying to use the app to get to a point where you feel like you’re ready to go to sleep?”.</li><li><strong>Follow-On Questions</strong>: <em>Questions to cover anything experienced during the test itself.</em> I.e. “Was there anything you found particularly unintuitive about the application?”.</li></ul><p>I found it difficult to define actionable tasks for the Test Plan. This is because the app is more of a companion to an activity that the user performs every single day (i.e. going to sleep), rather than something that enables or empowers the user to do something they couldn’t have done without using the app.</p><p>Additionally, the test relies heavily on a hypothetical use case (again, going to sleep), which you can’t ask testers to do for you during testing. With this in mind, I found there to be a level of abstraction to the tests which made it hard to define ‘actionable’ tasks.</p><h4>User Feedback</h4><p>Overall feedback on the application was largely positive. I got good comments on the general flow and layout of the app, which was described as logical.</p><p>I got mixed feedback on the nature of the bubbles, for which the general concept itself received praise, however there was some confusion about how (in practice) they work. For example, does the size of the bubble correspond to the time required for that activity, or to the priority of that activity? Also, are they merely being presented as suggestions for the user to accept, or tasks which the user is being encouraged to time-block for? This presented an interesting paradox which arised when attempting to offer users both flexibility and time-boxed scheduling within the same app — I’ve tried to offer users both options, however this may not fully satisfy either audience who would prefer just having one or the other.</p><h3>Conclusions</h3><p>All in all, I’m really happy with the progress made on this project. The initial prototype is detailed enough to build a solid foundation for addressing the issue, but it’s low-fidelity enough to revisit for future iterations and implementing the solid constructive feedback I captured during my testing phase.</p><h4>Next Steps</h4><p>More than anything else, I’d like to revisit some of my initial user research to better incorporate it into future iterations of the application. During this project, I conducted three additional user interviews, which due to time constraints (arising from time spent prototyping) I wasn’t able to meaningfully collate and implement the data gathered into a revised version of the prototype.</p><p>I’d also like to rework the bubble feature based on the feedback I received during the user testing, and maybe consider adding an expandable list of tasks which works as an alternative to the bubbles. I’m imagining a use-case where the user can switch between the bubbles view and the list view on an ad-hoc basis depending on how much control or structure they require in that very moment — with the former offering more freedom and spontaneity; and the latter offering more structure and customisation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=483c71fb9e83" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>