<?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 Sebastian Nils Mitchell on Medium]]></title>
        <description><![CDATA[Stories by Sebastian Nils Mitchell on Medium]]></description>
        <link>https://medium.com/@snilsmitchell?source=rss-3b9759c2c248------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*g_EVQjNZpvamPtabJ_0hVA.jpeg</url>
            <title>Stories by Sebastian Nils Mitchell on Medium</title>
            <link>https://medium.com/@snilsmitchell?source=rss-3b9759c2c248------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 07:37:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@snilsmitchell/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[What creative hobbies have taught me about UI design]]></title>
            <link>https://uxplanet.org/what-creative-hobbies-have-taught-me-about-ui-design-12c05b3c7e66?source=rss-3b9759c2c248------2</link>
            <guid isPermaLink="false">https://medium.com/p/12c05b3c7e66</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[hobby]]></category>
            <dc:creator><![CDATA[Sebastian Nils Mitchell]]></dc:creator>
            <pubDate>Wed, 04 Apr 2018 10:47:35 GMT</pubDate>
            <atom:updated>2018-04-04T10:49:41.804Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uwKmpyy7jJwoLh2QHPEr6w.jpeg" /><figcaption>A photo I took in Laos</figcaption></figure><p>UI design is a creative job. Although it’s much more constrained than other artistic activities (e.g. painting or pottery), there’s still a lot of scope for creativity.</p><p>Recently, I began thinking about what other creative fields have in common with designing digital products -and whether or not I could apply techniques and concepts across disciplines.</p><h3>Photography</h3><p>When I started learning about photography, I read about composition, balance, and energy. These are all present in a user interface too, (although energy/direction is less important).</p><p>In the past, my mind was often concerned with questions like “should I make this margin 4 pixels or 6 pixels wide?”. Photography has helped me to always step away from the screen now and then and consider the design as almost an object of art — what would people’s impression or emotional reaction be? How symettrical is the whole?Are the colors balanced? Where is the eye drawn to?</p><p>Sometimes, to improve my photography, I’ve focused on one thing at a time (for example, using a specific lens, or only taking landscape shots). My second lens was a prime lens (I couldn’t zoom with it) — suddenly I had to “zoom with my feet” and learn to quickly size up distances and whether or not I had enough space to jump in front of something.</p><p>When visiting Hong Kong last year, I focused a lot of time on street photography, which helped me to anticipate what was going to happen and find a spot where I could capture it unfolding.</p><p>I’ve done this in the past with UI design, by focusing intently on improving my knowledge about a specific sub-discipline like typography or color theory. While I don’t always directly apply this knowledge to my subsequent work, it has often filtered back into my other designs in small ways, improving the overall quality of my output.</p><p>Photography has also helped me to think more objectively about my design process. Every amateur photographer knows you need to take a LOT of pictures to end up a good one. Typically, 1 in every 100 photos I take is good enough for me to want to print it. Even working the same scene 20–30 times, trying out different angles and compositions sometimes yields nothing good.</p><p>With UI design, instead of a perfectionistic approach, I now consider designing as more of an exploration of ideas, a reflective process. If I can’t think of a good solution immediately, I try to generate many ideas, pick one that feels like progress, and create more variations of that one.</p><p>It becomes a method of discovery — the pixels are already there, I just have to find the best way to put them together. It’s why we have exercises like 8-up sketches. It’s a much more energising and effective way of creating than sitting down and trying to force out a single high quality idea.</p><h3>Music</h3><p>I’ve been playing music for years — I produce electronic music, DJ, play guitar and ukelele, and sing.</p><p>One thing I learned early on in music was the value of repetitive practice. Consciously repeating the same motion over and over again, getting it perfect, and wringing all the musicality you can out of it all force it to stay in your muscle memory.</p><p>When I first started designing many years ago, I of course used Photoshop. I spent so many hours in that application that I started creating my own keyboard shortcuts and really mastering everything. Over time, I became a better designer simply because I was able to create ideas faster — there was less friction between the concepts in my head and how quickly I could bring them to life before I forgot them.</p><p>From producing music, I also learned the value of watching highly talented people work to my own creative abilities. Producing music is pretty hard, and for a long time I could get nowhere near the level of depth, wideness, and clarity that professional tracks have. One thing that helped me immensely was by watching videos of very talented producers working and talking about their process. I would see the little tricks they used and what they ignored, copy them, and immediately improved.</p><p>This is applicable in any field, but is especially easy with design. Want to know how to easily version control your designs? Just watch some videos on youtube of someone who’s been doing it for a while and copy them. How about choosing a great color palette for your project? Just watch some designers at work in their studios talking through their choices, and you’ll learn what considerations are important under which circumstances.</p><p>My musical interests have also taught me that my creative process differs project-to-project. For example, when I’m producing a track, I sometimes spend a very long time on one part, without much success. Other times, everything just flows. With design, sometimes it’s hard to narrow down to the best idea, and other times I put in a lot of effort and none of my concepts feel like the right ones.</p><h3>What can we learn from other creative professionals?</h3><p>I also started researching other people’s creative processes, and found some common themes.</p><p>Many highly talented creatives focus intensely on a problem or piece, then give their minds rest by doing mundane tasks like showering or driving. The insights or new ideas they couldn’t find while working come to them during these rest periods. I’m trying to adopt this practice by trusting my intuition more — and dedicating time to relax!</p><p>Many artists, photographers, musicians and writers also agree that you need to feed your brain a lot of raw input for your unconscious mind to have material to play with when generating new ideas. It doesn’t just involve consuming other people’s work. It’s an active process involving learning the patterns of structures, and ‘playing around’ — adding, extracting, and recombining elements from an existing artefact. I haven’t figured out how to apply this approach to designing user interfaces yet.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12c05b3c7e66" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/what-creative-hobbies-have-taught-me-about-ui-design-12c05b3c7e66">What creative hobbies have taught me about UI design</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Radically Simplify your Product]]></title>
            <link>https://uxplanet.org/how-to-radically-simplify-your-product-727a1321bb56?source=rss-3b9759c2c248------2</link>
            <guid isPermaLink="false">https://medium.com/p/727a1321bb56</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Sebastian Nils Mitchell]]></dc:creator>
            <pubDate>Wed, 14 Mar 2018 14:19:43 GMT</pubDate>
            <atom:updated>2018-03-14T14:21:39.313Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9rZyUYMp7r6d4AWQ9b-2gA.jpeg" /></figure><p>Which is the best tool? The complicated one with many features, or the simple one with limited features that’s essential for one specific task?</p><p>The answer, of course, depends on which persona you’re designing for. But unless you’re targeting expert users on purpose (usually professionals or users who have devoted hundreds of hours to mastering your product), it’s generally better to simplify your product. Focus on making it an excellent tool for a narrow range of goals.</p><p>This flattens users’ learning curve, makes them feel more powerful and effective, and, crucially for business, keeps them coming back.</p><p>One example I like is the humble hammer. It has a heavy, flat head and a handle — an effective tool for pounding in nails. It also has a claw at the back, useful for removing nails (an important secondary task if you’re like me).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/382/1*GXi25cUpyowg5etXedFIsQ.jpeg" /><figcaption>Simplicity itself</figcaption></figure><p>Let’s look at another nail-hammering tool…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*9Ct87iW3APn8PiWFT94HnA.jpeg" /><figcaption>Looks intimidating… where’s the ‘on’ button?</figcaption></figure><p>This is the Metabo KHE76 600341420 2-Inch SDS-MAX Rotary Hammer, a formidable $700 power tool. It has anti vibration technology and adjustable impact strength.</p><p>While ostensibly the better tool (it has more features) for hammering, it would like overwhelm the majority of new and intermediate users. They may actually be less effective at meeting their goals. The simpler tool would be more suitable for them.</p><p>This principle applies equally well to digital products.</p><h3>Simplifying Digital Products</h3><p>To interact with an interface-based product, users need to understand what’s on their screens. When you force people to decipher what they’re seeing, they spend mental energy figuring out what they can and can’t interact with. You’re preventing them from achieving their goals effectively.</p><h4>Removing visual complexity</h4><ul><li>Visual decoration (e.g. excessive colours and shapes) is waste. Often popular designs on Dribbble are guilty of this. While sometimes necessary for branding, try to reduce elements that aren’t interactive or contribute to your users’ goals. A classical example is using too many lines and boxes. Create visual structure through typography, aligning objects to a grid, and Gestalt principles like proximity and similarity.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wUSYMCVHdOYmObh5eSMxUA.jpeg" /><figcaption>The design on the left has too much visual decoration. The design on the right is a simplified version.</figcaption></figure><ul><li>Kill skeumorphic designs (digital interfaces that mimic real-life controls). Thankfully these are almost extinct these days. However, some types of software, like music production tools, imitating classical analog hardware) still use it. While comforting for some users used to a more analog age, in general skeumorphism is useless visual clutter.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/258/1*QF6wUOHoBhiIhgTTLAY0Qw.jpeg" /><figcaption>The excellent audio compressor The Glue unfortunately still has a skeumorphic interface. Bizarrely it even includes screws in the corners (like an analog rack-mounted compressor)</figcaption></figure><ul><li>Remove or cleverly hide controls that are rarely used.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PUEuO2fr8eGKsRrqrj-kmQ.jpeg" /><figcaption>Dropbox’s designers have pared down the UI to a bare minimum — and you can even hide elements further. The one obvious task is “Upload files”.</figcaption></figure><p>I want to pay special tribute to booking.com here, one of the sites I find the most frustrating to use. I went on a 4 month trip to Asia last year, and unfortunately had to use booking.com sometimes to find last minute rooms.</p><p>My heart sank whenever I started searching in their interface. When my search results came I’d be bombarded with prompts, little warning signs, and small popups, all urging me “last room available here!”, “rooms are running out!”, “book soon! hurry!”. All of this over an already maximalist interface with no graceful collapsing/hiding of data.</p><p>While no doubt good for the bottom line, probably bumping booking.com’s conversion rates up a little bit, users are more distracted and it takes more thinking for them to complete their goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vMZYTb9SR-W-V_PQg8HrXg.jpeg" /><figcaption>Aaaarrrgghh!!</figcaption></figure><p>Simplifying a digital product also means making the interface visuals and interactions consistent across views and sections of the application. With professional or enterprise-level software this can be difficult — especially when development teams have added features ad hoc over the years.</p><p>One solution to this is to simplify the development and design process itself by building a design system to work from when expanding an application.</p><p>When I worked at Ushahidi, the design team there created a pattern library to guide the product design of the new version of the company’s flagship data collection and mapping platform.</p><p>Building from this collection of repeatable, scalable elements allowed the platform designers to keep the experience consistent for users when viewing and interacting with data in different ways (for example, whether through charts or in a list).</p><p>Previously the developers had spent years deploying features on an as-needed basis in response to urgent humanitarian needs — leading to a highly consistent interface. The new pattern library was a big step towards simplicity.</p><h3>Removing cognitive complexity</h3><p>Anything your user has to think about when using your product that doesn’t contribute to their goals is cognitive waste.</p><p>In About Face, the authors divide what users do into Goal-Directed tasks and Excise tasks. Goal-directed tasks are activities which get users closer to achieving their goals. For example, if your goal is to go to London, getting on the plane directly contributes to your objective.</p><p>Excise tasks are activities which fulfil requirements of your tools or other agents. Buckling your seatbelt and keeping it on is something we’re required to do by airlines, and isn’t something that contributes to our goal.</p><p>Excise tasks only create friction — removing them creates smoother interactions, minimises cognitive load, and makes your users feel more powerful.</p><ul><li>Simplify your navigation. Don’t make your user jump around to different windows, sections, or areas of your application unnecessarily.</li><li>Removing modal error messages and obnoxious “are you sure?” dialog boxes. Making users click twice to delete something is unnecessary.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/428/1*z9uy-PO-RbD3KUFJpPajeg.jpeg" /><figcaption>pinup.com making a common interaction design mistake. Yes, I’m sure I want to delete it, that’s why I clicked on the delete button. And why is there no ability to undo this kind of action?</figcaption></figure><p>Also think about which tasks you can automate. Don’t ask if users want to do something if it happens relatively often. Just go ahead and do it, and provide an easy undo option. This requires careful judgement, but in some cases you can make your product learn what’s the best course of action.</p><p>For example, I often use Ableton Live to produce music. When I start the application again after it crashes, I am given the option, with a somewhat verbose modal dialog box, to recover my work (the softwares saves the last Undo state as a backup).</p><p>The software could easily analyse my behaviour when this happens — if I choose to go ahead 9 times out of 10, say, it’s a safe bet to just recover my work automatically when restarting after a crash.</p><p>Often focusing on helping users achieve a single goal is a great basis for simplifying your product.</p><p>For example, years ago when I was living in Brazil I started a side project to create an augmented reality app. When you go to a big event outside with lots of people, like a huge concert or festival, it’s sometimes hard to find your friends. Usually these events don’t have landmarks/meeting points, and the large amount of people make moving around difficult.</p><p>My plan was to create an app that would take someone’s location and display it on your phone using augmented reality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*YcWbO3-4P6dxNpxHpCMSeA.jpeg" /></figure><p>I could have added tons of extra features to this — alerts, a messaging system, an indicator showing how close someone was to you if they were using the app, etc. — but I deliberately kept it straightforward.</p><p>If my app didn’t fulfil its one core reason for existing, then it was worthless. In the end I discovered that GPS wasn’t quite accurate enough for the purpose I had in mind, and gave up the project, but I remember the thinking behind it.</p><p>Ultimately, simplifying a digital product often takes careful consideration and can take time, but the satisfaction boost it will give users often more than makes up for the investment.</p><p>This article originally appeared on my site, <a href="http://snmitchell.com/">snmitchell.com</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=727a1321bb56" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/how-to-radically-simplify-your-product-727a1321bb56">How to Radically Simplify your Product</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Attract Users by Targeting Their Actual Abilities]]></title>
            <link>https://uxplanet.org/how-to-attract-users-by-targeting-their-actual-abilities-3c4ae1121644?source=rss-3b9759c2c248------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c4ae1121644</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Sebastian Nils Mitchell]]></dc:creator>
            <pubDate>Fri, 07 Jul 2017 19:31:53 GMT</pubDate>
            <atom:updated>2017-07-08T09:57:44.680Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4nCfYbAl7IuIFNh8f1LmmQ.jpeg" /><figcaption>Support beginners, in every field!</figcaption></figure><p>Just as all your users may not be the same age, in the same location, or even speak the same language, each of them will have a different <strong>skill level</strong> when using your product.</p><p>Accommodating everyone from the most uncertain novice to the overconfident power user is a delicate balance. Get it right, and you’ll see a visible improvement in churn rates and user loyalty.</p><p>Designers typically divide users into three groups: <strong>Beginners, Intermediates, </strong>and<strong> Experts</strong>.</p><p>The arc of skill acquisition mimics progress in other fields, such as sports.</p><p>Let’s take surfing. Beginners practice how to paddle and pop up on the board quickly and accurately. Then, using a big longboard, they venture out to the smallest waves and practice catching them. Like novice users of software, they focus on grasping the basics.</p><p>As their skill improves, they attempt bigger and bigger waves. Often they get wiped out, but they begin to catch more and more of them.</p><p>Soon, they graduate to intermediate level. They start focusing on improving specific skills, and graduate to using a smaller board to be able to manoeuvre more. Just like intermediate software users, they know their tools’ limitations and can operate functionally.</p><p>Expert surfers, like expert software users, focus on the most challenging waves (tasks), and seek the maximum performance from their boards (or their software).</p><p>Like the tide (how far can I go with this metaphor?), <strong>users’ ability levels aren’t static </strong>— they drift constantly. Beginners move towards intermediacy as they learn how to achieve their goals, whereas expert users slowly revert back to intermediate level if they don’t practice their skills often enough.</p><p>The result is that <strong>most users aren’t beginners or experts, as you’d imagine, but intermediate-level</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*cTO9_48c_lQZ7L2CIj26lg.png" /><figcaption>Intermediates are the biggest user group</figcaption></figure><p>Let’s have a look at each user level in more detail.</p><h4><strong>Beginners</strong></h4><p><strong>It’s easy to scare beginners</strong>. They’re intimidated by complexity, and may be tempted to abandon your app if they can’t figure out how to manipulate the basic features after a bit of exploration.</p><p>Novices will put in <em>some</em> effort to learn the basics. Nobody wants to stay a beginner, and learning and achieving goals is intrinsically motivating.</p><p>Ironically, Beginners often don’t bother to read the manual (logically the shortest path to skill acquisition — see the <a href="https://www.nngroup.com/articles/paradox-of-the-active-user/">paradox of the active user</a>). <strong>Beginners dive in and try out any features that look vaguely useful. They learn by doing</strong>.</p><p>Your goal should be to reinforce this process. Well-designed software should ease Beginners into the fundamentals, flatten their learning curve, and support discovery. Crucially, it should stop them from giving up altogether.</p><p>An oft-neglected ‘extra’ user group are the Prospective Buyers. They occupy the same end of the spectrum as beginners, although before the purchase has actually been made.</p><p>Prospective Buyers share many similarities with beginners, although remember that they may not actually be the end users of your product. They chiefly evaluate software on how clean, polished, visually-appealing, user-friendly, and easy-to-grasp it seems (see: <a href="http://asktog.com/atc/the-third-user/">The Third User</a>).</p><h4><strong>Intermediates</strong></h4><p>As we saw with the bell-curve above, most users tend to fall into the intermediate group.</p><p><strong>Intermediates have a solid grasp of the basic features, and care most about accessing the tools they use most frequently</strong>. Once they’ve found a way that works, they don’t bother learning faster or more efficient methods.</p><p>After spending time away from using the software, Intermediates’ memory tends to slip. They have a general idea of how to accomplish a task, but may not remember exactly how to access the feature or which menu it was in.</p><h4><strong>Experts</strong></h4><p>Experts typically use your software professionally, and have spent many hours mastering features and perfecting their workflows.</p><p>They automatically memorise the nuances from the sheer frequency of their repetition. Maintaining this status is hard work and requires constant practice.</p><p>Experts aren’t intimated by powerful new features, and usually even appreciate them.</p><p>It’s important to remember that <strong>Experts may only have that status in some areas of the software</strong>. They may be Intermediates or even Beginners in others.</p><p>I’ve used Photoshop for over 12 years, and have honed my ability to create UI designs to a high level. But ask me to enhance a photo with Photoshop and I’ll most likely have to consult a tutorial.</p><h4><strong>Why bother accommodating everyone?</strong></h4><p>Imagine getting in a car that has every control labelled. Even the steering wheel has a post-it note attached (“Turn to steer the car left or right”). If you’ve been driving for years, you’d probably find this very irritating.</p><p>Now imagine stepping into the cockpit of a jet airliner for the first time and trying to get the plane in the air. If it were me, I’d run back down to the tarmac.</p><p>Unfortunately, one of these two scenarios is what you’re most likely subjecting your users to. Whether they’re just starting out with your product, or are already experts, you’re either annoying them with too much help, or overwhelming them with a bewildering array of controls.</p><p>You stay in business by giving your users (i.e. your customers) what they need. You want users to remain loyal by giving them a useful tool which helps them achieve their goals. You <em>need</em> to make new features easily discoverable so beginners get as much positive reinforcement as possible as they progress. And you need to support the experts who constantly demand more power, speed, and complexity.</p><p>Sacrificing one user group’s needs for the sake of another’s is generally not a sustainable business model.</p><h3><strong>Making sure everyone is accommodated</strong></h3><h4><strong>Beginners</strong></h4><p>Often, software developments teams graft on new features to existing interfaces without much consideration for how Beginners will perceive them.</p><p>Developers are expert-level users by default, and see additions from that point of view. They don’t realise that <strong>each new feature increases the likelihood of confusing and ultimately alienating new users</strong>.</p><p>The solution is to limit the number of features first-time users see. Only present what they need, and keep the expert-level functionality hidden. You may even find that by offering fewer features initially, Beginners end up using more of them!</p><p>As I mentioned earlier, your goal should be to support beginners as they explore your product. However, you shouldn’t be too intrusive — don’t make them feel stupid. Provide instructions that are fast and goal-oriented.</p><p><strong>Helping novices “just in time” can really propel their learning</strong>. If a user is creating a new document type, for example, it may be a good time to gently explain how to add a header (the first thing they may want to add to the new document).</p><p>Identifying such critical tasks with good user research will help you decide how and where to place these guides.</p><p>Here are some more guidelines for supporting Beginners:</p><ul><li>Let new users easily undo actions. This softens the learning experience by giving beginners an easy escape hatch from their inevitable mistakes.</li><li>Provide previews of features, like the previews of filters in Photoshop. This speeds up learning by showing beginners a feature’s effect without requiring them to commit to it.</li><li>Adhere to <a href="http://www.usabilitybok.org/principles-for-usable-design">basic usability principles</a>. Doing so reduces cognitive overhead and leaves users more brain-power to actually focus on your product and learn.</li><li>Make the interface beautiful. Studies show that users spend more time with and are more forgiving of an interface if it’s visually appealing (see: <a href="https://uxplanet.org/why-investing-in-ui-design-saves-costs-increases-revenue-and-retains-customers-c762b78c0526">Why Investing in UI Design Saves Costs, Increases Revenue, and Retains Customers</a>).</li></ul><h4><strong>Intermediates</strong></h4><p>Intermediates have grasped your product’s purpose and limitations, but their abilities are constantly growing or diminishing as a result of how frequently and diligently they practice.</p><p><strong>To support intermediate users, give them easy access to the tools they use most frequently</strong>, and reveal more features to them as their abilities evolve. Use progressive disclosure to visibly let these users explore more and more of your software’s functionality as their confidence increases.</p><p>Don’t push Intermediates towards using advanced features. These users mostly don’t have time to invest in learning advanced functionality anyway.</p><p>Intermediates don’t want to see the guides provided to beginners, so hide these instructions. You should provide small tooltips to jog Intermediates’ memories though, as they’re prone to forgetting exactly where a feature is located.</p><p>You should also provide support documentation that’s easy to use. so intermediate users can look up features they’ve forgotten about, or easily learn new features.</p><h4><strong>Experts</strong></h4><p><strong>Advanced users care most about speed, automation, and customisability.</strong></p><p>If your product is mission-critical for experts, make sure the interactions feels snappy and everything loads fast. It may even be worth creating a native version for expert users which exploit all the power of the device it’s being used on.</p><p>Experts seek efficiency. Shorten the navigation paths to features, and create shortcuts for everything.</p><p>Allow experts to customise their own shortcuts and interface as much as possible. Customisability pushes an expert users’ efficiency beyond what you can provide out of the box, and hooks them into your product. After years of using Photoshop and creating dozens of shortcuts for frequent actions, I’m very wary of changing to another image manipulation application.</p><p><strong>Let experts remove help features and wizards designed for beginners.</strong></p><p>Remember that experts may still need help — be sure to provide in-depth support documentation that they can consult when handling the most advanced features. Try to conduct regular usability studies to ensure your product is meeting their evolving needs, too.</p><h4><strong>Should you be targeting anyone in particular?</strong></h4><p>In general, you should aim to support everyone and help them progress to the next level. There’s a tradeoff between simplicity (useful for beginners) and number of features (useful for experts) involved here.</p><p>As we saw earlier, the most common user type is intermediate, since beginners always improve and experts’ abilities tend to wane.</p><p>However, depending on your product and your business goal, you may want to prioritise one section of the user spectrum over the others. You should aim to properly understand how skills are distributed among your users before doing this.</p><p>For example, your company’s goal may be to scale up to having as many users as possible. In this case, prioritise the beginner experience, and focus on guiding new users to intermediacy quickly and smoothly.</p><p>If, on the other hand, you want to target technical experts who use your software professionally (e.g. engineers or accountants), design mainly with the advanced user in mind.</p><p><strong>If you’re unsure, focus on supporting intermediate users the most</strong>, with minor accommodations for beginners and experts. Many software development teams inverts this by focusing most heavily on beginners and experts, which are statistically the smallest groups.</p><p>Importantly, you should make your product adapt to users’ changing skill levels and interest. That’s the best kind of user experience, albeit the hardest to design.</p><p>****</p><p><em>Supporting your users’ actual skill levels improves loyalty, increases referrals, and reduces churn. If these sound like outcomes you’re interested in, </em><a href="http://snmitchell.com/"><strong><em>get in touch with me</em></strong></a><em> and I’ll help you redesign your product with your real users in mind.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c4ae1121644" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/how-to-attract-users-by-targeting-their-actual-abilities-3c4ae1121644">How To Attract Users by Targeting Their Actual Abilities</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Investing in UI Design Saves Costs, Increases Revenue and Retains Customers]]></title>
            <link>https://uxplanet.org/why-investing-in-ui-design-saves-costs-increases-revenue-and-retains-customers-c762b78c0526?source=rss-3b9759c2c248------2</link>
            <guid isPermaLink="false">https://medium.com/p/c762b78c0526</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[roi]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Sebastian Nils Mitchell]]></dc:creator>
            <pubDate>Mon, 29 May 2017 16:24:51 GMT</pubDate>
            <atom:updated>2017-05-30T13:11:06.063Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QuJJGCHdjukSVQ7p_R_Xgw.jpeg" /></figure><p>I hang around in a number of groups and forums for SaaS founders. Amongst all the discussions, I see very little mention of how to invest in UI/UX or even the benefits of doing so. Functionality, performance, and stability are typically higher on the priority list.</p><p>I find this baffling (and not just because I’m a UI designer!). <strong>Investing in your product’s UI/UX has a potentially very large ROI</strong>, which many SaaS companies are missing out on. And it’s not as complicated as it may seem.</p><p>This is especially true for products which have a higher-than-desirable churn rate (usually<strong> </strong>an indication that the software isn’t easy enough to use or doesn’t fit in well enough with users’ lives).</p><h3><strong>So why is the ROI of UI/UX improvements so high?</strong></h3><p>The exact ROI is hard to quantify since each product has different metrics.</p><p>The general rule of thumb in organisations that routinely focus on improving UI/UX is that every dollar returns $10-$100.</p><p>This is because the cost of changing part of your SaaS product increases nonlinearly as development goes on. Focusing on design saves costs down the line, especially early on in the product development cycle.</p><p>An oft-quoted statistic from <em>Software Engineering: A Practitioner’s Approach</em> by Roger Pressman is that fixing a problem in development costs 10 times as much as fixing it in design, and 100 times as much if you’re trying to fix the problem in a product that’s already been released.</p><p>Want to add offline syncing and version history to your data collection app?</p><p>It’s easy in the requirements gathering or wireframing phases — just spend an extra week scoping the functionality and designing user flows.</p><p>Want to add those same features when your product is live and being used by thousands of people?</p><p>You’re looking at months of development time, potentially disrupting the service of your existing users, and dozens of unforeseeable bugs and issues.</p><p>Which would you rather deal with?</p><h3><strong>The business benefits of improving visual design and usability</strong></h3><p>Improving the cost effectiveness of your development process isn’t the only benefit of investing in UI/UX.</p><p>Focusing on design also helps your bottom line by improving a wide range of business metrics such as user retention, customer loyalty, and user productivity.</p><p>Usability guru Don Norman is fond of saying that emotions change the way humans solve problems. If you’re in a positive mood, you’re more open, creative, flexible, and patient.</p><p>Contrast that with how you act when frustrated or tense — your focus narrows and your lateral thinking abilities shut down.</p><p>Let’s apply that concept to software interfaces. If a UI is well-designed (i.e. it’s aesthetically pleasing and follows universal design principles), users feel good when they interact with it, boosting their problem solving abilities. The more effectively they can solve problems, the more they’re going to be able to accomplish with your product.</p><h3><strong>Are well-designed interfaces actually easier to use?</strong></h3><p>The “Aesthetic Usability Effect” — the phenomenon that aesthetic interfaces seem easier to use — certainly exists. Most studies find that users perceive the usability of a system to be better when the design is aesthetically pleasing. There are many nuances though, which we can explore through some very interesting studies.</p><p>In a <a href="http://www.sciencedirect.com/science/article/pii/S0003687009001148">2010 study in Switzerland</a>, researchers gave 60 teenagers two simulations of mobile phones and asked them to perform a number of typical tasks on them. Although both simulations had exactly the same features, one was designed to be visually appealing, and the other was designed to be garish.</p><p>Predictably, the participants rated the nice-looking phone to be more usable than the other one. However, the visually appealing phone also had an impact on task performance — on average, the participants took less time to complete their tasks. This indicates that a visually appealing interface helps users to work more quickly.</p><p>It’s important to note here that the participants <em>perceived</em> the more appealing option as easier to use — beyond reduced task completion time, the appealing design wasn’t measurably easier to use.</p><p><a href="http://dl.acm.org/citation.cfm?id=871496">A study in the Netherlands</a> asked 828 participants about a generic website. The researchers found that how easy the site was perceived to be and how enjoyable the participants found it were strongly influenced by how visually pleasing it was.</p><p><a href="http://www.medvet.umontreal.ca/techno/eta6785/articles/Screen_desing_violation.PDF">Another study in Canada</a> showed that people process information more efficiently and are more patient when completing tasks when using an interface that follows the principles of good design.</p><p>The theory is that an ordered, clean design minimises the need to manually process data — it happens more automatically. It’s also thought that visually appealing interfaces create an atmosphere that is pleasant and engaging, which is why they hold users’ attention for longer.</p><p><em>“Performance (as represented by response time) increases with increasing aesthetics level. This evidence provides strong support for the implementation of aesthetic layout principles in interface design”</em>. (<a href="http://theses.gla.ac.uk/4256/1/2013salimunphd.pdf">The relationship between visual interface aesthetics, task performance, and preference</a> by Carolyn Salimun)</p><p>You should take into account cultural differences when designing interfaces. Users might not perceive an interface as beautiful depending on their culture and background. If your users come from many countries, it may be worth investing in designing variations for each culture. <a href="http://dl.acm.org/author_page.cfm?id=81350583575&amp;coll=DL&amp;dl=ACM&amp;trk=0&amp;cfid=761144549&amp;cftoken=80248988">This study by Katharina Reinecke explains more</a>.</p><h3><strong>So why do increased perceived usability, more efficient information processing, and greater willingness to stick with an interface help your bottom line?</strong></h3><p>The easier an interface is (or is perceived to be), the more users will be willing to learn it and keep using it.</p><p>When users stay longer with your app, the likelihood that they’ll learn how the app works properly and/or complete a task (or their goals) goes up — there’s a better chance that they’ll see the value in your product for them and become (or stay) a paying customer.</p><h3><strong>Improved Trust</strong></h3><p>A polished visual design also increase users’ trust in your product and company. The most important factor for evaluating how credible a web product is is how professional its website looks (even more so for B2B!).</p><p>This makes sense — people subconsciously think that because a company’s web presence looks attractive and shows attention to detail, so must their products.</p><h3><strong>What is involved with investing in UI?</strong></h3><p>When I talk about investing in the UI/UX of your app, I mean anything from trying a different button colour to a full-blown overhaul with user interviews, user testing, complete look and feel redesign etc.</p><p>Here are the basic investments you can make:</p><h4><strong>1. Research</strong></h4><p>Attitudinal studies indicate how users think or perceive a product. They tend to be less useful, because while users say one thing, frequently their behaviour is different.</p><ul><li>Focus groups and Surveys- good for getting a general opinion, but not very helpful otherwise</li><li>Card Sorting: getting user input into the structure and information architecture of your site by getting them to order cards into topics that they find makes sense.</li></ul><p>Behavioural studies capture actual user behaviour. They are useful for getting an objective view of people’s reactions to your product.</p><ul><li>A/B testing: Creating two (or more) variations of a page and sending traffic to both, and keeping the variation that converts best. Requires a reasonable volume of users but can be extremely effective, especially when used continuously.</li><li>Eye tracking studies: using sensors to capture and record users’ eye movements as they interact with a product.</li></ul><p>A mix of behavioural and attitudinal studies is also popular. One example is unmoderated remote panel studies (e.g. usertesting.com), in which users record themselves interacting with your product and thinking out loud.</p><h4><strong>2. Design</strong></h4><p>Analysing and interpreting research results: Looking for patterns in UX research and suggesting improvements.</p><p>Creating customer personas: Summarising the characteristics of your target audience to guide product design choices.</p><p>Designing improvements: creating wireframes, prototypes, high-resolution mockups, and communicating design specifications with developers.</p><h4><strong>3. Development</strong></h4><p>Actually building and implementing changes can be the most expensive part (but not if you do it early on).</p><p>You should also consider the time and overhead it requires to plan, manage, and execute all of the above.</p><h3><strong>How to invest</strong></h3><p>Critics claim that it’s very difficult to know whether or not UI/UX improvements actually lead to things like increased revenue.</p><p>The argument is that because these kinds of changes take place in non-controlled experiments (i.e. there aren’t 2 versions of the product being tested at the same time), it’s difficult to tell whether UI/UX changes actually make a difference to conversions.</p><p>This is true on some level. However, it IS possible to choose good baseline metrics which are closely connected to revenue, retention etc. before you make any design changes, and test those.</p><p>Before you invest in UI/UX improvements, <strong>pick the right metrics to track</strong>. The narrower your metrics, the easier it will be to judge the ROI of your usability investment.</p><p>For example, if you choose to track the entire number of sales across the site, that metric could be influenced by many other external factors beyond your control.</p><p>But if you choose to only measure drop-off rates at a critical part of your product’s sign-up process or sales per page view, it will be much more clear whether your usability improvements contributed to the result.</p><p>For SaaS products, we can break metrics down into 3 groups:</p><p><strong>1. Development metrics</strong> (Goal: reduce costs). Your development team needs to be organised to keep track of these metrics.</p><ul><li>Current development costs per month, quarter etc.</li><li>Development time or effort per feature or bug fix</li><li>Current maintenance costs</li><li>Current redesign costs</li></ul><p><strong>2. Sales</strong> (Goal: increase revenue). The narrower the better here.</p><ul><li>Current sales volume</li><li>Current traffic volume (to a product page, site section, or entire site)</li><li>Current customer churn</li><li>Current amount of new customers per month or quarter</li></ul><p><strong>3. Product Use</strong> (Goal: improve product effectiveness)</p><ul><li>Number of user errors</li><li>User satisfaction (you can gauge this with surveys)</li><li>Ease of learning (measured with user testing and indirectly through usage, e.g. number of page views or actions completed on first sign-in)</li><li>Current support costs (measured by the amount of queries your customer support team handles in a specific timeframe)</li></ul><p>Once you’ve chosen your metrics, you need to spend time capturing good baseline data so you can see ‘before and after’.</p><p>You’ll need decent traffic here — as with measuring conversion rates, any data that involves fewer than 1000 unique visitors isn’t going to be that reliable.</p><p>You should also be thinking of improvements in UI/UX as continuous optimisation instead of a one-off investment. Compounding your efforts like this is what can lead to massive increases in conversion rates and sales.</p><p>Another thing to consider creating as early as possible is a style guide — redesign and create a style guide (flexible, scalable and cost-efficient, but also customizable, reusable and consistent. saves development time and cost down the line — do it as early as possible).</p><p><a href="http://bamanda.com/joomla_uploads/whitepapers/AM+A_ROIWhitePaper_20Apr0%201.pdf">You can see many case studies here</a><strong>.</strong></p><p>Human Factors International have a very popular <a href="http://humanfactors.com/coolstuff/roi.asp">UX ROI calculator</a>.</p><p>CareerFoundry has an excellent <a href="https://careerfoundry.com/en/blog/ux-design/how-to-conduct-user-experience-research-like-a-professional/">guide to conducting UX research</a> which I recommend.</p><p>Want my help improving your product’s UI and usability? <a href="http://snmitchell.com/contact/">Contact me</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c762b78c0526" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/why-investing-in-ui-design-saves-costs-increases-revenue-and-retains-customers-c762b78c0526">Why Investing in UI Design Saves Costs, Increases Revenue and Retains Customers</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Stop Enraging Your Users & Start Getting More SaaS Customers]]></title>
            <link>https://uxplanet.org/how-to-stop-enraging-your-users-start-getting-more-saas-customers-47ed1d91d85a?source=rss-3b9759c2c248------2</link>
            <guid isPermaLink="false">https://medium.com/p/47ed1d91d85a</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Sebastian Nils Mitchell]]></dc:creator>
            <pubDate>Wed, 03 May 2017 17:40:08 GMT</pubDate>
            <atom:updated>2017-05-04T16:55:35.380Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wM5amjha5Y20mmv-ho7NXQ.png" /></figure><p>To your users, small annoyances in your app are like flaws in a romantic partner. They can handle one or two, but if more and more pile up they just end up miserable. If you frustrate your users with small inconveniences too often, they’ll react the same way they would to a bad spouse — they’ll move on to something better (see: <a href="https://www.nngroup.com/articles/does-user-annoyance-matter/">Does User Annoyance Matter?</a>).</p><p>Good UI design minimizes the number of annoyances in your application and boosts your product’s business value, and is worth investing in. You’ll get more users from word-of-mouth, your sales efforts will be smoother (because your sales team will believe in your product more), and keeping paying customers will be easier.</p><p>It’s not possible to generalise and cover every potential annoyance — each application has its own particular subtleties and sticking points. However, I’ve compiled a short list of the most common annoyances which I’ve seen over the years I’ve been designing user interfaces, and the appropriate UI design pattern to combat them.</p><h4>Don’t assume your users know what your app’s terminology means</h4><p>If you come up with new terminology (think labels, features, or button text) that isn’t self-explanatory, or contradicts what your users have probably experienced on other products, you’re going to force people to make small mistakes. This will likely block them from completing their goals successfully, and a user who can’t do what she wants is only going to get frustrated.</p><p>Additionally, if your users don’t understand your app’s language, they’re effectively unable to use that entire feature as you want them to, denting the value of your product. Imagine a fridge which has a brand-new door design that actually doesn’t make sense to fridge-users. Nobody can open the door, so they end up flipping the fridge on its side and use it as a desk instead. Nobody wins.</p><p>For example, back when I worked at Ushahidi, the product team was redesigning the company’s flagship crowdsourcing software. They created a feature which allowed users to create and save a curated group of posts, and called this group of posts a “Set”. But it wasn’t until going through testing and talking with users that they realised nobody understood what a “Set” was (because nobody had encountered a “Set” in software before, and the phrase wasn’t self-explanatory). They quickly changed it to “Collection” which people grasped immediately.</p><p>Even though it can sometimes be difficult to come up with the right term to describe a new element or feature, try to use terminology people are already familiar with, or that are very obvious (but test your assumptions too!). Think about it; which is better — calling a user-generated collection of songs a ‘Mixtape’, or a ‘Playlist’? I’d definitely go for ‘Playlist’.</p><p>Make sure that your app’s terminology is consistent with what users are familiar with. If you need to call a feature of your product a ‘cart’, it should behave like the other carts users are likely to have encountered (e.g. Amazon’s). Also, never call the same element in your UI by two different names — keep it consistent in all your touchpoints with the user.</p><p><a href="https://www.interaction-design.org/literature/article/principle-of-consistency-and-standards-in-user-interface-design">Principle of Consistency and Standards in User Interface Design</a> goes into more detail on this topic.</p><h4>Don’t make your application speak like a computer</h4><p>This is a common problem (especially for older software), and most frequently seen in error messages. Your user makes a mistake, or something unexpected happens, and an application proudly presents something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/0*QpMM0pzHrb68NU2S.png" /></figure><p>Why is this frustrating? Because it interrupts and confuses users. Which error occurred? What should I do? Will it happen again? Was it my fault? Can I do what I want? Is this the right application for me?</p><p>One of the main causes of this issue is letting developers write error messages. Developers (more often than not) see things from a programming perspective, and aren’t used to putting themselves in the user’s shoes.</p><p>How can you make error messages less infuriating? Use these guidelines from the usability canon:</p><ul><li>At the very least, <strong>include some kind of error message</strong>. The most enraging error is one that the system doesn’t even acknowledge.</li><li><strong>Explain the problem accurately</strong>. What caused the error? Was it the user or the software?</li><li><strong>Be constructive</strong>. Tell the user what to do next — give them a path out which makes them feel confident.</li><li><strong>Make error messages sound like a friendly, polite human</strong>. The most common web error (404 Page Not Found) doesn’t sound like this — it sounds like a boring server.</li><li><strong>Use plain language</strong>.</li><li><strong>Don’t blame the user!</strong> Their workflow has already been interrupted — don’t throw salt on their wound by making them feel incompetent.</li><li><strong>Test your application with real users</strong>. This will help you anticipate common errors and plan helpful messages.</li></ul><p>This error message in Mailchimp observes these guidelines:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/259/0*C2KWFcUjgwnWSleB.png" /></figure><p>Many well-known platforms get some of these points right but mess up on others. For example, here’s an error message I see frequently on SoundCloud (and which makes me want to punch the screen sometimes):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*it_3SlNio6zeZeJd.png" /></figure><p>While it doesn’t sound like a computer, it tells me nothing about what went wrong (SoundCloud acts like it doesn’t even know) and offers me no alternative but to “retry” (how do I know the same thing won’t happen again?).</p><h4>Don’t validate forms badly</h4><p>Forms are normally a critical part of your app. Usually you’re getting visitors to sign up to become users, or input their payment details to becoming paying customers. When you confuse and waste user’s time when they’re filling in forms, you’re not just annoying them — you’re potentially draining the lifeblood of your business.</p><p>The #1 rule is to avoid allowing your users submit a form with errors, only to be taken back to the same form with an error message.<strong> Validate forms inline and save their time</strong>. Here are some more form usability guidelines:</p><ul><li>Put your validation messages in the right place. This is usually as close to the source of the error as possible — for example, right next to or above an input field.</li><li>Make your messages the right colour. Red is universally “error” or “warning”, and green is almost always “correct”. Make your app accessible to users with disabilities by not only relying on colour to provide feedback — include a symbol or icon as well.</li><li>Make your messages appear at the right time — as soon as the user makes an error or tries to progress.</li></ul><p>Here’s an example from the signup process in Square. The message appears as soon as I move to the next field, turns the whole field and label red, and even adds a little warning sign. It’s hard to miss.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_6fMWiylsNfkWBFT.png" /></figure><p>For a more detailed look at handling errors and exceptions well, have a look at <a href="http://www.uxmatters.com/mt/archives/2015/11/error-messages-are-an-anti-pattern.php">Error Messages Are an Anti-Pattern</a>.</p><h4>Avoid bad or unconventional interactions or layouts</h4><p>Unusual terminology isn’t the only thing you should avoid. Whenever you stray from established UI design patterns and layouts, or choose bad ones, you slow your users down and confuse them. The more you force users to figure out how to use your product, the more frustrated they’re likely to feel.</p><p>Why make users work harder? They’re paying you to make their problems smaller or disappear, not to make them think about what to do.</p><p>A great example are drag and drop interactions. I used to add these to interfaces I designed before realising how bad they are. Drag and drop needlessly complicates actions that could take one step (a click) by turning them into many (click, decide where to drag, drag, release).</p><p>Users often find it difficult to figure out the correct place to drag something to. Moving your mouse while holding down the left-click button or moving your hand around the trackpad are both awkward. There’s no point in making your users go through the extra hassle — pick a simpler UI design pattern.</p><p>Also see: <a href="https://medium.com/@dfeldman/drag-drop-think-twice-49e7bf3e6b31">Drag &amp; Drop: Think Twice</a>.</p><p>Similarly, <strong>don’t try to innovate with your layout</strong> (let your features and UX do that). You should keep layouts consistent with what users are familiar with. For example, keep your navigation menu in the top or left part of the screen, and your logo in the top-left corner or the top-center. Forcing your users to figure out how to navigate your app is only going to annoy them, just like making them drag and drop.</p><p>What’s the solution? Use straightforward design patterns that users are already familiar with. A great resource is <a href="http://ui-patterns.com/">UI-patterns.com</a> (which also has a guide to some <a href="http://ui-patterns.com/blog/User-Interface-AntiPatterns">common UI design anti-patterns</a> — bad patterns that get often and inexplicably reused).</p><h4>Don’t assume new users know what they should do when they get to your app</h4><p>Enterprise-level SaaS apps can be bewildering for first-timers. Your users want to learn to use your product as quickly as possible (after all, they’re paying for it), and it’s vital that you support them during this phase. Abandoning your first-time users in the middle of your application with no guidance will only aggravate them and make them more likely to leave.</p><p>How can you support new users? Don’t give them too many details/options at once. Either cut down the number of features and elements in your interface, or use progressive disclosure to gently lead users to the actions they want to complete.</p><p><strong><em>“</em></strong><em>It takes at least one second and often two seconds to decide between two possible interaction techniques which is why it is usually better not to offer users a choice. (A second may not seem like much, but it translates into about $100 million in lost productivity per year world-wide.)</em><strong><em>” — Jakob Nielsen</em></strong></p><p>It helps to try boiling down your app to its essence. Think of the #1 function or milestone you want users to succeed at, and help the user get there.</p><p>For example, Twitter’s team attributes their massive growth and user retention to focusing on helping new users manually follow 5–10 accounts in their first day, and helping people follow back people they knew.</p><p>Better yet, walk them through how to use your application by <strong>designing for the ‘empty state’</strong>. When a user first signs up to your app, they’re likely to see empty screens (since they haven’t populated them with data yet). Think about how to guide and direct the user here.</p><p>Provide helpful messages telling them explicitly what to do and how. This doesn’t have to be complicated — here’s an example from Amazon Photos for Android:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*SMX6eIqBok29grLK.png" /></figure><p>Sometimes words aren’t even necessary. In the 80s, when Apple changed the default empty state in MacWrite from a blank screen to an empty document with a blinking cursor (indicating that you could write), users got to grips with the product much faster.</p><p>Here’s a <a href="https://medium.com/rareview/ui-design-for-empty-states-zero-data-and-on-boarding-264cdb92826e">great case study of how effectively planning for the empty state increased conversion rates 30–40%</a>.</p><p>It also helps to get users invested in your app as fast as possible. For example, when I sign up to Trello, the first thing I’m asked to do is to name my team and choose people to invite to it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*h3udSM3HeXmaRrUX.png" /></figure><p>After coming up with a (frankly, really good) team name and sending out invitations to my team members, first-time users like me are much less likely to abandon Trello in frustration.</p><p>You may have already tried to deal with this problem with a long tutorial — don’t do this! In-depth tutorials can kill a users’ momentum and enthusiasm. Instead, focus on supporting <strong>discoverability</strong> by letting the user explore your application on their own (with your helpful hints), rather than shoving a manual in their face.</p><p>Listening to users as they navigate your app is the best way to learn whether or not it’s too difficult or confusing. I recommend <a href="http://usertesting.com/">usertesting.com</a> if you’re starting out.</p><h4>Don’t make the interface slow or unresponsive</h4><p>Users find it very unpleasant when they have no idea what’s going on. You need to tell them where they are, what’s happening, what’s going to happen, and what just happened — as much as possible. This information needs to be clear and highly visible.</p><p>Apart from <strong>progress feedback</strong> (what is the app doing? How long until it’s finished?), the interface elements in your app need to clearly indicate how to interact with them. For example, when you hover your mouse over a button, on most interfaces it changes in some way to let you know that it can be clicked (changes colour, state, etc.). These are called affordances (definition: a characteristic of an element that implies how it is used, e.g. a door handle).</p><p>If you fail to provide feedback on affordances, you slow down how quickly users can discover how to use your application. If you fail to provide proper feedback on processes, users will feel like you’re stopping them from completing their goals.</p><p>Consider the timing and delivery of your feedback too. Don’t interrupt a users’ experience to tell them what the backend is doing — do it asynchronously, in a different part of the interface to the one in which your user is working.</p><p>Your product’s <strong>response time</strong> should be as fast as possible. Some guidelines:</p><ul><li>To users, if anything in the app takes <strong>longer than 100 milliseconds</strong> to react, they will lose the feeling that they are manipulating the software in real-time.</li><li>For delays <strong>between 100 milliseconds and 1 second</strong>, users don’t need to be alerted about the app’s progress, but they’ll feel like the app isn’t responding quickly.</li><li>For delays <strong>over 1 second</strong>, it’s best practice to provide feedback. Aim to provide progress (e.g. a percentage done) than simply an activity indicator (e.g. spinning ball).</li></ul><p>Also, I’d recommend <strong>avoiding gratuitous animations</strong> (like the ones that are popular on Dribbble) — they needlessly slow down your users and offer nothing in return. If you must use them to indicate progress, follow these <a href="https://www.smashingmagazine.com/2016/12/best-practices-for-animated-progress-indicators/">Best Practices For Animated Progress Indicators</a>.</p><h4>Don’t Avoid Designing for Edge Cases</h4><p>An edge case is a bug or problem that occurs very infrequently and only at the extreme ‘edge’ of an interface’s parameters. For example, what if a 101-year-old wants to use your app but the input field for age only supports two digits?</p><p>It’s very <strong>difficult to plan for edge cases</strong> because they happen so rarely, but when they do occur they inevitably annoy the user. If you want to create a well-rounded product, it pays to anticipate as many of these potential snags as you can.</p><p>User testing often doesn’t help you to identify edge cases, since testers are given general instructions and their interaction is time-limited. It helps to have more developer input here, as designers are usually more concerned with core functionality.</p><p>My advice is to <strong>have your designers working especially closely with QA engineers and developers</strong>, and ask your devs to be especially analytical when brainstorming potential edge cases.</p><p><a href="https://medium.com/@nelsonjoyce/dealing-with-edge-cases-in-product-design-f90ecbf0dffd">Dealing with Edge Cases in Product Design</a> has a good example of the tradeoffs designers of large products face (HubSpot in this case).</p><p>In summary:</p><ul><li>Use terminology that users will likely be familiar with.</li><li>Make your application sound like a friendly, polite human when talking directly to the user.</li><li>Stick with established interface patterns and layouts.</li><li>Guide first-time users through your application with friendly prompts.</li><li>Make your product as snappy as possible, and let users know what’s going on if interactions are likely to be slower than 1 second.</li><li>Validate forms inline, using the right colors and message placement.</li><li>Plan for as many edge cases as you can.</li></ul><p>These guidelines should help you to smooth out your app, improving user satisfaction and the business value of your product. My final piece of advice is not to skip talking with your users — every product will have frustrating details that you can only identify and fix by getting direct feedback.</p><p><em>Thanks for reading! If you’d like to collaborate on a design project, reach out to me at </em><a href="http://www.snmitchell.com/"><strong><em>snmitchell.com</em></strong></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47ed1d91d85a" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/how-to-stop-enraging-your-users-start-getting-more-saas-customers-47ed1d91d85a">How to Stop Enraging Your Users &amp; Start Getting More SaaS Customers</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>