<?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 Ryan Brakspear on Medium]]></title>
        <description><![CDATA[Stories by Ryan Brakspear on Medium]]></description>
        <link>https://medium.com/@ryanbrakspear?source=rss-393310d024d0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3r6hVBfdqtmHWcIEQjsJsA.png</url>
            <title>Stories by Ryan Brakspear on Medium</title>
            <link>https://medium.com/@ryanbrakspear?source=rss-393310d024d0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:03:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ryanbrakspear/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[Eppik]]></title>
            <link>https://ryanbrakspear.medium.com/eppik-d221c20322d5?source=rss-393310d024d0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d221c20322d5</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-process]]></category>
            <category><![CDATA[ux-thinking]]></category>
            <dc:creator><![CDATA[Ryan Brakspear]]></dc:creator>
            <pubDate>Tue, 16 Feb 2021 13:06:33 GMT</pubDate>
            <atom:updated>2021-03-09T13:47:40.390Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3EGajb5_nHcE1WronQaOxg.jpeg" /></figure><h4>Mobile app</h4><h3>Overview</h3><p>As a final project with General Assembly, we were put into a group of three and assigned to a real client with a real problem to solve. This was the pinnacle of the course and the main reason why I chose this UX bootcamp. To say I was excited is an understatement.</p><p>We were to work with <a href="https://www.eppik.com/">Eppik</a>, a photo album digitisation company. Their mission: “to safeguard your family stories for generations to come.”</p><p>I would be working with <a href="https://www.linkedin.com/in/dana-chahine/">Dana Chahine</a> a wonderfully passionate UX newcomer, and <a href="https://www.linkedin.com/in/julia-schwarz-design/">Julia Schwarz</a> who I sought a lot of advice from during the bootcamp for her previous experience as a visual designer. We made an epic team together!</p><h3>Goal</h3><p>Eppik came to us with the following issue: their user’s engagement with the web platform was falling off after the initial sign up. After having their photo albums digitised and seeing them on the platform, users stopped there. However the platform becomes more powerful for users if they add details to the photos.</p><p>Our overarching goal from Eppik was to <strong>increase long-term user engagement</strong> through the design of an iOS mobile app. They decided this could be done in two phases:</p><ol><li>Data entry</li><li>Data utilisation</li></ol><p>We had two weeks so we prioritised phase 1: how to get the users to add information to their photos. Eppik insisted that we used their branding and styles so this was a UX focussed project.</p><p>Below is a project canvas we drew up to visualise the scope of the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5WNzlnq4vAoCYSwt2nRyzA.jpeg" /></figure><h3>Design Process</h3><p>We used an iterative approach with four phases, discover, define, develop, and deliver known as the double diamond process. The idea being to diverge and gather information and ideas, then converge to distil this into actionable insights to take to the next phase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fsr-2pt55YG_gic-CqIkgQ.jpeg" /></figure><ol><li><strong>Discover</strong> — Competitor research, Survey, User interview, Usability testing existing site</li><li><strong>Define </strong>— Affinity map,User Persona, Experience map, Problem statement, How might we’s</li><li><strong>Develop</strong>— Design studio, Feature prioritisation, Hook model, Sitemap and card sort</li><li><strong>Deliver</strong>— Wireframes and usability testing, Prototype</li></ol><h3>Discover</h3><h4>Competitor research</h4><p>We took a look at some direct and indirect competitors to see what features they offered. We have some unusual competitors here, like WhatsApp, but we know it is a popular platform for sharing and engaging with photos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tHOynU8dPlsUXKOzYh_CSw.jpeg" /></figure><p>There were some clear standout features that we decided were important like notifications, comments, tagging, reactions, and the ability to share, and forward content with social networks.</p><p>I wanted to get to the bottom of how popular products drove their users to engage, so I did some further analysis on the high engagement competitors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MxxxVQcOPLajkmiG4SbZgA.jpeg" /></figure><p>I wanted to understand some of the biggest and most engaged with products to see how they keep users coming back and I found a few common threads.</p><ul><li>They are all very <strong>easy to use</strong>, accessibility being a key to their success</li><li>They all have very strong <strong>mobile apps</strong> for use on the go</li><li>They all promote <strong>identification</strong> so that users know who they are engaging with, which allows for a network effect.</li><li>And lastly, they all make use of <strong>push notifications</strong> to bring users back onto their platform.</li></ul><h4>User survey</h4><p>We sent a survey to our network as well as Eppik’s to identify the ideal users to interview further. We had 115 responses which resulted in a rich interview pool as well as some helpful information.</p><p>In the graphs below you can see some of the key insights we gathered before the interviews.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X-7CllFwgdfKbeGZ-lG8Xw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JcpDLIBPi8ZfPCGSMfjANA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a8LjkltSB3aeqnRVGAhACw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d-xYn5HZKCdOY3bdUvHkDw.jpeg" /></figure><p>Main motivations by far, is to keep and re-live memories. The top responses all centred on this idea of participating in each other’s lives.</p><h4>User interview</h4><p>We then interviewed 4 Eppik users and 5 non-eppik users about their experience with photos, photo albums, what they did with them, and why. We then put the feedback on sticky notes and used a process called affinity mapping to expose patterns and trends in our research.</p><h4>Usability testing existing site</h4><p>With the 4 eppik users we did an initial usability test on the website to see if we could learn something to take to mobile and we affinity mapped that feedback as well.</p><p>We learnt that users loved how good the image quality is, and relished in reliving memories and discovering old photographs</p><p>We also learnt that we needed to address</p><ul><li>how sharing is done</li><li>how users interact with the platform</li><li>how users add information to their photos</li></ul><h3>Define</h3><h4>Affinity map</h4><p>Below is the master affinity map where we began grouping feedback and insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rvUtFdfbyLIo5oxp4WGhXA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4YUaO91Fark6EpS_Gbe8xQ.jpeg" /></figure><p>We further distilled the findings into a much more digestible data set that we could use which you can see here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*edsSOPO5wDZoV0dRHcMLbg.jpeg" /></figure><ul><li>We found that the motivators for keeping and sharing photos and albums is to: <strong>preserve memories, connect with others, and share </strong>those lovely feelings like comfort, joy, and love.</li><li>Users mostly <strong>share with their phones over WhatsApp</strong>, and people want either acknowledgement or reciprocation for sharing their photos.</li><li>Users mainly <strong>responded to notifications</strong>, but the memories feature, and just seeing the photo often brought them back into these memories.</li><li>Users particularly<strong> battled with finding their photos</strong> and then the fact that they were spread over not just a few apps but also across devices, and sometimes hidden in a box under the stairs</li></ul><h4>User persona</h4><p>A user persona is a useful tool to help designers develop products for the users that will actually be using them, with more empathy we can make better decisions to serve their needs and not what we think is best.</p><p>Meet Karen, the user we developed based on our research:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oaWKZQ5cmTQ2ek7F0cYFmA.jpeg" /></figure><h4>Experience map</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ltt7duGNbO-ITOyL3pcnuA.jpeg" /></figure><p>It’s clear from the emotional journey that Karen’s greatest frustration is around easily adding data to the digitised version of the physical photo. So, the problem that we need to solve for Karen is…</p><h4>Problem statement</h4><blockquote>Karen needs a way to easily add structure and information to her photos so she can search, access and share them with her friends and family.</blockquote><h4>How might we</h4><p>To help spark ideas, we created what is called “how might we” statements, which is a UX tool to help designers frame the question in different ways to expose more possible solutions. The different How might we’s we decided on were:</p><ol><li>How might we <strong>prompt Karen to add information to her photos?</strong></li><li>How might we <strong>add structure to Karen’s photo’s using AI?</strong></li><li>How might we <strong>make organising photos more fun for Karen?</strong></li></ol><h3>Develop</h3><h4>Design studio</h4><p>With each of those “how might we” statements, we scheduled a design studio with the founders of Eppik. A design studio is a diverging framework that takes the How might we’s and attempts to come up with as many solutions as possible.</p><p>The five of us set about sketching on paper and came up with lots of ideas. We then voted on those ideas to narrow them down into a list of features for consideration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E1TeFoN6I94-Auqj6sbd_g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n-wZ_n4iRF-WwMXh4BjdBA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZeqkBVlQqOjSClZTExJnhw.jpeg" /></figure><h4>Feature prioritisation</h4><p>We narrowed down our list of features even further to identify those that <strong>must</strong> be included in the first iteration of the app. The “must have” features selected here were identified as being quick wins that would be essential to getting the basics right for creating an engaging experience to keep users coming back again and again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AZ7od6RMoDP45rRfx4C0ig.jpeg" /></figure><h4>Hook model</h4><p>To really understand how best to do that, we analysed these features through the lens of a “Hook model” which at its core is about creating user habits through four stages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YZJcsHaQXL5XeNCXvfnzDA.jpeg" /></figure><p>Firstly, we are looking to trigger users with notifications from the app as well as through the network effect.</p><p>The simplest actions a user can do to get a reward would be to add comments, share photos, and react to the shared content.</p><p>The rewards in its base level come from the reactions and discussion around photographs and albums.</p><p>And we are compelling users to invest and come back again by making it as easy as possible for them to input their information and tell their stories in the app.</p><h4>Sitemap and Card sorting</h4><p>The sitemap is the structure of the website and determines how a user flows through their journey. A common feedback in our usability testing was that navigation on the Eppik website was difficult and we thought we could simplify it for the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a4mp_JW2wGXpnprBeUT7yA.jpeg" /></figure><p>To help re-think navigation, we used a UX tool called card sorting to understand how users might expect information to be organised. Users are given a list of unsorted items and asked to group them where they expect to find them under what titles.</p><p>We tested this with 7 users, giving them the base level information to organise into their own categories, and then analysed the results for similarities and differences.</p><p>We used Trello for the remote tool as you can see below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b8hofRBqk8CRgN65KwXdqQ.jpeg" /></figure><p>By analysing the results, we have come up with the following app map. The black cards will be the menu icons in the navigation bar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*89nFDpKWZOJLMfNXNlAXxw.png" /></figure><h4>Wireframes and Usability testing</h4><p>With the structure, features, and style guide in place we used figma, to collaborate and design the wireframes starting in low detail (low fidelity) and working up to high fidelity. At each level of detail we tested our wireflow on users to ensure the product was easy to use, intuitive, and that the uploading of information felt easy.</p><p>The following are the wireframes as they developed with the feedback and iterations we developed from the tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z8NkLRch40LavtnS6dW0lg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Av46S4D3oIh6rfA-3qMDiw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T5J1Go-PnGadtLYYZOA4gg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w_96LitZUZXlbYfxDehPpQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yOotdl9Rq3ujh8ZLWIW1Zw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ht6Dgb6WP5K0ZPzxilaUvw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CTO1IW9d-S0nenp6CEvpPA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s0xJzedOjEQ-K6WZgWi6EA.jpeg" /></figure><h3>Deliver</h3><p>As I had taken the lead with the client throughout the project, I kicked off a very successful client presentation over Zoom after which we handed over the Figma design files, and the Zeplin file for development. Eppik is currently seeking investment to take the mobile platform live.</p><h4>Prototype</h4><p>You can find a version of our prototype <a href="https://www.figma.com/proto/SnT7jGES3BhVy451iVcpuT/Designs?node-id=194%3A2997&amp;viewport=305%2C432%2C0.5&amp;scaling=min-zoom">here</a> which I would welcome any feedback on.</p><p>Or there is a very quick run through on Youtube.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F5jQwrX_52nY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D5jQwrX_52nY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F5jQwrX_52nY%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/40bcbec04bf5743bce78329bcbd674aa/href">https://medium.com/media/40bcbec04bf5743bce78329bcbd674aa/href</a></iframe><h3>Learnings and What’s next</h3><h4>Learnings</h4><p>During the initial design we discovered that the three of us broadly disagreed on how we should structure the app and although we had not accounted for a card sort in our project canvas we decided that it would be the best way to discover how best to layout the product.</p><p>We found that adding an extra layer of certainty not only saved us time but also fortified our design process to deliver the best product for the users.</p><p>In this project we had nobody take the lead on sketching and prototyping so we collaborated on each wireframe via Zoom in the beginning which slowed our process and did not allow for cohesive design. By giving ownership of screens to each team member we sped the process up and still delivered screens that felt consistent as we had a set design system to follow.</p><h4>What’s next</h4><p>Eppik is seeking funding to develop their product further and has asked us to stay in touch. They also have very big plans for gamifying their product further which would be exciting to be a part of.</p><p>Thank’s for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d221c20322d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ocado]]></title>
            <link>https://ryanbrakspear.medium.com/ocado-9b4410a600a8?source=rss-393310d024d0------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b4410a600a8</guid>
            <category><![CDATA[ux-thinking]]></category>
            <category><![CDATA[ux-design-process]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-writing]]></category>
            <dc:creator><![CDATA[Ryan Brakspear]]></dc:creator>
            <pubDate>Tue, 16 Feb 2021 11:51:01 GMT</pubDate>
            <atom:updated>2021-03-09T14:02:14.452Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pqQ1ofYEiFh81z2j21fLbg.png" /><figcaption>Ocado hobby kit header image</figcaption></figure><h4>Hobby kit mobile app</h4><h3>Overview</h3><p>For the first <strong><em>team</em></strong> design project we were tasked with designing a native application to add a new product to our “client’s” existing offering. The client for this concept product was <a href="https://www.ocado.com/">Ocado</a>, a British online supermarket delivering groceries and home essentials to their customers. In our brief, Ocado wanted to respond to a growing need (due to the Covid 19 lockdown) for home baking with “hobby packs”.</p><p>My team was made up of fellow General Assembly students that were chosen at random. We had two weeks to design a solution for our “client” over Zoom and other remote working tools.</p><p>Meet the team:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N6qyd-Wc-nzEichB-9FtxQ.jpeg" /><figcaption>Team from left to right: Fina Khalil, Faisal Rasouli, Izel Osman, Ryan Brakspear</figcaption></figure><p>I took the lead on user research and project management for the team.</p><h4>Goal</h4><p>Our goal was to design and prototype a feature as part of Ocado’s native mobile app that brings a new product offering to their customers. In the two-week sprint we needed to:</p><ul><li>Establish customer needs and goals</li><li>Determine the feasibility of the new product</li><li>Add a feature to Ocado’s app that meets the customers needs</li><li>Use the Ocado design system to stay on brand for a seamless integration</li></ul><h4>Assumptions</h4><p>To keep the project realistic, we made a few assumptions that we felt would influence our design process and make the project realistic.</p><ul><li>We would not be changing the sitemap/architecture of the app</li><li>We would not change the UI, or brand</li><li>We would use the same layout where possible</li></ul><h3>Design Process</h3><p>One of the reasons I love UX is that designs are led by data and there is a structure and process to follow to ensure nothing is missed. Below is a diagram I drew (of a common process in UX) to show the steps we followed in this design sprint. It illustrates the diverging of information gathering and idea generation, and the converging where the information and ideas are distilled into actionable insights and prototypes. This process is iterative and we often revisited phases when needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KlPo1wV9DNpSR473WmUFYg.png" /><figcaption>Double Diamond Process</figcaption></figure><ol><li><strong>Discover — </strong>Client brief, User survey, User research, Competitor research</li><li><strong>Define — </strong>Affinity map, Key insights, Persona, Empathy map, Experience map, Problem statement, How Might We</li><li><strong>Develop — </strong>Design studio, User flow, Sketches, Wireframes, Usability testing</li><li><strong>Deliver —</strong> Final screens and Prototype</li></ol><h3>Discover</h3><p>In the discover phase, we are gathering as much relevant information as possible. We started by looking into the client and their expectations, the competitors, and lastly the users (customers).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tjA-TqcLxVTd6KLkpuKp1w.jpeg" /><figcaption>Covid lockdown and more time is leading to interest in new hobbies</figcaption></figure><h4>Client brief</h4><p>To achieve the best product, Ocado gave us some constraints to work with:</p><ul><li>Customers should be able to <strong>choose from a range</strong> of hobby packs. The</li><li>Customers should be <strong>able to customise</strong> a pack based on items they may already have</li><li>Customers should be able to <strong>access guidance</strong> for how to use the items in the hobby pack</li></ul><h4>Competitor research</h4><p>We divided the competitor research between us, each taking a company we thought met similar goals for customers looking for hobby packs. Below is a section of the key findings where we explored the way they handled aspects like reviews, descriptions, selecting products, and their baskets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ZQ5UV-dSEao8zXT1ahJ9w.jpeg" /><figcaption>Competitor’s features comparison</figcaption></figure><p>There were features from each of these that we thought could work in our designs and some served as a proof of concept. For example Tasty (a very successful recipe app) led us in the layout of the wireframes designed for the recipe page.</p><h4>User research</h4><p>User research is the key to a great product so it was important that we found the right users to interview. I took the lead on the user research as it is an area I am comfortable with. We designed a questionnaire to send out to our network to help us narrow down the users we should speak to. In a few hours we had 61 responses of which we identified 11 users to speak to with a fairly even split between men and women mostly between the ages of 25–34 which we identified as the primary target market for online shopping.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gGizZmkLw4eUgSG8nTyiXA.jpeg" /><figcaption>Survey response demographics</figcaption></figure><p>While the responses were coming in, I wrote a few guideline questions you can see below to ask the users from which we could pursue further insights from.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ZfwBf8RqmI5bAbZCYuKlw.jpeg" /><figcaption>Interview questionnaire</figcaption></figure><p>Once we had conducted the interviews, we wrote down the answers onto post-it notes and put them up on a big board all together. An example of some of the answers we received are below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oY3vZHdAlce9u_9Hdlzq2w.jpeg" /><figcaption>Example of interview post-it notes</figcaption></figure><h3>Define</h3><p>At this stage in the sprint we have diverged and gathered many insights we can move forward with. The define stage now takes this data and narrows it down to create a clearer picture of who we are designing for and what goals and objectives we need to meet for the user.</p><h4>Affinity map</h4><p>An affinity map is a UX workshop that takes all of the above mentioned data and attempts to find patterns. We take all of the post-it notes and start putting them with similar notes.</p><p>This is to expose popular trends in the data so that we can see what users are looking for, what they want to avoid; their likes and dislikes, needs and wants, and much more. Following is a top level view of these patterns, on the right you can see the types of insights we gathered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*99J7ncAnViAu20yvMxW7HA.jpeg" /><figcaption>Affinity map of interview data</figcaption></figure><h4>Key insights</h4><p>Firstly, we took the data from the affinity map and drew out some key insights. They were:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a6STDTGfyIBs6m6facd4fg.jpeg" /><figcaption>Key insights from the interview and survey</figcaption></figure><h4>Persona</h4><p>As I was the lead on the user research, I took the information from the user surveys and the interviews and created a user persona.</p><p>This process in UX is so that designers can get a clear picture of who they are designing for and design for them rather than themselves. Things that need to be outlined are the user’s biography, behaviours, needs and goals, and pain points.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nPrfpqV8o71em5couiPd2A.jpeg" /><figcaption>User persona: Alexa</figcaption></figure><h4>Empathy map</h4><p>An empathy map is a visual tool that allows designers a deeper understanding of the behaviour and attitude of users. We try get to the point we can empathise with our end users and this tool helps us do this. Faisal took our persona and drew up the following for us:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*emzgzVNYI4TfdHZSNwQRZA.jpeg" /><figcaption>Empathy map: Alexa</figcaption></figure><h4>Experience map</h4><p>Together we developed an experience map which shows Alexa’s experience whilst trying to achieve her goal. It is by mapping her actions, and thoughts, to her emotions that we can identify her pain point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-OjRUSbUvrF4u_D4zEG27Q.jpeg" /><figcaption>Experience map: making kombucha</figcaption></figure><p>You can see in the above graphic that Alexa is unhappiest when she is looking for instructions, and then trying to buy all of the ingredients to make her kombucha.</p><h4>Problem statement</h4><p>Now we know more about Alexa and we can see where she is struggling we identified a specific problem to solve for her which we recorded in a problem statement:</p><blockquote>Alexa needs a<strong> new hobby </strong>to relax outside of work which is<strong> </strong>simple to learn<strong>, reasonably priced and not time consuming </strong>because she has a <strong>demanding lifestyle.</strong></blockquote><h4>How Might We</h4><p>A “how might we” helps us to frame Alexa’s problems in questions that opens up brainstorming and ideation sessions. We wrote a few but decided on:</p><blockquote><strong>…help Alexa find a new hobby.</strong></blockquote><p>We took this statement and carried out a design studio.</p><h3>Develop</h3><h4>Design studio</h4><p>A design studio is a type of UX workshop that allows for divergent and convergent thinking. Each member takes the How might we statement and thinks of as many possible solutions. It is often helpful to think of big hairy ideas, ones that go outside the box. We limited our time to 6 minutes and then wrote them down like you can see below. We then discussed with the group and used a dot voting process to determine the ideas we wanted to push through with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uc6aI2_z7Elrcu3oxdCMjQ.jpeg" /><figcaption>Design studio</figcaption></figure><p>The idea is to sketch your ideas down, but in the limited time, I decided to write mine down and then draw them out if I had time but I didn’t get there before we had to sell our ideas to the team.</p><p>The outcome of the design studio were the following ideas:</p><ul><li>A mystery subscription box service</li><li>Skills builder</li><li>Special filter function</li></ul><h4>User flow</h4><p>Once we had an idea of the features we needed to incorporate and the steps for Alexa to go through, we were able to draw the following flow Alexa would take in order to achieve her goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pwXWn-XCwl5is1HuoBRoJQ.jpeg" /><figcaption>User flow</figcaption></figure><h4>Sketches</h4><p>Each of us drew some wireframes of how we thought we could layout the pages and we then discussed the best elements from each. Here are a few of the sketches we did:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mGki8CmYuYaEr8O3ERrbrQ.jpeg" /><figcaption>Initial sketches</figcaption></figure><h4>Wireframes</h4><p>We started with drawings (low fidelity) and moved up in detail until they resembled a real app (high fidelity). Fina is a visual designer by trade, so she ran lead on the visual design, creating the UI elements we were to use. We each took ownership of certain screens and designed the wireframes ourselves. Below is a look at the screens I personally designed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5JoIBFIC_jsw-UX-Y-Vv1A.png" /><figcaption>My low fidelity wireframes</figcaption></figure><h4>Usability testing</h4><p>At each level of detail we carried out usability testing to see how users interacted with the wireframes and made tweaks to features, layout, positioning, sizing, names, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Iigon2kA9Ov5RzgVDA2wtw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gVtz87n44h_hg19zY-AxLw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8doF8LFAIMYmnxv6qDc6qg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3dQKLsaAyWq-HUcEmaM2MQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zv4dYczIzGcs4J2s_tA9ZQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0O-1XzHnyVdHeKgAnOfpPQ.jpeg" /></figure><p>Once we were happy that we had addressed the issues raised in the usability tests, we took our designs to the high fidelity prototypes to follow.</p><h3>Deliver</h3><p>The outcome of the sprint was this prototype you can find by following this link: <a href="https://invis.io/QGZ14P1H7DK#/434081582_Landing_Screen">Ocado Hobby Kit</a>. Please feel free to check it out and let me know what you think.</p><p>Here’s a high level view of the final UI screens if you don’t have time to play around with the prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8zeBazpBQFbCpynq8R9pVg.png" /><figcaption>Final UI screens</figcaption></figure><h4>Project management</h4><p>As I mentioned I was the project manager for this project. The following is a view of how I managed the sprint by sectioning it out in the beginning in Miro and adding our work as we went. This way we could see a visual representation of the progress we made as well as making it very easy to find and present each phase of the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zahHYhjav1qGJtPeUvhHOA.jpeg" /><figcaption>Project overview</figcaption></figure><h3>Learnings and What’s next</h3><p>In the design studio we had ideas that were a little more complex than the instructors had imagined. We went back and forth internally and with the course instructors who recommended we pull back on a few of the ideas and “keep it simple” which we did in the end.</p><p>I have a feeling they were worried about time but we finished our project two days early. I think we could have made an exciting product whereas it became a simple e-commerce app with elements of our ideas as smaller features. It is a good learning experience as I imagine future clients will often make decisions like this.</p><p><strong>What’s next</strong></p><p>As a concept project I won’t be taking this any further; however, if i were to the next steps would be to:</p><ul><li>More design iterations</li><li>More Usability Tests (on hi-fi prototype)</li><li>Incorporate “recipe preview” into the product page / earlier pages</li><li>Design + prototype “Surprise Me” Feature</li><li>Develop achievements feature further</li></ul><p>Thank you for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b4410a600a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Music Therapy Charity]]></title>
            <link>https://ryanbrakspear.medium.com/music-therapy-charity-7234fc2cc2b8?source=rss-393310d024d0------2</link>
            <guid isPermaLink="false">https://medium.com/p/7234fc2cc2b8</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[responsive-design]]></category>
            <dc:creator><![CDATA[Ryan Brakspear]]></dc:creator>
            <pubDate>Tue, 16 Feb 2021 11:40:12 GMT</pubDate>
            <atom:updated>2021-02-16T11:40:12.812Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yG8ZvB2ePsnNPapkodRT3Q.png" /></figure><h4>Responsive Website</h4><h3>Overview</h3><p>This project for the General Assembly UXDI course was only my second foray into the world of visual design, something I find challenging but so exciting! Visual design is the farthest from my previous experience so I felt like I was out of my depth. Despite this trepidation I couldn’t wait to tackle it.</p><p>The project was to rebrand and redesign a website for a Charity we could choose from a list. I connected with <a href="https://www.musictherapy.org.uk/">The Music Therapy Charity</a> as I love music and felt they have an amazing mission.</p><h4>Goal</h4><p>The goals I set myself would mimic what I imagined a charity would want to achieve by coming to me, those being:</p><ul><li>Establish a good brand image</li><li>Reach the people they aid</li><li>Showcase their work and success stories</li><li>Encourage donations and support</li><li>Build a community of likeminded people</li></ul><p>The deliverables are two pages of my choice (I chose the ones I considered paramount to the goals I have; the <strong>Home and Donation pages</strong>). These should be designed over three viewports; <strong>desktop, tablet, and mobile</strong>.</p><h3>Design Process</h3><p>In the short 5 day sprint I used my previous learnings to shape my design process which looked like the following:</p><ol><li><strong>Empathise</strong> — Competitor research, Client review</li><li><strong>Define </strong>—User personas, Branding, Tone of voice,</li><li><strong>Ideate </strong>— Design inspiration, Logo redesign, Feature prioritisation, Sketches</li><li><strong>Build </strong>— Wireframes, Style guide, Prototype</li><li><strong>Test </strong>— Feedback</li></ol><h3>Empathise</h3><h4>Competitor research</h4><p>I looked at a few charities to gain an insight into what they did really well and where I could learn from them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Bx1z7f7qBBE5oEuLcRWhA.png" /></figure><p>Here are a few of my key takeaways from these websites:</p><ul><li>Large and emotive images used throughout</li><li>Donate button is prominent</li><li>Social buttons at the top</li><li>Simple Nav bar</li><li>Search option always given to users</li><li>Very colourful pages</li><li>Fullscreen hero</li></ul><h4>Client review</h4><p>It was also important for me to look at the website itself and see where I would be able to make changes to meet the goals I had set.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2US6nbf87ju5zrqvRfTccA.png" /></figure><h3>Define</h3><h4>User personas</h4><p>When designing it is important to know who you are designing for and what their needs and goals may be. Often there are many users that need to be taken into account and this project is a good example. Without diving in too deep with the short timeframe I listed the possible users that I would need to accommodate:</p><ul><li>Researchers looking for funding</li><li>Sponsors and donors</li><li>Potential patients looking for information</li></ul><h4>Branding</h4><p>This project was a laundry list of firsts for me and rebranding is one of them. Currently the brand feels plain, flat, and unexciting. I wanted to change this, I believe the work they do is exciting, fun, and interesting while obviously being serious work. I needed to communicate this to the users.</p><p>I started by writing down some brand keywords that I wanted the brand to resonate:</p><ul><li><strong>Connect</strong></li><li><strong>Educate</strong></li><li><strong>Support</strong></li><li><strong>Reach</strong></li><li><strong>Celebrate</strong></li><li><strong>Dynamic</strong></li></ul><p>These keywords shaped how I made design decisions in the rest of the project.</p><h4>Tone of voice</h4><p>I now needed to describe how the brand speaks to the users. The client is heavily involved in research so I wanted the brand to be professional/academic in communication, goal orientated, as well as supportive.</p><blockquote><strong>The Music Therapy Charity supports high quality research into music therapy and music therapy services. We do this by connecting with our community, supporting researchers and practitioners with funding, and reaching new audiences to educate on the benefits of music therapy.</strong></blockquote><h3>Ideate</h3><p>This phase of my design thinking is to diverge and to make sure I have enough options and pathways to explore. The focus of this project was on the visual design of the website instead of the user flow and architecture so this phase of my process is to concentrate on the look and feel.</p><h4>Design inspiration</h4><p>I started by looking at websites like Dribbble using my keywords to find design inspiration, mapping them onto an artboard, and then pulling out ideas to build upon. Below is a look at one of my moodboards:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UazuBeDiQcoU58lXYFL62Q.png" /></figure><p>The aspects I wanted to bring into my design were:</p><ul><li>Simple colour palette with;</li><li>Highly contrasted secondary colours for CTA’s</li><li>Use the original light blue as it feels calm and relaxed whilst still professional</li><li>Incorporate gradient to simulate movement/flow</li><li>Mix serif and sans serif typefaces</li><li>Rounded edges</li><li>Accessible colours, typeface, and font sizes</li></ul><h4>Logo redesign</h4><p>The logo was an area I really wanted to put a lot of energy into, something out of my wheelhouse that could push me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/0*1Y-B7o4Ll4uO_yr6.jpg" /></figure><p>The current logo feels out of place to me. It feels slightly more on the playful and young side and doesn’t capture the authority I feel the brand should display whilst still communicating that it is supportive.</p><p>I used my keywords to start drawing shapes and styles that I thought could then use to capture the brand visually.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gdTKauG88jdJ337sQAO3ww.png" /></figure><p>I sent my final drawing (highlighted in green above) to a graphic designer who made my final logo for me. I feel it incapsulates the support and care of the charity, the interconnectivity of the community, the medium of therapy as well as keeping it on the professional side of fun:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_UpCLr1-qe-qwo4fDdXo7g.png" /></figure><h4>Sketches</h4><p>I used my whiteboard to sketch out the layout I thought would incorporate the important features in a logical and intuitive format.</p><p>To ensure the best experience for the user I designed from the smallest screen initially in a mobile first approach. The tablet will be much the same as the desktop on the right with padding and sizing considerations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tz4Wu3jBWygwKea-pCozqw.png" /></figure><h3>Build</h3><h4>Wireframes</h4><p>Due to the limited time of the project I took my first sketches straight to wireframes in Sketch. I started adding elements from my moodboard like type, font size, colours, padding, buttons, and images. I spent hours and hours making small changes as I went.</p><p>Every few hours I uploaded my wireframes to Miro so that the course instructors could feedback on my designs. Below you can see a screenshot of the review board where the instructors left notes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g7lUMdDEbW1suiFVLuMxww.jpeg" /></figure><p>My process took many iterations to get to the designs you can see at each stage, driving home the complexity and scale of the visual design job.</p><h4>Style guide</h4><p>A design system is a set of guidelines, components, and design considerations that should be used to develop and build products with. Whilst designing the wireframes, the elements and styles changed many times until I was happy so I couldn’t set the system until the end. The following is the final design system for The Music Therapy Charity that I have made. This would lead the departments of design, marketing, development, etc. in a company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IDzrrLE319MWv3lEpbTZsA.png" /></figure><h4>Prototype</h4><p>The following links show the prototypes of the different viewports that I have designed. As this project only required two pages for the concept there is limited functionality of the prototypes.</p><p><a href="https://invis.io/UZ100MBCY97T#/443151035_Mobile_Home_Page">Mobile prototype</a></p><p><a href="https://invis.io/ZQ100METCPGD">Tablet prototype</a></p><p><a href="https://invis.io/WF100MFCZXYC">Desktop prototype</a></p><p>Below is a side-by-side view of the webpages so that you can see where I started and the end result. The key design change is the responsiveness as the smaller viewports displayed the desktop layout scaled down. Perhaps this was why they needed to incorporate a font size selection in the website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zZlfWCjNF_r4BtIMAI1nxA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rYRgBP-vwdzhz0tWIz2LLg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9dyXUobLlfmLDSIl2ASbmg.jpeg" /></figure><h3>Test</h3><h4>Feedback</h4><p>In this project there was no usability testing with users as time was limited. However I constantly reviewed the designs with fellow classmates, instructors, and a graphic designer ensuring an iterative approach to my design process.</p><h3>Learnings, Limitations, and What’s next</h3><h4>Learnings</h4><p>This project brought the issue of padding and hierarchy to the forefront for me as a lot of my feedback was around spacing. I feel like I am progressing nicely but have much to learn still. Spacers are now constant components in my design process to ensure consistent padding.</p><p>In the first project without users to interview it also highlighted how important that is with projects. User research adds several steps but I believe that in the long run it saves time and results in better products.</p><p>I found other ways to test my work by setting up a review board on Miro that students could upload their work to and give and get feedback at a more frequent pace than waiting for the instructor to get to you. The instructor team then used this model to complete the project.</p><p>Lastly, I learnt that visual design is FUN!</p><h4>Limitations</h4><p>Due to the structure of this module there was:</p><ul><li>Limited time for each phase and priority was given to visual design</li><li>No interviews/user testing</li><li>Finding the right images to convey tone was difficult</li></ul><h4>What’s next</h4><p>At this stage I will not be taking this design further however if I was, it would be:</p><ul><li>Design a footer</li><li>Develop more screens and features</li><li>Add more content</li><li>Prototyping and usability testing</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7234fc2cc2b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome Home Hardwares]]></title>
            <link>https://ryanbrakspear.medium.com/welcome-home-hardwares-4d0a5ac0d6fd?source=rss-393310d024d0------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d0a5ac0d6fd</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-process]]></category>
            <dc:creator><![CDATA[Ryan Brakspear]]></dc:creator>
            <pubDate>Tue, 16 Feb 2021 11:38:57 GMT</pubDate>
            <atom:updated>2021-03-09T13:54:05.885Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LNvAKNcdXfSnKiZLzPBErA.png" /></figure><h4>E-commerce website</h4><h3>Overview</h3><p>The second project for the General Assembly UX design immersive was to design an e-commerce platform. The first part of the project was done in a team of 4. The team would dissect the brief, write a research plan, and carry out all of the research together. From there each of us would complete the rest of the project individually.</p><h4>Goal</h4><p>Showcase Welcome Home Hardware’s products, while maintaining their brand image, through a new E-commerce website.</p><h3>Design Process</h3><ol><li><strong>Empathise</strong> — Client and brief, User Research, Market research, Feature Analysis, SWOT analysis, Card sorting</li><li><strong>Define </strong>— User Persona, User flow, Sitemap</li><li><strong>Ideate </strong>— Sketches</li><li><strong>Build </strong>— Wireframes, Prototype</li><li><strong>Test </strong>— Usability testing</li></ol><h3>Empathise</h3><h4><strong>Client</strong></h4><p>Our client was Welcome Home Homewares, a local homewares store in Stratford, London. They operate from a high street brick and mortar location, servicing local customers from the store however they have decided they could help the community more by adding an e-commerce website.Their values are:</p><ul><li>Quality over quantity</li><li>Customer service</li><li>Reasonable pricing</li><li>Keeping it local</li></ul><h4><strong>Brief</strong></h4><blockquote>“Through a new e-commerce website, we want to showcase our products, while maintaining our brand image.”</blockquote><p>The client made it clear that the following were their priority for the new website which gave us a good starting point:</p><ul><li>Have clear ways of locating specific products</li><li>Support a single page for each product which can be linked to directly</li><li>Have an efficient way of purchasing one or more products</li><li>Steer customers toward popular products</li><li>Establish the brand and its points of difference</li><li>Allow customers to contact the business</li></ul><h4><strong>Market research</strong></h4><p>We decided to look at Ikea, John Lewis, and West Elm as major competitors that customers might look to to purchase the same products as well as a store called Indish that is also a local homewares store servicing local customers. The methods used to research these competitors was a feature analysis and a SWOT analysis of their websites.</p><h4><strong>Feature analysis</strong></h4><p>Below are the features we identified on each website; we took this information to identify the features that the competitors thought the customers needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*tG4C8WxMg43ldOTWv7URrg.png" /></figure><p>The features we decided were most important to include for the client are:</p><ul><li>Global navigation with drop down navigation menus</li><li>Hero slider to showcase the store, and sales</li><li>Popular product recommendations</li><li>Breadcrumb navigation</li><li>Large image tiles</li><li>Multiple product images</li><li>Product details and descriptions</li><li>Product reviews</li><li>Similar products</li><li>Wishlist functionality</li><li>Cart amendability</li><li>Purchase confirmation</li></ul><h4><strong>SWOT Analysis</strong></h4><p>A Strengths, Weaknesses, Opportunities, and Threats analysis was also done to see what the competitors did well that we could emulate and what we could improve on for the client and their customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*t0LeqJZF482ecNsbHVvOdA.png" /></figure><p>Following this research we wanted to bring the following to the clients website:</p><ul><li>Maximise the white space</li><li>Multiple navigation options</li><li>Related and popular products</li><li>Contact options</li></ul><h4><strong>User Research</strong></h4><p>Our research plan started with us writing a few questions separated into the users experience, behaviour, and the features they liked or didn’t to gain further understanding into how users met their goals. 5 users were interviewed that were between the ages of 25 and 27, both male and female, and were from different countries and backgrounds.</p><p>The <strong>key insights</strong> we took from these tests are as follows:</p><ul><li><strong>Reviews</strong> are very important</li><li><strong>Wish Lists</strong> are important as users window shop and come back</li><li>Users like to <strong>shop by sales</strong></li><li><strong>Contact options</strong> are important</li><li>Customer service makes a big impact</li></ul><h4><strong>Card Sorting</strong></h4><p>While we were interviewing users we also carried out 7 open card sorts and 5 closed card sorts. Card sorting is an exercise to determine how users categorise products so that we know how to label and organise the website to make sure the users had an efficient experience while using the website.</p><p>The responses were recorded and we received a broad range of category names that we then needed to approximate to identify the trends that are pictured below. This is how the products would be structured and where users could find them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*4uiHa_6xBMcJWb_ZM755nA.png" /></figure><h3><strong>Define</strong></h3><h4><strong>User Persona</strong></h4><p>I then developed a proto-persona which is a user that I invented to give me an idea of how a typical user would use the website. His name is Tim and he is about to throw the best dinner party his friends have seen! But he needs a few things first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*2cpnpyyju7d7p3pEBWjpwg.png" /><figcaption>User Persona</figcaption></figure><h4><strong>User flow</strong></h4><p>Tim has a goal in mind and wants to move through the process quickly as he needs to get back to his own sketches. He wants to buy plates for a dinner party. Below I have drawn what would be his ideal path through the website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*pQp1iIDgUUAQS8S6xJs3LQ.png" /><figcaption>Happy path of the user (Tim) for completing his task</figcaption></figure><h4><strong>Sitemap</strong></h4><p>With the information we had from the competitor research, I designed the sitemap pictured below to present the store to customers in a simple but easily understood structure. I used the results from the card sorting exercise to ensure users can find the items they are looking for without having to search too hard.</p><p>On the left, you can see the categories that I finally used but this is not the structure I started with. It took two rounds of testing and calling back on the card sort to arrive with this structure.</p><figure><img alt="Sitemap to show hierarchy of web pages" src="https://cdn-images-1.medium.com/proxy/1*tA5K8e4j_f7Xvi7O8nInCg.png" /></figure><h3><strong>Ideate</strong></h3><h4><strong>Sketches</strong></h4><p>I then set about drawing the different pages Tim would need to complete his goal with the features that users would want. The post-it notes detail the features we identified in the competitive research that would result in the best experience for Tim while he bought his plates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pNERLUUPckb2ETdu6w2Odw.jpeg" /><figcaption>Initial whiteboard sketches</figcaption></figure><h3>Build</h3><h4><strong>Wireframes</strong></h4><p>I used Sketch to create the digital wireframes that would be used to prototype and test on users to identify any shortfalls or improvements that could be made.</p><blockquote>In the sketches you can see that I only had three categories on the mega nav, hoping to increase the white space. This created confusion in my usability testing and as a result the information architecture was completely overhauled into seven categories. More on this later.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HyBiaeCoBbBF8UCHcPfHIA.png" /></figure><h4>More research</h4><p>I had heard about the complexities of the checkout process and forms, so I wanted to make this the focus of my project. I went and did extensive research on the checkout process best practices and design rules and designed with the following considerations to ensure an efficient checkout and minimise cart abandonment:</p><ul><li>Show the users progression and state along the process</li><li>Validate user information as they progress</li><li>Use simple forms with one input field per line</li><li>Allow users to view and edit at any point</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jTOgSLVlECmnsrk4FBAsHg.png" /></figure><h3>Test</h3><h4><strong>Usability testing</strong></h4><p>I carried out virtual usability tests on the first iteration of the website on six users and noted down their feedback. I carried out a more detailed test on the majority of the users to ask for detailed information about each page they visited but made sure not to guide their process which helped me collect detailed and rich insights that I was able to use to make changes.</p><p>I then carried out a second test and asked each user to simply “Complete the goal of purchasing a set of plates” this test allowed me to see how users would naturally move through the process. This test suggested that users were confident in the flow and found each element where they expected it to be.</p><h4><strong>Home Page Feedback</strong></h4><ul><li>Mega nav simplified too much. Users went to the wrong category to find the plates</li><li>Users unclear of the difference of the connect with us options in the footer</li><li>Users looked for contact details to make sure someone is on the other end</li></ul><h4><strong>Sub-category Feedback</strong></h4><ul><li>Users wanted more categories to sort through different tableware</li><li>Users want filter and sort functionality on this page</li><li>Users want to see product rating on the tiles</li></ul><h4><strong>Product Page Feedback</strong></h4><ul><li>Feedback was missed when users added a product to their cart</li><li>Overall product rating missing</li><li>Users took too long to find the reviews</li><li>CTA “Add to cart” was too small</li></ul><h3>Final Screens and Prototype</h3><p>Click here to see the <a href="https://projects.invisionapp.com/share/8YYP06CUKBD#/screens">final prototype</a> made with InVision.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HOzcj41NxBUFIH309KTWWg.png" /></figure><h3>Learnings and What’s Next</h3><p>I learned a great deal about the checkout process and cart abandonment while working on this project and that researching design best practices is hugely beneficial in designing products, features, elements, and pages.</p><p>I learned how important information architecture and <strong>testing </strong>is to the user flow as what I had initially planned tested very poorly. By nesting categories into others to save space I made the user work harder to get where they wanted to go.</p><p>In the design process I did not test a low fidelity prototype on users which I discovered later in the process may have meant that I missed some key feedback from users about the placement of certain features. I am hopeful that my second test picked up any feedback I would have gathered from it but understand its importance for future projects.</p><p>The <strong>next steps</strong> for this project would be to add the functionality of:</p><ul><li>Account sign in</li><li>Customer rewards</li><li>Wish lists</li><li>Live chat</li></ul><p>More usability tests should be carried out before moving to a high fidelity prototype and repeating the usability tests. At this stage I will not be developing this further.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d0a5ac0d6fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recipe.Me]]></title>
            <link>https://ryanbrakspear.medium.com/recipe-me-7317049f655d?source=rss-393310d024d0------2</link>
            <guid isPermaLink="false">https://medium.com/p/7317049f655d</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ryan Brakspear]]></dc:creator>
            <pubDate>Tue, 16 Feb 2021 11:30:42 GMT</pubDate>
            <atom:updated>2021-03-09T13:50:27.546Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1EKLq3-XD6NOCBsYFLLm1w.png" /></figure><h4>Recipe finder app</h4><h3>Overview</h3><p>For the first project of the UX Design Immersive course with General Assembly, I was the sole contributor on a mobile app that needed to address a problem area that our class partner had chosen from a list.</p><h4>Goal</h4><p>Design and prototype an app to solve my partner’s chosen problem.</p><h3>Design Process</h3><p>I followed an iterative design process with 5 clear steps but as I worked I made sure to update my understanding of the problem and solutions I was designing, especially at the build phase.</p><ol><li><strong>Empathise</strong> — User interview, Experience Map</li><li><strong>Define </strong>— User Persona, User Storyboard, Problem statement</li><li><strong>Ideate </strong>— Brainstorming, User flow, Sketches</li><li><strong>Build </strong>— Prototype</li><li><strong>Test </strong>— Usability testing</li></ol><h3>Empathise</h3><h4><strong>User Interview</strong></h4><p>Due to the lockdown, the whole course was held via Zoom so the learning curve was steep when it came to the user interview. With my previous experience in HR and as a teacher, I am used to talking to people and understanding their perspectives. This was a little different, but I quickly got into the swing of it. The first 5 min interview I established that it was his relationship with cooking he wanted to address. I then took 15 minutes and prepared an interview.</p><p>A few of the questions I covered to understand his pain points around food are:</p><ol><li>Please describe your current cooking routine?</li><li>Can you tell me what you enjoy about cooking?</li><li>What do you like to cook?</li><li>What do you dislike about cooking?</li></ol><h4><strong>User Experience Map</strong></h4><p>The interview gave me some rich insights that I used to make a user experience map for Jack and see where his pain point is. He was clearly struggling with inspiration for what to cook and this was frustrating him.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ARFS5Pao4lGAlqs2MfZ-g.png" /><figcaption>User Experience Map</figcaption></figure><h3>Define</h3><h4><strong>User Persona</strong></h4><p>Armed with my user research, I then wrote up a persona for Jack to refer back to as I worked to understand his pains and designed him a solution that would get rid of the stress of deciding what to cook.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-I8xP6viL_n7jBhUuOqj_g.jpeg" /><figcaption>User Persona for Jack</figcaption></figure><h4><strong>User Storyboard</strong></h4><p>I am still working at my drawing skills, but I loved sketching out a story board for the project, complete with ‘appropriate expressions’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/1*O19HUTi49HFj8taYJmpkkA.jpeg" /><figcaption>Storyboard</figcaption></figure><ol><li>Jack starts to feel hungry and decides he is going to cook something for dinner</li><li>Jack looks in the fridge and doesn’t know what to cook</li><li>Jack opens his handy app to give him some recipe ideas</li><li>Jack is happy and cooking a new recipe with the food he had in the fridge</li></ol><h4><strong>Problem Statement</strong></h4><p>The user research I gathered and the assumptions I made led me to the following problem statement from which I could start to ideate:</p><blockquote>“Jack needs a simple way to find healthy recipes to cook because he lacks inspiration”</blockquote><h3>Ideate</h3><h4><strong>Sketches</strong></h4><p>I diverged during the ideation process to come up with 6 different and <em>big </em>ideas to solve Jack’s problem. Three ideas came to me quite quickly and I was quite attached to them.</p><p>The last three ideas were unsurprisingly difficult to come by and odd if I am honest. These were my wild reaches which eventually turned into my favourite ideas. They were drawn back to “simple” and attempted to solve Jack’s problem in novel ways. Each iteration was simpler than the last and more focussed on Jack’s problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FlvWseGnhGYj7gH9D2nTKw.png" /><figcaption>Sketches</figcaption></figure><blockquote>I realised my first three ideas didn’t actually solve Jack’s problem in a way that would be useful to him, I saw right away how important it is to come up with as many ideas as possible as I would have stopped with the solutions I liked and missed the better solutions.</blockquote><h4>Build</h4><p>The solution I chose to prototype and test was an app that took what Jack already had in his home and gave him ideas of recipes that were possible to make. I used pen and paper to draw the screens and then loaded them onto Marvel to test with some of my classmates.</p><h4>Test</h4><p>I tested the first prototype with 3 users and collated their feedback to iterate on the design. I summarised the results onto the original sketches as seen below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/932/1*zl8gusebskxjVGqYMzEWJA.jpeg" /><figcaption>Usability testing insights</figcaption></figure><h3>Final Prototype and UI Screens</h3><p>You can find the final clickable prototype <a href="https://marvelapp.com/prototype/697d50h/screen/72317876">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*DooikT_eq3kN43Leaokh1w.jpeg" /><figcaption>Final UI Screens</figcaption></figure><h3>Learnings and What’s next</h3><p>Although a fairly simple and short design sprint, I loved putting the theories into practice. Mostly I loved seeing that my sketching ability was much better than I thought and am now more confident with a pen and paper.</p><p>The biggest take away from this project is how helpful ‘big and not initially obvious’ ideas are to the design process. As I mentioned I likely would have gone with an easy (and inferior) solution if I had not sat and brainstormed all 6 ideas.</p><p>I used a big, orange post-it note book to draw my original sketches on, which added complications to my presentation as well as making the prototype strange colours. In future I will ensure I use white paper for my sketches.</p><p>As a concept project I won’t be taking this design further.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7317049f655d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>