<?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 Gregory Ma on Medium]]></title>
        <description><![CDATA[Stories by Gregory Ma on Medium]]></description>
        <link>https://medium.com/@gregoryma?source=rss-15d842793f70------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*-8I4KAwfkzjvxnwB.</url>
            <title>Stories by Gregory Ma on Medium</title>
            <link>https://medium.com/@gregoryma?source=rss-15d842793f70------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:17:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gregoryma/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[Kuucall — Call Tracking Web App]]></title>
            <link>https://medium.com/@gregoryma/kuucall-call-tracking-web-app-ef534287f4b6?source=rss-15d842793f70------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef534287f4b6</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Gregory Ma]]></dc:creator>
            <pubDate>Sun, 02 Oct 2016 21:29:53 GMT</pubDate>
            <atom:updated>2016-10-02T21:29:53.359Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AoLueGvkr8ib33UbDEkB7w.jpeg" /><figcaption>3 Week Group Project, Real Client</figcaption></figure><h4>UXD Professional Program — REDAcademy</h4><p>For our 5th project at REDAcademy, we were given a pre-existing call tracking web app. This project would not be handed off to RED web development. We needed to approach it from the perspective of a consultant.</p><h3>The Project</h3><p>The scope of this project differed greatly from our past RED projects. Rather than designing a website or app, we would be working on optimizing a pre-existing system. We were provided a much different set of content to tackle.</p><p>We were given:</p><ul><li>An existing landing page (website)</li><li>A beta for the web app</li><li>An updated prototype for the web app (proposed by another company)</li></ul><p>Having such a strong foundation to begin with meant we would be focusing on proving and disproving pre-existing content and tools.</p><h4>The Client</h4><p>Who is Kuucall?</p><p>Kuucall is a call tracking web app service. It collects data from phone call tracking, recording, and other analytics to optimize marketing strategies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5KoTk45UQJgR1KCU1toGmg.jpeg" /><figcaption>Users track where calls come from, and collect useful marketing data</figcaption></figure><p>Users can purchase numbers within the Kuucall app, unique to their marketing piece (ex. email, business cards, etc…) The unique numbers are linked back to their main host number, allowing the app to track where the calls come from. Kuucall supplements this tracking with other useful data (ex. call length, keywords for online, etc…)</p><p>Kuucall can be used by marketing agents with multiple companies as clients, or single small businesses looking to personally improve their marketing.</p><h4>Problems</h4><p>Kuucall is a data driven self serving application. Data is heavy, and only useful when used in the proper context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5zyGIh9m2xWXdwYc87o-HA.jpeg" /><figcaption>Kuucall Prototype initial screen</figcaption></figure><p>Our client’s worry was over the usability and accessibility of the current app. Regardless of how useful the data collected is, it is useless without user knowledge. To put it short, users get confused, users stop using the app.</p><blockquote>The learning curve for the Kuucall app was too steep.</blockquote><p>The secondary problem we found was with Kuucall’s website. It did a poor job educating users as to what Kuucall provided as a service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1WHo1Z4N602pzlud-NK86A.jpeg" /><figcaption>Kuucall does call tracking, but what does that mean? (Current website landing page)</figcaption></figure><h4>Opportunity</h4><p>One thing to take note of, call tracking is not a unique service. Therefore, the opportunity here is differentiating Kuucall from other call tracking services. The most effective and beneficial way to do it?</p><blockquote>Make Kuucall easy to use, and easier to learn.</blockquote><h4>Our Task</h4><p>Optimize the existing web app prototype, and educate users through a streamline onboard process (from website to web app.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-r74TnKzLezi8Hjssp2Ibw.jpeg" /><figcaption>User Interviews | Domain Research | User Testing</figcaption></figure><h3>Research</h3><p>Our research set out to answer specific questions about Kuucall’s existing app, and call tracking in general.</p><ul><li>Who is Kuucall’s target user?</li><li>What is the user’s level of knowledge? (with regards to call tracking)</li><li>How do other call tracking apps function? (in comparison to Kuucall)</li><li>What is the usability of Kuucall’s prototype?</li></ul><p>To find answers to these questions, we approached a total of 12 potential users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g5RUD9ZZVMHXI0un-TuyWQ.jpeg" /></figure><h4>User Interviews</h4><p>Initial user interviews set out to gauge our audience’s knowledge of call tracking. We began by asking people (with and without a marketing background) a simple question. “What is call tracking?”</p><p>The responses were unanimous.</p><blockquote>“What is call tracking?”</blockquote><p>When call tracking was explained to them, users immediately saw the benefit.This was especially prominent with regards to marketing professionals. Upon viewing sample data collected by Kuucall, marketing users were quick to point out the benefits (with some excitement I might add.)</p><h4>Domain Research</h4><p>At this stage we had to find out where Kuucall stood in relation to other call tracking applications. We needed to know how Kuucall, in its current state, was better or worse than other call tracking apps.</p><p><strong>Our discovery?</strong><br>Kuucall is just another tool, no different from the next call tracking app.</p><blockquote>Kuucall is call tracking. Call tracking is data. Data is boring.</blockquote><p><strong>Our conclusion?</strong><br>Find a way to make Kuucall more than just another call tracking tool.</p><blockquote>Using data is beneficial. Make using data easy. Easy benefits equals user happiness</blockquote><h4>User Testing</h4><p>Our user testing was conducted using 2 apps. Kuucall’s prototype, and its closest competitor’s app.</p><p>Users were educated on what call tracking was, and how it benefited them. They then proceeded to carry out identical tasks on each of the applications.</p><p>Our goal with testing was to find out…</p><ul><li>ease of usage</li><li>user enjoyment and engagement</li><li>if a user interaction cycle existed*</li></ul><p>*user interaction cycle refers t0 a seamless interaction flow between a product and its user</p><p>To summarize our key findings:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rMLErRwoVlstAKdPMTwQjA.jpeg" /></figure><h4><strong>Discoveries</strong></h4><p>From our research, we learned…</p><ul><li>Kuucall’s target user: Marketers</li><li>Users have little to no knowledge of call tracking</li><li>Kuucall is not unique to other call tracking services</li><li>Call tracking services collect useful data, but are useless without knowledge or direction on how to use it</li><li>The learning curve is very steep (huge drop off of interest during the early stages of testing)</li><li>There is a gap in the user interactive cycle (users set up companies and phone lines, then have to wait for data to collect)</li></ul><p>With this information, we headed into our planning stage. Our goal? Educate users on call tracking, teach users how to use Kuucall and it’s data, and create a seamless user interactive cycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1l-CeBAABtOYQMcJ14_FSw.jpeg" /><figcaption>Persona | Customer Journey Map | Sitemap</figcaption></figure><h3>Planning</h3><p>Our planning phase focused on organizing and solving problems discovered in our research. Create a persona, take said persona through our scenario, highlight the pain points, create solutions.</p><h4>Persona</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/276/1*4bqnBUgoDgi-YmnpmMc0QA.jpeg" /></figure><p><strong>Paulette Li</strong></p><ul><li>Marketing Agent (Digital)</li><li>Aged 30</li><li>Ambitious &amp; Motivated</li><li>Likes: effective systems that can improve client business</li><li>Dislikes: High input work yielding low outcome results</li></ul><p>Paulette Li just got a new job at a marketing agency. She is given a set of clients she will be in charge of. Her clients express a concern over their phone marketing. Paulette has experience in marketing, but doesn’t have much knowledge on call tracking. Paulette needs to find an effective way to improve her client’s phone marketing. A colleague suggests Kuucall.</p><h4>Customer Journey Map</h4><p>Here is a glimpse into Paulette’s emotional journey when using the current Kuucall app. Paulette’s journey begins with creating a Kuucall account, and ends with her using the data collected to benefit her clients marketing strategies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*5u9VOds5Bd_U9oJSMHCvEA.png" /><figcaption>The above chart clearly displays Paulette’s emotional highs and lows</figcaption></figure><p>To summarize, there are 4 main pain points:</p><ul><li>Learning about call tracking (on Kuucall’s website)</li><li>Adding tracking numbers</li><li>Waiting to collect data (on initial set up)</li><li>Navigation of data</li></ul><h4>Sitemap</h4><p>To streamline usability of the Kuucall prototype we took out repetitive sections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hciQh-QSlB7aVdUKmllsIw.jpeg" /><figcaption>All tools and functionality were kept</figcaption></figure><p>The biggest change we made was in splitting the companies menu. In the prototype, there were two distinct tools that were clumped together.</p><p>Viewing data &amp; managing companies were both under a single tab. This made users click more than necessary in order to reach their goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a8S2dop01dQUkA_plQyGvg.png" /><figcaption>Viewing data &amp; managing companies is all under one section.</figcaption></figure><h4>Solutions</h4><ul><li>Educate users on call tracking at the Kuucall website landing page by highlighting the benefits</li><li>Make adding tracking numbers easy (call to action within the app)</li><li>Create an overview page that makes the data more digestible and gives advice on maximizing potential of the app</li><li>Create a notification system that keeps users in the loop</li><li>Have a transparent and easy to navigate interface (reports &amp; manage separated)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cGLJJreEdQLmtR-_LVbwgQ.jpeg" /><figcaption>Low Fidelity Sketches | Mid Fidelity Digital | High Fidelity Digital</figcaption></figure><h3>Design &amp; Testing</h3><p>Here we went from low fidelity, to high fidelity while testing along the way.</p><h4>Low Fidelity Sketches</h4><p>We started with the website landing page. We concentrated on creating an obvious call to action. The call to action would be supported by functionalities of the app, and their benefits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w1cZoSZrD4PoHCjy7lt9Ng.jpeg" /><figcaption>Landing page of Kuucall’s website. A user’s first interaction point with the app. (Email bar added after the fact to test)</figcaption></figure><p>Next was the onboarding process (profile set up and user education).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*03HEp9_sgqPhNaCD6FWlBw.jpeg" /><figcaption>Password setup screen</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KELCafHvIHgMe7YZ9XR1dg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gjpm1A1pZaRKOL809ykopg.jpeg" /><figcaption>Kuucall app overview page and tutorial overlay</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4zL3W2SQNLRbylpROZNRKA.png" /><figcaption>Account agency overlay screen</figcaption></figure><p>Through testing our sketches, we found there was an excess of overlays within the app. The amount of overlay screens was overwhelming for users.</p><p>We also concluded that the overlay screen was over saturated. It did a poor job at easing the user into using the app.</p><h4>Mid Fidelity Digital</h4><p>Based on our sketch test results, we altered a few designs.</p><ul><li>Initial tutorial overlay screen removed in favour of a checklist on the overview screen</li><li>Overlay process for setting up account made more streamline</li><li>Overview screen dedicated to summarizing data</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bxvePG0Dh3a8BVIl5809NA.jpeg" /><figcaption>Website landing page mid fidelity</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QpndZwa33W-0pThHJfsQXw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RKVR7SGR56yRc7vXMV7TTQ.jpeg" /><figcaption>Kuucall web app profile creation screens</figcaption></figure><p>For the mid fidelity digital version, we created two sections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X-XGmDOa85cysQUu6xo5Ww.jpeg" /><figcaption>Mid fi overview page</figcaption></figure><p>On the left placed the user’s call tracking tools.</p><ul><li>Overview: summary of data being tracked, as well as tips and tutorial information (main interaction point with user)</li><li>Reports: all the call tracking data (viewable and comparable)</li><li>Manage: editing companies and agencies</li><li>Billing: pricing can be checked</li></ul><p>On the top we placed the navigational options.</p><ul><li>Profile: who you are in the app (Paulette Li)</li><li>Account: a grouping of the companies being worked on (RED Agency — for example is Paulette’s agency. She can be given access to another user’s account to view or manage it)</li><li>Company: the company that is creating lines and collecting data</li></ul><p>Through mid fidelity testing, we discovered call to actions would need to be an indicative colour.</p><p>We also discovered putting an email bar on the landing page would benefit marketing purposes. Even if the user does not sign up, their email can be used to further pursue them as a client.</p><p>The last thing we needed to fix was a gap in the user interactive cycle. Users could now easily sign up for an account, and set up call tracking lines. The problem? They still needed to wait for data to collect.</p><p>The solution? Custom notifications including emails updating users on data and giving them advice to improve their experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*NUvPqctwFRwZJxn2xBMKjA.jpeg" /><figcaption>Example of initial email sent to a user who just signed up</figcaption></figure><h4>High Fidelity</h4><p>Here’s a look at the results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G9S0dFCl7ydrh_1BM_AZ3Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*buC-a7E88C_qaC5xab-IAQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bDx3lmhOv4hsdfFLTqf9SA.jpeg" /><figcaption>Onboarding from the Website</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hYNRVMC47gKR1n5BDV9Big.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a4ZNzwWnXpcU0ms-1yx2uQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3hJGLYS-RWMbzc26zzVhYA.jpeg" /><figcaption>Initial set up of call tracking lines</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BU6nx1DlbiVdp74XvNmGCA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*txzoHOkoU4jl1RG7SNUntw.jpeg" /><figcaption>Management and Report tools &amp; interfaces</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FI6bTQGGIaZ8%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DI6bTQGGIaZ8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FI6bTQGGIaZ8%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/409918157f6eb79cbfd74cafb2df5ceb/href">https://medium.com/media/409918157f6eb79cbfd74cafb2df5ceb/href</a></iframe><h3>Summary</h3><p>The scope of the project was large and heavy for a 3 week student project. Optimization of a data driven application can never be taken lightly.</p><p>The results from our 3 weeks of work are something I am proud of. Had there been more time, we would have considered a few more options (Communication platform, fully customizable overview interface.)</p><p>The goal in this project was to optimize a data driven application. Through our research, planning, designs, and continuous testing, we came to a positive result.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef534287f4b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rise Women’s Legal Centre]]></title>
            <link>https://medium.com/@gregoryma/rise-womens-legal-centre-273164b6acec?source=rss-15d842793f70------2</link>
            <guid isPermaLink="false">https://medium.com/p/273164b6acec</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Gregory Ma]]></dc:creator>
            <pubDate>Tue, 06 Sep 2016 07:27:32 GMT</pubDate>
            <atom:updated>2016-09-06T07:27:32.697Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JuftqqSccs4_8KC9lo43vg.jpeg" /><figcaption>3 Week Group Project, Real Client</figcaption></figure><h4>UXD Professional Program — REDAcademy</h4><p>This case study takes you through my fourth project at REDAcademy. This was our first client project at REDAcademy. This was also our first project to be handed over to web development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*32rpIo1hz1DUvJuW1A7WwQ.jpeg" /><figcaption>The Project | The Client | Problems | Opportunity | Our Task</figcaption></figure><h3>The Project</h3><p>There was quite a bit of anticipation leading up to this project. This would be our first chance to tackle real client problems as a group. Prior to this, we had been interacting with a piece of paper (fictional project brief). Pieces of paper have an interactive limit. Luckily, human clients do not. Well, less of a limit than paper anyhow. Let’s get into it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AMtHUogk82a7CcvV9Cx41w.jpeg" /></figure><h4>The Client</h4><p>Our client for this project was Rise Women’s Legal Centre. Rise is a community legal centre serving all individuals who self-identify as women. They currently provide services primarily in the area of family and child protection law. Their legal services are provided by upper year law students from the University of British Columbia who receive training and supervision from on-site lawyers.</p><p>Rise was created out of necessity, in order to fill a gap in BC’s legal world. Legal aid for family law matters has been drastically cut back since 2002. So much so that only very low income people qualify. Those who qualify only get services for high conflict cases. When a woman meets these restrictive criteria, she rarely gets enough time with a lawyer and is usually left to represent herself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7HyR9KquZlT3H87sfKocpA.jpeg" /></figure><h4>Problems</h4><p>Rise’s current website misrepresented them. The visual design focused heavily on femininity. While it is correct that Rise serves individuals who self-identify as women, it was not their goal to personify femininity within their brand. Rise already suffers from a credibility deficit because their “lawyers” are students. The fact is, they provide legal services in a professional capacity. The current website was slightly undercutting that fact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O4ZCsYLkM7JB4BB19qdrUQ.jpeg" /><figcaption>Example of Rise’s “Make an Appointment” page being overly feminine.</figcaption></figure><p>Another main problem was the website’s content. It was very text heavy, making it hard for visitors to digest important information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J84BPc-yyP3lcZtHXRRdjA.jpeg" /><figcaption>Example of Rise’s “Our Services” page having areas with text heavy content.</figcaption></figure><h4>Opportunity</h4><p>Give Rise proper brand representation, and educate people on what the organization does (and how they do it).</p><h4>Our Task</h4><p>Redesign Rise’s website (content and visual). Make user interaction easier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-iIJYMfun0HejlMJL8sCIA.jpeg" /><figcaption>User Interviews | Contextual Inquiry</figcaption></figure><h3>Research</h3><p>Our group as a whole knew very little about the legal world. Our research would have to inform our planning and design decisions moving forward. It needed to answer a few basic questions.</p><ul><li>Who is our user? (Who is interacting with the website?)</li><li>What does our user need to accomplish?</li><li>How does Rise want to be represented?</li></ul><h4>User Interviews</h4><p>Our initial point of contact was the Executive Director of Rise. She gave us the story behind Rise’s formation, and the intricacies of what they do. We also received a list of potential interview contacts from her. This afforded us a very strong foundation of which to begin.</p><p>Through those contacts we interviewed 7 individuals. Rise’s operations manager, an articled UBC student lawyer, a major donor, a board member, a clinical educator, an advocate, and a women’s transitional home facilitator.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pS4SwPOpk6wfoRDTM0Izdg.jpeg" /></figure><p>We learned our users are new clients (primary) and potential donors (secondary)</p><p>New Clients:</p><ul><li>Need to easily contact Rise</li><li>Need to know if Rise is able to help them</li><li>Must fill out a form before being able to meet with a student lawyer</li><li>A high percentage interact with the mobile website</li></ul><p>Potential Donors:</p><ul><li>Need easy access to information about Rise (If they know how their donations can help, they may be more inclined to contribute)</li><li>Need a straightforward donation process</li></ul><p>Rise wants to be represented as professional, and strong (but not intimidating, stiff, or unapproachable)*</p><p>*striking a balance of welcoming yet credible is key.</p><h4>Contextual Inquiry</h4><p>Our user interviews gathered valuable information on the scope of our project. However, we were missing one piece of the puzzle.</p><p>Being that Rise’s work touches on a delicate subject, it became difficult for us to contact “New Client” users. This made it difficult to gauge the specifics of our primary user.</p><blockquote>We needed to find out more about our primary user, but did not have the means.</blockquote><p>Contextually inquiry to the rescue!</p><p>Our solution to this dilemma was to take to the streets with a guerilla style research approach. Our goal? Find our primary user group, and see them interact with websites.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qbH6v2voka1hl-Kf9PRUKA.jpeg" /><figcaption>Vancouver BC, Canada — Carnegie Centre</figcaption></figure><p>The main thing we tested was the primary user’s technological savvy. We needed to see their ability to navigate websites based on iconography and content. From this we found that our primary user was very explorative. Most had a very “try it and see” mentality. They also displayed a very mid to low level of technological knowledge.</p><p>We had assumed that our primary user had a lower level of technological knowledge, but until this point it was merely a hypothesis. Now we had something concrete. We had validation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u4y6pRiQeJ1WxyWBytqm2g.jpeg" /><figcaption>Persona | User Scenario | Informational Architecture</figcaption></figure><h3>Planning</h3><p>Our planning phase was straight forward. Use our research to pinpoint our primary persona, create a scenario for said persona, and optimize the informational architecture of the website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K-C5l9r4DoQpc13xfBZ_NQ.jpeg" /></figure><h4>Persona</h4><p>Based on our research we came up with our primary (user) persona. Our primary persona comes from a lower income bracket (but does not qualify for legal aid). She is feeling distress in her own home. She is uncertain of her children’s future. She does not have an understanding of the legal system and has means of legal assistance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/246/1*QvXVOtCyj9VLiP2yepO02g.jpeg" /></figure><blockquote>This is Katerina Petrova.</blockquote><p>She is a 30 year old stay at home mother. She is responsible, attentive, and resourceful.</p><p>All she wants is to feel safe again.</p><h4>Scenario</h4><p>Katerina is experiencing threats and abuse from her husband. She is afraid for her children’s safety. Consequently, she has sought help from several legal aid services, but has been rejected.</p><blockquote>This makes her very frustrated.</blockquote><p>A close friend suggests checking out the new women’s legal centre named Rise. She decides to look them up on her phone to find out if they are able to help her with her situation. If they can, she wants to contact them right away.</p><blockquote>She has a limited amount of time where she is away from her husband.</blockquote><h4>Informational Architecture</h4><p>The first thing we did was reference Rise’s old website. It was easy to find and remove unnecessary pages. For example, the “Our Blog” and “Events” pages were removed. This left us with content focused on our two main user goals: New client contact, and informing potential donors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*WdUhpy7f9n7a5SZx5JQqeQ.jpeg" /><figcaption>Figuring out Rise Women’s Legal Centre’s website IA</figcaption></figure><p>We settled on 8 distinct page sections (With a strong content strategy in mind).</p><ul><li><strong>Home</strong> (Display direct links to contacting Rise, and donation information)</li><li><strong>About</strong> (Information on how and why Rise started)</li><li><strong>Services</strong> (What Rise does, and who they can help)</li><li><strong>Resources </strong>(If Rise can’t help a new client, alternate resources are provided here)</li><li><strong>Students</strong> (Explains the relationship between law students and Rise)*</li><li><strong>Donate</strong> (Educates potential donor as to how their donations can help Rise and the women they provide legal service to)</li><li><strong>Contact</strong> (Location, hours, email, phone #, and parking information)</li><li><strong>Legal Contact Form</strong> (A fillable online form that needs to be filled out in order to meet with a student lawyer)</li></ul><p>*The “Student” page was not initially planned. It was buried within the “About” page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fxkQB6QQ-3DxiQrxs8H3mA.jpeg" /><figcaption>Sitemap Rough Sketch</figcaption></figure><p>After finalizing how the IA interconnected (how the pages linked to each other), we were ready to design and test.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-lzQ8q1_FCcXOMoJw3gVBw.jpeg" /><figcaption>Low Fidelity Sketches | Mid Fidelity Digital | High Fidelity Digital</figcaption></figure><h3>Design &amp; Testing</h3><p>In this phase we went from low to high fidelity while testing each stage along the way. Mobile was designed first. The initial mobile design was then altered for desktop to create a responsive website design.</p><h4>Low Fidelity Sketches</h4><p>This stage was about quick and efficient idea conversion from brain to page. We wanted to test our initial IA/sitemap, and the language used to navigate the site.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O-7VPgawjCiXUDSDYMG3Tg.jpeg" /><figcaption>Early whiteboard sketch of (mobile) homepage layout</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dVytK7fCX4S7f844PcjEnQ.jpeg" /><figcaption>Low fidelity (mobile) paper sketch of home page</figcaption></figure><p>For our low fidelity user tests, we first asked individuals to fill out a legal contact form. The first test validated user accessibility when finding and filling out a legal contact form.</p><p>We then asked them to find information on Rise from the perspective of a potential donor. In this test users found donor information with relative ease. However, there was slight confusion over page content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i9DZ478gbyp-LtsIX9S57g.jpeg" /><figcaption>Low fidelity paper sketch testing</figcaption></figure><p>In our initial IA, the “Student” section could be found within the “About” page. Most users were confused as to why it was buried there. Some never even came across the student information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CyGO9h65gQ-NEkUIsvf0Hg.jpeg" /><figcaption>Whiteboard brainstorming for a separate “Students” page</figcaption></figure><p>A decision was made to separate the content. The “About” page would focus on Rise as an organization. A dedicated “Students” page would focus on the law students at Rise.</p><h4>Mid Fidelity Digital</h4><p>Here we focused on making the content more digestible. The old website had large text heavy sections that needed to be broken up and simplified.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u7DDbldoun31tlFXwjNhhw.png" /><figcaption>Mid fidelity (mobile) digital pages</figcaption></figure><p>Our mid fidelity test mirrored our low fidelity test.</p><p>The first test was for users to find and fill out a legal contact form. There was little to no resistance with this process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TKpPDHlo8wIQ783qWgtQ2w.jpeg" /><figcaption>Mid fidelity (mobile) online form pages</figcaption></figure><p>The second test was for users to find information about Rise from the perspective of a potential donor. Again, information was easily found by the user. During this test, another content issue appeared.</p><p>Information important to a potential donor (about Rise’s law students) was not being found. Potential donor testers did not visit the “Students” page in any of our tests. They primarily navigated to the “About” page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*idTa5kE4oC9uI3IZMx1Y3Q.jpeg" /><figcaption>“Students” link added to the bottom of the “About” page</figcaption></figure><p>A short summary and link about the law students was added to the bottom of the “About” page. This adjustment allowed for potential donor users to reach the “Students” page when retested.</p><h4>High Fidelity Digital</h4><p>By this stage user testing had exposed most of our problems. The main goal here was to enhance the visuals of the website and give prominence to Rise’s brand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LWNRBkRgVZpUAP1ZMr6R1A.jpeg" /><figcaption>High fidelity (mobile) pages</figcaption></figure><p>For the high fidelity tests, we sent our users through the same scenarios (as the low and mid fidelity). This validated the adjustments made on our earlier iterations.</p><p>The main problem that users came across at this stage was the UI of our buttons. We initially used flat design as the standard for our buttons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jF10cgp8tWfxOS-uIbngGw.jpeg" /><figcaption>Initial design (right) compared to reiteration (left)</figcaption></figure><p>The flat design buttons were not obvious enough to users as actionable. Shadows were added to buttons to differentiate them from iconography.</p><p>We then gave the mobile app a final polish and transitioned it to a desktop version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SAYlmYXpDnWejKxg6cHFNQ.jpeg" /><figcaption>High fidelity (desktop) pages</figcaption></figure><p>The final prototypes were then presented to the client (and can be viewed in the videos below.)</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D1WIvApCHyb8&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F1WIvApCHyb8&amp;type=text%2Fhtml&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/15a880e57d91723344d83115aa2d5b9a/href">https://medium.com/media/15a880e57d91723344d83115aa2d5b9a/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DTaTcDvutXrI&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FTaTcDvutXrI&amp;type=text%2Fhtml&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f5266b5b05e2901d59988916ca051533/href">https://medium.com/media/f5266b5b05e2901d59988916ca051533/href</a></iframe><h3>Summary</h3><p>Our client loved the redesign. They were excited over how much thought went into the whole project.</p><h4>Results</h4><p><strong>Research</strong> found who our users were, and highlighted their goal.</p><p><strong>Planning</strong> solved any obstacles stopping them from accomplishing those goals.</p><p><strong>Design</strong> gave proper representation to Rise’s brand while further leading users through their flow.</p><p><strong>Testing</strong> unearthed the unforeseeable blunders in our planning &amp; design choices.</p><h4>Future Considerations</h4><p>We received feedback from our client pertaining to the language used. Initially, the “Legal Contact Form” and “Who can we help?” buttons were labelled “Book Appointment” and “Do I Qualify?”. Rise felt the language was too similar to the words used for legal aid application. Adjustments were made, and the project was sent off to web development.</p><h4>Reflection</h4><p>Looking back on the project, I realize how much fun I had. Having human interaction made for an interesting dynamic. The group worked very well together from start to finish. In the end, we created a piece of work we are all proud of.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=273164b6acec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning to work in a Group]]></title>
            <link>https://medium.com/@gregoryma/learning-to-work-in-a-group-b008626bf5d2?source=rss-15d842793f70------2</link>
            <guid isPermaLink="false">https://medium.com/p/b008626bf5d2</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Gregory Ma]]></dc:creator>
            <pubDate>Mon, 15 Aug 2016 06:41:47 GMT</pubDate>
            <atom:updated>2016-08-15T06:41:47.152Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jWGbGw-V3G-kmAP4Q4hHvg.jpeg" /><figcaption>2 week group project. Fictional client.</figcaption></figure><h4>UXD Professional Program — REDAcademy</h4><p>The following case study describes yet another step in my educational journey of UX Design knowledge &amp; experience.*<br><em>*AKA. my first UX Design group project</em></p><h4>Setting the Scene</h4><blockquote>“To put it bluntly, anything involving multiple personalities is never simple.”</blockquote><p>For the third project of the Red Academy UX Designer Professional program, we were placed into a group of 4 to create a mobile app for a fictional client. The focus of the project was to apply the design tools we had previously learned (Research, Planning, Design, and Testing), to a 2 week project while working in a collaborative group setting. Simple, right?</p><p>To put it bluntly, anything involving multiple personalities is never “Simple”. That being said, this project was chock full of learning opportunities and experiences for all around.</p><p>Let’s begin.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EARd95DL1zNL4seQt1zqQg.jpeg" /><figcaption>Project | Problem | Opportunity</figcaption></figure><h4>The Project</h4><p>For this project, our group was tasked with creating high fidelity design for the mobile app, NOMO FOMO*. Along with designing the app, documentation of the process through research, planning, and testing needed to be kept.</p><blockquote><em>“Vancouver is a melting pot for food, music, arts culture and events. Whatever the season, there is always something happening and new to explore. Whether you are a visitor, from somewhere else or born and raised, there is always a certain degree of anxiety in the fear of missing out (“FOMO”)** in events both big and small, and either local or just amongst your many friends.”</em></blockquote><p>To summarize, Vancouver is full of events and culture. People want to discover and share them in a convenient matter.</p><p><em>*NOMO FOMO stands for “No More Fear of Missing Out.”</em></p><p><em>**FOMO stands for “Fear of Missing Out”. It is fearing that you may have made the wrong decision on how to spend time, as you can imagine how things could be different.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nP3gSgUHhmCvAoN1zShRVw.jpeg" /><figcaption>Vancouver BC, Canada</figcaption></figure><h4>The Problem</h4><p>Users do not have a platform allowing them to search the internet for the many events and culture, while seamlessly scheduling and sharing them amongst their peers. Multiple services and platforms have to be used by the User to complete these tasks.</p><h4>The Opportunity</h4><blockquote>Allow Users to do all of the following, on a single mobile app.</blockquote><ol><li>Filter events &amp; happenings based on own taste &amp; preference</li><li>Follow &amp; connect with trend setters around the city (Be a part of what they’re up to.)</li><li>Create &amp; share own events with others (Have the ability to become a tastemaker* yourself after a number of followers &amp; events.)</li><li>Share events through social media</li><li>Create a feed of your own “NOMO FOMO’s” (A way to organize events &amp; happenings around you.)</li></ol><p><em>*A tastemaker is a person who decides or influences what is or will become fashionable.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fHh2kf1SgUfv2-NvfwVi2w.jpeg" /><figcaption>User Research | User Interviews | Persona | Domain Research</figcaption></figure><p>Before I get into the details of the research, I’d like to give you some context of the group dynamic during this phase.</p><p>At this point our group was feeling optimistic, motivated, and under the impression that we were all on the same page. Roles and work were eagerly delegated. Plans were set forth. The key element in maintaining this dynamic?</p><blockquote>Time. We still had lots of it.</blockquote><p>For this step, data would be collected through different forms of research. The data would then be organized and compared to gain a holistic viewpoint of the project at hand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oDOWsvSCrB6FrqBbmQ4suQ.jpeg" /></figure><h4>User Research</h4><p>The goal with our User Research was to find out who needed this app. Surveys were conducted to find the scope of our User’s age range, occupation, and gender, amongst other values. Approximately 30 survey responses were collected and organized.</p><p>Here are key points that were pulled from our survey.</p><ul><li>Age range 20–25</li><li>Student</li><li>Single</li><li>50/50 split on Male or Female</li><li>Optimistic &amp; Extroverted (slightly)</li><li>Technologically Competent</li><li>Average to high social media usage</li></ul><p>This information gave us a general idea of our target User. However, it did not give us the whole picture. It needed to be supplemented by more intimate interviews.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fp_BQRiVhEWdY29pX5hz_Q.jpeg" /></figure><h4>User Interviews</h4><p>Each of our group members set out to conduct separate User Interviews. Through these interviews, our group was looking for emotional highs and lows when dealing with finding, creating, sharing, or communicating events. A total of 8 interviews were conducted.</p><p>To summarize, our key findings were:</p><ul><li>Likes: Movies, clubs, food events, museums, art, speaking panels, and live music.</li><li>Dislikes: Scheduling and coordinating plans, not knowing the latest in events and happenings, and flakiness.</li><li>Sharing experiences with friends is a huge focus</li><li>Potential to share a moment with peers outweighs the negativity of setting up plans</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RRt2Dz-3byzd09YvEJ6i1g.jpeg" /></figure><p>Results: The people we interviewed had a large range of interests. Their dislikes focused on the finding and planning of events pertaining to these interests. Most importantly, sharing these moments with their peers was above all else.</p><h4>Persona</h4><p>Based off of the research collected, our group created a target persona.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/286/1*hHBEMGfQR5nOWhRAWMftGQ.jpeg" /><figcaption>“I love having a good time and being carefree”</figcaption></figure><p><strong>Meet Joanne Summers.<br></strong>Age: 25<br>Occupation: Student<br>Location: Vancouver, BC<br>Status: Single</p><p><strong>Joanne wants to:<br></strong>-<strong> </strong>Easily find out about local events<br>- Share events that she finds out about with her peers<br>- Know what her peers around her are planning<br>- Find personalized suggestions based on her interests</p><blockquote>“Joanne is a student who lives in Vancouver, BC. Her main priority in life is convenience, often putting location, comfort, and enjoyment above finances or stability. She can be found at home studying, eating, or watching tv. She likes going out with friends and enjoys activities among people. She is always curious about current local events that may interest her. Being up to date and avoiding extra work are challenges that Joanne is trying to solve. She does not consider herself “lazy”, but does admit to be a person who prefers the easier choices in life.”</blockquote><h4>Domain Research</h4><p>Next, our group looked for comparable competitors within a similar domain. We found a large group of competitors, but narrowed it down to a select few. Here are 3 of the most comparable companies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a7TOddGvKxVVZJNYnYkdfQ.jpeg" /><figcaption>Pocket Social (Closest competitor), Bored in Vancouver, and Meetup.</figcaption></figure><p>Pocket Social and Meetup were found to have a mobile app. Bored in Vancouver did not. All 3 had a website that allowed for Users to do a variety of things. But let’s just focus on Pocket Social.</p><p>Pocket Social was the closest competitor to what we were trying to achieve with NOMO FOMO.</p><p>Here’s a quick run-down of what Pocket Social does.</p><ul><li>What: Pocket Social is a local social planner. Helps you find events and activities locally and share them with others.</li><li>User can create and promote events in one spot. Collect money with no fees. Check in guests with their phone.</li><li>Strengths: Allows for social media sharing. Event planning and sharing options cover all the bases. Helps with finding info on events and activities and sharing with others.</li><li>Weaknesses: The interface is cluttered. The amount of options jammed into the application makes for an over saturated layout. Finding things becomes overwhelming.</li></ul><p>Pocket Social does a good job covering some of the goals of NOMO FOMO, but there is room for streamlining. There are also opportunities to improve certain areas to create an app more inline with NOMO FOMO’s goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MBmls3OKup2mttppuwfpxw.jpeg" /><figcaption>User Scenario | User Flow | Features List</figcaption></figure><p>At this stage in the project, the group became discombobulated. As a group, we were struggling to get past a conceptual and theoretical level. Regardless of being on the same page or not, work was being done orally rather than physically. Cyclic sessions of conversation erupted and our group hit a lull in production.</p><blockquote>From a physically productive standpoint, we were stuck.</blockquote><p>Given an unlimited amount of time to complete this project, we may have been stuck forever. But that’s unrealistic. We knew we had a time limit. We felt the pressure of that time limit. In a reference to the proverb “Necessity is the mother of invention”:</p><blockquote>The need to finish became imperative, and we were forced to find ways of achieving it.</blockquote><p>This lead to a Lean* approach for the remainder of our project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PClBDG5OZGIPb48-wyW8ow.png" /><figcaption>Lean Process captured in a visual cycle</figcaption></figure><p><em>*Lean means creating more value for customers with fewer resources. The ultimate goal is to provide perfect value to the customer through a perfect value creation process that has zero waste.<br></em><strong><em>Simply put, work efficient based on your user.</em></strong></p><h4>User Scenario</h4><p>Here we referred back to our target user, Joanne Summers. Creating a scenario realistic to her persona became key in defining specific needs. We needed to figure out our user’s needs &amp; flow to define &amp; prioritize specific features for the app.</p><blockquote>“Joanne loves music. She enjoys the local music scene and is constantly looking for new events to attend and share with her friends. Most of the time, she goes onto google and various blog sites to keep up to date with the music scene. However, being a student leaves Joanne with very little time to cruise the internet looking for these events. This causes Joanne to miss out on some of the local music events she wants to attend. She begins to feel out of the loop in the local music scene. Joanne begins suffer from FOMO”</blockquote><p>Key points to take from Joanne’s scenario:</p><ul><li>Joanne wants to find local music events</li><li>She doesn’t have time to search all over the internet for these events</li><li>She wants to find these events so she can attend and share with friends</li><li>She doesn’t want a temporary solution to finding these events</li><li>She wants an easier way to keep up to date (With her interests.)</li></ul><h4>User Flow</h4><p>For our user flow, we concentrated on Joanne finding an event. We also concentrated on finding options for her that would allow her continue finding events around her. This formulated the ideas for individual events, and curated lists.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_1_Q4fJoUDm2RQVoWB3UGA.jpeg" /><figcaption>To keep things simple, we followed single decision paths</figcaption></figure><h4>Features List</h4><p>Based on the target user’s needs, we decided on a list of “Must-Have” features for the NOMO FOMO app.</p><ol><li>Events<strong><br></strong>Users are able to <strong>create</strong>, <strong>find</strong>, and <strong>share</strong>, events. <strong>Events</strong> are sorted through <strong>categories</strong> (General terms: Music, Sports, Food, etc…), and <strong>tags</strong> (Specific terms: Jazz, Football, BBQ, etc…) as definitions.</li><li>Lists<br>Users are able to <strong>curate</strong> lists of events. They are free to choose from any of the events created, found, or shared. These <strong>lists</strong> can then be <strong>shared</strong> or <strong>followed</strong> by other users. The original curator is also able to <strong>update</strong> these lists, allowing them to be a <strong>tastemaker</strong>. Lists, like events, are also defined through <strong>categories</strong> &amp; <strong>tags</strong>.</li><li>Customization (Follow or Favourite)<br>Users are given the ability to <strong>follow</strong> other users or <strong>favourite</strong> lists and events. <strong>Following</strong> a user keeps you up to date with what others are doing. <strong>Favouriting</strong> lists allows for users to be continuously updated by other users on the latest events &amp; happenings. <strong>Favouriting</strong> an event allows for users to “bookmark” individual events that may interest them. They can then revisit these events at a later time to decide whether they would like to attend or not.</li><li>RSVP<br>Users can <strong>RSVP</strong> to events found through any of NOMO FOMO’s means. That means users can create, search, share, keep updated, and RSVP to events all in one place.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YavZ-SZOMG9PK3QhoL6f7g.png" /></figure><p>Upon deciding on these key features, our group was ready to move into the Design &amp; Testing phase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DrHR5Ci5uUYRgvy6fmfoQg.jpeg" /><figcaption>UI Paper Sketches &amp; Testing | Digital Mid-Fidelity Design &amp; Testing | High-Fidelity Prototype</figcaption></figure><p>The moment our group hit this point, it became a mad dash to the finish. The stage was set, but time was running out. As a group, we were beginning to come together again. The there must have been some relatability in the lack of time we all shared. Never the less, we dove into the design and testing of our app (mostly on the same page as one another.)</p><h4>UI Paper Sketches &amp; Testing</h4><p>Through an attempted scrum* process, our group came up with a flurry of paper sketched UI’s.</p><p>The key screens that were focused on were:</p><ol><li>Onboarding**</li><li>Lists Homepage</li><li>Individual List Page</li><li>Events Homepage</li><li>Individual Event Page</li><li>Favourites</li></ol><p>*Scrum process is a technique that has groups split into divisions to work at a problem or task. Each division is given the same task, and an allotted amount of time to come to a solution. After the time is up, the group reconvenes and discusses each other’s solutions.</p><p>**Onboarding refers to the mechanism through which new users acquire the necessary knowledge over a new app, while also personalizing their own experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/742/1*W9FqvlLX6SHoSaFr6bxQdg.png" /><figcaption>Early on sketches of NOMO FOMO app including onboarding process, and main screens</figcaption></figure><p>After finalizing and organizing our app flow, we set out to test it’s functionality.</p><p>Some of our questions we had were:</p><ol><li>Is the Onboarding process too long?</li><li>Are there too many features and functions?</li><li>Is joining an event streamlined enough?</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/1*z5tnm-vcvTDnpbSJtJTW_w.png" /><figcaption>More defined paper prototype screens that were used in User Testing</figcaption></figure><p>The results of our <strong>Paper Prototype</strong> testing proved to be very helpful. It went on to answer some of our initial questions.</p><ol><li><em>Is the Onboarding process too long? </em><strong>NO<br></strong>People did not mind the length of our Onboarding process (3 steps asking for preferences and interests.)</li><li><em>Are there too many features and functions? </em><strong>YES<br></strong>Favourite, Share, Create, etc… was all on the initial screens for each of the <strong>Lists</strong> and <strong>Events</strong>. This created a saturated interface that became consitently difficult for users to navigate. All features and functions were removed in favour of a singel <strong>Favourite button</strong>.</li><li><em>Is joining an event streamlined enough?</em><strong> NO<br></strong>In the paper prototypes, we initially had 3 options embedded in the RSVP section of an event page. Users could select from 3 icons (remove event, rsvp to event, and favourite event.) We realized that users spent a huge amount of time deciphering this section. It had to be removed in favour of a single <strong>RSVP function</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0oMxNu8jWqXatW3-n_bxRA.png" /><figcaption>Paper Prototype Testing</figcaption></figure><h4>Digital Mid-Fidelity Design &amp; Testing</h4><p>The Onboarding and Main Screens were quickly digitized on <a href="https://www.sketchapp.com/">Sketch</a> and placed into <a href="https://www.invisionapp.com/">Invision</a> to be tested.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6CwEVRpfW_rTEuq9Bjm0Pg.png" /><figcaption>Sketch Artboards for NOMO FOMO (Mid-Fidelity)</figcaption></figure><p>One of the biggest recurring problems we came across was on the home pages for Lists &amp; Events. The vertical spacing made it hard to differentiate which description and image matched.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*ykcc-Y_e1d-VQ8CVUPa8Ew.jpeg" /><figcaption>Does the text go with the above image? Or the one below?</figcaption></figure><p>To fix it, we used arrows and image overlay. This made the relationship between descriptions and images obvious to the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*IYhDZQe5mesJw3hZH7swSQ.jpeg" /><figcaption>Box where text sits points to corresponding image. Image can be seen through slight transparency.</figcaption></figure><p>Another problem that came up was on the Event RSVP confirmation. In the mid-fidelity prototype, pushing JOIN EVENT would prompt a toaster style overlay. The overlay would spring up from the bottom of the screen, validate the user’s action, and give sharing options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/891/1*YnP1cLvokX6mYRfGp8t12A.jpeg" /><figcaption>Join Event button pushed &gt; Event Joined prompt (with share options) pops up</figcaption></figure><p>The problem can be seen in the above image (on the right screen). The share options take priority over the EVENT JOINED prompt. This caused many tester to become confused as to whether or not they had joined the event yet.</p><p>The fix, create a visual hierarchy that promotes the EVENT JOINED message above the share options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/891/1*tDoShhaLECKYT2UWnNXRsw.jpeg" /><figcaption>EVENT JOINED! (on the right) takes visual priority over the share options</figcaption></figure><h4>High-Fidelity Prototype</h4><p>Through quick cycles of testing with users, our group finally came to a final result. A High-Fidelity Prototype for the NOMO FOMO mobile app.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FXYgxWerADTc%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DXYgxWerADTc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FXYgxWerADTc%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/de01cf5db4f78bdacf774787bd9eff78/href">https://medium.com/media/de01cf5db4f78bdacf774787bd9eff78/href</a></iframe><h4>Summary</h4><p>Given the time constraints and context of the project, I feel as though my group came up with a pretty solid result. Looking back on the entire scope of this project, there is little I would do to change the experience. The whole process was a messy web of misguided ideas and direction lead by different personalities. There were many hurdles and challenges along the way that we faced as a group, both divided and united.</p><p>Ultimately, the whole project was an amazing experience. It put a focus on group dynamics and efficiency. Everything I have learned during this project will and can be used in projects moving forwards.</p><p>I am happy to say, I am finished my first UX Design group project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b008626bf5d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LEARNING BY DOING]]></title>
            <link>https://medium.com/@gregoryma/for-the-second-project-of-the-red-academy-ux-designer-professional-program-i-was-tasked-with-a-ba435dc4126a?source=rss-15d842793f70------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba435dc4126a</guid>
            <category><![CDATA[students]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Gregory Ma]]></dc:creator>
            <pubDate>Wed, 27 Jul 2016 08:02:33 GMT</pubDate>
            <atom:updated>2016-07-27T08:11:07.492Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fSjyINbHdhlgJB5uAvYXEw.png" /><figcaption>Project | Problem | Opportunity | Process</figcaption></figure><p>The following is a case study written by yours truly. The view point shared is that of a very “green” UX designer, eager to learn anything he can.</p><h3>The Project</h3><p>For the second project of the Red Academy UX Designer Professional Program, I was tasked with a redesign of the <a href="http://shopmain.ca/">Shopmain.ca</a> website.</p><p>The project required a mid fidelity prototype of the website, supplemented by research, planning, design, and testing deliverables.</p><h3>The Problem</h3><p>Shopmain.ca, with a focus on shopping local, contains information about stores and events along Main Street. While the popularity of shopping local is increasing, local shops are projected to lose in retail sales to online stores. Independent retailers generally have a poor online presence, making them a prime target for online retailers. The concern is Canadians will lose interest in shopping local as they are drawn towards online alternatives.</p><blockquote><em>Independent Stores + Poor Online Presence = Big Problems</em></blockquote><h3>Opportunity</h3><p>There is a silver lining to this all. The fact is, shopping is going online. You may ask yourself, “Well, good. But how does that help?” Simple. Bring the Main Street shopping experience online. Allow for customers to shop local from the comfort of their home.</p><p>The Job? <br><em>Create an e-commerce site integrating all Main Street stores.</em></p><p>The Goal? <br><em>Up sales, and increase social media presence.</em></p><blockquote>“The fact is, shopping is going online.”</blockquote><p>Below is my process broken down into 4 key steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*itUs1_MKDxlUsMANSePzBg.png" /><figcaption>Process of the project broken into 4 key stages</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e6ij2achnTfvFk-FqDQ_dg.png" /><figcaption>Existing Website Research | User Research | Domain Research</figcaption></figure><h4><a href="http://shopmain.ca/">Shopmain.ca</a></h4><h3>Existing Website</h3><p>A quick glance at the existing website and I had already formulated some ideas for the site’s new direction. The primary navigation was confusing and disorganized, and the overall feel of the website screamed “BLOG”.</p><h3>User Research</h3><p>My research began with understanding the User. To understand the User, I had to ask some key questions.</p><ul><li>What do they like or dislike about in store shopping?</li><li>What is Main Street to you?</li><li>What is the biggest determining factor for your shopping?</li><li>Is shopping local important to you?</li></ul><p>Supplemented by other questions, key information was unearthed.</p><ul><li>People enjoy buying things (of course)</li><li>People prefer convenience (distance, transit, and time all being factors)</li><li>Shopping local is important, but convenience ranks higher</li><li>Cost (a factor, but does not dictate decisions)</li></ul><blockquote>“Shopping local is important, but convenience ranks higher”</blockquote><h4>Direct</h4><h3>Domain Research</h3><p>To gather some context, I looked at organizations with similar websites. As a direct competitor, I focused on Mount Pleasant Business Improvement Area.</p><p><a href="http://mountpleasantbia.com/"><em>http://mountpleasantbia.com/</em></a></p><p>Mount Pleasant BIA had a built in search engine to assist in finding information. However, the primary navigation was also confusing and disorganized.</p><h4>Indirect</h4><h3>Domain Research</h3><p>With a focus on e-commerce, indirect competitor research was collected. Who better than large online merchants to draw inspiration from?</p><p>To list a few:</p><ul><li>eBay</li><li>Amazon</li><li>Etsy</li></ul><p>These companies deal with massive quantities of varying product every day. Even though they lacked the “local” aspect in their e-commerce, there was valuable insight to be drawn from their respective business’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_wpY9Slzvb6IkDNrq2cFMg.png" /><figcaption>Obstacles | Organizing | Sitemap | Userflow</figcaption></figure><h3>Obstacles</h3><p>Main Street has a very broad &amp; eclectic range of stores. People visiting Main Street also do so for varying reasons. This posed a problem. How do you group them into categories?</p><h3>Organizing</h3><h4>It came down to the following.</h4><p>Main Street consists of…</p><ul><li>Stores &amp; Services</li><li>Restaurants, Cafes, and Pubs/Bars</li></ul><p>People visit Main Street to…</p><ul><li>Shop</li><li>Eat &amp; Drink</li><li>Socialize</li></ul><p>From there it was clear. Mainstreet.ca’s primary navigation was set.</p><ul><li>Shop</li><li>Food &amp; Drink</li><li>Promotions &amp; Events</li></ul><blockquote>“From there it was clear. Mainstreet.ca’s primary navigation was set.”</blockquote><h3>Site Map — User Flow</h3><p>Enter the foundation of Shopmain.ca.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_oABVVEgT08BWps-ExIsSQ.png" /><figcaption>Green indicating User’s ideal flow through the website Site Map</figcaption></figure><p>The primary navigation was stripped of all confusion and replaced with four key choices. Through the new site map, Users could browse and purchase items in a little as three clicks leading into checkout.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nJqqykSwCjGWjsJENaCxOA.png" /><figcaption>UI Paper Sketches | Paper Testing | Digital Mid Fidelity Prototype | Digital Testing</figcaption></figure><h3>UI Paper Sketches</h3><p>Paper sketches are a great way of getting ideas onto paper. They require minimal time investment, and allow for multiple versions to be communicated.</p><p>Below are a few mid-high fidelity UI sketches for the Shopmain website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/562/1*8iOtw2UzOmnQIw0tZ2J5bQ.jpeg" /><figcaption>Mid-high fidelity Paper UI for Shopmain.ca Homepage</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f3-JCzDcK7kZYNFXy0ozog.jpeg" /><figcaption>Mid-high fidelity Paper UI for Shopmain.ca Product Page</figcaption></figure><h3>Paper Testing</h3><p>I cannot stress the importance of testing throughout the design phase enough. The ability to find and fix problems in the design early on is invaluable. You save time, effort, and a ton of headaches in doing so.</p><p>During my paper prototype testing I came across some User dilemmas.</p><h4>Store tiles had two buttons. VISIT &amp; SHOP.</h4><p>The confusion here was in the language. User’s found it confusing defining “VISIT” as a link to store information, and “Shop” as a link to store products.</p><h4>Deals &amp; Events grouped on Homepage</h4><p>The problem with Deals &amp; Events grouped together was that they did not relate to one another. This did little to confuse the user in their journey, however it created an option that distracted from the ideal User flow.</p><h3>Mid Fidelity Prototype — Digital Testing</h3><iframe src="https://cdn.embedly.com/widgets/media.html?url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dz56TP_0M8Ws&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fz56TP_0M8Ws&amp;type=text%2Fhtml&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/533bc5ad221ed415f0f07f627d12bf92/href">https://medium.com/media/533bc5ad221ed415f0f07f627d12bf92/href</a></iframe><h4>The Problems</h4><p>Users had concerns over the placement of filters (for sorting products &amp; stores). There was also confusion over types of filters available. The biggest problem Users came across, was differentiating the Store Pages from the Product Pages.</p><h3>Summary</h3><p>After designing these prototypes, the final product was a far more streamline experience for the User. Now Users would be able to support local business through the convenience of online shopping. As a company, Shopmain.ca remains relevant by drawing from an expanding market.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba435dc4126a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>