<?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 Mitch Mills on Medium]]></title>
        <description><![CDATA[Stories by Mitch Mills on Medium]]></description>
        <link>https://medium.com/@xihlus?source=rss-6a352745a253------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*jOc8t_V7-7RmSGS5LyLumw.jpeg</url>
            <title>Stories by Mitch Mills on Medium</title>
            <link>https://medium.com/@xihlus?source=rss-6a352745a253------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 05:26:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@xihlus/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[How a dated feature could be tomorrows usability standard.]]></title>
            <link>https://medium.com/swlh/how-a-dated-feature-could-be-tomorrows-usability-standard-57d8bd5b2b16?source=rss-6a352745a253------2</link>
            <guid isPermaLink="false">https://medium.com/p/57d8bd5b2b16</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Mitch Mills]]></dc:creator>
            <pubDate>Fri, 15 May 2020 23:51:23 GMT</pubDate>
            <atom:updated>2020-05-16T21:11:15.278Z</atom:updated>
            <content:encoded><![CDATA[<h4>Gaining UI inspiration from the past.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NHhkmb0VjVzMPNiVnLYH3A.jpeg" /></figure><h3>If you could travel through time with a single idea from today, which idea would you choose and where would you travel too? A simple yet truly fascinating question that gives way to a variety of answers, many in the hopes of achieving status or wealth by visiting the past. More interestingly however is just how few of us would think to carry that idea forward into the future. 🤔</h3><p>Have you ever accidentally sent an incomplete message, or maybe made a transfer with the wrong amount to someone. These sort of blunders happen frequently, often all it takes is a tap of a finger.</p><p>Sometimes the unintentional press of a button can have dire consequences for a user, leading to the loss of data, requiring rewriting paragraphs of lost content, frustrating support calls, submitting tickets, and other various stressful situations. This phenomena is uncommon in testing, in fact over the last two years of conducting product testing i’ve only ever come across a situation like this once, and that was due to the lack of a <a href="https://medium.com/allenhwkim/modal-or-not-modal-3d65de64d82c"><em>modal dialog</em></a> to prevent an unconfirmed deletion of an account; the traditional method in place aimed at preventing such occurrences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Y6VeDKBDwyalDvnykCffw.png" /><figcaption>modal dialog example</figcaption></figure><p>This method in itself is tried and true, it provides security against unintentional action on the users behalf and only requires an additional tap, a universally agreed upon interaction cost.</p><h4>Question Convention:</h4><p>Are you familiar with the idea of synergy? Simply put, synergy is achieved when: “the whole is greater than the sum of its parts”. A common expression in the world of upper management, we strive to create team dynamics that help amplify our team members potential and output. When we look into the systems we create as experience / interface designers it&#39;s not unlike that of a team (“things” working together to do “something” greater), so the principle of synergy remains true.</p><p>In the case of a modal, the user clicks “Do this thing”, and is then met with a window exclaiming “Please verify”… This takes two actions to achieve two things, firstly initiating an action and secondly confirming the action. In synergy terms its 1:1, not terrible but theres certainly room for improvement. Let’s strive to do more with less.</p><h4>Exploring Solutions:</h4><p>When i first began down this train of thought I hypothesized that it would be possible to reduce both an intent and confirmation of intent in a single action. Essentially, bypass the need for a modal, which seemingly flet like a bandaid for an otherwise inadequate interaction method at this point. I took inspiration from existing solutions; check boxes, captcha, hiding the button behind the fold, and so on. While some of these solutions were more elegant than others, they all required two steps to complete, be it a scroll to tap or multiple taps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t11iaoMbRYmSLsnuHWkVNQ.png" /></figure><p>Slide to unlock in its traditional use, is a feature we haven’t quite seen in awhile, and for good reason. Hardware capabilities have allowed us to develop faster, more convenient and secure ways of entering our phones. Think biometrics or facial recognition. These innovations have effectively rendered this interaction unnecessary for the greater part of a decade. Looking back, this elegant solution to a lack of physical switches or buttons; leave it to apple, is exactly the type of interaction I was searching for. It achieve the interaction synergy at 1:2, one ‘input’ required to both perform an action and validate it.</p><h4>Implementation:</h4><p>Buttons are wonderful, multiple buttons less so. When looking at usability and UI its important to eliminate the complexity of a system, each interaction can be thought of as having a cost associated, ‘interaction cost’, the more a user is required to spend, the less likely they are to stick around your platform. Fortunately we were able to leverage on ‘old’ feature to help us achieve synergy in our interaction, as shown:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_B01lQVxnsOuIeHoOP_42g.jpeg" /><figcaption>Traditional two step verification (Supported with haptic &amp; audio feedback)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HSfjb-CssCiq9LrSu2iqrw.jpeg" /><figcaption>Single step verification (Supported with haptic &amp; audio feedback)</figcaption></figure><p>We can see that in this particular case, leveraging an old feature allowed us to create a new standard of usability. We achieved synergy, ultimately improving usability and reducing interaction cost (friction). So let me ask you again, If you could travel through time with a single idea from today, which idea would you choose and where would you travel too?</p><p><strong>Thanks for reading! I hope you enjoyed this article, gained some meaningful insights and find inspiration for tomorrow by looking at the past</strong>. <strong>If you want to collaborate, talk shop, or simply share a conversation over coffee, drop me a line at hello@</strong><a href="http://www.mitchmills.com/"><strong>mitchmills.com</strong></a><strong> or connect via </strong><a href="https://www.linkedin.com/in/mitchmills/"><strong>LinkedIn</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57d8bd5b2b16" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/how-a-dated-feature-could-be-tomorrows-usability-standard-57d8bd5b2b16">How a dated feature could be tomorrows usability standard.</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we simplified user on-boarding of 925's mobile app — a UX Case Study]]></title>
            <link>https://blog.prototypr.io/how-we-simplified-user-on-boarding-of-925s-mobile-app-a-ux-case-study-27e5de165fea?source=rss-6a352745a253------2</link>
            <guid isPermaLink="false">https://medium.com/p/27e5de165fea</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Mitch Mills]]></dc:creator>
            <pubDate>Fri, 24 Apr 2020 23:21:41 GMT</pubDate>
            <atom:updated>2020-04-25T12:23:31.135Z</atom:updated>
            <content:encoded><![CDATA[<h3>How we simplified user on-boarding of 925&#39;s mobile app — a UX Case Study</h3><h4>Connecting businesses to people looking for flexible work.</h4><figure><img alt="Image of iPhone 11 Applicaiton Mockup" src="https://cdn-images-1.medium.com/max/1024/1*O3VRZ_Hap6UeUrinlHHMvA.jpeg" /></figure><p><strong>Prologue:</strong> While this is fundamentally a showcase of our process in the hopes of helping others, it’s also a story about the realism of limitations when working with clients and how we ultimately were able to deliver a product the client was pleased to receive and call their own.</p><p>On a day like any other autumn day in the office, I was approached by my employer with a rather vague request, “We have some business friends, they have a bit of a budget and would like us to rework the UX of their app, can you?” … A seemingly straightforward request right? Well yes but if there’s anything I&#39;ve learnt working closely with clients is that things are never as simple as, “Here’s a bunch of money, do the thing you do.” Oh no, don’t let yourself fall into that trap. Validate! Always validate what the expectations of an initiative are so that you can better meet those expectations but also gain greater control over what those expectation might be in the first place. Anyways after probing my employer further about the project I finally had my answer “We have some money, do UX” 🤦‍♂️</p><p>Unsatisfied with the lack of a brief I recruited one of out project managers to help me obtain one. The following morning we called the client and began asking questions, a 14 minute call later and we had exactly what we needed … “We are seeing a tremendous amount of drop-off through the sign-up process.” … “Can this be done before the end of the month.” … “We don’t really have a consistent UI system in place.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*CJykOx6Jv98v5kCrAm38SA.gif" /></figure><h3>Research Strategy</h3><p>Achieving a ‘better result’ requires taking a suitable approach. Design thinking has been a-well-known problem-solving method infused in the psyche of designers and start-ups. Design Thinking was familiar and quick to execute which suited the aggressive timeline set-forth by 925&#39;s investors. Design thinking was how we were going to do it.</p><figure><img alt="Design Thinking Process Diagram. Empathize, Define, Ideate, Prototype, Test" src="https://cdn-images-1.medium.com/max/1024/1*cRqAwDLIQofE8GxzKdI9ag.png" /></figure><h4><strong>Empathize</strong></h4><p>Having an aggressive timeline and fixed budget, it wasn’t going to be achievable spending much time conducting interviews. This is where UX fundamentally hinges, it’s absolutely crucial we base decisions in data and remove our own bias out of the equation as much as possible. However, this doesn&#39;t eliminate our ability to improve a product by identifying points of friction and alleviating points of pain through the user journey.</p><p>It&#39;s important to communicate this limitation to stakeholders when creating without genuinely complete user information and data. “I can make this, it will however be based on these assumptions that we agree upon and it’s recommended these decisions are validated in the near future … sign here”</p><p>So how did we empathize with the user? … Well we started by using the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5h-1AtW7qbmj9xAz5IieLA.jpeg" /></figure><h4><strong>Defining the Problem</strong></h4><p>A team of three, including myself set out to spend a small working session going through the sign up process and exploring the app. We were however unable to successfully complete the sign up process in any realistic amount of time, being periodically hindered by externally linked verification methods and forms. It became immediately apparent why users were not completing the registration process.</p><p>We confirmed this was a wide spread problem by having various co-workers and family members run through the same process, all of which had the same struggle with the app, which is :</p><p>That the 925 app was kind of confusing, the sign-up process asks for an exorbitant amount of information, mainly in the form of a background check performed through a third party service. This required the user to jump into a seperate browser to complete this section of the process. This web service also wasn’t optimized for mobile making it extremely difficult to use. At this point in the process users are unable to evaluate the offerings of the app and are instead met with a variety of challenges while trying to register.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b9txJ6OJGKJFpAl3GeJHfw.png" /><figcaption><em>Rule of thumb, keep people on your platform! redirecting users often causes confusion and frustration.</em></figcaption></figure><p>Our next step was to itemize all of the concerns people were experiencing through the registration process. It helps to get this research to the board to better organize and address these concerns in a prioritized manner. What we settled on was essentially a pseudo approach at user stories. None the less a valuable tool moving forward.</p><h4><strong>Ideate Solutions</strong></h4><p>We were faced with at least one glaring issue and a limited amount of time and budget to execute much else. The next step was to define <strong>How Might We</strong> notes. There’s never only one way to achieve something, this allows us to explore a variety of ideas (Diverge) so that we can better narrow down the ones that will work best for us later (Converge).</p><p>I speculated that the drop off was occurring due to the effort vs reward of the background check. This was however a key component of the service 925 offered. Workers needed to be vetted in order to build a trustworthy platform that employers would be comfortable using … or so it would seem.</p><p>One of the initial solutions that simulated the client during a post research / pre design meeting was the idea of “Uber for Work”, perhaps a little contrived but none the less an exciting proposition. It also had the added benefit of helping me pivot the structure of the app around a centralized feature (location based, map interface) versus say a traditional job listing. Simple but promising. Plus the idea had the support of the client behind it, that doesn&#39;t inherently make the decision the right one, but it&#39;s important that clients feel heard, this so happens to be a great way of achieving just that.</p><h4><strong>Wireframes</strong></h4><p>The process of creating wireframes is seemingly outlined the same way but in actuality is almost always some weird mixture of fidelities. While we strive to start with a paper sketch, followed by a lo-fi and eventually hi-fi interactive digital prototype, our workflow and project constraints may not necessarily allow us to segregate our ideation in such a linear fashion. For this project I did the very thing I was often told to avoid during my time in school and jumped right into digital creation. It worked, but it’s important to understand why it’s typically not a good idea to skip the doodles:</p><p>Sketching allows us to explore a greater amount of ideas in a shorter period of time, it allows us to get the bad ideas out of the way to make room for the good ones. When we begin with digital ideation, it can be extremely easy to explore certain directions that may not necessarily be all that suitable, hence wasting a great deal of time. It’s not a hard set rule to sketch first, it is however recommended and and will likely save you time later on.</p><p>I translated <strong>How Might We </strong>notes into a visual design solution, I began by creating art boards in Adobe XD with single words written on each one outlining the page or step in the flow, i based these around the existing user flow initially and later moved, added, and subtracted pages as needed until i had a flow that alleviated the barriers we experienced. Next i began writing a list of the required elements each of these pages would need to function. I like to think of this as sketching when working digitally, this stage is not about UI or visuals, rather structure and flow.</p><p>Once the structure has been defined you begin compartmentalizing and creating, because of the nature of app design we are constantly reusing visual elements, in a way its self referential which allows us to create quickly and consistently, i followed <a href="https://bradfrost.com/blog/post/atomic-web-design/">Atomic Design</a> Principles when building out the UI to keep consistency across screens.</p><p>Here’s the Adobe XD wireframes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QeB34WK88b-VkUSxTYT9ig.jpeg" /></figure><h4><strong>Prototype</strong></h4><p>Simulating a working product is going to allow us to conduct user testing quickly and in a way that best reflects the final product. It additionally allows us to present out design in a context that the clients will understand (not everyone has the ability to imagine how static images will interact with one another) this ultimately gives us a greater chance of approval when presenting our work. I used Adobe XD’s built in prototype tools to quickly link together the wireframes, while this allowed me to execute quickly it would mean giving up integrated access with <a href="https://maze.design/">Maze</a> a wonderful tool that allows you to gain accurate user feedback remotely.</p><h4><strong>Validation</strong></h4><p>In order to validate our ideas, we tested the design periodically against the original app with staff across the office and connections the client that best reflected the demographic who would be using the platform.</p><p>There are several steps that users went through. First, we showed them the original application and had them register. Followed by the same process using the new prototype. A-B Testing, although rudimentary allowed us to directly measure the impact of the changes made with users.</p><h3>Retrospective &amp; Conclusion</h3><p>Being a specialist in a <em>smaller agency</em> is seldom a picturesque role of performing a specific type of work every day. The reality is you’re often required to adjust your skill set as projects require. This project was one of those rare cases where I was given complete ownership over the project with support offered across the agency as required, essentially “You’re the expert, steer the ship” The interesting part about being the captain, is you have to know where you&#39;re going and how you&#39;re going to get there. This project came with a steep learning curve in the sense of project management; specifically dealing with client communication, time-estimates, budget, and billing.</p><p>At the end of the day, the final prototype can continue to be improved as more insights into user behaviour are discovered and pivot as new business cases arise. Overall this project was a great learning experience given both its opportunities and constraints.</p><p>If you’d like to review the app it is available on the <a href="https://apps.apple.com/us/app/925-freelancing/id1400043879?ls=1">App Store</a> and <a href="https://play.google.com/store/apps/details?id=com.ninetwofivefreelancing.ninetwofivefreelancing">Google Play Store</a>. Check out more about <a href="https://925freelancing.com/">925 Freelancing</a> to see how they are striving to help connect businesses to people looking for flexible work.</p><p><strong>Thanks for reading! I hope you enjoyed the UX process for this project. We discovered meaningful insights that will be very useful in future projects</strong>. <strong>If you want to collaborate, talk shop, or simply share a conversation over coffee, drop me a line at hello@</strong><a href="http://www.mitchmills.com/"><strong>mitchmills.com</strong></a><strong> or connect via </strong><a href="https://www.linkedin.com/in/mitchmills/"><strong>LinkedIn</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27e5de165fea" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/how-we-simplified-user-on-boarding-of-925s-mobile-app-a-ux-case-study-27e5de165fea">How we simplified user on-boarding of 925&#39;s mobile app — a UX Case Study</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Trove: A UX Case Study]]></title>
            <link>https://medium.com/nyc-design/trove-a-ux-case-study-e54b1ee6efc1?source=rss-6a352745a253------2</link>
            <guid isPermaLink="false">https://medium.com/p/e54b1ee6efc1</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[new-york]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Mitch Mills]]></dc:creator>
            <pubDate>Sat, 08 Sep 2018 23:46:40 GMT</pubDate>
            <atom:updated>2020-06-04T02:17:29.970Z</atom:updated>
            <content:encoded><![CDATA[<h4>Exploring the Habits of Wastefulness.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NjkR_Bd9VTSzKx3H.png" /></figure><p>For a moment, consider the fact that<strong> </strong>a third<strong> </strong>of the food grown annually for human consumption is never eaten. For one reason or another, it often ends up in the trash. Yet at the same time,<em> </em>815 million people around the world are starving. It’s a problem — however one with no shortage of solutions.</p><p>I, along with most people I know, reluctantly throw away a great deal more spoiled produce then we care to admit. Over the years, I have tried a few meal planners in hopes of helping remedy the often pungent decay of my compost bin and save a little money while at it. To no avail, I decided to put my UX designer hat on, venture into the wild, and validate my problem.</p><p>The following is a detailed look into my process, methodologies, findings, and challenges as I seek to answer the question <em>“How can we reduce the amount of food we waste?”</em></p><h3>My Design Process.</h3><p>To ensure my design decisions accurately reflected the needs and motives of users I based my process on <a href="https://uxplanet.org/empathy-and-product-design-669d71236fb2">Empathetic Design Thinking</a> and <a href="https://www.ideo.org/approach">IDEO’s Human-Centered Design</a>. As challenges arose, I would integrate aspects from various design methodologies to help best overcome the challenge at hand. These systems will be mentioned throughout the study.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/715/0*hmEWgWXgHwWmpX_u.png" /></figure><h3>Empathy in Design.</h3><p>As designers, its easy to make the mistake of just <em>doing the thing</em>. That is we take requests at face value. A client says to you, “I need a new website.” to which you respond, “Ok! Not a problem.” But is that really what they need to achieve their goals? It may very well be, however in this scenario we’ve missed an important part of any design process.</p><blockquote>It’s one thing to build something right, its another thing to build the right thing.</blockquote><p>User Experience design allows us to give the spotlight to an often overlooked aspect of creative projects. <em>Validation</em>, important because its one thing to build something right, its another thing to build the right thing the right way. By validating the existence of our problem we can effectively create purposeful designs with meaningful solutions.</p><h4>User Research Prep</h4><p>With a problem in mind, the first thing I needed to accomplish was verifying that others where also experiencing inconveniences regarding food waste. Focusing in on obtaining <a href="https://medium.com/ethnography-matters/why-big-data-needs-thick-data-b4b3e75e3d7">Thick Data</a> was the way I was going to accomplish this task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_kzbAORIFJJi6V-Q.png" /></figure><h4>Ethnography</h4><p>I conducted a few separate ethnographic studies, the first at a local grocery store and the second an ongoing observation on friends and family members. My goal was clear, disregard assumptions, simply observe and learn. These were some of my findings:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*epFu3bCuGXP78BBq.png" /></figure><ul><li><em>80% </em>of shoppers purchased fresh fruit or vegetables with <em>2/3</em> opting for organic produce.</li><li><em>75%</em> of all shoppers used a smartphone when grocery shopping.</li><li>Over <em>50%</em> of all dinners were planned within an hour of being made.</li><li>Only <em>30%</em> of meals were made from scratch.</li><li>In a household setting, <em>1/3</em> dinners remained unplanned and up to individual choice, concurrently frozen or instant meals were <em>80%</em> more likely on these days.</li><li><em>90%</em> of newly made meals were aided by a recipe viewed on a mobile device.</li></ul><h4>Interviews</h4><p>Following initial observations i composed a list of questions that i could use when conducting interviews. Not wanting want to badger people with otherwise systematic questions, i decided to use them to initiate points of interest, encouraging participants to tell me a contextual story. This allowed me to see a broader picture to the habits i observed earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Yxo31jPYIx4J_Ze6.png" /></figure><blockquote><em>“Even the other day i had to throw out some bad lettuce, its really my own fault though, i eat out often and forget whats in my fridge.” — Anders</em></blockquote><h4>Persona</h4><p>It was important to create a collective representation for my audience to easier reflect on who i was designing for. This was something that I came back to throughout my project to guide my design decisions and priorities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/0*d7_r1zilrumjSqMv.png" /></figure><h3>Defining the project.</h3><p>With my initial assumptions either validated or quelled and the problems facing users clearly identified, it was time to organize all of the new found data into useable tools.</p><h4>User Stories</h4><p>To better understand user needs and motivations, I used the <a href="https://jtbd.info/replacing-the-user-story-with-the-job-story-af7cdee10c27#.nq8fuuwk1">Jobs To Be Done framework</a> to explore different contexts in which an individual may proactively manage food consumption and waste management.</p><p>The following are some of the user stories i created based on interviews and contextual inquiries:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rQQNoPlcKtvYxEP6.png" /></figure><h4>Brainstorming</h4><p>This stage of the process is messy, raw, and undeniably paramount in the formation of an idea into an explorable concept. Below are some of the results of divergent ideation through the ‘discovery’ phase of Diverge &amp; Converge Design Thinking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/488/0*G-gjYB7N74mQhGsY.png" /></figure><p>A great deal of my initial ideas were … ambitious to say the least. I spent a great deal of time exploring the context in which the application would exist. Resulting in some interesting explorations into system architecture, logistics and, technological limitations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*faojB52xPgMGWa2q.png" /><figcaption>Whiteboard Conceptualization</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/0*FbQOH6R9tA-wfsoN.png" /><figcaption>Ecosystem Matrix (Revised)</figcaption></figure><h4>The Backlog</h4><p>Having a limited amount of time and no fixed scope, I decided to implement aspects of Agile to better plan and prioritize the project goals. I began by creating a backlog, this was used to estimate and prioritize the work effort over 60 days based on a prioritized list of user stories. The backlog was used to define key metrics and define project objectives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/0*bXzqGMF3ud24LvWh.png" /></figure><h3>Exploring Solutions.</h3><p>Before you can design something, you need to identify what that thing is going to be. Based on my previous ethnographic and contextual findings I concluded that a mobile application would be an accessible product that would fit into the lives of users with minimal friction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/97/0*4QCPhlJomvy6tIl0.png" /></figure><h4>Card Sort</h4><p>Easy to conduct and invaluable to the organization of information, i asked a number of peers to simply organized a stack of post-it-notes each with a function or feature of the application written on each note. The participants were instructed to organize the notes into groups then name each catagory as they saw fit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*_5F_SQRKk0m79tsn.jpeg" /></figure><h4>Task Flow</h4><p>I also created a variety of brief task flows to help envision what a certain process may look like, allowing me to better identify points of pain prior to building a prototype. Below is a simplified login model i used to evaluate the friction created via a login system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/0*arlyk5S_L_mHpR0e.png" /></figure><h4>Interface Flow</h4><p>When i began sketching I wanted to address points of pain. I explored a variety of concepts from unconventinal navigation systems to content navigation systems. Eventually leading to some early lo-fi mockups.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/0*a0ESxr-bcZTtApCN.png" /></figure><p>I did some preliminary validation on the Lo-Fi UI sketches and used the feedback to refine my sketches and narrow down my solutions for the Hi-Fi mock-ups.</p><h3>Building the Thing.</h3><h4>Prototyping and Validation</h4><p>When it came to building out a digital prototype, I decided to work with software that is quickly becoming common place in industry. Using Sketch I began to translate the Lo-Fi sketches into Hi-Fi mockups. I later used the Craft plugin to quickly create a clickable prototype in app, that could later be exported to InVision for on device testing. Lastly I created Hi-Fi interface animations using Principle to better demonstrate the tone and feel of certain interactions.</p><blockquote>“prototypes allow us to see things in one of two ways: Things that don’t work, and things that need work”</blockquote><p>Loosely following <a href="http://bradfrost.com/blog/post/atomic-web-design/">Atomic Design</a> Principles, I would sometimes build basic interface elements, such as a header or a new button. Other times, I would explore entirely new interactions, although often leading to time consuming conceptual systems like a new take on navigation. But that’s really the fun of it all, prototypes allow us to see things in one of two ways: Things that don’t work, and things that need work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/0*oVkn-rcjFiU-IpTY.png" /></figure><h4>Usability Testing</h4><p>I tested the Lo-Fi prototype with a 3 new individuals, later expanding to 5 as prototype fidelity improved. Insights from the initial usability tests led me to reiterate upon a traditional fixed navigation, later incorporating a news feed style hub, allowing for greater content navigation and isolation of important information as needed.</p><h4>Mental Model</h4><p>I reviewed my notes of the initial tests and created a variety of post-it-notes each containing a point of pain. I used these data points to create a Mental Model. The mental model was used better visualize and address friction across a person day and how the application may address those concerns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*plcyyey92MAyuLW_.png" /></figure><h4>Iteration</h4><p>Using the mental model i was able to identify and address the three gratest points of pain that users experienced, diagnosing its negative effects and a implementing a solution for each.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/0*g5FDTGbZ9PZ4A9XT.png" /></figure><p><strong><em>Point of Pain: Feed (Hierarchy of Information)</em></strong></p><p><strong>Challenge:</strong> In the initial iteration of the ‘feed’, information was linear, time stamped with the newest update being at the top. However the testers showed interest in being able to isolate information as arduously scrolling to find something from weeks ago, while intuitive, wasnt time efficient.</p><p><strong>Solution: </strong>At first i thought a filter menu on the upper navigation would work nicely, however while building the UI for the interaction i created a toggle style switch, it got me thinking. Why not filter important information at the tap of a switch, where anything ‘marked’ either by the user or the system would filter to the top of the feed and other content would become hidden. In addition older content could ‘fold’ into a simplified view after a certain amount of time, reducing scrolling time by half.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/0*oJjmznFrG3zVUMf5.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/257/1*1_jBxJ_ADAxIOvZW1aWxNg.gif" /></figure><h3>Retrospective</h3><p>My Greatest takeaway from this project was the importance of scope manangement. Having been a self-directed project over the course of 3 months I kept a rather flexible schedule. This resulted in a lack of time to complete UI refinements and a rather rushed documentation of the design process. While the project had received two awards, i feel its true success was in demonstrating the benefits of failure. Having failed to meet my own criteria of success.</p><blockquote>… You either win or you learn.</blockquote><p><em>Trove, in its entirety is an extension of the narrative I’ve created for the company </em><a href="https://www.behance.net/gallery/69991941/Making-Medial"><strong><em>Medial.</em></strong></a><strong><em> </em></strong><em>The project was incited through school and is a reflection of the work I produced as a student while attending the Digital Design program at Vancouver Film School.</em></p><p><strong>Thanks for reading! If you want to collaborate, talk shop, or simply share a conversation over coffee, drop me a line at hello@</strong><a href="http://www.mitchmills.com/"><strong>mitchmills.com</strong></a><strong> or connect via </strong><a href="https://www.linkedin.com/in/mitchmills/"><strong>LinkedIn</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e54b1ee6efc1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nyc-design/trove-a-ux-case-study-e54b1ee6efc1">Trove: A UX Case Study</a> was originally published in <a href="https://medium.com/nyc-design">NYC Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Language Are You Speaking?]]></title>
            <link>https://medium.com/@xihlus/what-language-are-you-speaking-fa04490bac93?source=rss-6a352745a253------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa04490bac93</guid>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[humor]]></category>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[digital]]></category>
            <dc:creator><![CDATA[Mitch Mills]]></dc:creator>
            <pubDate>Wed, 05 Sep 2018 18:03:41 GMT</pubDate>
            <atom:updated>2018-09-07T21:21:39.487Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Simple Guide To Effective Client Communication.</h4><p>That moment when …</p><blockquote>“So I’m thinking we collaboratively streamline client-centric applications using objectively viral intellectual capital.” — The Client</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*snijqZUbgyJqjWv3xtAmZA.gif" /></figure><p>Nothing quite stings an ego like being on the receiving end of an unsuspecting onslaught of unfamiliar technical terminology. As the victim, we gaze blankly through dead eyes as our comprehension of life, the universe, and everything fades from a respectable “<em>i get it”</em> to a dismal “<em>uhhhh”</em>.</p><p>Alright, perhaps a bit dramatic. It does however raise the question: <em>Why should I trust the success of my business to a person who doesn’t understand what I’m saying? </em>Below I share a simple discovery that has profoundly changed the way I interact with clients, manage stakeholders, and ultimately improved the quality of service I offer as a designer.</p><h4>The Languages of Experience</h4><p>Each skill you learn — be it Accounting, Carpentry, or in our case, Design — you’ve inherited the ability to speak a unique ‘language’. In effect, this is how we are able to interact efficiently within a particular professional landscape.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ndV0ikXCYzugPWkeHsFN-w.png" /></figure><p>The trouble being, not everyone knows the same ‘languages’, often resulting in the classic, <em>“I don’t know what you’ve just said but I’m going to nod so i don’t look like an idiot.”</em> to which we interpret that as being a sign that the other person understood exactly what we intended to communicate … Tragic!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K1TNKVmwIKw5G3_kRvLB3Q.png" /></figure><p>When you can identify and match the language of another individual, your ability to communicate effectively improves substantially. You are seen as an ally, helping your client achieve a goal together as opposed to being a barrier.</p><h4>Don’t Panic!</h4><p>Lets say our new business meeting was going swimmingly — that is, until the client begins asking questions about the design process. In a showcase of design prowess, we proceed to unleash a lexicon of specialized terminology …</p><p><em>Oh my, i think we’ve lost them!?!</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TW8rFVVRzYlQ4kV8nC-ciA.png" /></figure><p>It would appear our new client doesn’t speak the language of design. Infact, none of our clients do! Alright, what does this mean? What can we do to ensure our clients understand us?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uqhjQAsgGtC_VtfUQDP4Vw.png" /></figure><p>While there is no one clear answer to any given problem, there is a rather simple solution; Learn a new language … to be specific, the language our client knows best. In this case, <strong>business</strong>.</p><p>Our clients are more or less business minded individuals. As designers, we are hired on as professionals and yet are told how to do our jobs. <em>“No that button can’t be purple, my ex wife wore purple!”</em> … perhaps justifiably so — We say <em>“Designer”</em> they hear <em>“Adult who draws on computer for a living”</em> … We say <em>“Improve RoI by 23% this quarter”</em> they hear <em>“Valuable asset to their business.”</em></p><h4>The Point of The Thing!</h4><p>By now you may be sitting there thinking to yourself, <em>“Wait, so all i need to do is learn business terminology?”</em> To which I would say <em>“Only 20% correct as usual Morty”</em> …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*Rxq8wTXI_yc_U72wX4VTCg.png" /></figure><p>Ultimately, design is about identifying and diagnosing problems; where people complain or friction occurs, opportunity exists.</p><p>By identifying the language of our clients we are better able to communicate the results of our work, the tangible benefits, or the monetary value in a way that the stakeholder can understand. We are able to tailor our message to better create a frictionless experience that helps us move from working <em>for</em>, to working <em>with </em>our clients.</p><p>… <em>Easy Peazy!</em></p><p>Thanks for reading! I hope this article can help you better connect with your clients. If you want to talk shop, or simply share a conversation over coffee, drop me a line at <strong>hello@</strong><a href="http://www.mitchmills.com/"><strong>mitchmills.com</strong></a> or connect via <a href="https://www.linkedin.com/in/mitchmills/"><strong>LinkedIn</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa04490bac93" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>