<?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 Jason Ng on Medium]]></title>
        <description><![CDATA[Stories by Jason Ng on Medium]]></description>
        <link>https://medium.com/@jsanng?source=rss-613b9749cdf2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*qakblxWM2zFiV0OY.</url>
            <title>Stories by Jason Ng on Medium</title>
            <link>https://medium.com/@jsanng?source=rss-613b9749cdf2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:58:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jsanng/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[Small changes boast big performance gains.]]></title>
            <link>https://medium.com/@jsanng/small-changes-boast-big-performance-gains-43622c42657e?source=rss-613b9749cdf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/43622c42657e</guid>
            <category><![CDATA[virtual-reality]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[oculus-rift]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[a-b-testing]]></category>
            <dc:creator><![CDATA[Jason Ng]]></dc:creator>
            <pubDate>Thu, 30 Mar 2017 18:35:59 GMT</pubDate>
            <atom:updated>2017-03-30T18:35:59.179Z</atom:updated>
            <content:encoded><![CDATA[<p>Companies today fall and rise though design of they’re websites, but how much can one company actually improve customer satisfaction and sales though design? Taking a beloved industry’s website, I took a chance to improve a efficiency and effectiveness of industry leader in VR.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*atpfGs8q15v6jul1ubVF-Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/943/1*b0bCt6gn67zqwPXQnT0odw.png" /></figure><p>HTC VIVE is the leading performance VR headset retailer in the world. Outselling the Oculus Rift by a fair margin. With a industry giant HTC at the helm, one would suspect they would have a great website for they’re great product. Don’t get me wrong, it is not a bad website. It’s just that its not very well optimized.</p><p>(You might want to read this on a desktop for the next section down)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6bOwMIZD9RVQsdUPRe-2fg.jpeg" /></figure><p>The site is beautiful visually, with black ascetics to make colours pop and great product shots to showcase the awesomeness that is the VIVE. But under the colors and imagery lies a sleeping beast that needs to be addressed.</p><p>Lets start from the top, VIVEPORT. What does that mean? If the label was to draw in clicks, yes it may work but as for a person that is trying to navigate the site itself, its horrible. HTC logo on the right is confusing, yes VIVE is owned by HTC but this is VIVE’s website, HTC logo should be placed somewhere else where it isn’t competing with VIVE’s and its just over the shopping cart. Am I shopping at HTC or VIVE?</p><p>Wording is bunched up together and slow to read in the hero image. CTA unexpected just pushes you to the shopping cart adding a VIVE directly. It is possible for some users that want to just buy the VIVE without any other consideration, but for most part people want to go though the product information before buying.</p><p>Videos autoplay somewhat useless looping backgrounds which slow down the load time of the already long website and the video down below is arguably useless.</p><p>I will cut my list short. I do admit all of the above are elements I just view to be problems without actual numbers behind them and maybe HTC has found this really has worked for them.</p><p>But if you really took a deep look at VIVE’s website I’m pretty sure you would see some glaring issues as well. I mean the webpage is still going down next to what I am writing still.</p><p>There are many things to test and retest about the actual success of the website and how quickly users can navigate though the website, but I choose 3 task which I believe are believable and pit the original website with my optimized website.</p><h3>Rules of the Game:</h3><p>First of all I should clarify what my boundaries are for the site :</p><ul><li>Must keep all functionality of homepage intact</li><li>All content used must already exist within website</li><li>Changes boast a 80% success rate &amp; lower timings</li></ul><p>I had some ideas of what I wanted to do to tackle the issues of what I saw, but they could be mostly split in to the following:</p><ul><li>Reduce travel time to target — lower time to task completion</li><li>Improve readability — improve findability and lower task time</li><li>Focus on single persona narrative — reduce failures and unnecessary links</li><li>Consolidate similar categories/links — increase findability and decrease task time</li></ul><h3>The Journey</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/865/1*sJIU99mTPcM0tWPe8SS40A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/905/1*9uQ4ro1QJjflIpw8q8zgGw.jpeg" /></figure><p>Addressing the copy at the top navigation and the logo, the navigation has seen a few changes on top. Pulling the language/country selection that was placed in the footer to the top right so that people wouldn’t have to run though the whole site just to change the region. Removing news links from the page and placing a blog page cleaned up the main page and allowed a more focus narrative for the user to move though.</p><p>Copy though out the front page has been spaced out a bit more to allow breathability between lines making it less stressful to read and allow a quicker glance at the information. Each module of the website has a clear action that invokes the user to take or move down the page, every part of the site is prodding the user to take a path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/893/1*nsZdOcdhSPwUOIZeazgInA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/953/1*FA9cSeu_vi8SyR09hI0tEA.jpeg" /></figure><p>Grouping of parts of the landing page have been grouped up different to be more relevant and more effective for the user to find. Font and copy was made sure it made was up to standards for readability for accessibility. No grey on grey or white text on photos colored photos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/789/1*qUIK07VVJqQo0C6MngjaYQ.jpeg" /></figure><p>Cutting out 40% of the site to reduce travel to target was a bit tricky. I created 2 versions of the site to test a theory that adding my version of the narrative would be more affective then the one currently used. Version 1 had the modules in the same order with my adjustments made. Version 2 was fully adjusted.</p><h3><strong>The Adventure</strong></h3><p>The time came when I felt happy with the work done. The optimizing took a bit less then 2 days work on and off. I would conduct an A/B/C test for the original, version 1, and version 2.</p><p>Task to be given to the sites where not going to be like “find the price of the unit” or “where would you go find contact information”. My task where more common task I the public would probably wish to find out.</p><p>Task 1: You are interested in trying on the VIVE VR headset in person. Where would you click to find a place near you?</p><p>Task 2: Where would you go to see if your computer system was VR Ready?</p><p>Task 3: Where would you check on shipment status of your order?</p><p>The task results would be judged on success of task and time on task.</p><p>Ready, set. go!</p><p>After waiting over the weekend, I received 47 online participates. Unfortunately, many of them dropped before finish the test and had to be disqualified from the results. Only 22 of the 47 results where used. Now 22 is surely not enough of a sample size to be accurate, but should be a good ballpark figure if improvements where made or had the opposite affect on the site.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/808/1*6DIiw1hMMPajT-GhqSoT_w.jpeg" /></figure><p>Results where not overly surprising, but improvement numbers where. On average the original site was just shy of an average of 65% success rate an average of 27.5 seconds for the 3 task. The version 1 pulled much better already then the original with just changing the labels and minor visual tweaks. Version 1 pulled just shy of 15% more successful then the original and was just shy of cutting the task on time by half. Version 2 wrecked the original site. Average task success was 92.5% and a task on time under 50% of the original.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_1ZJLWscJXl_2ZHQoKVfIw.png" /></figure><p>The changes where not very big, other then the reordering of the modules around everything looked very similar to its original counterpart. But you can’t argue that the original site can be improved upon greatly for the user using it.</p><p>In the end small changes on the existing site was enough to improve on the effectiveness and efficiency of what the users needed to do. In the real world, speed of accomplishing the task and the smoothness of doing are a big factor of the user bailing out of a sale or even considering it. Remember it doesn’t take a redesign of the site to get great numbers. Sometimes…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*duZeQ61pzQuGTGd8QPn6cA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43622c42657e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Trust is needed in the digital and real world when designing]]></title>
            <link>https://medium.com/@jsanng/trust-is-needed-in-the-digital-and-real-world-when-designing-a-ux-case-study-728e8d3433e6?source=rss-613b9749cdf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/728e8d3433e6</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jason Ng]]></dc:creator>
            <pubDate>Wed, 22 Feb 2017 09:33:48 GMT</pubDate>
            <atom:updated>2017-03-27T14:09:59.132Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Parts of the service and company in this study are under NDA so you will have to excuse some vagueness.</em></p><p>Have you ever had that time when your supervisor or boss tells you to do a job and leaves no instructions or help on what you need to do then leaves early off work to leave you alone in the dark? Yah, it’s that kind of story. Lucky, UX is a researched based approach to a problem. So let’s figure out how to start this.</p><p>The project was to help a local startup business to help them with designing a mobile app for listing spaces to rent out. When we were given the outline of what the company was doing, we were feeling a bit left in the cold when we found out that would be the jist of what they would be providing us (well they gave us their logo). Maybe it was just our expectations of a startup would have more information to give to us or maybe we were hoping for a more support on driving our research process quicker. The site they had was a slightly modified template which did the functionality of their idea but the site was overall broken with many functions not being easily usable or slightly broken in its functionality. Basically the site was in a sense a place holder for their concept and would be revamped soon when they had the time to do so.</p><p>With nothing in hand except a lackluster website and the core concept of the service the team was trying to provide we were off to the races. 3 weeks to provide a high fidelity prototype, documentation of our process, and a summary of our findings in a report.</p><p>We initially thought we would start off finding out what users liked or disliked about service in hand, but the owners were very uptight about giving their clients emails to us as they had made a wrong decision before by overloading them with emails daily. You could imagine why they don’t want any emails sent out to them. It was a big blow to our research as we couldn’t find out what people like about the service or any insight about the process of the service that was done offline. With the road we were lead down to go on, we decided to do what we could and stir up our own number with our own survey. We drafted one up on day two and sent them out to everyone and anyone that would do it. It was a general survey in general asking people if they used a service like it or would the even use a service we had in mind. What would their fears or motivations for using such a service? The numbers gave us a start on our persona, somewhat a bottleneck for our team to continue with our next phase. It is hard to build something when you don’t know who its for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_2YyPI5PsLSxQDnwtp8Ryg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m2EyJwDIT3yjV7oc8xBJIA.png" /><figcaption>“Cash strapped host” and “Alternatives renter”</figcaption></figure><p>We built up two personas with our survey information and labeled them “Cash strapped host” and “Alternatives renter”. The app had its users and we where off to find out what was most important to the users when using our app. Turns out like most services in the world, a big concern was not the app itself but the service provided when using the app. Being a kind of middle guy for host and renters left the question of trust and security problems in most of our survey replies. 81% of the surveys said the service was useful, but 54% said they would not likely use the service themselves. So what gives?Diving a bit in our open ended questions 95% of the surveyors replied in regards to fears or concerns about trust or security issues. Something we had very little control over due to nature of the service provided.</p><p>In most startups trying to enter a very competitive scene, trying to build trust and some sense of reliability is tough. How does any person really learn to to be trusted? To do what everyone else does, copying everyone first. They learn how to do the fundamentals of what they try to accomplish and set an example of themselves. Other companies have already done the research before hand. The information is out there if you just blow off the dust off the first layer. In our case we went to AirBnB, Facebook, and Uber to find out what they did to help build trust. We first looked at security measures such as verification, social media login, and actual physical security measures. But we ultimately found that those features provided more of a secure feeling, but not trust. You can give your money to the bank and you would feel secure about your money in it, but I doubt many people really trust their bank. So we turn our heads elsewhere, what other factors did we overlook? As most easy answers are hard to find, we had to end up brainstorming about the idea of what the company wanted to build that was inline with AirBnB, Facebook, and Uber. Community was the golden egg we were searching for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cOtogC2ncwQ9Ls30936nRg.jpeg" /><figcaption>Brainstorming trust and security</figcaption></figure><p>Though building of a community of users could grow the trust and security of the company to act as a responsible mediator between parties. Looking at other sites we decided on a few elements that we felt would be easy to integrate in our design as well help with building community and expanding trust. We ended up with a few but major ones were friendly copy, social integration, profiles, and phone verification. With our new tools in hand and our goal to make an app that was build around not only the service but to also build a sense of community of users. We were off to design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*NWt53B8jr3fZw2DdtcITmg.png" /></figure><p>The design was very much a mash up between AirBnB and CouchSurfing apps. Working with our core function of the app we built upon a layer of “nice to have” features that complemented the app as a whole.</p><p>As a group we rushed our mid-fidelity screens, each member taking an arm of the app itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*aUJS9O3aGWm60IRQBVutjQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*oBXURBEgiwYg1Aw9M5rTow.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*6rAixRuurtauOHmN75eEfQ.png" /><figcaption>Few of the mid fidelity screen I made</figcaption></figure><p>Seeing many of our members where more then willing to do the wire framing and UI parts. I turned my head with a fellow partner on the two major parts to our project. The presentation and summery report of our project. I was never much of a writer (even this case study is asking much of me), so I opted for the presentation route and hoped my skills in visual cues could make for a better visual deck during presenting. But it wasn’t all I was getting in to. With all my other members busy with their duties, I realized the whole flow and content of the presentation was left in my hands. I spent two days thinking of the flow of the presentation and what aspect to included. We had 15 minutes to present our process and our prototype functionality to our client. I knew it would at least take 6 minutes to do the prototype run through, leaving less then 9 minutes to talk about our findings. As we had two audiences to please (the clients and our classmates), I broke up the presentation up in to intro, research, conflicts, UI, and prototype. Introduction was just to bring the classmates up to speed with our actual project so the clients and classmates where on the same starting page. Research dove in to key findings we found interesting (survey and domain research) and lead to our conflicts(trust and security). UI was touching on our UI choices (duh) and finishing with a demo of our personas running though our prototype and it’s features. I choose to go with one of company’s colors to do the presentation. Infographics is something new to me, but taking a few cues from other classmates and having taken a lesson on the topic just the day before helped me develop a style I felt comfortable with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6IJXxqdM98vZyNGrabcAKg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KY40hBKym99nA-5CpAylAg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uNNivec_Adh6XKBXXZiEnA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9VEyt0iDbjV-R2eTkSctDw.jpeg" /></figure><p>The slides where all design in sketch then imported in to goggle slides for the presentation. Small complications of small edits some members wanted to make with their slides regarding their part of the presentation would have to be done by me since I had the working file and fonts for the slide was a small price to pay for more interesting slides.</p><p>Presentation came day came too soon, but we felt confident in our end product and our research was solid. We even did a trial run of our presentation the day before as our clients were not going to be present during our time. We had to stream our screen while skyping them. We did our best to simulate the actual event as best we could but nothing is ever perfect. We ended up with a lag in our presentation where our slides didn’t transition well sometimes. It may have had to do with the fact we were streaming, skyping, and running the slide of the cloud. If done next time, it would probably be best to run the slide offline to reduce the internet usage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ordbv4ajsLXSeE7bP1gP7w.jpeg" /><figcaption>Presentation run though the night before</figcaption></figure><p>This had been our first project with a real client in hand, and a very memorable experience. It is also the first time in our project cycle where I wasn’t in touch with every aspect of the project. As trust was an issue with our project, trust was also factor with our members. We have always had our hand in everything we produced from head to finish because we wanted to learn and get used to every aspect of the design process. With sprints you tend not to have that luxury of being able to do so. Learning to see other member strengths and passion for something should ease the thought of moving on to work on other parts that are needed. We are in the age where waterfall method is dated and isn’t the most effective in sprints. Building relationships with your members does pay greatly in this case. It is the reason I probably stuck with them going in to the next project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=728e8d3433e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Distillery Brick Road Story]]></title>
            <link>https://medium.com/red-academy/the-distillery-story-ux-case-study-8cdfa7aeb6cd?source=rss-613b9749cdf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/8cdfa7aeb6cd</guid>
            <category><![CDATA[students]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Jason Ng]]></dc:creator>
            <pubDate>Mon, 30 Jan 2017 10:40:46 GMT</pubDate>
            <atom:updated>2017-03-27T14:10:16.935Z</atom:updated>
            <content:encoded><![CDATA[<p>After burning through the first week of class at Red Academy UX design professional, we were quickly pushed onto our second project. Unlike our first, this time it was a group project of 4 members. Our assignment was to assess one of three markets in the downtown area and create a ecommerce solution for them to help them boost their sales. The assignment was to be released for a desktop browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*okd1TnwwmlEWPnMdhaCL1g.jpeg" /><figcaption>Our quick view of the 3 markets we could choose from.</figcaption></figure><p>After grouping up with my fellow members: Rebecca, Vivian, and Juhi. We took a quick glance at the choice of markets we had before us and decided on the Distillery District. Rebecca had never been to the Distillery and we were deciding that it would be beneficial if we all took a look at what we were getting ourselves into.</p><p>When we arrived, it was rather cool being -5 degrees Celsius with some wind picking up. The alleys were rather empty and we thought it would be rather hard to gather any interviews in such weather. But since we were there we tried our best and managed to scavenge a few from some locals that were on their usual daily walk with their dogs and some store owners before closing. That night we launched our online survey for their general online shopping concerns, habits, and values. We quickly gained 50 surveys replies and closed the survey because of time constraints and needed conclude our first round of our research.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nNVYpbDE0qqC40Sp0rc7cA.jpeg" /><figcaption>The Distillery District</figcaption></figure><p>With a few interviews and sizable survey sample down in 2 days we felt pretty good on our outreach research. We of course personally wished we could gather more information but we had to sum up our findings to match our schedule for the due date. What we found was in general, online shoppers value quality goods and a competitive low price for the item they were buying. They mostly worried about items not being true to their online descriptions or pictures and lack of customer support for questions and return options once purchased. The trip to the Distillery and interviews showed us the area was mostly targeting people with higher quality or unique items in mind. A strong emphases on customer service because of the owners being in store and being a tourist area.</p><p>The problems we could identify were that the pricing bracket was rather high and there was no real marketing help from the Distillery District owners. The store owners mostly had a online presence in one form or another, but the range in the experience and quality of the sites ranged from Facebook pages to quality online ecommerce stores. The Distillery District website did little justice for the atmosphere or experience the physical location provided.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/747/1*f7lAC1lm7mgTb2DTj-N4tw.png" /><figcaption>Original Distillery Website</figcaption></figure><p>We gathered up our data and put up an affinity diagram that produced 4 personas which we thought would be all the likely possible users of our platform. We compared the Distillery’s website without high scaled shopping locations such as Yorkdale, Holt Renfrew, and Toronto Premium Outlet. All which had a clean layout like the Distillery’s but lead a much higher standard to the content and interaction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/447/1*qaxaE3a6hbGjV9jEGEl9Tg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*ckAefnYZNTUyQvL2ADqzaA.png" /></figure><p>Storyboards, flow chat, scenarios, stories, and user cases where pumped out with the vast amount of data that seemed to accumulated at our feet. Then our first group meeting for a recap of our status at the end of our first week came. We might have came off with the idea trying to please as many people as possible with our many personas. The amount of work we had done during our planning phase was probably a lot of work that didn’t need to be done if we focused on our primary persona. With some advice from our teachers we decided to provide a more focus experience for our primary persona rather than perhaps what might have been a watered down version of what we should have done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/577/1*VzwLOavvxHWisPSvqNQqUA.png" /><figcaption>Our primary persona, The Fashion Connoisseur.</figcaption></figure><p>With a focused target in mind we now where on way to figure how to fit all our researched in our design. Some of our research was a little bit irrelevant as our original idea of e-commerce and target persona was changed during our meeting. We reformed what we thought was relevant and repackaged the deliverable. Targeting a fashion connoisseur persona the product would be would be packaged to cater to a person who was looking for a quality unique items which would overlook the pricing. Something that was inline with the Distillery’s market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H425WIupX2xA8ACj5UvsCQ.jpeg" /><figcaption>Affinity diagram post-it attack!</figcaption></figure><p>We put our flow chart up on the scrub board and drew up a hybrid site map to help visualize the actual screens and flow of the user interacting with the site. It helped members realize what would be needed in each page better and a better feel of what the overall sense of the site was going to be. Having spend some time reassessing our target and reassuring our goals before we moved on , it was nice to see our actual product on the board in some detail. We could see the finish line. Though time was getting close to the deadline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*98MCg5jvzdC7-xFW5Us2Dg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jU56ypDsGx1TAfcJ2xeXLw.jpeg" /><figcaption>Sitemap planning and UI brain storming.</figcaption></figure><p>The wire framing came pretty quickly with all of us wanting to do our part (though it would bite us later one). We had our first prototype done and it was simple, but inconsistent as we had different styles of what we wanted and spacing for everyone was different. We had the same header or footer, but the main part of pages would vary. Me and Vivian ended up doing the clean up as time was short and having everyone redo their own pages might just end up having us double check everything anyways. With some QA down. We were pleased with our prototype to let it be tested.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wwZfhpS13_AUDY6kKKnHsw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ibhtw3iGdc21XI5BPuMWSg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j2qTMwFX83ZeugbTr9v8Mw.png" /><figcaption>First versions of prototype pages.</figcaption></figure><p>The response was average, many users needed context of how things were being use. It was usable, and many users thought it was good for what it was. Though they didn’t see the true underlying mission. The prototype still lacked the cohesion that a tuned website had. It’s ability to push our ideal of telling a story of the vendors and the district was lacking in our layout. Grid formats and having a slightly text heavy design didn’t go well with our high quality and unique story telling we wanted. We took our front page’s design of mosaic of stories layout and applied it to the rest of the pages to give the feel of a magazine. Tuning the nav bar’s lackluster naming to something more in tune with the story telling theme and fixed more of the spacing issues we came up with our final product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4yzbOs4ezv5UVOQxfJrU9A.jpeg" /></figure><p>Our Invision Prototype: <a href="https://projects.invisionapp.com/share/RZA6PVLJ4#/screens">https://projects.invisionapp.com/share/RZA6PVLJ4#/screens</a></p><p>We managed to finish the final version of our prototype only the day before the presentations. One of our members was away for the day as well. We had to build up our presentation during our after hours. We split up our workload up in four parts with each person responsible for each phase of the project. I was responsible for the research. There was very little time to do anything really polished. Figuring what to put in the 10–15 minute presentation was hard enough with less than 4 minutes for each person to talk. I figured though a research was a big part and tried to rush though as much as I could as it was the research that pushed us down this path. Visuals where something I really wanted to put in the presentation but time didn’t allow for it. I tried to follow our theme of storytelling and try to lead the presentation though a story of how we started our process, it would not last though the presentation but at least would grab the attention of the viewers from the start at least.</p><p>After the presentation, I was glad to hear the overall good reviews from our teachers. We had a very poor slides to accommodate our own speeches but we stayed true to showcasing our process which seemed to shine out bright. It gave me a second light on the process I believed to be very natural. Research facts that leaded to a logical plan. Everyone in our group of course was still learning and still was very hands on every part of the project. Perhaps if we split the work we would have done better or effectively, but something about walking with my peers step by step down the path as something I don’t think I would want to take back. Very much like Dorothy walking with her 3 newly found friends down the golden brick road. We supported each other through every trial learning ourselves and teaching when others they needed the help. That’s a UX design experience worth experiencing again if time permits.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8cdfa7aeb6cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/red-academy/the-distillery-story-ux-case-study-8cdfa7aeb6cd">The Distillery Brick Road Story</a> was originally published in <a href="https://medium.com/red-academy">RED Academy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Be like the lawn mower]]></title>
            <link>https://medium.com/red-academy/be-like-the-lawn-mower-an-ux-design-process-case-study-34c61e9245fe?source=rss-613b9749cdf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/34c61e9245fe</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Jason Ng]]></dc:creator>
            <pubDate>Sat, 14 Jan 2017 22:53:27 GMT</pubDate>
            <atom:updated>2017-03-27T14:10:36.912Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This case study outlining the process I went through as students at RED Academy working on my first individual project. The assignment handed to us was to interview a classmate and develop an app in which could help them in their problem or frustration.</em></p><p>Hi my name is Jason Ng, an inspiring student at Red Academy to become a UX Designer. As our first week of class just passes, we have already race though the basics of user experience design process.</p><h4>Opportunity:</h4><p>Our first project was to produce an app to help with a classmate’s problem/frustration we discover during a quick interview with them. My partner for the project was Gabriel, a mid aged stand up guy that has been happy married for a year and a half. He had a interest in listening to music and reading books. Enjoyed and wished to improve on family relations as most of his family is out of country. He is educated in English at University of Toronto and continued on to teacher college.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvwbOWroj4w2-WWc8bWjmw.jpeg" /><figcaption>Gabriel’s Persona based on his interview.</figcaption></figure><h4>Problem:</h4><p>So there were two problems I singled out. One being his wanting of more communication with his family members afar and the other being organizing his collection of records for him to be accessible at any time. I went with the family communication route as it seemed more interesting to me.</p><h4>Reflection:</h4><p>It had been 2 days since we started this project and we needed to present our findings and our answer by the end of the week (2 days later). The snag in the back of my head was still looming. The activities that Gabriel were already kinda addressing the issue he had. The app wasn’t really solving or adding the the solution much. The problem at end hadn’t been solved to the degree I wanted it, it wasn’t clear cut the problem had been solved after the use of the app. I went back to the notes and slides to see if anything could help out with the development of the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*RL4B1aGr5euf2cgMouF5zg.jpeg" /></figure><p>I came back to the example of the lawnmower. The product was simple and had a sole purpose. The use of the product solved your problem right after you used it. My app didn’t have that, it was failing.</p><p>I was in a dilemma. I literally had a day and a half to solve this problem.</p><h4>Revisit:</h4><p>I went back to Gabriel about the second problem which was about his collection. I got to know the reason why he would like like to index his collection and have it with him. The example of having a chance to buy a record but not fully knowing if they had it already out of the many records he already was a problem that had a clear cut problem and end goal. I had found my new project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*88wiv052jidRGvphM1hY8g.jpeg" /></figure><h4>Research:</h4><p>So I was to make a list or archive of records. Asking about how people would make such a list, many of them would go about as of writing a list down. A very practical but not very efficient way of cataloging a large about of items, especially when that list will be growing.</p><p>Apps that made list all had the common trait that you would type in your list of items or check mark them off a pre existing grouping. Again with typing, and checking off a list that maybe in this case over thousands if not millions of listing is not a practical scenario.</p><p>Like a ray of sunshine Gabriel did blurt out an idea to me randomly. He said “Would be great to have a index of inventory like stores do.” My mind flashed to the cash register scanner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*4GRqBlq9JhixpmTfab2SvA.jpeg" /></figure><h4>Solution:</h4><p>Retail stores don’t write down what they own, this isn’t the 18th century. Retail stores have an inventory system built on scanning. Incoming and outgoing goods are put through the system in which records what they have or just sold. Putting that back to our case. What if we were a store, as most collectors are just like a warehouse. Scanning items to record our list of collectibles is just super effective (if not it wouldn’t be used today in retail).</p><p>An app that creates list by scanning objects! I know the retail world uses UPC codes, but for fun I expanded the idea to visual covers because visual scanning is kinda a thing and not everything in this world has a UPC code. No more typing and a quick way to report back to you whether you have an item or not without searching for the item in your list yourself.</p><h4>Designing:</h4><p>The idea was a simple one with three steps:</p><ol><li>the ability to scan an item and pull up what it was</li><li>to put the item in a list if it is not exist in the list yet</li><li>to report back to the user if the item already existed in the list</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*34xnH9-yoIg5Fkg-Wm3-2Q.jpeg" /><figcaption>First and final drafts of user flow of entire app.</figcaption></figure><p>The flow of the app was very straight forward. It almost made me think I did it wrong because it was so simple. Fully flushing out the idea would complicate the flow, but not by a lot.</p><h4>Prototyping:</h4><p>The version first prototype was set up very quickly the following day. The usability was limited as we were performing the simulation though POP but it would give a good idea of how the app would perform. I gave the product to several other classmates to try. They mostly gave me a positive reaction, without much direction most of them knew it was an app to make a list and it used visual scanning to do so.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6tSjQ7JJKWousOnikLNNkQ.jpeg" /><figcaption>First paper prototypes.</figcaption></figure><p>Snags that came along where ideas of the app being a photo album app or it was just a list simple list maker. The core function was clear but enforcement of what it truly was for may have been needed. Insights of other classmates about this app’s true target and flow of how they navigated the app initially helped focus the direction of the final product. The difference between a collection and a list needed to be made clear. Making a few more screens about collections gave a bit more context of what the app was doing.</p><p>After some redesign and detail to some elements I received a more stable reaction from users.</p><h4>Summary:</h4><p>I am happy that I have a somewhat of a product I can called finished. It has been a rush to bring an idea to actual developing stage in such a short time but a very positive experience in my mind. The many suggestions and pointers out of my first prototype helped me push and enforce the idea of what app was for, but it was the clear cut goal of what needed to be done that lead me here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KKeSKQJeWxhkjWHFLC1emA.jpeg" /><figcaption>The latest iteration of the app.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34c61e9245fe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/red-academy/be-like-the-lawn-mower-an-ux-design-process-case-study-34c61e9245fe">Be like the lawn mower</a> was originally published in <a href="https://medium.com/red-academy">RED Academy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>