<?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 Louie Wai Hang on Medium]]></title>
        <description><![CDATA[Stories by Louie Wai Hang on Medium]]></description>
        <link>https://medium.com/@whlouie?source=rss-d377f22150a5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*0z9GPIaQ6FJah2dwjtTfNw.jpeg</url>
            <title>Stories by Louie Wai Hang on Medium</title>
            <link>https://medium.com/@whlouie?source=rss-d377f22150a5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:48:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@whlouie/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[Website Redesign: Common Objective]]></title>
            <link>https://medium.com/@whlouie/common-objective-redesigning-a-b2b-fashion-platform-e0a1646861e1?source=rss-d377f22150a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0a1646861e1</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[fashion]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Louie Wai Hang]]></dc:creator>
            <pubDate>Fri, 06 Mar 2020 14:11:22 GMT</pubDate>
            <atom:updated>2020-03-11T16:52:11.578Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A5WM_zlMh5tTXuL-VwLLLw.png" /><figcaption>Common Objective’s current landing page for members: a dashboard with personalised content</figcaption></figure><h3><strong>BRIEF</strong></h3><blockquote>Our client, <strong>Common Objective</strong> is a business-to-business website platform for fashion professionals to learn about sustainable fashion practices, and to connect with other members around the world.</blockquote><p>In this client project, we as a team of four UX design students were invited to improve Common Objective’s current website in terms of navigation and content engagement. Our client identified two main issues from their current users:</p><ol><li>it is hard to find the right content as the website is hard to navigate;</li><li>users find the website not engaging hence return rate is low.</li></ol><h3><strong>CHALLENGE</strong></h3><h4>Interviewing Fashion Professionals</h4><p>To kickstart the project, our group of four UX Design students at General Assembly had our first client meeting. Our main objective was to have a better understanding of our client’s product. We understood that the target users would mostly be fashion professionals, and immediately we identified that our first obstacle was to find the right users to research within the limited timeframe of this project. We received 5 sets of interview data from our client and managed to contact 8 more fashion professionals to conduct our initial user research. In our user interviews, we mainly focused on understanding our users’ behaviours and routines. These included nature of their jobs, personal life goals, frustrations, way of obtaining information related to or not to their profession. In addition, we also tried to understand their subscription patterns, as this would inform us on how we should approach the problem of user engagement for Common Objective. I shall discuss the interview insights in the next section when I cover the distillation of research findings.</p><h4>Twofold Competitive Analysis</h4><p>A second challenge emerged when we were trying to do competitive analysis. It was because there are not many competitors out there that do what our client does. Common Objective’s website is an innovative platform where users can read about sustainable information like you do on an online magazine, while having the feature to allow users to actually explore, source and connect with other fashion practitioners on the platform. In order to research what competitors were doing, we tackled this through separating the core functions of the website and compared each of these with competitors that provided the same service. In case this was not clear, the two core functions we identified were being a sourcing network, as well as a sustainable information platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W2zPUe54IqtEHMkVwKAE8Q.png" /><figcaption>Competitive analysis based on the two core functions of Common Objective. For each category, our team benchmarked Common Object with different measurements and industry common practices / features</figcaption></figure><p>As you could see from the above comparative tables, we identified what competitors were doing that Common Objective was not.</p><blockquote>From this exercise, we could identify what Common Object was lacking in, as well as what is lacking across competitors.</blockquote><p>In this case, an innate is not a common feature found in sourcing platforms but would deem useful for a platform that actually provides connecting with other members feature. Whereas, in terms of an editorial platform, all competitors demonstrated some form of <strong>content hierarchy</strong>, and all but one used more than <strong>one font </strong>in their font pairing.</p><h4>Team Coordination</h4><p>The third and final challenge was more about dynamics of the team. Our group had a rather flat hierarchy, and decision making was not optimal given the limited time scope. In the first week of our sprint, we came to a consensus that this would hinder our progress going forward. Hence, two of the team members who had more experience working in teams including myself stepped up and co-led the group. My partner Fernanda facilitated stand-ups, design studio, took charge of the presentation flow; while I focused on analysing and quantifying insights, managed the project through Kanban, and delegated tasks. We both shared leadership role on the final content coordination and quality assurance of our deliverables.</p><h3><strong>PROCESS</strong></h3><p>This project was approached based on the double diamond framework. That means the project was an iterative process that was roughly categorised into four areas: <strong>Discover</strong>, <strong>Define</strong>,<strong> Develop </strong>and<strong> Deliver</strong>.</p><h4>Web Audit</h4><p>After tackling the challenges we faced within the research phase of the process, we felt like it was paramount for our team to understand how users were actually struggling with the navigation of the website. Hence, we decided to conduct web audits with some users to see how they interacted with the current website.</p><p>We conducted usability tests with <strong>7</strong> different users, where each of them were asked to perform 3 tasks. For the sake of testing the website navigation, our users were asked not to use the search bar function. I also instructed my team to record the time for each task to be completed for all the tests, that would aid me in analysing the results by using quantifiable data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Eo1M0cFekyp53ZXeyaqSyw.png" /><figcaption>Task 1 and 2 test the main functions of Common Objective while Task 3 acted as a control.</figcaption></figure><p>The first two tasks aimed to test the two core functions of the website, with the average time to complete the first task (to find an article around organic cotton) to be just around<strong> 1 minute</strong>. While the average time to complete the second task (to find and connect with a footwear supplier) is <strong>2 minute 13 seconds</strong>. Whereas the third task acted as a <strong>control</strong> for the second task to see if users would spend shorter time achieving the objective since they had gone through a similar process in task two. The third task demonstrated that the average time indeed reduced to approximately <strong>1 minute 20 seconds</strong>, after users having familiarised themselves with task two. We could establish from the third task result that users could navigate easier with practice, but a time we were looking to beat after we improved the product with our solution.</p><p>From our web audit, we identified three areas of main improvement. We could confirm that users struggled the most with the ‘Connect’ function, and through both observation and questioning, we found the following insights.</p><blockquote>Do you recall what our client identified as the main project objectives?</blockquote><p>We were to improve <strong>navigation</strong> and <strong>content engagement</strong>. Our web audit found the following results in terms of navigation:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WHP9Ihruss_tDofs_QhAkg.png" /><figcaption>Key insights for the overall navigation of Common Objective website</figcaption></figure><p>While members will land in a tailored dashboard every time they visit Common Objective website. It would be essential that this landing page was assessed by our users, hence I used this page to gauge for insights revolving content engagement:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E_OmXcZ9fSL6Yx0Vcg1enA.png" /><figcaption>Content engagement on the dashboard was not engaging members in a personalised way as intended</figcaption></figure><blockquote>To summarise the web audit’s insightful results, we gladly told our client that our findings matched what they identified. We verified through usability tests that Common Objective’s current website is indeed suffering from a difficult navigation system and a lack of content engagement.</blockquote><h4>Affinity Mapping</h4><p>With competitive analysis, user interviews and web audit completed, we had enough data to work with and so we moved onto <strong>affinity mapping</strong>. Although this only revolved around user interview data, we still used other research collected to provide more of a holistic view when analysing these findings.</p><p>The main goal we used affinity mapping was distill findings, and to identify emerging trends. This would help us identify characteristics and behaviour that our average user had, and assist us in the final steps in the define stage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iopKzU87om4NojUk7pB9KQ.png" /><figcaption>Grouping interview findings under trends to find a pattern that represents our average user</figcaption></figure><p>From our affinity map, we identified some main trends that would make sense when put together to become a persona. So it could be said that the persona is a summary of our research insights. We created Francesca, our persona.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T8m7ppNHVOlsQw3V0443WA.png" /></figure><p>Utilising Francesca, we mapped out an experience map for her current journey when she needed to perform one of the tasks we set for our web audit users. In this scenario, Francesca wanted to source a footwear supplier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jm9eUBOyVn9-12sY0n8jHg.png" /><figcaption>Francesca would get more frustrated as she tried to use Common Objective but failed to solve her problem</figcaption></figure><p>From here, we defined our problem statement and hypothesised a solution to help Francesca achieve the goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2EIi2OGnZ42te8NMUdGYyQ.png" /><figcaption>Problem Statement</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C7LMHMCD1qWC_whUzebtuQ.png" /><figcaption>Hypothesis Statement</figcaption></figure><blockquote>These tools served to anchor our project’s direction in the next steps, and made sure our team’s creativity was aligned towards the objectives of this project.</blockquote><p>With our problems and solution defined, this marks the beginning of the next stage: <strong>Develop</strong>.</p><h4>Design Studio</h4><p>In order to make sure we were on the same page as our client when it came to designing the solution, our group participated in a design studio with Common Objective.</p><blockquote>This exercise was to engage with stakeholders as early as possible to ensure their input was valued and reflected in the solution, it could also help eliminate mismatch in expectations.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-S06g6KrhrpgKA8QLjc5IQ.jpeg" /><figcaption>Design Studio sketches, dot voting to pick out the most popular ideas for consideration</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vR7PpGIn_dDc6WrUuaq7wA.png" /></figure><p>Our design studio involved the Co-founder and Head of Content from Common Objective, and the two ideas that received the most votes were: a <strong>trending news </strong>feature<strong> </strong>and a <strong>bookmark system</strong> that incorporates collection lists (think Pinterest / Instagram).</p><h4>Prototyping</h4><p>With the problems defined, solution proposed and ideas generated, we moved forward to create paper prototypes for initial testing and feedback iteration. Our first prototype was a combination of all our individual designs, which I asked everyone to sketch and test by themselves before we combine our effort and feedback. This way, we could have a bank of ideas to fall back to if something didn’t work quite as we expected. We then combined the best features of all our designs and created one set of paper prototype. This was quickly tested around with users again to gather feedback for further iteration, and here are some insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ISSM1OgdyjADtk9HSBMdsQ.png" /><figcaption>“Learn” seemed to be a contentious term for some users as they struggled to click in there to locate articles</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v47mNx-Pj0Rmzxs9nRtRgQ.png" /><figcaption>“Trending News” implemented from design studio was well received in our initial round of test</figcaption></figure><p>Moving forward, our team fixed on one low-fidelity prototype to expand. We all worked separately on different pages for the creation of the mid-fidelity prototype. This proved to be very challenging as we did not have the right tools to work on a collaborative Sketch file, and everyone was very keen to participate in the wireframing process. Seeing the problem as co-leader, I suggested that everyone pick one page, and focus on working on it plus its relevant variations (i.e. with filter, highlights, popups). In addition to my pages, I also designed the global navigation and footer, and designed a few variations for more testings.</p><blockquote>While the low-fidelity prototype mainly tested out overall navigation and ease of use, the mid-fidelity prototype focused on testing out features and functionality of the website.</blockquote><p>This was tested with <strong>6 </strong>new users to make sure they weren’t familiar with the project, and here are some insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vbdXMtR-0UEZ-4uxB5lt6g.png" /><figcaption>We tested with different bookmark icons and discovered that the traditional bookmark-shaped icon was the most well received</figcaption></figure><p>At this point, we were almost moving onward to developing our high-fidelity prototype but something was not addressed yet. It was the content engagement part of the brief. From our tests, users had been constantly talking about the site was not editorial or fashionable enough for the services it offered. Hence, we looked at competitors again and revisited competitors who have presence as online editorials.</p><h4>Competitive Analysis Revisited</h4><p>This time we focused our research on content engagement strategies, i.e. content hierarchy and font system. We looked at how prominent online editorials and sustainable information platforms alike layout their articles and landing pages, as well as how they pair up different fonts for a more user-engaging experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uy29K4uABcs4MqOaVW8_eQ.png" /><figcaption>Competitors demonstrated to have used more than one font, or in different weights to create a more user-engaging editorial space</figcaption></figure><p>For the current Common Objective website, there is only one font, and used only in one weight: Gotham. Fernanda did some extra research on the font and found out that it was heavily used in the politics scene, most notably in Obama’s presidential campaign and many other politicians who followed. From this fact, we decided to keep Gotham to convey a trustworthy accent and worked around pairing fonts with it. We finalised our decision on <strong>Libre Bodoni </strong>as the title font, and <strong>EB Garamond</strong> as the content font. The illustration below shows comparison between the current and our proposed font system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3UDpZLb3vgv42h2xdhraMQ.png" /><figcaption>A comparison between the original and our proposed font pairing on Common Objective</figcaption></figure><h3>SOLUTION</h3><p>Now that we concluded the <strong>Develop</strong> phase, our team moved onto <strong>Deliver</strong>-ing the product in the form of a high-fidelity prototype.</p><h4>Navigation</h4><p>The solution our team created was a result of 3 rounds of usability tests, with over 20 users in total. It also comprised 3 rounds of competitive analysis spreading across different service providers. Here are some final iterations we made. In order to address website navigation, we proposed these designs:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ljwDPBzk_IQ_sfq629WBEg.png" /></figure><p>This is our rendition of the Find Connections page opposed to the original, where the filters were not obvious to all users, and the pre-selected filters proved unintuitive for most of our 7 test users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pVB0YQSt5BI-OgStCNFdaQ.png" /><figcaption>Filters are preselected for users on the current website, users found this an unintuitive experience</figcaption></figure><p>I also looked at how we might improve the global navigation as we discussed in usability test, users were not so sure what to click as they were presented with too many options. So I proposed a new navigation interface and did A/B test with 5 uses to see which one they preferred.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H7422yzmQzkbCPyxiH8AJA.png" /><figcaption>The new navigation system followed normative design and have the search bar, messenger and accounts on the right, while grouping other core functions on the other side</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8bm7jLFgLCaFYak2ygTqbQ.png" /><figcaption>A/B test results showed that users preferred the new navigation system</figcaption></figure><h4>Content Engagement</h4><p>The other objective being to improve engagement with users, we took inspiration from competitive online magazines as well as sourcing platforms to implement new features so that Common Objective can gain a competitive edge in the editorial space, accommodating a member base of fashion professionals. According to user interviews, fashion professionals are always on-the-go and they need to utilise their time very wisely. A few suggested they do research while they commute, hence we that an export/download function would be ideal. It can also serve as an alternative to a Common Objective mobile app in the meantime.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XiQnBdWHhxNbw6jspP_L6Q.png" /><figcaption>Extend the potential of current bookmark feature to allow the list of ‘Collections’, and the ability to share or export articles for offline consumption</figcaption></figure><p>From our design studio, our team aligned with our stakeholders that a trending article or trending member section would be useful for promoting members to consider signing up for a subscription. This idea was also tested in our low-fidelity prototypes and was general well received by users as they indicated that sometimes they wouldn’t know what they were looking for and would like to read about popular trends.</p><p>A direct messenger was also designed because we saw that as an opportunity from competitive analysis. It would only be intuitive for a networking platform to have a feature that allows members to communicate with each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*67rdNR-1DqE4WWAaA4BRNA.png" /><figcaption>Extra features to improve content engagement</figcaption></figure><h3>RESULTS</h3><p>The final product culminated in a high-fidelity prototype where Francesca revisited the tasks of finding information on organic cotton, and sourcing a new footwear supplier. But in this case, we understood that users like Francesca had a busy job and vibrant life, Common Objective can now fit into Francesca’s daily routine better by allowing her to save the things she liked, and to revisit them under her personalised dashboard whenever she wants.</p><p>Here is the clickable prototype if you would like to try it out yourself: <a href="https://invis.io/27VWREYJGN8"><em>https://invis.io/27VWREYJGN8</em></a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FPLgBVaAPQJk%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DPLgBVaAPQJk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FPLgBVaAPQJk%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/31fc8c030ecd3a28f6bde1f1f71f2bfb/href">https://medium.com/media/31fc8c030ecd3a28f6bde1f1f71f2bfb/href</a></iframe><h4>But this is not the end</h4><p>We did a forth (final) round of testing with our high-fidelity prototype, asked 8 users to perform the same tasks as we asked the previous 7 users. But this time only two tasks without the control. The results were very, very positive:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-9MNbu4owIkLvfOykSlcMA.png" /><figcaption>Through observation and feedback, almost all users found the site easy to navigate and would like to use it again</figcaption></figure><blockquote>To measure our success, we also timed this round of usability test and compared, the first task took about half the time to complete now and the second task only takes about a quarter of the original time to complete!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AKLudvPjwofz6870AibN0Q.png" /><figcaption>Metrics for the success of our high-fidelity prototype in terms of navigation</figcaption></figure><h4>Next Steps</h4><p>The next steps of this project will again go back to our competitive analysis, where we felt that Common Objective could benefit from an <strong>onboarding video</strong>, as well as <strong>compare feature for profiles</strong>. In the current website, there is already an algorithm that measures all profile’s sustainability level. So it might be something our client already invested in, that we may consider incorporating into this feature. Other ideas for next step include a <strong>sustainability self-help clinic </strong>as our client pointed out that a lot of their members did not know what they were looking for, they just knew they wanted to bring their businesses to a more sustainable level. Finally, as I just mentioned, we could also think about designing a mobile app that goes along with our member base that is a very dynamic and on-the-go bunch.</p><h4>Learnings and Client Feedback</h4><p>Overall, we were very satisfied with our product. In the scope of two weeks, we believe we achieved a lot as a team of four. From research to prototyping, four rounds of testing with almost 30 users! Personally, my biggest learning from this project is to never make assumptions, and it is always the best to test more and ask users what they think. The second learning I had from this project is that it is paramount to have an open conversation within teamwork. It is okay to make mistakes or have a disagreement, as long as we listen to each other’s feedback, communicate clearly and re-align expectations. Most importantly, mutual respect, appreciation and understanding the motives and reasoning behind everyone’s decisions.</p><p>Our client gave the following testimonial to show support for our work:</p><blockquote>“We were fortunate enough to work with Louie and the team on a UX sprint through General Assembly and were very impressed by their work. They showed a great deal of curiosity and care for the needs of our users, and were able to untangle complex challenges to create clean, simple solutions. I am certain they have a bright future in UX and product design ahead and I wouldn’t hesitate in recommending them.”</blockquote><blockquote>—<em> Qiulae Wong, Co-founder @ Common Objective</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qfJ1uvgwcM2024QVYAyxLw.png" /></figure><h3>Thank you for reading!</h3><p><em>Please get in touch if you have any feedback or if you’d like to chat.</em></p><blockquote>Email: louielwh@gmail.com<br>LinkedIn: <a href="https://www.linkedin.com/in/whlouie/">whlouie</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0a1646861e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mobile App Design: Boots Pharmacy]]></title>
            <link>https://medium.com/@whlouie/mobile-app-design-boots-pharmacy-73344687bec3?source=rss-d377f22150a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/73344687bec3</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[mobile]]></category>
            <dc:creator><![CDATA[Louie Wai Hang]]></dc:creator>
            <pubDate>Tue, 03 Mar 2020 13:55:05 GMT</pubDate>
            <atom:updated>2020-03-10T14:05:15.478Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>OVERVIEW</strong></h3><p>In an era of mobile fitness tracking, there is no lacking of mobile devices that help you keep track of different health indicators. In this scenario, Boots Pharmacy saw the opportunity to enter the health/fitness tracking sector, so that it can redirect old and new customers alike to the wide array of services they provide as a pharmacy. Our team of four junior UX designers were challenged to create a mobile app for boots to achieve these objectives.</p><h3>CHALLENGE</h3><p>Before I discuss the process in depth, I would like to present a challenge we faced after the initial research phase. In the first instance, following the project brief as described above, our group did competitive analysis, screener surveys, user interviews and affinity mapping. We even crafted a persona and while we were defining our problem statement, something did not feel right.</p><h4>User Needs vs Business Needs</h4><p>Our user research reflected that users would very much like a fitness <strong>one-stop-shop app</strong> that is similar to Apple’s Health app. However, our competitive research also indicated that the market is saturated with similar kind of fitness trackers. Our users indicated that they could not justify reasons to switch to Boots unless the app offers additional services or functionality to incentivise that change. So our group decided that in order to create a user-centric solution, we needed to communicate with our stakeholders, and managed to convince them with our research data that we needed to take the project in another direction. That means we had to start from square one, and to reassess opportunities that Boots could explore based on our findings.</p><h3>PROCESS</h3><p>After repositioning our app within (see <strong>Challenge</strong>), we went back to start from the beginning of the UX process.</p><h4>Competitive Analysis</h4><p>Before conducting user research, we first turned to comparative research for inspiration and data. This would help us understand what we were facing in the market, and would help align our understanding of the products before we turn to user research. This came in the form of competitive analysis where we identified new competitors according to the new brief. We identified five key direct competitors that were either medicine tracker apps or pharmacy appointment service apps. Our competitive analysis covered a lot of grounds, but the main insight from this exercise was to find out the following: Common features across competitor apps that we should consider adopting, as well as niche features that might be seen as opportunities for our Boots Pharmacy app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-qpROLgmIOjU4gEFnGmmiQ.png" /><figcaption>Refill reminder and user accounts were found in all competitors, hence it should inform our design to include these functions</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n3HK9WuWrQNLHeWtictu_g.jpeg" /><figcaption>Drafting initial survey and interview questions based on themes we wanted to learn from our users</figcaption></figure><h4>User Research</h4><p>In our <strong>initial</strong> user research, we devised two set of questions that went into a screener survey and an in-depth user interview respectively. The screener survey consisted of questions revolving the respondent’s current fitness tracking habits and their past experiences with the GP, appointment booking and Boots. The survey helped us find the potential users of our app for a follow up interview. Out of 24 survey responses, we contacted 18 of the respondents and conducted user interviews to learn more about our potential users’ fitness practices. In our <strong>second</strong> round of research after repositioning, we revisited our interviewees and asked them additional questions regarding their medicine taking habits and methods they used to keep track of such activities. We believed that this information would inform the direction of our design solution, and shed light on how we could utilise what Boots Pharmacy currently offers to add value to the product.</p><p>From the raw data collected from interviews, we used affinity mapping to find any emerging patterns and common features, then we distilled our insights and findings into a single persona. This will serve as a culmination of our user research and an alignment to keep referring back to throughout the whole design process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VcdEvZNFi1MhQQTEgMKa-w.png" /><figcaption>Affinity mapping to capture all insight from 18 user interviews</figcaption></figure><p>Following on the affinity mapping exercise, I took the initiative to study the data in a more analytical way. I wanted to be able to <strong>quantify</strong> the insights and to make sense of the massive spread of data with figures, so I looked into and measured key trends through <strong>metrics</strong>. I did this so that we could justify the design and functionality of our product through <strong>quantifiable user needs</strong>. The logic I used was to group trends of insights under the two main business objectives: increase awareness of Boots’ services, and medicine tracking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bxrKptNIQFtbNMG-bCQUcg.png" /><figcaption>Translating key insights into opportunities for Boots Pharmacy by matching up with business needs (purpose of the app)</figcaption></figure><p>After having quantifiable data to validate our new business needs in the brief were indeed matching up with what users really needed, I moved further to justify the features we ideated using the same set of data, this would affect what features to have in our design solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J4ELhn-AlMbPGSVMl5qFBQ.png" /><figcaption>Ideating features of the app through user-validated business needs (purpose of the app)</figcaption></figure><p>Now the direction of the product is clear, and research phase coming to a conclusion. We summarised all our research (user interviews, surveys, competitive analysis) to craft a <strong>persona</strong>. It is the representation of all our findings, and what the product’s average user should be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Emh6B8DQJ3A4zhgDH4er8Q.png" /><figcaption>Our persona Maggie, the summary of our research</figcaption></figure><p>With our persona Maggie as an anchor to the rest of the UX processes that followed, we essentially created a reference point to go back to when we were in doubt throughout the design process. Here is the <strong>problem statement</strong> we defined:</p><blockquote><strong>Maggie needs a way to remember to take her medication at specific intervals during the day because she keeps forgetting/using inefficient methods.</strong></blockquote><p>And our proposed <strong>hypothesis solution</strong>:</p><blockquote><strong>We believe that by creating a health tracking app with a medicine reminder notification system, Maggie will not miss a dose again.</strong></blockquote><p>From the problem statement and hypothesis solution, we further devised a current <strong>experience map</strong> for Maggie in this scenario, and proposed a <strong>user flow</strong> of Maggie’s journey when using the design solution:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4PxwdbG4WG97nNbamR7z3w.png" /><figcaption>Maggie’s current journey before using the design solution, this will highlight the pain points of the user, so we can focus on improving the experience</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HwRgPcZmVxMclLMm2x4lqw.png" /><figcaption>Proposed journey that Maggie has to go through when using our design solution</figcaption></figure><h3>SOLUTION</h3><h4>Features</h4><p>Research was very important in the UX process, but especially so in our concept project with Boots. That is because we needed to gauge users’ understanding and knowledge of Boots in order for us to be able to propose the right solution to increase awareness of Boots’ services (business needs). The market is also saturated with apps that can do all variety of functions so we needed to create something that Boots could immediate utilise as their competitive advantage. Hence we created a medicine tracking mobile app.</p><p>The app’s key functions were decided when we were analysing user findings (see <strong>Process</strong>), but we also ideated many more functions that might interest our users. These might be inspired by competitor apps or what we saw as an opportunity because of a lacking from the market. However, there were too many ideas and we decided to do a <strong>feature prioritisation</strong> exercise to focus on what were <strong>essential</strong> and <strong>low-cost</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s8WcdJVyfZqF-YeI3m7AcQ.png" /><figcaption>Priority should be given to features in the highlighted box</figcaption></figure><p>From this exercise, we created an initial <strong>site map</strong> for the app, it would help us categorise and prioritise what users see and interact with in the design solution. As well as help us decide how we should approach the next phase of design — prototyping. From our research, it was clear that users wanted a medicine tracker where they could track what kinds of medicine they needed to take in the day, and when. Our approach on relating this to Boots Pharmacy’s current services was the pharmacy service where the user could utilise the app to not only remind them about taking medicine, but also when they needed to refill their prescriptions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kXrpqVwcQXxH9kFECtm6Rg.png" /><figcaption>Initial proposed site map informed by research and feature prioritisation</figcaption></figure><p><strong>Prototyping</strong></p><p>Prototyping is another big chunk of the UX design process. It is a quick way to create wireframes and mock ups that allows usability testing to kick in as early as possible, so that designers can iterate feedback and make the product viable for the actual users before investing in the development of it.</p><p>The four of us each created some low-fidelity paper wireframes, and tested with 3 users each individually. Then we grouped our ideas and user feedback, i.e. the most well received feature / design, to create one combined prototype that we would bring into mid-fidelity for further testing.</p><p>From these wireframes, we have created two flows of the product: <strong>medicine tracker and reminder</strong>, and <strong>book an appointment with Boots Pharmacy</strong>. In the scope of this project, we decided to stick with the first flow and focus on medicine tracker and reminder as that was reflected in research to be prioritised by our users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eVFmaMO-wLAXoIIZUe93Sw.png" /><figcaption>Different sets of paper prototypes that we each created and tested</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wghAn7y9VWFcL-Dkzpqq8g.png" /><figcaption>Combining all our first round of usability test results and developing one prototype for mid-fidelity with two flows: Medication tracking and Appointment booking</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jAZaquao88KXM05GPv58cQ.png" /><figcaption>Mid-fidelity wireframes as a result of combining designs and all feedback from usability testing</figcaption></figure><p>From the mid-fidelity wireframes, we conducted some more usability tests to gauge users’ feedback on how users interacted with the functions now that there was a more overall feel of what the design and flow of the product would be like. Users were asked to perform 3 tasks on the prototype:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ThQnlmIRyCjdon6mDmTmnA.png" /><figcaption>3 tasks that our test users would perform, taking into account that this would be a scenario Maggie (persona) would face</figcaption></figure><p>The test were conducted with 8 new users so they would not have a sense of familiarity or any bias. The findings were very constructive, as most users found the app not as intuitive as we would’ve expected. Also, task 3 asked the users to change the dosage and 5 out of 8 users expressed concerns about the ability of changing the dosage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GzciJYwMyWmQEEPn4jeFLA.png" /><figcaption>Key insights from our usability tests of mid-fidelity wireframes</figcaption></figure><h3>RESULTS</h3><p>After two rounds of usability testing with about 20 users throughout low to mid-fidelity wireframes. We took into account their feedback, and moved into creating a high-fidelity prototype focused on medication tracker and reminder. This was mainly achieved by one teammate, while another teammate created alongside the main prototype an onboarding tutorial. While I focused on putting all our findings together and created by myself the whole presentation flow, and how to demonstrate everything that stakeholders would need to know in this 2-week sprint.</p><p>The following shows the main iterations we adopted to the final high-fidelity mock up:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uVfnU6gRZS4i0kwyEpJOVQ.png" /><figcaption>User feedback suggested the landing page (dashboard) should be less busy</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eZ7fzu_x72wjg0RY7r-eIA.png" /><figcaption>Users suggestions for changes to be made in the high-fidelity on the right hand side</figcaption></figure><p>Moreover, as 5 users commented on their concerns about medicine dosage. One teammate researched more about medication in order to improve the design of the tracker and reminder function. The research showed that our current product should focus on <strong>set interval dose medication </strong>(e.g. Antibiotics), so that through initial barcode scanning process, the Boots Pharmacy app would be able to obtain the correct dosage from the database, which would forbid users to change dosage by themselves.</p><p>What the users could alter though, are the <strong>time / day / date</strong> depending on how often the scanned medication should be taken, and <strong>when</strong> they would start their reminder so that the app could work out what time to send a reminder. Users could also opt in or out of a <strong>notification reminder</strong>. The below slide illustrated the screens user would see in the three scenarios: medicine to be taken <strong>per day</strong>, <strong>per week </strong>and <strong>per month</strong>. We decided for this scope of the project, we would leave PRN medication (taken as needed) for the <strong>next steps</strong> because that would complicate the problem and the need was not immediately reflected from our user research.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*03i_sYz9dO8boXPqpZaZTg.png" /></figure><p>We finally developed a high-fidelity mock up which is a clickable prototype, with all the feedback and improvement iterated as illustrated above. We were happy to find that out of 4 usability tests, users’ feedback were mostly positive. Final round of usability tests showed that users could navigate the app without problem, and that it was intuitive to use. Their main concerns though, was that the prototype’s figures were unrealistic (10 tablets once per week), and in general they would like more details on the set reminder. However, as you might recall, it was a decision from our mid-fidelity tests that we should reduce the amount of information presented. I believe that we needed to test the prototype with more users in order to get a larger sample to get the balance right.</p><blockquote>For now, we kept it to a small amount of information because one particular user who was also a long-term medication user actually raised concerns about <strong>anonymity</strong> when using the app in public. This comment was taken into consideration when we designed the app to deliver just the essential information on screen.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_1dXvTHyGh2nEkM_bxkTZg.png" /><figcaption>Areas of improvement identified by third round of usability testing</figcaption></figure><h4>Next Steps</h4><p>In the scope of this 2-week sprint, our group agreed that we achieved a lot more than we expected. As a conclusion, we went into the user research, and found out a mismatch between business needs and user needs. Based on that, we challenged the project brief, negotiated and convinced stakeholders to the let us approach the brief in another direction. One that was supported by user research. Although that took away our resources to complete the second flow: Appointment booking, we felt that this is an important lesson in UX design as it is a user-centric process. So the next step would definitely be to complete the second flow of the app, while testing the product with many more users. As mentioned, we would also like to start developing medicine tracking for PRN medication (taken as needed), so that the product can accommodate a wider range of users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iLJRciGxvJUNG6TS_i4baw.png" /><figcaption>Low-fidelity wireframe revisited, next step will focus on the highlighted flow: appointment booking</figcaption></figure><h3>Thank you for reading!</h3><p><em>Please get in touch if you have any feedback or if you’d like to chat.</em></p><blockquote><em>Email: louielwh@gmail.com<br>LinkedIn: </em><a href="https://www.linkedin.com/in/whlouie/"><em>whlouie</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73344687bec3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[E-Commerce Website Design: Sunshine Foods]]></title>
            <link>https://medium.com/@whlouie/e-commerce-website-design-sunshine-foods-d245bb645c1d?source=rss-d377f22150a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/d245bb645c1d</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Louie Wai Hang]]></dc:creator>
            <pubDate>Wed, 26 Feb 2020 23:08:24 GMT</pubDate>
            <atom:updated>2020-03-13T01:12:29.005Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W6WZE_3Z3uJNhsEe1rjqrw.png" /></figure><h3>OVERVIEW</h3><p>In this concept project, I designed in order to bring a local grocery store online by creating a brand new e-commerce website for it. The client — Sunshine Foods, is a next-door grocery that takes pride in its curated inventory, all hand-picked by their knowledgeable staff. The brand emphasises on providing the best customer service and give back to the local community by hiring local staff. To that extent, their main target audiences are local residents and small businesses nearby. Sunshine Foods values all customer needs, so they also provide an order-by-request service for those who could not find what they wanted in the shop. This was a solo project but initial research was conducted in group, consisting of four other junior UX designers at General Assembly.</p><h3>CHALLENGE</h3><p>The moment I received the project brief, I thought to myself:</p><blockquote>How am I going to make anything that is <strong>original </strong>and<strong> creative</strong> when there are already a ton of online grocery shops of all scale and variety?</blockquote><p>I immediately turned to the <strong>customers</strong> because I knew that although there are many competitors, they don’t all necessarily target the same target audience. So my first instinct was to sit down with my fellow research team, and we all came to the consensus that customers come first and we will need extensively thorough interviews to find out who our target audiences are, and <strong>why they shop where they do</strong>.</p><p>The challenge that followed however, was a solo project and everyone in the team would have their own spin on this concept brief.</p><h3>PROCESS</h3><p>As with any Agile UX design, this project was an iterative process. It meant that I kept testing and explored continuously for better alternatives to refine my solution based on user feedback.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UzNnhX4OzCdSlbRsZWBEZg.jpeg" /><figcaption>Contextual inquiry at a local curated grocery near Old Street, London</figcaption></figure><p>As a group of five, we combined effort in the initial user research. We located two independent grocery stores similar to our concept client in terms of market positioning and inventory. Our main purpose of this <strong>contextual inquiry</strong> exercise was to find out as much about shopper<strong> </strong>behaviour as possible, through observation and interviews. We had a total of two observations and four interviews on site, and we did a further 8 more interviews off site.</p><p>We distilled the interview results to find common themes and trends with an exercise called <strong>affinity mapping</strong>. This was essential to make sense of all the interview results, and fundamental for the next step, which was to create a <strong>persona</strong> for our client’s e-commerce website. My persona would be the embodiment of the interview findings, and would become my general average customer to refer back to when it comes to designing the solution. Creating a persona is a great way to anchor your creativity so that the solution stays true to the user needs, as well as business goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KJSisK2zc0gVnNdiqi6aZw.jpeg" /><figcaption>Affinity mapping to find emerging trends across 12 user interviews</figcaption></figure><p>After creating the persona, we started to identify key direct competitors. It is important because we want to know what they did well and not so well, and more importantly why customers like our <strong>persona</strong> would want to shop there. With the competitors identified such as <em>Planet Organic</em> and <em>Whole Foods</em>, I looked at their website to see how their online shop functions. I looked out for common features as well as those exclusive to certain brands, it allowed me to recreate what’s seemingly popular amongst competitors for Sunshine Foods. I also generated new ideas for the website’s functionality in order to highlight the client’s core values: <strong>Great customer service</strong> and <strong>supporting local communities</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_recUTmsLxVtp5uJ6wonNA.png" /><figcaption>Common features adopted from competitors, and ideated Sunshine Foods exclusive features</figcaption></figure><p>It is always great to have nice functions, but they won’t be useful to anyone if the users can’t find them. That is why I need to structure the information architecture next.</p><p>Creating the <strong>information architecture</strong> was one of the final steps before creating the paper prototype. It was a big process, and it required a lot of testing. This was important because it informed me as the designer <strong>how users actually processed, categorised and prioritised information</strong>. For this purpose, I utilised open and closed card sorting techniques to understand how my testers would categorise a sample selection of Sunshine Foods’ inventories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ivbwVXJmmt1zKqMifiXtcw.jpeg" /><figcaption>Open card sorting where user created his own categories for the inventories</figcaption></figure><p>The sample however, was very small and I only did 5 tests so the results were not very consistent. It was proving to be difficult to make a site map purely based on the tests I conducted, so I did more research on competitor websites and created my initial site map, based on the findings from my card sorting exercises and main competitors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lJriF7xhuRnnOhEjV5lLSA.png" /><figcaption>Proposed site map for Sunshine Foods, based on the sample inventory, 5 card sorts and comparative analysis</figcaption></figure><p>With the initial information architecture, Combining all my prior research, I was finally able to craft a <strong>user flow</strong> for my persona. This represents each step of the process an average user would take and go through if they were to perform a certain task on my e-commerce website. This user flow would then enable the creation of a simple paper prototype for more testing before I take the design further to create a more concrete solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gf08OjlCnhnCyva2-1z4eA.png" /><figcaption>Proposed user flow for my minimum viable product (MVP)</figcaption></figure><p>With the user flow confirmed, I started building paper prototypes for the e-commerce website. This was an effective way to test if initial ideas worked, because it was quick and cost-efficient. I was able to get three users to test the initial prototype before I iterated changes into the next prototype. As expected and explained above, they found the way I categorised the products confusing, some found it counterintuitive, while some said they were used to other kinds of categorisation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dS1E9Rge3f2o6Q1qxtMEsQ.jpeg" /><figcaption>Conducting usability test with paper prototypes, mainly to test the navigation and ease of use</figcaption></figure><p>It was interesting to see how users had very different opinions on the same inventory’s categorisation. Throughout the usability test phase, I also iterated a few changes to the interface in order to make the functionality less ambiguous. But overall the users gave positive feedback on the <strong>navigation</strong> and ease of use, despite all of them had their own ideas on what the product categories should be.</p><h3><strong>SOLUTION</strong></h3><p>The outcome was a series of Sketch wireframes and a clickable prototype. I included specific functions like ‘<strong>Curated by Sunshine</strong>’ and ‘<strong>Order by Request</strong>’ in the global navigation to highlight the brand’s core value: <strong>great customer service</strong>. It echoed with the project brief, but more importantly it was also supported by interview findings, where our interviewees noted their interest in finer/sustainable/exclusive products.</p><p>I also used a minimalist design to create a clean and neat experience, as was indicated by a majority of interviewees that these were measures they would take into account when determining if they had a pleasant in-store experience. I wanted the design to mimic a <strong>neat</strong> experience for them so they could focus on the products and other functionalities of the website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yk9umazvOl6wwy1KVdKJAg.jpeg" /><figcaption>A minimalist landing page with features that allow Sunshine Foods to deliver its signature sense of personal touch and a clean experience even when shoppers visit online</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jvUPmcid1_7hHkQOWkv4Sw.jpeg" /><figcaption>Users were very positive about this streamlined shopping cart with check out on the same page, a design informed by user interviews that our users like a neat experience and hated to wait</figcaption></figure><h3>RESULTS</h3><p>I tested the prototype with six users and I was proud to say they were all very satisfied with the navigation of the website. Three users commended on the highly integrated shopping cart and order page, while five out of six were interested in ‘Curated by Sunshine’. Two mentioned that they would go for this function if they were in doubt.</p><p>However, the shopping categories did not yield satisfactory results even after minor tweaking after the previous tests. Three of the testers still found the categories confusing and this proved that the card sort sample was too small for it to yield effective results. I believe this would have to be be the priority of this project’s next steps.</p><h3>IT’S ALL ABOUT THE USERS…</h3><p>Beyond the scope of this project, I attempted to do some branding for Sunshine Foods. So I returned to my user interviews and concluded that the brand statements should be as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*YAkZ_gu8c3-HVhoYOpwx_Q.png" /></figure><p>It also followed from the my interviewees’ strong personalities that my rendition of Sunshine Foods’ branding would be very <strong>bold</strong>, such that you either like it or hate it. So here are my brand affinities to demonstrate how <strong>bold </strong>I made the brand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vPGs5SL_0oqxw6Q18zR0zA.png" /></figure><p>From these branding elements, I crafted a simple style guide:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f6tQskWd5kfp6dlQcr7s1w.png" /></figure><p>And finally, some high fidelity mock up screens. When I presented my design to my users, they immediately had clear opinions about it. This proved that my style worked well for the branding, especially tailored for users I interviewed with in the very first place. Some find them quite bold that they could not agree with the choice of style, but the final design was selected based on seven A/B tests, where majority rule held. Although some of the panellists found my design controversial, they were convinced by the data and this was what users preferred. It was not about what I wanted, but what my users needed. Without further ado, here is the landing page of my controversial mock ups. A treat for sticking around and finished reading!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bcL9Wa_SodVFx8ua3iGJnA.jpeg" /><figcaption>Landing page with a bold bright yellow background to go with the branding that users preferred</figcaption></figure><h3>Thank you for reading!</h3><p><em>Please get in touch if you have any feedback or if you’d like to chat.</em></p><blockquote><em>Email: louielwh@gmail.com<br>LinkedIn: </em><a href="https://www.linkedin.com/in/whlouie/"><em>whlouie</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d245bb645c1d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mobile App Design: 4Hikers]]></title>
            <link>https://medium.com/@whlouie/mobile-app-design-4hikers-78fcdd91b1dc?source=rss-d377f22150a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/78fcdd91b1dc</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Louie Wai Hang]]></dc:creator>
            <pubDate>Wed, 26 Feb 2020 16:09:19 GMT</pubDate>
            <atom:updated>2020-03-10T14:06:22.035Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5nwRiNU6RWTRFSa4NgV24g.jpeg" /></figure><h3>OVERVIEW</h3><p>In this exercise, I designed a mobile app — <strong>4Hikers</strong> for my client David. The app is a simple planning and recording journal, targeted for hiking enthusiasts. I tried to keep the design simple because my user should find the app an enjoyable and effortless journey, and it should take away the pain instead of adding on to it.</p><h3>CHALLENGE</h3><p>The project marked the beginning of my journey in UX design. In this challenge, I was partnered up with my fellow classmate David in General Assembly. The outcome of this challenge was to design a mobile app to satisfy a need for your user. David, a regular hiker, revealed that predominant navigation apps such as Google Maps are inadequate for hikers when it comes to hike planning. He explained that it is taking up too much time having to look up different websites and sources for a fuller picture of the hiking routes that he would like to do. The information that he would usually need requires him to go onto different platforms and websites. He will have to almost visit a few websites for each category of information (reviews, routes, images etc.). He started to find it time-consuming, unintuitive and more importantly, stressful when it comes to planning for hikes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P2zZSlDV0_4MhIwq8R0OBA.jpeg" /><figcaption>Interviewing with David</figcaption></figure><p>Furthermore, David likes to record his hikes so that he can remind himself in the future what went well and what didn’t. Many a times, a planned route will be met with ad-hoc situations such as closure or weather conditions. David would like to have some kind of help in assisting him to record these changes after his hikes.</p><h3>PROCESS</h3><p>At the very first instance, I interviewed my partner David to understand what were his usual hiking procedures. He also briefed me through some pain points of this process while telling me what he wished could’ve been in place instead.</p><p>Following on the interview, I decided to draw upon the key needs and frustrations of David, and summarised his current hiking process using an experience map. From this exercise, I can understand the high points and low points of the user’s emotional journey, thus making sure the solution I propose meets the user’s needs as well as mental wellbeing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*tYXJgBScGNaEyUuDdojK1g.png" /><figcaption>David’s current hiking experience map</figcaption></figure><blockquote>“I spent too much time jumping from one website to another.”</blockquote><blockquote>David, Junior UX Designer @ General Assembly</blockquote><p>After that, I drew up a few sketches that include quick mockups of the app that might help with hike planning. I also started drawing a storyboard for David’s scenario. It is an easy way to help me keep track of the user’s situation, problem and desired outcome without having to go through my interview notes. This way, I will not lose my head while designing and help steer me away from designing on assumptions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*suyBnxYEvGX28qRdoLz80A.jpeg" /><figcaption>Wire flow and making the first prototype</figcaption></figure><p>The next step was producing paper prototypes and usability testing. I tested my prototype with three users, and the reason behind this exercise was to make sure the app was as intuitive as it should’e be from a fresh perspective. It sought to validate the design and made sure that I, as the designer, did not overlook certain assumptions. I got useful feedback on how the interface was more complicated than I thought it would be, also some icons were not as intuitive as I thought. I adapted these changes to my second prototype, which was a clickable interactive mobile app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TfLXTtGN8WKuy3edOKjg6w.png" /><figcaption>Usability testings with my low fidelity paper prototype</figcaption></figure><h3><strong>SOLUTION</strong></h3><p>In order to create the ideal clickable mobile app for my user, I collated the research findings from my usability tests to refine my ideas, the wire frames and the user flow. This led to a new wire flow, where the main focus was the ‘Happy Path’, the ideal user flow and what they will see in the proposed app for achieving their designated goals. The reason for the creation of this ‘Happy Path’ was to make sure this prototype is low cost and efficient when it comes to problem solving, and in this case, David’s needs. Hence, the clickable prototype will prioritise to test drive this scenario, with the newly adapted UI designs as reflected from the feedbacks of the usability tests.</p><h3><strong>RESULTS</strong></h3><p>The app prototype consisted of four main functions: <em>Plan</em>, <em>Review</em>, <em>Favourite</em> and <em>Journal</em>. These four functions should serve David’s needs in the least, if not, satisfy his needs in hike planning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yCFijfc9UrAG6FR5blShaA.png" /><figcaption>Final low fidelity prototype</figcaption></figure><p><em>Plan</em> involves using an intuitive customisable map interface that enables users to route and plan their hiking routes, alternative routes and potential point of interests via the simple means of dropping pins. <em>Review</em> allows users to search and look up point of interests around their designated hiking area by generating results from existing databases and platforms. <em>Favourite</em> allows you to save favourite routes, point-of-interests and even areas for your future reference. <em>Journal</em> automatically records all your planned hikes where you can review again anytime. It also allows you to edit the records so that you can amend according to any ad-hoc situations that occurred during your past hikes.</p><blockquote><em>“This is what I need, thank you Louie. I would use it, really!”</em></blockquote><blockquote>David, Junior UX Designer @ General Assembly</blockquote><p>I tried to keep the functions to a bare minimal because the app is only supposed to solve the user’s problems, in which case David’s concerns with time-consuming planning and post-hike journaling. However, I still added the function of favouriting something as I felt that it is only intuitive to do so when you can save something to another list almost on any other platform. I named the app <strong>4Hikers</strong> for the four functions and obviously, it is for hikers.</p><h3>4HIKERS</h3><blockquote>PLAN IT</blockquote><blockquote>ROUTE IT</blockquote><blockquote>REVIEW IT</blockquote><blockquote>REMEMBER IT</blockquote><h3>Thank you for reading!</h3><p><em>Please get in touch if you have any feedback or if you’d like to chat.</em></p><blockquote><em>Email: louielwh@gmail.com<br>LinkedIn: </em><a href="https://www.linkedin.com/in/whlouie/"><em>whlouie</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78fcdd91b1dc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>