<?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 Andrewcox on Medium]]></title>
        <description><![CDATA[Stories by Andrewcox on Medium]]></description>
        <link>https://medium.com/@andrewcox514?source=rss-f837f001860b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mmkGvijPLD9efDl7k3Ek3g.jpeg</url>
            <title>Stories by Andrewcox on Medium</title>
            <link>https://medium.com/@andrewcox514?source=rss-f837f001860b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:45:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@andrewcox514/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[My entire UX take-home assignment]]></title>
            <link>https://medium.com/design-bootcamp/my-entire-ux-take-home-assignment-e8dcd13a9a79?source=rss-f837f001860b------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8dcd13a9a79</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[wireframing]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Andrewcox]]></dc:creator>
            <pubDate>Sun, 02 Oct 2022 15:45:18 GMT</pubDate>
            <atom:updated>2022-10-04T04:46:47.125Z</atom:updated>
            <content:encoded><![CDATA[<p>Spoiler alert: I did not get the job (or feedback on the project).</p><h3><strong>Introduction</strong></h3><p>This was my first ever UX take-home assignment. I have been applying to UX jobs for the past few months and have had a fair amount of phone-screen interviews. So you can imagine my excitement when I finally broke past the first stage, the process looked like this:</p><p>📞initial phone screen with recruiter &gt;</p><p>🚀first zoom meeting with hiring manager &gt;</p><p>💻3 back-to-back zoom calls with hiring manager, VP of tech, and Senior UX Designer &gt;</p><p>📁take-home assignment</p><h3>Controversy around take-home projects</h3><p>I will admit that leading up to this point I had already read several articles and posts discouraging designers from participating in take-home projects. Some critiques you will find are that they are free labor or unfair as most of the time the interviewee is working a full-time job.</p><p>In all fairness, the hiring manager did go out of their way to assure me that they were not looking for free labor (<em>they brought this up on their own accord</em>), and they were empathetic to the fact I am working full-time — so not to stress about immediately turning it in. I knew from the first step of the interview process that there’d be a take-home assignment.</p><blockquote>The explanation was that they didn’t care about my solutions, they just wanted to see how I approached the problem.</blockquote><h3>Starting Point</h3><p>One last detail, this company operates in the finance industry. <strong>I was upfront with everyone I spoke to that I am not well-versed in finance and have no experience designing fintech products</strong>, which was met with ease of mind that they were aware and understanding of this.</p><p>At the very end of my 3-round interview, the hiring manager showed me the prompt:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/645/1*7djT5vk7JmeK4ws1WV2yvQ.png" /></figure><p><a href="https://www.raymondjames.com/client-resources/client-access-tour">Link to the “resource” above</a></p><p>🚨 the prompt was oddly specific to the company considering the point of this challenge was to see how I approach problems, but in their defense I was told not to stress <em>the actual solutions</em> too much. Additionally, this was an opportunity for them to truly assess my knowledge of the industry.</p><p>✔️one point in their favor was that I was told not to worry about high-fidelity designs, and that sketches or wireframes were more than enough. I am glad I did not spend an additional 5–10+ hours on just high fidelity UI.</p><h3>Understanding the problem</h3><p>This project was immediately humbling. I was on a high from my interview that I felt went well, then with this prompt quickly was reminded of my lack of expertise of the finance industry, robo-advisors, human-advisors, trends in fintech, etc. One of my resources before this stage was looking over these amazing case studies:</p><p><a href="https://builtformars.com/case-studies/ux-of-banking/">Built for Mars - UX case studies</a></p><p>I also had spent several hours leading up to my interview researching Raymond James and their competitors. I had a general understanding that they separate themselves from competitors with exceptional customer-service and building long-lasting relationships between clients and advisors.</p><p>I knew I needed a plan of attack, so I quickly jotted down some of the key areas I wanted to hit:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*RoENcQtyj_XPjDSEj9XnvA.png" /></figure><h3>Making assumptions &amp; considering business goals ⭐</h3><p>When reviewing the take-home prompt with the hiring manager, they clicked through <a href="https://www.raymondjames.com/clientaccess/demo/">this client access tutorial page</a> as a reference/guide for me to work off of. From my perspective, I made the following assumptions:</p><p>🔑the solutions are going to be web-based (there was potential for a mobile solution, however there was no client access tour for the mobile product to work off of).</p><p>📌the individuals we are solving for are already customers of Raymond James with an assigned financial advisor (you cannot gain access to the Client Access portal without this).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q7fUmxWAU5x5CQXzh6GTSA.png" /><figcaption>slides 1 &amp; 2 of final presentation</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CMfc5d5ob-Z__rvzE2bWyQ.png" /><figcaption>slides 3 &amp; 4 of final presentation</figcaption></figure><p>One note I’d like to make here is that in a real-world project I would have confirmed these assumptions and business goals with the project manager and other stakeholders before moving any further with this project. However due to time constraints and lack of communication mediums (no Slack, Trello, etc), it is generally common place to make assumptions and keep moving forward with take-home projects.</p><blockquote>In hindsight, if I could redo this assignment I would have reached out to the hiring manager in a quick email to confirm my assumptions.</blockquote><h3>Research</h3><p>Since this project did not require high-fidelity screens, I knew I wanted to spend more time and resources on research before jumping into wireframe solutions. Here is how I approached my research:</p><p>🔬<strong>sifted through numerous forums such as Reddit and YouTube:</strong> gathering quotes and insights from posts discussing robo-advisor platforms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ir1Z3zYZETmXhMaW-pNwMA.png" /><figcaption>Gathering quotes from Reddit from discussions of pros vs cons of robo-advisors</figcaption></figure><p>🎤<strong>performed an in-person interview with a friend</strong> who uses Fidelity Go, a robo-advisor platform.</p><p>☎️<strong>called Raymond James customer service</strong> (<em>called on 3 different days, left a voicemail, never spoke with anyone or received any calls back</em>).</p><p>📞<strong>called the Client Access support hotline</strong> (<em>they picked up and were very kind, although did not have any insight into pain points or customer complaints other than account authentication issues</em>).</p><p>🔧<strong>performed competitor analysis</strong> of 3 platforms with successful robo-advisor services, to identify opportunities to capitalize on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WeY7OpRrw4rX4HHgd3mCqw.png" /><figcaption>slides 5 &amp; 6</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-t_4AUOzEFXbxtcWguOszQ.png" /><figcaption>slide 7</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EJu2miIZGVyvbIvniPLDBA.png" /><figcaption>slide 8</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M4WEp5Tpz3Tany3nACgZwg.png" /><figcaption>slide 9</figcaption></figure><h3>Defining the problem to be solved</h3><p>At this point I felt I had enough information to craft an official problem statement that reflected pain points to be solved. To summarize my findings, younger people in general seemed less trusting of having a financial advisor and were less interested in face-to-face customer service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4gu8zQtT1DSakXf8E4bpIQ.png" /><figcaption>slide 10</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KSazFs1Jzfp8dUwHyAldPA.png" /><figcaption>slide 11</figcaption></figure><h3>Explaining how I came to my solution</h3><p>🔨the prompt did not explicitly state that Raymond James was interested in developing a robo-advisor, so that option was nixed.</p><p>🗡️while a virtual assistant could prove helpful, I assumed that this would be very costly to implement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wMtNalGF04owe0Xhv16icQ.png" /><figcaption>slides 12 &amp; 13</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*liDyh56cqf4w1GkLUjvjeg.png" /><figcaption>slide 14</figcaption></figure><h3>Wireframing my ideas</h3><p>I drew some rough sketches initially to give myself a general idea of what my solutions would look like. I eventually determined that using Figma to draw my wireframes was much faster for me personally, so in the name of saving time I stuck with this method.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*54OcBGJRx651KmHzR20z9A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tUNMIsoYSNFBzkrD7LRo-Q.png" /><figcaption>slide 15</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZDinPtvI2XmKUgavPQ8hJQ.png" /><figcaption>slide 16</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jamDBi1ChwfLLIrZSC9k8w.png" /><figcaption>slide 17</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QcAry7-FdbEEAi7_TlXjWw.png" /><figcaption>slide 18</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wrFLwciJ00LNvKAue3XvZQ.png" /><figcaption>slide 19</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ClI5f1up-bzh1_Vaqw4Lcg.png" /><figcaption>slide 20</figcaption></figure><h3>Final wrap-up of presentation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L-CPzW2rkh1gpTZMh5SqBg.png" /><figcaption>slide 21</figcaption></figure><h3>All finished, then what happened?</h3><p>For the record, I am a Google Slides guy when it comes to design presentations, however I was specifically asked not to use Google Suites for this assignment, so I chose PowerPoint.</p><p>I emailed the powerpoint file to the hiring manager a week after our last interview (<em>which we had agreed upon</em>). I did not get the opportunity to actually present the ppt, or voice design decisions in greater detail, or further explain any of my thought processes.</p><p>After a week went by without any updates, I politely reached out to the hiring manager via email, asking if they had any feedback on my assignment, as well as when I should expect to hear the final decision. A few hours go by, then I receive this email from the recruiter:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8J0xZ32zHDQ_gboiJi0Bdw.png" /></figure><blockquote>Hi Andrew,</blockquote><blockquote>I want to follow up regarding your interview and inform you that unfortunately the hiring team is not interested in moving forward. The feedback provided was that the team just didn’t see a strong enough fit for what they need in this role, and the search continues.</blockquote><blockquote>Thanks for taking the time to work with me on this!</blockquote><h3>Wait a second</h3><p>The team decided I wasn’t the right fit for the role, that’s fair. That’s business. That’s life. <strong>I respect their decision at the end of the day.</strong></p><p>After spending roughly 20 hours working on an assignment, I had hoped that I at least would have feedback on how I could improve as a designer or even as an interviewee.</p><p>Maybe I didn’t have enough experience, maybe my personality wasn’t the right fit, maybe I completely misunderstood the assignment, it could literally be a million different things. And that’s what is frustrating by the lack of feedback.</p><p>As a junior designer, I want to grow. I know that I’m going to fail at times, and I know that nothing is given for free. At the end of the day this was a valuable learning experience, and I was grateful that they considered me to this extent.</p><p>Would I do it again? Probably. While the end result was not ideal, I am eager to prove my value to whatever company is considering me. I had hoped that in exchange for my work I’d at the very least walk away with an idea of how I can improve. But I did learn that entering into a completely new industry (in this case, finance) as a junior designer is intimidating, and I have a new kind of respect to all of those who have done it.</p><h3>In argument of the whiteboard challenge</h3><p>After this, I can say with absolute certainty that I favor a whiteboard challenge over a take-home assignment. While it may be intimidating to be put on the spot so to speak, one cannot overlook the value of back-and-forth communication. Additionally, whiteboard challenges typically don’t last more than a few hours, which is much easier to squeeze in when working full-time.</p><h3>What do you think?</h3><p>Do you have any experience with UX take-home assignments?</p><p>Did I miserably fail with mine?</p><h3>Feel free to connect with me</h3><p><a href="https://www.linkedin.com/in/andrew-cox-ux/">https://www.linkedin.com/in/andrew-cox-ux/</a></p><h3>My portfolio</h3><p><a href="https://www.coxandrew.com/">Case Studies | portfolio</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8dcd13a9a79" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/my-entire-ux-take-home-assignment-e8dcd13a9a79">My entire UX take-home assignment</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: Heuristic eval & redesign of Intergy EHR (SaaS)]]></title>
            <link>https://medium.com/design-bootcamp/case-study-heuristic-eval-redesign-of-intergy-ehr-saas-df231d81fe52?source=rss-f837f001860b------2</link>
            <guid isPermaLink="false">https://medium.com/p/df231d81fe52</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <category><![CDATA[heuristic-evaluation]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Andrewcox]]></dc:creator>
            <pubDate>Wed, 29 Jun 2022 18:59:25 GMT</pubDate>
            <atom:updated>2022-07-05T12:55:53.903Z</atom:updated>
            <content:encoded><![CDATA[<h4>Identifying usability issues in Intergy — An Electronic Health Records (EHR) software used every day by thousands of healthcare providers.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KCgkVY8ZBNIuq5kDjC3gdA.png" /></figure><h3>Background</h3><p>In order for a healthcare provider to maximize their time and energy on their patients, they need a system that is intuitive, easy to navigate, and simple — without sacrificing the complexity of valuable chart information.</p><p>I decided to interview multiple healthcare providers, heuristically evaluate Intergy EHR’s charting system for physical therapy, and suggest design improvements.</p><p><em>I participated in this case study individually, all work here was done by me.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4x0UTMI2CijhZT44kAdbLw.jpeg" /><figcaption>Healthcare providers | <a href="https://www.freepik.com/free-vector/team-cartoon-hospital-clinic-staff-masks_18734155.htm#query=vector%20healthcare&amp;position=1&amp;from_view=search">photo credit</a></figcaption></figure><h3>Side notes</h3><ul><li>The interfaces used by healthcare providers are called <strong>EHR or EMR.</strong> (<em>Electronic Health/Medical Records</em>).</li><li>These are typically cloud-based <strong>Software as a</strong> <strong>Service (SaaS) </strong>platforms.</li></ul><h3>Ethnographic Study</h3><ul><li>Nielsen Norman describes <strong><em>lab studies</em> vs. <em>field studies</em></strong> as: <em>the user comes to us</em> versus <em>we go to the user</em> to conduct research.</li><li>In this case, I had the unique opportunity to observe and interact with ‘the user’ in their natural work environment. i.e. healthcare providers using the interface (Intergy EHR) in the outpatient physical therapy setting (my current job).</li></ul><h3>Pain Points</h3><p>After speaking with numerous healthcare providers about their experience with utilizing Intergy EHR for patient documentation, the following 3 pain points stood out the most.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/909/1*ZCeUWbZSDLct5Ucx4yt4Cw.png" /></figure><p><strong>Issue 1:</strong> The present documentation aspect of a “Daily Treatment Note” for a patient is similar to a Word Document. This causes issues when providers only want to edit some details of the document, however are given the opportunity to edit the entire document instead. This inevitably leads to errors and mistakes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wWHfxFlpLa9NIljgk7swmw.png" /><figcaption>Actual Physical Therapy patient encounter note</figcaption></figure><p><strong>Issues 2 &amp; 3</strong> are self explanatory. 😁</p><h3>Heuristic Evaluation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XoRQl9OXEoiOCbqAOSsaQw.png" /></figure><p>The above chart was created to represent the major usability issues within Intergy EHR. I went through each of the 10 usability heuristics for interface design and rated them off of 3 criteria: generally satisfactory, unsatisfactory, or somewhere in between.</p><p>This in conjunction with findings from interviews and field study helped to then determine the next course of action to improve the UX of the system.</p><p><strong>Key Takeaways</strong></p><p>⚡ ️<strong>User control &amp; freedom</strong> — too much control with editing a patient’s daily treatment note.</p><p>❌ <strong>Error prevention</strong> — the current format inevitably leads to documentation mistakes such as editing areas that should stay the same or accidentally deleting important charting information.</p><p>👉 <strong>Recognition rather than recall</strong> — it takes 7 clicks to print a patient schedule. One has to memorize this flow as it is imbedded deep within the software.</p><p>👔 <strong>Aesthetic &amp; minimalistic design</strong> — the present design could be more clearly structured and clean, there is an overall lack of visual hierarchy and the amount of information displayed is overwhelming.</p><h3>Sketching solutions</h3><p>After much reflection and thought, I decided that the best way to present a plethora of data in a organized and accessible manner was to utilize a dashboard interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/1*ZOB3aZgNUj1t8jaT_OpkSw.png" /></figure><p>I showed this sketch to my coworkers and they agreed that this solution was viable. They stated at their previous healthcare jobs the software interface was more akin to a dashboard as well.</p><h3>Designing in Figma — Challenges arise</h3><p>Once I had the basic structure of the dashboard, one obstacle I faced was how to break apart the information in both a meaningful and aesthetic presentation.</p><p>There is a lot of information to be presented, how should it be displayed without looking too busy? How big should each info card be?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/1*7l1XQMKg_D8WKneTuyPbMQ.png" /></figure><p>My solution to this was to divide the workspace (minus spacing) by 3 then begin filling in the information into each atom. Eventually I realized some of the atoms needed to be 2x in length or width as the information was lacking hierarchy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/1*tfatUBRC4qq8YT6hQILF0Q.png" /></figure><h3>First iteration &amp; feedback</h3><p>Below was the first iteration of my dashboard solution. It’s not beautiful, but the information is all there.</p><p>After reviewing it with coworkers and gaining feedback,</p><p><strong>I had a list of areas of improvement:</strong></p><ol><li>The text feels too crammed inside of the cards.</li><li>The gray boxes within the cards feels bland.</li><li>The hierarchy of information feels a little off.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yhWf1nz3RhKrHy35vC5p_A.png" /></figure><h3>Second iteration</h3><p><strong>Points improved</strong></p><ol><li>Typography was adjusted to give text breathing room as well as visual hierarchy.</li><li>White space utilized more appropriately within cards so they didn’t feel so cramped.</li><li>Headings more distinguished from body text, easier to differentiate at first glance.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ydaZuX2tI48bWNk4vCdDoQ.png" /></figure><p><strong>Additional Solution</strong></p><p>It is impossible to display ALL of the important information in the dashboard, so the user has the option to individually expand each card to reveal more details:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oz6o1I4wqilWxWZNZ-hxZw.gif" /><figcaption>Expanding individual cards to reveal more information</figcaption></figure><h3>Addressing all pain points</h3><p>✅ <strong>Notification of patient check-in</strong></p><p>In the present system, if a provider is editing a patient note, and their next scheduled appointment checks in, there is no system in place to notify the provider. The only way to know if a patient checked in is to back out to the main schedule and see the checkmark next to their name (<em>see above image for example</em>).</p><p><strong>Solution</strong></p><p><strong>Breadcrumbs: </strong>dismissible<strong> </strong>notification appears at top of screen that does not obstruct work flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6nqj7trUUCUuoZFxDs3YSA.png" /><figcaption>Dashboard with breadcrumbs at top of screen to notify provider of patient arrival.</figcaption></figure><p>💻 <strong>Printing patient schedule</strong></p><p>In the present system, It takes <strong>7 clicks </strong>to print a provider’s daily patient schedule. Below is an actual screenshot of the word document I created that I give to new-hires when I train them on our system, because no one can figure it out on their own.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vWC87RX8IPNUwExQgbnlOA.png" /><figcaption>Actual word document I created to teach new providers how to print their schedule.</figcaption></figure><p><strong>Solution</strong></p><p>Adding a button in the available space above the patient schedule is not only intuitive and easily accessible, but takes the process from 7 clicks-to-complete to 2 clicks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/693/1*Aem0T1HBNZBMOgB1Yu_zGg.png" /><figcaption>Provider main screen with button to print daily schedule.</figcaption></figure><h3>Final thoughts / Lessons learned</h3><ul><li>With common applications, a UX Designer <em>can</em> make educated guesses on usability issues, however more technical platforms (such as Saas) are much harder gain a read on without speaking directly with the user.</li><li>Heuristic evaluations are a relatively cheap and effective method of quickly assessing major usability issues within an interface.</li><li>While dashboards are an efficient way to present key information, there is certainly a balance between displaying enough information to be useful and simultaneously not overwhelming the user with too much info.</li><li>You likely will not get to the “pretty” solution without first having an ugly solution. (<em>“does the solution solve the problem?”</em> is of greater importance than <em>“does this look pretty?”</em>)</li></ul><h3>Talk to me</h3><p>I’d love to hear your thoughts and opinions!</p><p><strong>Connect with me on LinkedIn</strong></p><p><a href="https://www.linkedin.com/in/andrew-cox-ux/">Andrew Cox - Physical Therapist Assistant - Florida Medical Clinic | LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df231d81fe52" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-heuristic-eval-redesign-of-intergy-ehr-saas-df231d81fe52">Case study: Heuristic eval &amp; redesign of Intergy EHR (SaaS)</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Parallels between UX and PT]]></title>
            <link>https://medium.com/design-bootcamp/the-parallels-between-ux-and-pt-5a04932db163?source=rss-f837f001860b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a04932db163</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Andrewcox]]></dc:creator>
            <pubDate>Sat, 04 Jun 2022 15:30:13 GMT</pubDate>
            <atom:updated>2022-06-06T15:36:09.343Z</atom:updated>
            <content:encoded><![CDATA[<h3>The parallels between UX and Physical Therapy</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*II-OdaUP8w2WVdWLU52bmA.png" /><figcaption>Basic similarities and differences between UX and Healthcare</figcaption></figure><p>I have been working in healthcare as a Physical Therapist Assistant for over 3 years now. I am currently trying to break into the beautiful profession of UX, and have observed that this field overlaps with my personal experiences as a healthcare provider quite remarkably.</p><p>I decided to outline some of my observations of the parallels between my current role in healthcare and the duties of a UX practitioner:</p><ol><li><strong>User-centered design</strong></li><li><strong>Accessibility</strong></li><li><strong>Research methods</strong></li><li><strong>Stakeholders</strong></li></ol><h3><strong>1. User-centered design</strong></h3><p>The first likeness between UX and PT stems down to putting the user (or patient) first when talking about designing solutions. UX practitioners practically have the words “user-centered” tattooed on the back of their hand — it is literally the backbone of the field in its entirety.</p><p>In healthcare, and more specifically Physical Therapy — solutions are created to problems with emphasis on putting the patient first. For example, a patient may present to the outpatient clinic with complaints of back pain when getting out of bed in the morning. To someone with experience in PT, this sounds like a pretty standard patient. Where it gets tricky is tailoring your treatment <em>to that specific patient.</em></p><p>What worked for the last 10 patients with this same presentation may not work for this patient. The PT must spend their resources: time, energy, and thought — with <strong>this individual — </strong>and design their solution accordingly, not base their solution on assumption.</p><p>Similar to a UX designer going into a new project — they may have their own presumptions as to what the best solution is. They may even already have some low-fidelity sketches and ideas before even talking to their product users. But if something is discovered in research and interviews it has to be included. Conversely, if the initial solution doesn’t address all problems, or addresses the wrong problems, it must be improvised.</p><blockquote>When all is said and done, both the UX practitioner and healthcare provider must have their solution accurately reflect the user’s specific needs, which can only be achieved through careful, non-biased information gathering [<em>and testing</em> ;)].</blockquote><h3><strong>2. Accessibility</strong></h3><p>UX design is multi-faceted with its importance often undersold to outsiders such as stakeholders and other departments within an organization. Thanks to the inclusion of the word ‘designer’ in its title, UX teams are often painstakingly misunderstood as merely a team of people trying to make a product look pretty (not to knock graphic designers — this isn’t exactly a walk in the park either).</p><p>The reason why this couldn’t be further from the truth of the job description of a UX designer is that if you sit down with anyone working in UX worth their salt — they will adamantly tell you that designing with appropriate accessibility standards is at the top of the list of importance at any ethical organization.</p><p>The beauty of UXers goes back to the previous section — they love their users. That includes those with visual limitations and other impairments.</p><p>Similarly, healthcare providers rarely perform their jobs well because of the money. Rather, they too love their patients (users). Regarding accessibility, this means that any time I enter a building, I can’t help but meticulously (and often subconsciously) analyze the physical attributes of the layout and ensure it is accessible for everyone.</p><p>If you spent any time with me in public, you will at some point undoubtedly hear me mutter — “How the hell is someone with a wheelchair supposed to get into this building?”</p><p>And now more recently, anytime I visit a website with poor visual contrast, wrong text size, lack of audio options, subtitles, etc — I can’t help but blurt out “who greenlit this s***?!”</p><blockquote>At the end of the day, UXers and Healthcare providers alike never stop thinking about the people they serve.</blockquote><h3><strong>3. Research methods</strong></h3><blockquote><strong>“Design is really an act of communication, which means having a deep understanding of the person with whom the designer is communicating.” — Don Norman</strong></blockquote><p>Oh boy! You thought I was going to talk about UX and leave out one of the arguably most important facets of the team?!</p><p>Research, research, research. Where do I even start?</p><p>Nowadays research in UX is getting a lot more respect and attention (as it should). But for a long time (and unfortunately still in some places) UX team members were kicking and screaming to get more time and resources dedicated to research.</p><p>We know that research in UX is paramount to tailoring a solution that actually address the user’s needs, otherwise we are just designing a best guess.</p><p>In healthcare, the words “evidence-based interventions” were literally hammered into our heads on a daily basis in the classroom, and arguably even more so in the actual field. If a patient with a complex surgery to their shoulder is provided with an intervention outside of a very specific protocol, it could quite literally destroy their $100,000 surgical repair.</p><p>In physical therapy, we describe qualitative data as <em>‘subjective’</em> data and quantitative data as <em>‘objective’</em> data. Every single patient encounter has these two subsections that are updated at every visit. Without data collection, we are designing a treatment that is at best, a best guess.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yjAFh3Ee6GlVSZcNASOWZA.png" /></figure><p><strong>In-depth interviews — </strong>Both UX and Physical Therapy include the utilization of semi-structured interviews to gain user insights, pain points, and opportunities for improvement. This is arguably the biggest parallel between these fields, as one cannot design an effective solution without understanding the individual first.</p><p><strong>Benchmarking —</strong> Both fields require validation and justification for the present strategy to solve the user’s problem.</p><p>In UX, this includes measuring metrics such as: time spent on a given task, conversion rate, success rates, etc.</p><p>In the same vein, Physical Therapy providers measure quantitative data and compare it to previous data points with tests such as: Timed Up and Go test, Manual Muscle Testing, Berg balance scale, etc.</p><blockquote>Without measuring the effectiveness of the present system (whether it’s an interface or treatment approach), solutions are merely hypotheses.</blockquote><p><strong>A/B testing — </strong>When creating solutions to complex problems, one inevitably will reach a point where multiple solutions seem viable.</p><p>In User Experience, this could mean having 2 potential landing pages, 2 different home-screens for an app, different wording in a button, the list never ends.</p><p>Here’s and example — an e-commerce website, 2 carousels — 1 with a CTA, and 1 without. A team of researchers may go live with each version as a trial-run then gather data such as conversion rate, time spent on page, heatmapping, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XoYD_tlNzkPa9MlGmHAqZw.png" /><figcaption><strong>Top: </strong>carousel with CTA. <strong>Bottom:</strong> carousel without CTA.</figcaption></figure><p>In physical therapy, let’s say we have a young patient with a diagnosis of low back pain. The PT provider may try an entire treatment with flexion-biased exercises (<em>bending forward</em>) and then compare it to another treatment with extension-biased exercises (<em>extending backward</em>). They will gather qualitative data (<em>how do you feel now?</em>) and quantitative data (<em>such as pain rating scale</em>) and compare to two solutions — then proceed with the approach with the most <strong>measured success</strong>.</p><blockquote><strong>The only way to determine the best path forward is to put your possible candidates head to head.</strong></blockquote><h3>4. Stakeholders</h3><p>Last but not least, we have the lovely stakeholders.</p><p>According to the <a href="https://www.nngroup.com/articles/stakeholder-analysis/#:~:text=A%20stakeholder%20is%20anyone%20who,organization%20or%20external%20to%20it.">Nielsen Norman Group</a>,</p><blockquote>A stakeholder is anyone who has interest in your project or with whom you need to work with in some way to complete the project.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oS-LsXJoJtiHxIrpoU6A0Q.png" /></figure><p><strong>Product Manager vs. Physician</strong> — In UX, the PM bridges the gap between creative design and business goals. They generally focus on the big picture and ensure that product development is heading in the right direction.</p><p>Similarly in healthcare, patients typically have a primary care physician who takes responsibility for the comprehensive care plan of a patient.</p><p>Both of these roles are powerful individuals and you want to stay on their good side. How does one do this? Communication. If a feature the design team is working on has a bug that seems unfixable, or a patient suddenly has a change in their health status — that information must be effectively relayed in a timely manner.</p><blockquote>There is a hierarchy for a good reason in any organization. The clearer the communication among the rungs of the org, the more the end user (<em>or patient</em>) benefits.</blockquote><p><strong>Appeasing stakeholders </strong>— There are times in both industries where you have to take a step back and make sure that you are putting the time and effort into establishing rapport with your stakeholders.</p><p>Sometimes that means explaining exactly what your job entails, relaying expectations, and finding common ground. Other times it means sacrificing a little bit of your sanity to make sure that there are no conflicting priorities or unforeseen changes of scope.</p><p>In UX, this may transfer to sharing new research findings in a project, even if they contradict the hard work that you’ve put in up to that point. In healthcare, it may transfer to updating patient family members on their progress (or lack thereof) with their plan of care.</p><blockquote>Either way, while entertaining stakeholders may feel like one of the not-so-glamorous parts of the job, it safeguards your survival, and protects your team as well.</blockquote><h3>Wrap up</h3><p>There you have it, 4 parallels between serving as a healthcare provider and practicing as a UX professional. These are just some of the similarities I have observed, but the true list is far more extensive.</p><p>I’d appreciate any feedback, or even your own personal experiences if you are a UXer who previously worked in another industry!</p><h3>Talk to me</h3><p>I am currently looking to break into UX and would love to talk or connect with you.</p><p><a href="https://www.linkedin.com/in/andrew-cox-ux/">Andrew Cox - Physical Therapist Assistant - Florida Medical Clinic | LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a04932db163" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-parallels-between-ux-and-pt-5a04932db163">The Parallels between UX and PT</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hello, welcome to my portfolio.]]></title>
            <link>https://medium.com/@andrewcox514/hello-welcome-to-my-portfolio-23a3967e5a08?source=rss-f837f001860b------2</link>
            <guid isPermaLink="false">https://medium.com/p/23a3967e5a08</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-portfolio]]></category>
            <category><![CDATA[portfolio]]></category>
            <dc:creator><![CDATA[Andrewcox]]></dc:creator>
            <pubDate>Mon, 23 May 2022 09:46:18 GMT</pubDate>
            <atom:updated>2022-07-18T17:30:05.333Z</atom:updated>
            <content:encoded><![CDATA[<h3>Andrew Cox UX Portfolio</h3><p>Portfolio website: <strong>coxandrew.com</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/332/1*gEMakTZ6s0AHQ7_ZCZ9iAg.png" /></figure><h3>My work</h3><ul><li><a href="https://bootcamp.uxdesign.cc/designing-a-health-app-that-gets-results-a-ux-case-study-c4e3abc8151c">Case Study: Designing a health app that gets results</a></li><li><a href="https://bootcamp.uxdesign.cc/conversion-from-freemium-to-premium-a-ux-case-study-81d98dc14fb6">Case study: conversion from freemium to premium</a></li><li><a href="https://medium.com/@andrewcox514/case-study-heuristic-eval-redesign-of-intergy-ehr-saas-df231d81fe52">Case study: Heuristic eval &amp; redesign of Intergy EHR (SaaS)</a></li><li><a href="https://bootcamp.uxdesign.cc/improving-the-dog-adoption-process-ux-case-study-28c4ec6f13b7">Case study: Improving the dog-adoption process</a></li></ul><h3>About Me</h3><p>I love nature, neuroscience, and pancakes.</p><p><strong>I have a gift of story-telling and an avidity for solving problems through research, understanding, and design.</strong></p><p>I am driven by the desire to help people, and became attracted to this field when I discovered it bridges empirical research with creative design.</p><p><strong>I have a background in Engineering</strong> and have always had an affinity for complex problem-solving, however I learned over the years that <em>I particularly am attracted to psychological principles, creative design, and understanding people.</em></p><p>I went into healthcare because I knew I wanted to help people.</p><p><strong>Then I discovered UX</strong> — the perfect synchronicity between understanding/helping others and creative design.</p><h3>Lets Connect</h3><p>LinkedIn: <a href="https://www.linkedin.com/in/andrew-cox-ux/">https://www.linkedin.com/in/andrew-cox-ux/</a></p><p>Email: A.cox514@yahoo.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23a3967e5a08" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: conversion from freemium to premium]]></title>
            <link>https://medium.com/design-bootcamp/conversion-from-freemium-to-premium-a-ux-case-study-81d98dc14fb6?source=rss-f837f001860b------2</link>
            <guid isPermaLink="false">https://medium.com/p/81d98dc14fb6</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Andrewcox]]></dc:creator>
            <pubDate>Fri, 20 May 2022 10:26:14 GMT</pubDate>
            <atom:updated>2022-06-10T17:55:46.212Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="5 key high-fidelity screens from end of project" src="https://cdn-images-1.medium.com/max/1024/1*fAfeCi6hXmpSeSLNVPkUKQ.png" /></figure><h3>Case study: Conversion from freemium to premium</h3><h3>Intro</h3><p>This case study revolved around enhancing the conversion process of a successful mobile-media product for a fictitious startup company.</p><p>The product has been operating as a free service for 2 years, and the company now is planning to rollout a paid Premium model.</p><p><em>This was an independently performed case study: I was solely responsible for research, design, and user testing. All designs and prototypes were made in Figma.</em></p><p><strong>Business Goals</strong></p><p>The organization hopes to facilitate a profitable revenue stream by delivering a paid product with enhanced features that <strong>incentivize users to pay the subscription fee</strong>. The given goals for this scenario included:</p><ol><li>Create a sign-up/registration flow that incentives users to subscribe to the Premium product.</li><li>Create opportunities for existing users to convert to Premium both in the sign-in flow as well as within the product.</li></ol><p><strong>Starting Point</strong></p><figure><img alt="Initial mobile wireframe screens given at start of project: sign up, homescreen, play content." src="https://cdn-images-1.medium.com/max/1024/1*gF8j-2BAux5xqcP2Hr5_tA.png" /><figcaption>Basic low-fi wireframes were given as a base to begin this project</figcaption></figure><p>At the beginning of this project, I was given the above low fidelity designs that the platform has been implementing for the past 2 years. The existing sign-in, sign-up, and general interface had no CTAs to convert users to Premium services.</p><p>Additional details given at the beginning of the project included the target user base and company brand:</p><figure><img alt="Chart outlining user base and brand characteristics." src="https://cdn-images-1.medium.com/max/870/1*ZInbuSnDrvQ2Ots8_2TlNA.png" /></figure><p>From this information, I designed a simple Style Guide to use as inspiration as well as maintain consistency throughout the design process.</p><figure><img alt="Style Guide with Typography, Brand Attributes, and Brand Colors." src="https://cdn-images-1.medium.com/max/1024/1*GV_R8-w--aELBhd2KaIxEQ.png" /></figure><p>Color palette — I decided that a dark-mode application (<em>with some pizzazz</em>) best fits the user needs and the brand. From both research and personal usage, dark-mode is the favorable choice in streaming platforms because it limits eye-strain and the emphasizes the content itself.</p><p>Typography — I felt that Lora and Nunito balanced with each other well for this particular brand — Lora, a serif font (smart, bold) meets Nunito, a sans serif font (hip, fun).</p><p>Logo / loading screen — I additionally designed the below logo and loading screen to inspire the remaining high fidelity screens that would follow after wireframes and user-testing.</p><figure><img alt="Loading mobile screen with brand logo." src="https://cdn-images-1.medium.com/max/228/1*79KD40I_8bkuc9HIufcq6Q.png" /></figure><h3>Research</h3><p><strong>Secondary research</strong></p><p>Before jumping straight into designing solutions that addressed business goals, I spent some time reviewing existing media platforms that already have successful Subscription models. The primary questions I wanted to answer were:</p><blockquote>What current approaches are already being utilized for conversion from freemium to paid services?</blockquote><blockquote>Can current approaches be modified or improved to meet this particular company’s needs?</blockquote><p>The below competitor analysis was designed by myself to fully visualize solutions implemented by Spotify, YouTube, and Pandora — companies who have had a plethora of time and resources spent thinking about these problems.</p><p><strong>Competitor Analysis</strong></p><figure><img alt="Outline of competitor analysis including a list of important notes and takeaways from their conversion process for Premium memberships." src="https://cdn-images-1.medium.com/max/1024/1*DHuf-LTXnqoU4C-8N_k_Lg.png" /><figcaption><a href="https://drive.google.com/file/d/12s7HT6NQX8-JsOSZxIHiHJjOyePLCAtH/view?usp=sharing">link to higher resolution</a></figcaption></figure><p>Some interesting takeaways from this analysis were:</p><ol><li>None of the big industry leaders above included CTAs for Premium subscription in their sign-up flows.</li><li>All 3 companies had occasional pop-up modals that nudge users into upgrading to Premium.</li><li>A common theme <em>teeters</em> on the use of dark-patterns — user is given the illusion of a feature, then upon attempt to use said feature they are met with an opportunity to upgrade to Premium instead.</li></ol><p><strong>Primary Research</strong></p><p>After gaining some insight into present solutions, I conducted 1-on-1 interviews with participants who met the company audience criteria. I wanted to better understand what motivates people to actually pay for premium services.</p><p>At this point I had a good amount of information but wasn’t quite sure how to express it and connect the dots. Qualitative Findings were then clustered which helped me identify patterns and trends gained from the 1-on-1 interviews.</p><p><strong>Data Clustering</strong></p><figure><img alt="Sticky notes organizing different ideas and conclusions from user interviews." src="https://cdn-images-1.medium.com/max/1024/1*-LEbd3PZYZi4MUxV2ZvklA.png" /></figure><p>Key takeaways found from interview sessions are outlined below:</p><figure><img alt="Additional list of takeaways from user interviews." src="https://cdn-images-1.medium.com/max/1024/1*006tVP8dlWB_xLqBz-yY3g.png" /></figure><p><strong>Journey Map</strong></p><p>To better visualize the existing user experience and identify pain-points (as well as opportunities to improve navigation and outcomes) I drafted the below Journey Map.</p><p>This specific method was chosen because it helps hone in on the least enjoyable moments when interacting with the platform — these low points are great places to give the user the opportunity to avoid them in the future.</p><p>I used <a href="https://www.nngroup.com/articles/journey-mapping-101/">this article</a> about Journey Mapping from the Nielsen Norman Group as a reference and guide.</p><figure><img alt="Journey map outlining user feels and thoughts throughout process of using media-streaming apps." src="https://cdn-images-1.medium.com/max/991/1*tliG7VVw3rmS64K2bTco6w.png" /></figure><p><strong>User Flows</strong></p><p>After ascertaining places that the user might become frustrated and other instances to input calls-to-action, the following user flows were created to address the exact business goals outlined at the beginning of this project.</p><p>These user flows helped ensure that there were no missed steps along the user path with signing in, signing up, and using the platform as an existing user.</p><figure><img alt="User flow chart" src="https://cdn-images-1.medium.com/max/1024/1*GjJdae2XB6L_ihF07i32DA.png" /></figure><figure><img alt="flow chart" src="https://cdn-images-1.medium.com/max/1024/1*vI8TQBH9TLsd3_FuO1qcyA.png" /></figure><p><strong>Persona</strong></p><p>The last step taken after conducting research was designing a quick Persona of the average user of this platform to help empathize with this specific user-base and maintain focus on who exactly we are designing for (I myself did not fall into the brand’s “target user”)</p><figure><img alt="Persona of average user" src="https://cdn-images-1.medium.com/max/1024/1*jrLCz9LHfoAUiwZ27W4Cug.png" /></figure><h3>Initial Wireframes</h3><p>Once I felt that I had a wholistic viewpoint and comprehensive understanding of the company platform, its user-base, and its goals — I was confident to start designing wireframes that could satisfy both company and user needs.</p><figure><img alt="Initial wireframes designed for this project." src="https://cdn-images-1.medium.com/max/1024/1*2thouTCQh0zHLtcTQVS0pQ.png" /><figcaption><a href="https://drive.google.com/file/d/1kZo0EyycH67yiZ09W9mBHOUiWcOJN4qZ/view?usp=sharing">link to higher resolution</a></figcaption></figure><p>While designing the above wireframes, I frequently reviewed my notes from the 1-on-interviews to make sure my solutions addressed wants/needs as well as pain points and concerns.</p><ol><li>Sign up flow — while the industry giants themselves did not have a “solution” to this, it was still a task that was asked from the Project Manager. This was relatively simple in the context of the sign-up flow, however later on you will see that I found an additional opportunity to add a CTA in this first flow.</li><li>Sign-in flow (returning freemium user) — I did not want to harass and bother the existing loyal users by all of a sudden limiting and diminishing their experience. The solution here was to automatically give all existing users a free month without any credit card required.</li><li>CTAs within freemium — for users who chose not to upgrade to Premium, the solution here was inspired from Spotify — allow users to freely use app, however the user eventually runs into edge cases (such as downloading music for offline listening) that are restricted to Premium services. User then has call to action to upgrade or dismiss pop-up message.</li></ol><h3><strong>1st Round of Testing</strong></h3><p>Once preliminary wireframes were finished, usability testing was conducted to see how these solutions played out, and if there were any errors or new ideas that could be smoothed out before time and resources were spent designing higher-fidelity screens.</p><p>Participants were given the following tasks to complete while thinking aloud as they went:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*MKNaxre_nrL-UTqZhh_3cg.png" /><figcaption>list of tasks from usability test</figcaption></figure><p>Participants in the usability test were able to complete each task without any significant errors or concerns. Some notes from testing (below) that stood out included:</p><ol><li>1 free month to returning users without credit card was well-received.</li><li>Inclusion of edge cases was “a little sneaky” but participants understood why they were included.</li><li>Non-intrusive banners and raffle contests were seen as positive incentives that did not interrupt UX.</li><li>There was heavy emphasis on ease-of-pay: being able to upgrade within app (Spotify doesn’t have this feature) and use of Apple Pay for convenience.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O-XmlL8eLCXUni4jgJVXqA.png" /><figcaption>notes added to wireframes from usability testing</figcaption></figure><h3><strong>High Fidelity Screens</strong></h3><p>After making a few small changes that reflected the above discoveries from usability testing, high fidelity frames were designed.</p><p>While designing the sign-up flow and considering notes gathered, I discovered an additional opportunity to incorporate a CTA for premium service [4th frame in top row]. Informing users of why their birthdate was needed served as a good opportunity to illuminate Premium Perks during their birth month.</p><figure><img alt="high fidelity mobile screens" src="https://cdn-images-1.medium.com/max/1024/1*MY5Jc3EA0GtKDADp9pXLtw.png" /><figcaption><a href="https://drive.google.com/file/d/1ExTH4vorehhMHJieJu_MIkQp2KjZ9Aba/view?usp=sharing">link to higher resolution</a></figcaption></figure><h3>Prototype &amp; Re-Testing</h3><p>The next step was to create a Prototype in Figma. To keep things simple and consistent, I was able to use the same usability test script from the first round of usability testing.</p><p><a href="https://imgur.com/hOjoGEq">Link to usability test script</a></p><p>This round of usability testing results were more reflective of input on the user interface and overarching design of the platform rather than the previous lower-fidelity usability tests which more so emphasized the user paths and flows.</p><p>Participants again were able to complete the given tasks with relative ease. Thinking aloud as they went along their process gave insight into design choices and gave feedback as to what can be visually improved.</p><ol><li>One item that was quickly revealed was that there was a lack of success screens. Taking the time to design these screens contributed to a more wholesome and enjoyable user experience.</li></ol><figure><img alt="high fidelity mobile screens — success screens" src="https://cdn-images-1.medium.com/max/1024/1*aqwoxoM7RdqTbzf7Q7dOfg.png" /><figcaption>Success screens for each of the membership options</figcaption></figure><p>2. It was discovered that the sign-in flow did not have a recovery option for forgotten username or password (below, left).</p><figure><img alt="High fidelity mobile screens — updates included after usability testing" src="https://cdn-images-1.medium.com/max/1024/1*pEDqjwDwz2eBdSKw69f7eg.png" /></figure><p>3. The first “Premium Perks” screen was noted by one participant as ‘forgettable and lacking something.’ This screen was redesigned to better capture the attention of users in the sign-up flow (above, right).</p><figure><img alt="Screenflow of prototype" src="https://cdn-images-1.medium.com/max/337/1*s9ngeFLoJxpP8H-2ul-lMQ.gif" /><figcaption>Sign-in flow with Call To Action</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2Flr3WnreAOvCXtxp3Ux1XUS%2FCapstone-2-hifi-screens%3Fpage-id%3D0%253A1%26node-id%3D2%253A701%26viewport%3D709%252C-190%252C0.25%26scaling%3Dscale-down%26starting-point-node-id%3D2%253A660&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2Flr3WnreAOvCXtxp3Ux1XUS%2FCapstone-2-hifi-screens%3Fpage-id%3D0%253A1%26node-id%3D2%253A701%26viewport%3D709%252C-190%252C0.25%26scaling%3Dscale-down%26starting-point-node-id%3D2%253A660&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2F787412aa-1023-45af-9382-27f3836ff00c%3Fheight%3D450%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/275e05a269a5917f5048a0298db4ef46/href">https://medium.com/media/275e05a269a5917f5048a0298db4ef46/href</a></iframe><h3>Final Thoughts &amp; Lessons Learned</h3><ol><li>Dark Patterns can have a definitive place in design if used appropriately and not obnoxiously.</li><li>There is a delicate balance in conversion tunnels between bothering the userbase versus nudging them in the right direction.</li><li>It is possible to limit availability of features without completely ruining the user experience for free users (you never know who may eventually become a paying user, and do not want to lower your retention rate).</li><li>Users value simplicity &amp; convenience, and are more likely to make financial decisions when Calls To Action are tactful and non-intrusive. i.e. the less they have to think, the more likely they will upgrade (<em>Amazon’s ‘Buy Now’ 1-click purchase is a good example of this</em>).</li></ol><p>If more time and resources were allocated to this project — I would have enjoyed designing:</p><ul><li>screens educating users on the sharing of revenue with content creators (<em>an insight from 1-on-1 interviews)</em>.</li><li>a feature for Premium users where they could download ‘Celebrity Playlists’ (<em>ex. Rhianna&#39;s personal favorites playlist</em>).</li><li>a process in which Premium members can leave comments on songs and playlists.</li></ul><h3>Contact</h3><p>Feel free to reach out to me on LinkedIn!</p><p><a href="https://www.linkedin.com/in/andrew-cox-ux/">Andrew Cox - Physical Therapist Assistant - Florida Medical Clinic | LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81d98dc14fb6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/conversion-from-freemium-to-premium-a-ux-case-study-81d98dc14fb6">Case study: conversion from freemium to premium</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: Improving the dog-adoption process]]></title>
            <link>https://medium.com/design-bootcamp/improving-the-dog-adoption-process-ux-case-study-28c4ec6f13b7?source=rss-f837f001860b------2</link>
            <guid isPermaLink="false">https://medium.com/p/28c4ec6f13b7</guid>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[google-ventures]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[design-sprint]]></category>
            <dc:creator><![CDATA[Andrewcox]]></dc:creator>
            <pubDate>Mon, 11 Apr 2022 20:37:57 GMT</pubDate>
            <atom:updated>2022-06-09T10:04:45.465Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jPRCOVzPtCJjS6ZP9jbsOw.png" /><figcaption>Landing page for final design of prototype</figcaption></figure><h3>Introduction</h3><p>This case study is a modified Google Ventures Design Sprint, where an Agile approach was taken to identify and solve UX issues quickly and efficiently in a 5-day process.</p><p><strong>Scenario:</strong> CityPups is a (<em>fictitious</em>) new startup that wants to help people living in cities find the perfect dog to adopt. They are a 3rd party company that finds dogs from organizations/shelters. The design constraints given were that the solution must be a desktop or web app.</p><p>The project begins after CityPups has taken the liberty of performing research, interviewing participants, and creating a persona — Ellie — a 27 year old living in NYC who lacks confidence that she’ll find the right fit for her situation.</p><h3>Day 1 (Understand/Map)</h3><p><strong>Problem: </strong>Through research and interviews, CityPups determined that people living in cities struggle to find the right dog to adopt due to their unique needs.</p><p><strong>CityPups Goals:</strong></p><ul><li>Increase adoption rate</li><li>Happier owners (customer satisfaction)</li><li>Better “forever” homes for the dogs (decrease dissatisfaction/return rate)</li></ul><p><strong>Research Synthesis:</strong> Below is a chart I created that helps visualize 4 areas of concern that interview participants commonly mentioned:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/803/1*rhn_ZSRYWu1uF0oEHrVdLQ.png" /><figcaption>Considerations based off of user interviews.</figcaption></figure><p><strong>Pain Points</strong></p><p>After carefully listening to participant interviews and watching usability testing with CityPups’ original prototype, pain points in the user journey were identified:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/776/1*gfD4u2WtbHzKUSqSnJtvAQ.png" /></figure><p><strong>User Map</strong></p><p>After much consideration and review of research synthesis, the following user map was designed as a quick and efficient ideation for an end-to-end experience that both addresses the user’s needs and mitigates pain points.</p><p>The reason this approach was taken was to minimize total time (cost) spent understanding the customer journey while still putting myself in the user’s shoes enough to relate to their struggles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*HOAfRxevaUAowwlzydBUiA.png" /></figure><h3>Day 2 (Solution sketch)</h3><p>After identifying key pain points and creating a user map as a framework, day 1 was in the books and day 2 was spent performing a solo version of a lightning demo (competitor analysis) and then ideating physical solutions.</p><p><strong>Lightning demo</strong></p><p>To better understand how other organizations have solved a problem similar to CityPups scenario, a quick round of searching the internet was performed to see existing solutions and improvise them to solve our own problems.</p><p>In the problem CityPups is attempting to resolve, the user has a specific desire (dog), wants to search a website to find it, and be presented with choices that match their specific needs. 3 existing products who excel at this are: Care.com, Tinder, and Apartments.com; all exist to match users to a specific goal (<em>babysitter, partner, home, respectively</em>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oCzOoDBEoYa7hpM5m57wTw.png" /></figure><p><strong>Crazy 8’s</strong></p><p>Based off of existing solutions, the crazy 8’s method was used to ideate the most critical screen users would be utilizing for the CityPups platform.</p><p>This approach was used again for consideration of time (respecting the nature of a design sprint): by quickly ideating solutions to the above user map &amp; pain points without harping too much on making it look pretty, a balance was achieved of creating an effective yet resourcefully-conservative solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/926/1*orGJXfmZjI63avc8zkRjZw.png" /><figcaption>Crazy 8’s exercise — 1 minute per box</figcaption></figure><p><strong>Solution sketch</strong></p><p>After deciding which screen in the above crazy 8’s was best suited to serve as the critical screen for the CityPups prototype, the screens immediately preceding and following the critical screen were sketched to obtain a more well-rounded idea of how can strengthen the user experience of this solution.</p><p>The critical screen (center, below) that was chosen was inspired by the solution commonly seen in dating apps. The user journey of adopting a pet is not far removed in commonality from the way we date in the 21st century. So naturally, a user would want to filter their ideal match before-hand, then see their “best matches.”</p><blockquote>I felt that seeing one match at a time would particularly make the overall experience more intimate for the user.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/982/1*NrQuGIOlzLbvkqgpBAOayg.png" /><figcaption>solution sketch flow — user edits preferences &gt; recommended match &gt; call to action (schedule visit)</figcaption></figure><h3>Day 3 (Decide/Storyboard)</h3><p>Now that we understand the user’s needs and have a preliminary idea of the salient user flow, day 3 was spent creating a storyboard to help fully visualize the user journey and potentiate low-fidelity solutions that can be quickly turned into a functioning prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wnd21QjGwXtQjgLJyyzTcw.png" /></figure><p>Considerable attention was paid to the pain points discovered in day 1 when drafting the above solution. The following are hypotheses that I hoped to validate with user testing:</p><ul><li>Personally editing choices [<em>size, age, energy levels, etc.</em>] eliminates the burden of choices that don’t align with the user’s needs (saves time).</li><li>Users will have increased confidence that they found the right fit (more details specific to dog).</li><li>Optimum end-to-end experience — appointment scheduler included in user interface minimizes cognitive load, which should increase usability.</li></ul><h3>Day 4 (Prototype)</h3><p>Before testing the aforementioned hypotheses, I had to swiftly design a rough prototype that could be utilized to validate my design choices and assess how well my solution addressed CityPups goals and objectives.</p><blockquote>The software I chose to use for this prototype was Figma. The reason Figma was best suited to create a prototype is the utility of UI kits concomitant with the built-in prototype feature, so everything could promptly be done in one place, which saved lots of time and energy.</blockquote><p>I decided while creating this prototype that the user could potentially have more control and freedom (heuristic assessment) if given the choice to edit preferences<strong><em> </em>[user flow #1]</strong> OR answer questions <strong>[user flow #2]</strong>.</p><p>Why? Some users might want to have tailored results, however they may lack confidence in what they actually want or need; By having the option to answer questions, those users now have a sense of assurance that they are being matched with a good fit!</p><p><strong>User flow #1</strong> — <strong>Individually select preferences &gt; recommendation</strong></p><p><em>(better for users who want more specificity, know exactly what they want)</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jgLZnu7XAIAVKGZ5HU5Mow.gif" /></figure><p><strong>User flow #2 — Answer questions &gt; recommendation</strong></p><p><em>(better for users who aren’t exactly sure what they want).</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mkeL1kmGb1ZCYCFUokR8Zg.gif" /></figure><p><strong>Full Prototype</strong></p><p>Here is the fully functioning prototype if you would like to try it for yourself!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FB30kD16FIAZOikGyDUj6is%2FCityPups%3Fpage-id%3D0%253A1%26node-id%3D2%253A48%26viewport%3D249%252C48%252C0.25%26scaling%3Dscale-down%26starting-point-node-id%3D2%253A48&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FB30kD16FIAZOikGyDUj6is%2FCityPups%3Fpage-id%3D0%253A1%26node-id%3D2%253A48%26viewport%3D249%252C48%252C0.25%26scaling%3Dscale-down%26starting-point-node-id%3D2%253A48&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2F66fe0e6b-0f95-4267-b06c-4ba4252cc179%3Fheight%3D450%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/67ead32de1e07e8b4ee599150c36d286/href">https://medium.com/media/67ead32de1e07e8b4ee599150c36d286/href</a></iframe><h3>Day 5 (Test/Validate)</h3><p><strong>Testing Begins: </strong>After performing some dry runs through my prototype and ensuring that the red routes were functioning correctly, it was time to test the interface with 5 participants.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/671/1*fPU4JOYBwrNIAxRKELhs1w.jpeg" /><figcaption>Snapshot from usability testing (permission granted from participant)</figcaption></figure><p>These interviews were structured using Google Ventures 5 Act Interview as a loose framework to abide by. Participants were encouraged to think aloud as they walked through each step of the prototype, with reassurance that any critical input is valuable, and that no feelings would be hurt.</p><p><strong>Participants</strong></p><p>The participants in this user testing consisted of coworkers and friends I inquired who most closely fit the description of the user base of CityPups, ie. individuals who have personally been through the process of adopting a dog or who would be interested in the prospect of adopting a dog.</p><p>Those who have never owned a dog or were uninterested in the adoption process were not included in user testing. Below are some characteristics of the 5 individuals who agreed to participate:</p><blockquote>Jeremiah — 22 y/o, male, lives in a house (near city) with family, owns a dog.</blockquote><blockquote>Heather — 46 y/o, female, lives in a house (rural area) with family, owns a dog.</blockquote><blockquote>Brain — 30 y/o, male, lives in an apartment (in city), does not presently have a dog, but has a family dog at parent’s house. Interested in future adoption.</blockquote><blockquote>Keira — 27 y/o, female, lives in an apartment (near city), no present dog but grew up with a family dog, interested in future adoption.</blockquote><blockquote>David — 50 y/o, male, lives in a home (suburbs), owns 3 dogs.</blockquote><p><strong>Key Takeaways</strong></p><p>Usability testing with this prototype was relatively straight-forward; each of the 5 participants were able to successfully perform the given task of “find a dog based off of your individual preferences and schedule an appointment to meet them” without any redirection, assistance, or hints.</p><p>Regarding the initial pain points noted from user interviews on day 1 of this sprint, participants in the prototype usability testing did not air the same concerns.</p><blockquote>Participants reported they particularly liked the idea of filtering their preferences then having a system that matches them to dogs.</blockquote><p>There was some critique by participants regarding the UI of the initial prototype, which was to be expected considering the limited time constraints under the design sprint pressures and parameters. One critique was that the UI felt too powerpoint-esq. A few hours were spent after the testing phase to address this and reorganize the prototype interface. If given additional time, this is something that would be even further addressed.</p><p><strong>Last notes / Lessons learned</strong></p><p>If more time and energy was to be allotted to this project — I would further develop the interface for users who would prefer to see all dogs at once, then incorporate a filter that eliminated choices from the pool of results. Additionally, I would like to further design a user-flow that allows users to speak to a real-time expert (this could be AI as well).</p><p>This project certainly proved valuable to understand the principles and procedures of a Design Sprint approach to solving UX issues in a practical scenario. One aspect of this process I particularly enjoyed was that each day built off of the previous day’s work — this compartmentalized approach lends structure without limiting intuitive creativity — still allowing freedom to make non-linear changes.</p><h3><strong>Connect with me</strong></h3><p><a href="https://www.linkedin.com/in/andrew-cox-ux/">Andrew Cox - Physical Therapist Assistant - Florida Medical Clinic | LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28c4ec6f13b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/improving-the-dog-adoption-process-ux-case-study-28c4ec6f13b7">Case study: Improving the dog-adoption process</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Designing a health app that gets results]]></title>
            <link>https://medium.com/design-bootcamp/designing-a-health-app-that-gets-results-a-ux-case-study-c4e3abc8151c?source=rss-f837f001860b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4e3abc8151c</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[Andrewcox]]></dc:creator>
            <pubDate>Tue, 22 Mar 2022 10:51:52 GMT</pubDate>
            <atom:updated>2022-06-13T13:49:51.705Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case study: Designing a health app that gets results</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1kCiv-6Uw3HLrc_B9E-1Ow.png" /></figure><h3>My Role</h3><ul><li>I was solely responsible for the creation of this entire project: conduction of research, user interviews, and designing all of the content below.</li><li>Duration: 3 months</li><li>Platforms used: Figma, Miro</li><li>Springboard Capstone — weekly 1-on-1 mentor calls with industry expert (previously of Spotify and LinkedIn) where I was given critique and feedback.</li></ul><h3><strong>Problem Space</strong></h3><p>It’s 2022, most of us have unbounded access to information and resources around health, <em>yet we have a dire health crisis</em>. According to the CDC, 1 in 4 deaths in the U.S. are caused by heart disease.</p><p>Technology has been a paramount transition in the timeline of humanity, yet it is clear that we haven’t yet figured out how to maximize its potential for our own advantage when it comes to health.</p><p><strong><em>Where are we falling short when it comes to the bridge between tech and health?</em></strong></p><h3><strong>Secondary Research</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/803/1*TdazkI_gligB0j-VATJaHA.png" /></figure><p><strong>Takeaway</strong></p><p>There is a large body of people who are interested in improving their health, especially in a time where your health could determine how well you fight off viruses such as COVID-19. The current systems in place have failed us, and people are turning to themselves and apps like MyFitnessPal, Nike Run Club, and the Apple Health App.</p><p><strong>Questions to answer with primary research</strong></p><blockquote>How do people define health?</blockquote><blockquote>What are people’s primary goals and motivations when it comes to health?</blockquote><blockquote>What products are people using or have tried to use to change their health?</blockquote><blockquote>Where are the pain points or obstacles with current platforms and applications that already exist?</blockquote><blockquote>What are the most common setbacks and obstacles people face with their health?</blockquote><h3>Primary Research</h3><p>With a more comprehensive idea of what questions there were to answer, the next step was to conduct 1-on-1 user interviews.</p><p>The goal — gain an understanding of what motivates people to change their health, what products they are using or have tried to use to improve their health, and what obstacles/pain points they encounter.</p><p><strong>Participants</strong></p><ul><li>n=5</li><li>Age 18–70</li><li>Interested in health [current interest or desire to change]</li><li>Fair familiarity with using smartphones, tablets, computers</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/1*ZsAJD1fC2Z3-WSeZI5LpRg.png" /></figure><p><strong>Key Findings</strong></p><blockquote><strong>Users overwhelmed with possibilities</strong> - Too much to keep track of. End up forgetting to check their apps.</blockquote><blockquote><strong>Users want to not feel intimidated</strong> - Incorporate different goals for different user levels — beginner/novice/advanced. Motivation driven by achieving goals and obtaining rewards.</blockquote><blockquote><strong>Users want to address all aspects of Health</strong> - Incorporate component of the psyche. Users want deeper meaning.</blockquote><blockquote><strong>Users want to feel connected to a like-minded community</strong> - Motivated by family and friends; Friendly competition.</blockquote><h3>Research Synthesis</h3><p>After user interviews were conducted, the new found information was processed into an affinity map, empathy maps, and JTBD framework to help visualize and organize data as well as better empathize with the user-base.</p><p><strong>Affinity Map</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hHIFWePpy-z15v-dR4FldQ.png" /><figcaption><a href="https://i.imgur.com/6secoVB.png">Link to full-sized picture</a></figcaption></figure><p><strong>Empathy Maps</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eVt5VKvMwUHg8hZlDLTGJA.png" /><figcaption><a href="https://i.imgur.com/tiZpxHI.png">Link to full-sized picture</a></figcaption></figure><p><strong>Jobs To Be Done</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/805/1*H6sRChEO-4TbjpsZvGDLHw.png" /></figure><h3>Ideation</h3><p>Once the key take-aways from the user base were better understood, early sketches were created to begin an attempt to solve pain points and ship a product that performs the tasks users need. HMW statements were used in this process to keep early designs focused on specific tasks:</p><p><strong>How Might We</strong></p><blockquote>Fit everything into one place?</blockquote><blockquote>Integrate social-dynamic?</blockquote><blockquote>Have realistic expectations for users?</blockquote><blockquote>Address mental &amp; emotional components of health?</blockquote><p><strong>User Stories &amp; Minimum Viable Product</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/1*h1-QuMZBboC693U6vrSweA.png" /><figcaption>Organizing important findings to ideate a Minimum Viable Product</figcaption></figure><p><strong>Information Architecture</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*xyJm_1DQOl75FSwZwLFupw.png" /><figcaption>Using <strong>site maps</strong> to visualize user journey from homepage</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4-rjDkqHf6rohKd0UKCMAw.png" /><figcaption>Using <strong>user flows</strong> to envision potential red-routes</figcaption></figure><h3>Prototype</h3><p>After establishing the paths necessary for users to accomplish their goals, I began sketching ideas to visualize how exactly these goals could be carried out. At this stage I relied upon HMW Statements, my JBTD Framework, and Nielsen’s 10 Usability Heuristics to design minimalistic and intuitive screens. One obstacle I faced early on was what to include in the home screen. With many different potential user paths, it was challenging to not lose discoverability of different features.</p><p><strong>Sketches</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*ZL36usHeqlO3tveiCS3YPg.png" /><figcaption>How Might We — Fit everything into one place?</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*Y_bc03b4ZhGv0GHK9v5Ftw.png" /><figcaption>How Might We — Integrate social dynamic?</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iXp4DXyFY2Dxm2zygQEafg.png" /><figcaption><a href="https://i.imgur.com/9Ef0Wmh.png">Link to full-sized picture</a> of red-route sketches</figcaption></figure><p><strong>Wireframes</strong></p><p>After a round of Guerilla Testing (<em>done with</em> <em>POP by Marvel</em>) with the initial sketch design and 5 participants, there were a few pain points discovered in early sketches that were addressed and resolved prior to wireframing.</p><blockquote>Participants wished the app would recommend individualized content.</blockquote><blockquote>Participants took extended time to find the screen to view and join groups.</blockquote><blockquote>Participants desired a “favorites” section to return to for future reference and personalized content.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yirpYQSTndZoN_6ktjn7Ig.png" /><figcaption><a href="https://i.imgur.com/4aYxuul.png">Link to full-sized <strong>wireflow</strong></a></figcaption></figure><p><strong>Mood board</strong></p><p>Prior to creating high-fidelity screens, a mood board was created to inspire creativity as well as set the landscape and tone desired for this project. The main idea was to create an app that felt minimalistic, inviting, and sharp — while not sacrificing UX in the name of a pretty UI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fTqjYgdhDdMj3LFl-KcwMQ.png" /><figcaption>Mood board created to rouse imagination and visualize high-fi screens.</figcaption></figure><p><strong>Style Guide</strong></p><p>The below style guide was created and modified throughout this project to keep screens consistent as well as assist with design choices. The color purple was chosen as my primary color to balance between the stimulating nature of red and the calming aspect of blue. As an app designed to motivate users without overwhelming them, purple was the perfect choice as it is non-assuming and slightly mysterious to keep things fun.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ii_hZS4WgrOPF3QVxhhV7A.png" /><figcaption>Style Guide implemented for consistency and standards.</figcaption></figure><p><strong>High Fidelity Screens</strong></p><p>With wireflows finished and a style guide in place to maintain a clean design system, high fidelity screens were created for established red routes to create a MVP for user testing. During this phase of design, valuable weekly input was prescribed by my mentor that consisted of best practices and industry standards. These recommendations were then reflected in the evolution of my design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YQP-hX1FeOq6dA1RdJ-3ig.png" /><figcaption><a href="https://i.imgur.com/z5czOAT.jpg">Link to high-resolution</a></figcaption></figure><h3>Test</h3><p><strong>Usability Testing</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iejDuxlid-78VLKcI4_gKQ.png" /><figcaption>Screenshot of usability test on Zoom with Figma prototype (permission gained by participant to post).</figcaption></figure><p>With high fidelity screens in place, a prototype (also made in Figma) was created for usability testing. 5 moderated usability tests were performed (<em>per Nielson Norman Group recommendation</em>) where users were instructed to perform 4 tasks:</p><blockquote>Find a new exercise that involves running and complete it.</blockquote><blockquote>Share one of your saved recipes with your friends.</blockquote><blockquote>Find a new group and join it.</blockquote><blockquote>“Make” a healthy steak recipe, upload a picture, and leave a review.</blockquote><p><strong>What was learned</strong></p><p>Participants were able to complete all the above tasks with relative ease, <em>except</em> task 2 — share one of your saved recipes with your friends. Below is the initial prototype flow, where the user navigates to <strong>Favorites </strong>via the <strong>Profile button</strong> in the tab bar. The main takeaway when participants were questioned on this flow was that they did not immediately think to look under the profile to find the favorites section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/502/1*u_gBxTCn9Mjor1v4ytm0Wg.gif" /><figcaption>Initial user-flow to find the <strong>Favorites</strong> screen</figcaption></figure><p><strong>Revision</strong></p><p>With the above findings, the prototype was edited to improve discoverability and offer a quicker affordance to the user. The conclusion to this issue was to simply add a <strong>Favorites </strong>button to the tab bar. The initial MVP did not have a user flow for the <strong>Logs </strong>button in the tab bar, which actually slightly confused some users. This area was resultantly replaced with the Favorites button. You can see these changes reflected below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/502/1*wUZtKg1icRas4JUWJLvO2g.gif" /><figcaption>Updated prototype with improved affordance.</figcaption></figure><p><strong>Results</strong></p><p>The second round of usability testing revealed that the above changes to the prototype were meaningfully impactful. Participants were able to quickly and seamlessly perform all 4 tasks with complete success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*5ZCwEtFEEthth1wK6uwOIQ.png" /></figure><p>One small detail that was additionally reflected was the incorporation of a tool-tip for the first time usage of the app; One participant in the first round of usability testing stated that they did not recognize the Floating Action Button at the bottom of the screen, so the incorporation of a tool-tip aids in the showcasing of the affordability of this button:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/206/1*yvZqU0IFB2DZ0iosf6-_Zw.png" /><figcaption>Tool-tip for First Time Use of App</figcaption></figure><h3>Reflection</h3><p>The process of applying a Design Thinking mindset— identify a problem space, define an unresolved problem, ideate solutions from scratch, and then prototype/test those solutions (while maintaining a human-centered approach) was rewarding and an excellent opportunity to grow as a UX researcher and designer.</p><p>As someone who would enjoy personally using the app I designed, there were certainly challenges with creating solutions that reflected the users’ wants and needs without projecting my own assumptions on to the project.</p><p>Collecting data with research, user interviews, and usability testing was paramount to maintaining focus on the user and staying unbiased to the design process. Additionally, frameworks like JTBD and HMW statements were integral in keeping this project on track as the design process evolved.</p><p>Future iterations would include the design of features such as: talking to an expert, using a built-in calendar, inputting and logging data, and further development of the mental-health areas of the app.</p><h3>Final Prototype</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FYDrGkKY4gwlryy9eJkRzkw%2FCapstone-backup%3Fpage-id%3D0%253A1%26node-id%3D9%253A3839%26viewport%3D249%252C48%252C0.06%26scaling%3Dscale-down%26starting-point-node-id%3D9%253A3839&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FYDrGkKY4gwlryy9eJkRzkw%2FCapstone-backup%3Fpage-id%3D0%253A1%26node-id%3D9%253A3839%26viewport%3D249%252C48%252C0.06%26scaling%3Dscale-down%26starting-point-node-id%3D9%253A3839&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2F34d019de-667f-4dab-99a1-d6b51a54a260%3Fheight%3D211%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/a33af704438d20db0d19650c248c1a56/href">https://medium.com/media/a33af704438d20db0d19650c248c1a56/href</a></iframe><h3>Contact Me</h3><p>I’d love to hear your feedback on my project. Feel free to message me on LinkedIn!</p><p><strong>LinkedIn</strong> — <a href="https://www.linkedin.com/in/andrew-cox-ux/">https://www.linkedin.com/in/andrew-cox-ux/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4e3abc8151c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/designing-a-health-app-that-gets-results-a-ux-case-study-c4e3abc8151c">Case Study: Designing a health app that gets results</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>