<?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 Ceara C on Medium]]></title>
        <description><![CDATA[Stories by Ceara C on Medium]]></description>
        <link>https://medium.com/@CearaCrawshaw?source=rss-8fa4899f7d71------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jo1Ty75H_ivFpyelDocC1A.png</url>
            <title>Stories by Ceara C on Medium</title>
            <link>https://medium.com/@CearaCrawshaw?source=rss-8fa4899f7d71------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 06:21:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@CearaCrawshaw/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[The UX pattern that reflects really well on designers AND developers]]></title>
            <link>https://medium.com/design-bootcamp/the-ux-pattern-that-reflects-really-well-on-designers-and-developers-f67d0c9f170d?source=rss-8fa4899f7d71------2</link>
            <guid isPermaLink="false">https://medium.com/p/f67d0c9f170d</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[patterns]]></category>
            <category><![CDATA[loading]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Ceara C]]></dc:creator>
            <pubDate>Tue, 06 Apr 2021 05:58:03 GMT</pubDate>
            <atom:updated>2021-09-14T20:37:20.395Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*GszrpTdxd43bsGlrc4q_sw.gif" /></figure><h3>Getting your loading UX pattern right</h3><h4>Sussing out the right UX patterns when people are waiting takes consideration, and technical collaboration to get right.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*2iNK7e-6fd8N-JT9TFRt2w.gif" /><figcaption>Waiting is not fun</figcaption></figure><p>When we’re in line at the checkout in a grocery store, there are certain signals that tell us the line is moving. The sound of the till, the person in front of you putting their basket away, them tapping their card on the payment machine.</p><p>On the flip side, hearing the shuffle of the person behind you, the feeling of hunger, the movement of the other lines around you can make you feel like you made a catastrophic decision of picking <em>this </em>checkout line.</p><p>This is loading feedback in the real world.</p><p>In the digital world, loading feedback is what <em>buys</em> user trust in the promise that the platform is working as quickly and diligently as possible to get them from point A to point B. You can think of it like a type of UX currency. Loading states not only sets expectations about what the system is doing, it can also buy user anticipation in seeing new updates or results.</p><p>Loading feedback is one of those UX patterns which a designer cannot design in a bubble and then hand off to a developer. It has to be in sync with the back-end and front-end team because, when a user is trying to load a data-heavy table or start an important upload, they need to know what to expect from ‘the machine’ in a user friendly way. Applying the incorrect loading feedback can have a reverse effect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*2EHnYCRyU8OVGOL9" /><figcaption>Spinning forever makes people rage out</figcaption></figure><p>Too quick and you can’t be sure it was done properly.</p><p>Too long and you wonder if it was done at all.</p><p>And god-forbid they find the ubiquitous ‘spinning wheel of death’ that is universal for something has been <a href="https://en.wikipedia.org/wiki/FUBAR_(disambiguation)">FUBAR’d</a> 😱 (Now, spinners aren’t <em>always</em> bad. You just need to know the right use cases to implement them in.)</p><h3>Know how the machine works 👾</h3><p>Good UX designers and design-minded developers know that we aren’t just talking about how to make spinning wheels more cute. We’re talking about loading the interface and content in smarter, user-friendly ways and letting the protagonist know when the task is finally over the hill.</p><p>Small moments (below 0.1s) and big moments (10s and over) are approached differently because each pattern communicates different things to the user (not to mention the personality of the product itself). Here are important factors that will inform the choice of loading interactions you can use:</p><p><strong>Can we predict the timing of the content to load?</strong></p><p>Knowing if it’s going to be a long or short wait up front is something we can design for.</p><p><strong>What is the range and </strong><a href="https://pencilandpaper.io/articles/user-experience/ux-pattern-analysis-loading-feedback/#scope"><strong>scope</strong></a><strong> of what needs to be loaded?</strong></p><p>The larger the scope of what’s being loaded, the more creative and dynamic your loading feedback will need to be. You might be able to trigger different messaging based on timing thresholds.</p><p><strong>How frequently is the back-end returning information to the page?</strong></p><p>For example, it’s better to let the user wait a little longer so that more items in the page are loaded before you let them see it.</p><p><strong>Is data synchronized in real-time or does it need to be triggered?</strong></p><p>User triggered actions mean you need to show <a href="https://pencilandpaper.io/articles/user-experience/ux-pattern-analysis-loading-feedback/#deciding-on-your-logic">active loading states</a>.</p><h3>Make the user feel like they picked the right checkout line</h3><p>Once you’ve clarified the logic behind how the page loads you can start to have fun with it.</p><p><strong>If they need to wait a while, let them know when it’s their turn.</strong></p><p>For <a href="https://pencilandpaper.io/articles/user-experience/ux-pattern-analysis-loading-feedback/#between-2-and-10-seconds">loading scenarios</a> that are longer (between 2 and 10 seconds i.e. it’s a big task to complete), let the user know, right away, that you received the request and indicate how long they should expect to wait.</p><p>The goal is to balance the perceived wait time with the perceived value of the task at hand. Whether it’s navigating to another page or breaking up the loading time into smaller moments to show dynamic messaging, the user will be willing to wait for an important task to be done properly as long as there isn’t an excessive lull in loading progress.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*aAj4vE7sfq4TG1-s" /><figcaption>Loading feedback on a list item</figcaption></figure><p><strong>There’s a way to let people know that you’re not sure about the waiting time and not lose face.</strong></p><p>Sometimes, you just can’t predict how long something will take to load — you can show a progress indicator on a loop or give them an option to be notified when it’s done. Just <em>don’t </em>show a static message. Think about how annoying it is when you’ve been waiting a long time and the person at the counter keeps repeating the same message like a broken record. By showing dynamic messaging to the protagonist, you’re reacting to the fact they’ve been waiting for a long time. This is the blurry space between machine and customer experience in which loading feedback lives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YKBs9h84AtmPoQL0" /><figcaption>A modal showing estimated time remaining with an email notification message</figcaption></figure><p><strong>Has a new checkout line become available since Tracy came back from her lunch break?</strong></p><p>For loading data that is not being continuously synced to the app but would be valuable for the user, you need to inform them that there is an action to be taken. Especially in dashboards or project management tools that might have several people making updates to the data asynchronously, the user will want to be informed of the freshest possible data set. Needing to remember to refresh or even worse, learning that you need to vigilantly sit and refresh a tool multiple times a day is a big UX fail.😿🛑</p><p>Think about how Jira and Twitter does it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dLvDt5lRS6oxcelu" /><figcaption>This Jira example shows the user that data has been updated and gives them a trigger to reload the page</figcaption></figure><p><strong>Give them something to appreciate — the lil’ machine earned it.</strong></p><p>The illusion of breathing room is something that’s <a href="https://uxmag.com/articles/let-your-users-wait">hotly debated</a> but I side with showing a delay commiserate with the scale of the task. Not to mention, if it’s an action that the user <em>may </em>need to undo, a delay actually works in their favour! Efficiency refers to the speed with which something is done but in order for the user to perceive this sense of speed and effort, they need a chance to experience that wait or build-up (just a teensy bit).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*1_nNVRVcaRosWYtX" /><figcaption>Loading feedback that shows the steps the machine is going through — sometimes you can simulate this to communicate with the user</figcaption></figure><p>Nailing loading feedback in your product is part art but mostly logic which means you can definitely nail it whether you have a designer sitting next to you or not. Every time a user triggers an important action or is trying to load a page, they are looking for validation that everything happened as it should. Credibility as a tech product is earned through excellent implementation of UX patterns like this.</p><p>🤓 Come nerd out with me on <a href="https://twitter.com/PencilPaperUX">Twitter</a> and <a href="https://dev.to/cearacrawshaw">Dev.t</a>o for more content like this :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f67d0c9f170d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-ux-pattern-that-reflects-really-well-on-designers-and-developers-f67d0c9f170d">The UX pattern that reflects really well on designers AND developers</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making tables work: How good UX helps users make complex decisions]]></title>
            <link>https://medium.com/design-bootcamp/making-tables-work-how-good-ux-helps-users-make-complex-decisions-f8694600d571?source=rss-8fa4899f7d71------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8694600d571</guid>
            <category><![CDATA[datatables]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ceara C]]></dc:creator>
            <pubDate>Fri, 26 Mar 2021 06:14:42 GMT</pubDate>
            <atom:updated>2021-09-14T20:31:20.185Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LI-vEpBJekfseFz_tH97yw.png" /></figure><p><em>Tables won’t suck if you keep these principles in mind</em></p><p>At the heart of almost all enterprise apps is a table.</p><p>Think of all the “dashboards” that people create in Excel, Google Sheets. It’s one big table. Tables are such an important part of any product or platform. However, not all tables are created equal.</p><p>A good table allows you to sort and digest information easily. The most important and used actions are easily accessible but don’t clutter the screen. Users can get complex tasks done because the data can be manipulated really easily.</p><p>On the other hand, a bad table tries to show you all the possible data and actions up front. You need to really focus in order to interpret the columns and rows and after a while, the information in the tables starts to blur together because of the sheer volume presented to the user. No one intends to design a bad table, it’s just that by the time it’s deployed, so many trade-offs have been made and interactions overlooked.</p><p>First things first, a way to identify the potential ‘gotchas’ is to sit down with the product owner or key stakeholder and nail the requirements and context around using the table. Here are some key questions that you should be able to answer about the table you’re working on:</p><ul><li><strong>What type of data are we dealing with? </strong>The interactions and design you choose will vary if the information is short numerical strings like dates and amounts versus more complex data like paragraphs of text, links and files.</li><li><strong>What is the job to be done with this table? </strong>For example, knowing if the user is expecting to be able to scan it quickly for important information or do a comparison between values will also influence your design decisions.</li><li><strong>Is this table informational only or actionable?</strong> For example, if interpretation of data is the priority, ‘viewing options’ are an excellent emphasis. On the other hand, if taking action is the priority, ordering actionable fields and emphasizing interaction is the emphasis</li><li><strong>Who are all the stakeholders who will view the table? </strong>Different people have different viewing needs — they might even prioritize information differently.</li></ul><p>What you should end up with is acceptance criteria that will dictate which designs, styling and interactions you should pick for the table and making design decisions a whole lot easier.</p><h3>5 best practices</h3><p>I’ve designed many, many tables in my time as a designer and there are some tried and tested principles that have helped myself and developers I work with to deliver amazing results. (<em>btw, if you want to dig in deeper about tables, I made a </em><a href="https://bit.ly/3hvIqCy"><em>masterclass</em></a><em> you can check out if you’re curious</em>)</p><p>Good design is more than just the UI, it’s also about user comfort. When dealing with a feature that is, by nature, going to require a lot of brainpower to use, the following best practices can really help with that.</p><p><strong>🔬Pay attention to what’s going <em>in</em> your tables as much as the interface itself</strong></p><p>You’d be surprised at the quick wins you’ll get from addressing text and numeric alignment issues in your tables. By understanding how people scan text versus numeric values, you can ensure that what’s going into the table, isn’t going to throw off your great design and implementation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/765/1*J53yZSoqhZmaTDoO6OP97Q.png" /><figcaption><a href="https://pencilandpaper.io/articles/user-experience/ux-pattern-analysis-enterprise-data-tables/#elements-of-a-table">Text alignment</a> can be tricky with tables but is very doable.</figcaption></figure><p>For example, <a href="https://pencilandpaper.io/articles/user-experience/ux-pattern-analysis-enterprise-data-tables/#types-of-data">as a rule of thumb</a>, text should be aligned left (most comfortable for people that read languages that go left to right) and quantitative numeric values should be aligned to the right (dates and such can be left aligned, especially if it’s the first column of the table).</p><p><strong>😎 Don’t skip the fun</strong></p><p>Data can be enhanced by cute UI anchor points like icons, avatars, colourful statuses, progress bars and more.</p><p>When you consider the usage of colours, font weights and font sizes to highlight or diminish levels of information in the table, you can convey complex information more quickly and break up the monotony of a full table (it’s a good idea to design with the full state of the table as well as the empty state)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*BYSrD3yc6mWk8goD4WtEXQ.png" /><figcaption>Colour coding can enhance how easy things are to scan.</figcaption></figure><p>Colours are fun but ensure you’ve validated the signal they convey. For example, we all know that red is typically an indicator that something is wrong.</p><p><strong>🏆 Prioritize table functionalities that will yield the highest returns for the user</strong></p><p>Tables can be as deep as the ocean. You can get pretty deep in the weeds on a specific set of interactions within the table and miss the bigger picture around what the table is helping get done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*loH3lVumIHs12hJsViYuUg.gif" /><figcaption>An editing interaction shown in a table row</figcaption></figure><p>This is where the research at the start is essential and where validating with power users helps see what really matters. When considering how rows and columns should be grouped, the sorting / searching / filtering of data, the scroll behaviour or even bulk actions — you can base your design around interactions you know your users are going to be so relieved to have.</p><p><strong>✋ You can do better than buttons (hot take incoming)</strong></p><p>It’s a common mistake to overload tables with buttons all over the place. This only makes the table more dense or conversely, the page too wide or long.</p><p>Not to get too meta but the purpose behind a button is making an action to the user really obvious. We rely a lot on those little rectangles but there are other options you can use</p><p>A hover over a row could indicate that there is more data to be viewed if you clicked on it — didn’t need a button.</p><p>Open up a 3-dot menu icon and see the secondary information in a modal or sidebar — didn’t need a button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*psd7dc9euun4P6WQKX2kNw.gif" /><figcaption>Actions being revealed on a table (in the context of a desktop app)</figcaption></figure><p>You get the idea.</p><p>While it may cost a bit more technically, allowing users to perform inline actions or dynamically showing actions based on a trigger behaviour, helps with keeping clutter to a minimum. However be mindful that you address possible user input errors when taking a non-button route.</p><p><strong>✅ If your table has editing functionalities, you need to nail the success and error states</strong></p><p>Last but not least, if the table has editing functionalities, they should know when their information has been correctly saved. This is <strong>crucial </strong>if it’s enterprise software which involves a lot of data input. People need to feel like this table is reliably capturing all the information they’re putting into it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/370/1*qbgWyvTDXBG6Gk-FjslRLg.png" /></figure><p>👋 If you’re attempting a table or you’re not feeling a table that’s being actively used, consider some of these best practices and let me know what you think.</p><p>In the meantime, I’m on <a href="https://twitter.com/PencilPaperUX">Twitter</a> and <a href="https://dev.to/cearacrawshaw">Dev.t</a>o for more content like this :)</p><p><a href="https://bit.ly/3hvIqCy">Pencil &amp; Paper Labs</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8694600d571" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/making-tables-work-how-good-ux-helps-users-make-complex-decisions-f8694600d571">Making tables work: How good UX helps users make complex decisions</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX debt symptoms]]></title>
            <link>https://uxdesign.cc/ux-debt-symptoms-dba9e2fd1cc5?source=rss-8fa4899f7d71------2</link>
            <guid isPermaLink="false">https://medium.com/p/dba9e2fd1cc5</guid>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ceara C]]></dc:creator>
            <pubDate>Thu, 07 Jun 2018 15:10:32 GMT</pubDate>
            <atom:updated>2020-07-31T01:05:17.946Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sBh0NBf8JYwI26riit2W7A.jpeg" /></figure><p>User experience (UX) design has a <strong>wide scope</strong> and touches many things in both a product and in an organization. The field itself is fairly new and evolving rapidly along with technology. It’s no wonder that many of us in the technology and business world can lose track of UX’s latest evolution.</p><p>It can be hard to imagine how the UX process and philosophy can actually translate to your situation. To that end, I created a <strong>UX debt symptoms list</strong>, to help you identify the need for UX in your world.</p><h3>General Symptoms</h3><p><em>(applicable to products, established businesses)</em></p><ul><li>We <strong>aren’t actually sure who our users are</strong>, we’ve prioritized ‘everyone’, so we’re not sure how to get to know them.</li><li>It’s difficult to understand <strong>each step our users go through</strong> to meet their goals.</li><li>We know that we’re ‘<strong>supposed to do UX</strong>’ but it’s not obvious how UX maps to our situation.</li><li>We have <strong>so many metrics</strong>, but don’t know how to <strong>fix the problems</strong> we’re seeing with how our users use the product.</li></ul><h3>Product-oriented symptoms</h3><ul><li>We haven’t <strong>all gotten together as a product team </strong>to discuss the product and design problems.</li><li>We’ve <strong>tweaked features,</strong> but those changes don’t seem to have <strong>made a difference</strong>.</li><li>You find that your team is sticking to a plan or <strong>roadmap rigidly,</strong> and that you’re losing sight of why certain things are prioritized over others.</li><li>It seems random as to <strong>how features get prioritized</strong>, sometimes we don’t know why we’re building what we’re building.</li><li>On the team, we’ve usually experienced a ‘<strong>design hand off</strong>’ where the final design is delivered and that’s what we go from. We sometimes <strong>don’t get the results we want</strong>.</li></ul><h3>In closing</h3><p>While reading this, If you have done a <strong>face palm</strong> or <strong>shook your head </strong>quite a few times, I would wager that a healthy infusion of UX is in order. I’m a firm believer that problems are actually often easier to solve than we initially think, and the UX toolkit of skills, practices and philosophy can help.</p><h3>Other reading</h3><p>This is a handy article on<strong> tech debt</strong>, the parallels are quite interesting:<br><a href="https://www.techopedia.com/definition/27913/technical-debt">https://www.techopedia.com/definition/27913/technical-debt</a></p><p>This article shows signs of<strong> UX Debt for enterprise software</strong>:</p><p><a href="https://pencilandpaper.io/articles/user-experience/ux-redesign-enterprise-software/">https://pencilandpaper.io/articles/user-experience/ux-redesign-enterprise-software/</a></p><p>This article paints the picture of how weird <strong>perceptions of UX design emerged</strong>:</p><p><a href="https://uxplanet.org/the-evolution-of-ux-process-methodology-47f52557178b">The Evolution of UX Process Methodology</a></p><p>This breakdown of the<strong> UX process</strong> is a handy checklist to do design project planning:</p><p><a href="https://uxchecklist.github.io/">UX Project Checklist</a></p><p>This article is a meaty read about the current argument on <strong>design thinking </strong>(and an interesting history of user-centred design):</p><p><a href="http://interactions.acm.org/archive/view/may-june-2018/the-divisiveness-of-design-thinking">Interactions</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dba9e2fd1cc5" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/ux-debt-symptoms-dba9e2fd1cc5">UX debt symptoms</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A UX dream projects list]]></title>
            <link>https://uxdesign.cc/dream-ux-projects-list-10fa03628fdd?source=rss-8fa4899f7d71------2</link>
            <guid isPermaLink="false">https://medium.com/p/10fa03628fdd</guid>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Ceara C]]></dc:creator>
            <pubDate>Thu, 08 Mar 2018 03:58:23 GMT</pubDate>
            <atom:updated>2020-07-31T01:02:57.923Z</atom:updated>
            <content:encoded><![CDATA[<h4>What are the UX projects you wish you’d work on?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0lmwrg6o6rT0yD2py3oWmQ.png" /></figure><p>Over the past few months, I’ve reflected a lot on what I want to do in my field of UX design. That was prompted in part by really noticing things I didn’t want to do. I thought to myself: ‘Well, here’s what I don’t want to do, what DO I want to do anyways?’.</p><p>So I put together my first list of UX dream projects — putting them together is part one, and part two is releasing them into the world. (Whoosh.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w0MiWoUg-qDvQvPZDn_ViA.png" /></figure><h3><strong>Designing novel interactions that don’t exist yet</strong></h3><p>Our job as designers in technology is to work within the frameworks we have now, but to also push things forward. I want to expand what ‘interaction’ means now by designing:</p><ul><li>Screens without screens,</li><li>interaction in x/y/z axis (look up, down, side to side),</li><li>new controllers (game controller + your body),</li><li>voice commands (that don’t make you feel awkward),</li><li>gestures that don’t exist yet with our current devices.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U0HFGTXF-aCwF3C8pExIFA.png" /></figure><h3>Sound UX design</h3><p>“Beep boop beep”, but better. I’ve always loved editing sound and making animations. I think that sound design on within UX is really interesting. You’re conveying meaning and feeling in small sounds — I love the idea of being creative with this medium.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M93wdXVVIl-FORdIXZ4G6Q.png" /></figure><h3><strong><em>Designing a holistic experience of a entire user journey</em></strong></h3><p>We often design a <strong>small fragment of a larger picture</strong> but all the while appreciate that this does not capture ‘experience’ in the aggregate. I would love to design the <strong>entire scope of a user journey</strong>. This could be from the point in time that the user becomes interested, to acquiring and experiencing a product (in-person and digital products) and beyond.</p><p>Examples of possible scenarios:</p><ul><li>Booking a reservation and eating at a restaurant</li><li>Researching, buying, unpackaging and using a new phone</li><li>Procuring a complicated software (working through a lot of interactions online, different sales people, field people, setting up the software, deploying the software)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7znQLxYFcgljb0NztW-3og.png" /></figure><h3>Study user experience of employees for better workplaces</h3><p>Workplaces want their teams to work well together. Yet I see little evidence of resources and research put to this complex problem (beyond surveys sent by HR depts). Generally speaking I find people are fairly <strong>bad at asking other people for feedback</strong> (either asking in the wrong way/asking the wrong things/not asking and assuming) — this is where UX research methods come in to gather feedback on a larger and more comprehensive scale.</p><p>UX research has an amazing toolset to capture people complexity — I want to use this toolkit to <strong>ultimately help people thrive in their environment</strong> by working with upper management to mold culture/policies/teams for the better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uT4RDRq7PXiR5iCG9wvINQ.png" /></figure><h3><strong><em>Designing a product from scratch</em></strong></h3><p>Every UX designer’s dream I know. I would love to design a product from the ground up (no baggage, yay! and no understanding of what works, oh.). It would be so cool to include developers in the process, so that we can create architecture that makes sense. I envision a ‘full stack’ collaboration team including users, brand people, writers, you name it. Great ideas never just come from a individual designer scheming and dreaming on their own.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R2uUiWoGiP469KiRDgCnkA.png" /></figure><h3><strong>Designing in lesser known industries</strong></h3><p>I think how people work is so interesting. I also think that there’s a ton of cool operational lessons to uncover from lesser known industries and apply them in unexpected ways across industries and disciplines. These are some industries I’m dying to work in:</p><ul><li><a href="https://en.wikipedia.org/wiki/Logistics">Logistics</a> — it’s really complicated with a lot to gain if done well</li><li>Gaming — it’s large range of human emotion (motivation, competition, satisfaction, determination etc)</li><li>Robotics — interacting with computers x 1000</li><li>Green energy — complexity and cultural adoption</li><li>Finance — understanding and making solutions in a complex system</li></ul><p>Ok, I’ll stop now.</p><p>This concludes my fairyland wishlist of dream UX projects, well the first version at least.</p><p><strong>I’d love to hear from you!</strong></p><p>What about you? What are some of your dream projects in the world of tech/business/people?</p><p><strong>About Ceara</strong></p><p>Ceara Crawshaw founded UX agency <a href="https://pencilandpaper.io/">Pencil &amp; Paper</a> who specialize in complex domains (FinTech, BioTech, Employee UX, Startups and Enterprise Software).</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10fa03628fdd" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/dream-ux-projects-list-10fa03628fdd">A UX dream projects list</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Onboard yourself to a new UX job/gig]]></title>
            <link>https://uxdesign.cc/an-onboarding-todo-list-12105d47b5c8?source=rss-8fa4899f7d71------2</link>
            <guid isPermaLink="false">https://medium.com/p/12105d47b5c8</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[lists]]></category>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[professional-development]]></category>
            <dc:creator><![CDATA[Ceara C]]></dc:creator>
            <pubDate>Mon, 11 Dec 2017 19:12:07 GMT</pubDate>
            <atom:updated>2018-07-25T21:58:10.385Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/918/1*WQbEvFIgsNsC36afgmxQIg.png" /></figure><p>A while ago, I had this idea to write myself some instructions about onboarding* as a UX designer… collecting the I <em>did well</em> and noting what I <em>should do next time</em>. (Onboarding = to a new job, new project, new environment). It’s hard to stay aware in the moment, so I thought: “Why not get my smart past-self to help my current self?”</p><blockquote>“Why not get my smart past-self to help my current self?”</blockquote><p>I hope this list works for starting a new job or getting a new (longish term) contract gig — this article leans in the ‘established product’ direction but lots of points can be considered in other situations too.</p><h4>Active action</h4><p>This list describes ‘active’ things to do, to take control of your learning, instead of waiting for others to onboard you, or for osmosis to kick in.</p><blockquote>Taking an active role in your own onboarding is a sign of professionalism and commitment — and a practical necessity because it’s not always something that is carefully considered by the group you may be joining.</blockquote><p><em>I also acknowledge that I may be missing stuff due to my assumptions or because I have a lens of my own experiences. So please </em><strong><em>write comments</em></strong><em> and help me flesh this out further and this guide can improve and become a living thing!</em></p><p><strong>Ok here goes </strong>(a brief version is available at the bottom).</p><h3>Onboarding To Do List</h3><h4>Navigating the organization</h4><ul><li><strong>Get the who’s who overview</strong>: aside from my outward disdain for org charts, they are at least a <em>starting point</em> to understand who is who — but you’ll need to flesh these out by adding more relevant contextual design (ok, so-and-so is the lead of this team, but what are they working on now? What is their overall remit? Goals for the year? Interconnectivity with other teams, how would you work or interact with them with them?)</li><li><strong>Get or make a desk map with names</strong> (if you’re onsite or offsite really — you gotta know who the people are, maybe you’ve been awkwardly walked around the office, maybe not. Either way, you won’t remember any of them really, so get a cheat sheet — draw it if needed)</li><li>When you receive recommendations of people you should talk to about X,Y,Z, <strong>write them down immediately </strong>because you’re not going to remember anything (sensory overload alert)…don’t be stingy on the context you include to your future self.</li><li>On that note, <strong>write down pretty much everything you possibly can</strong>. Again, it’s hard to remember things — also, I’ve learned to <strong>clarify points in the moment</strong> as much as possible, rather than feeling like you’ll figure it out later magically.</li><li><strong>Arrange for 1:1</strong>’s with people (ere on the side of more) — one from each functional area if possible. UX is all about unlikely brain connections (technical, psychological, creative, emotional, practical) and people connections (collaborating with groups you would not expect AND facilitating collaboration between groups that don’t normally work together).</li></ul><p>Ask them:</p><ul><li>About their experience with UX</li><li>What their goals are — their personal/professional/team goals</li><li>What in the way they work or see things might facilitate collaboration (may or may not be applicable to working together right now, but might be great context nonetheless)</li><li><strong>Be relentlessly curious/inquisitive</strong>. Remember that this beginning is a great chance to give yourself that <strong>curiosity mindset</strong> and ask <strong>whichever dumb of questions you like</strong> (I think that asking questions and challenging people’s assumptions is always useful, <em>but especially when you’re starting off </em>you can feel totally open at first, so you might as well <strong>establish this habit/pattern</strong> now)</li></ul><h4>Learning the product(s)</h4><ul><li><strong>Get your paws on user-facing documentation</strong> that is as up-to-date as possible then comb through it, noting questions or ‘design smells’ as you go along (your fresh eyes are incredibly valuable, being so new that you may not be able to contribute ‘deliverables’ right away, but your sensitivity to the content is a great thing to help others challenge assumptions. You don’t have to get into people’s facing with your perspective yet, but certainly capture it while you’re still fresh)</li><li>Ask for <strong>internal documentation </strong>— this can be all over the place, but if you can find key docs people use for:</li><li><strong>Reference</strong> (ex. glossary, personas, client list, architecture diagrams, personas)</li><li><strong>Project tracking documents </strong>(what release is it on? What’s coming? Is there a ‘roadmap’)</li><li><strong>Style guides</strong> (marketing/brand versions — look at the brand messages being communicated in them, look at how that plays out in real life assets like the website and printed doco, even swag)</li><li><strong>QA documentation</strong> (ex. Consistently tested scenarios (including edge case scenarios) docs on expected behavior, this will help you ‘be’ someone as you really dig and explore the software)</li><li><strong>Access</strong> <strong>to Zendesk </strong>(or equivalent) and/or the <strong>support</strong> team: this is a treasure trove of UX info, but it could be hard to navigate, so asking to be connected with support might be your best bet. Zendesk might be your only source of ‘design intel’ from the standpoint of sore spots in the product. Specifically try to find out:</li><li>If <strong>feature requests</strong> are collated, if not look at some</li><li>If <strong>support tickets</strong> are quantified, reported (also look at some)</li><li>Get the temperature on<strong> supportability </strong>and how removed or connected the support team is with the rest of the teams</li><li>Find out <strong>how/where to login to the product(s)</strong> and how to get the right data into the system for the product to make sense (harder than it sounds sometimes — worth asking about accessing a complete list of products and find out the supported versions)</li></ul><h4>UX-specific intell</h4><ul><li>Find out who <strong>advocates design</strong>, be friends with them and meet them, get to know where <strong>your philosophies intersect</strong>.</li><li>Find out <strong>who talks to users </strong>in the company (field team, support, sales, client relationship people of all kinds) Then be friends with them.</li><li>Talk to <strong>devs/dev team leads</strong> and get the temperature for UX maturity by asking things like: What’s your impression of UX design overall? How have you worked with designers previously? How would you like to work with designers now? What are grey areas that you want to know more about? What do the dev teams care about the most (in terms of doing good work)?</li><li>Ask (everyone): what keeps you <strong>up at night</strong> about your product?</li><li>Ask: Who are the <strong>UX personas</strong>? Which features do they use? How were the personas arrived at? Are there scenarios built around the personas?</li><li>Ask: what role does <strong>user-testing</strong> play? What part do users play in the grand scheme of things</li><li>Ask: how does the design team <strong>work together</strong>?</li></ul><h4>Business context</h4><ul><li>Find out who are the <strong>main competitors</strong></li><li>What <strong>share of the market</strong> does this product/service have?</li></ul><h4>In Conclusion</h4><p>This isn’t everything about doing good design and doing your job well. It’s more oriented around paving the way for getting things done in a new environment. As I see it, your relationships are the most valuable thing to doing good work. Secondly, showing professionalism by leading the initiative in your own learning is powerful thing.</p><p><em>Again — if you wonder why I included something and not something else, I’d love to hear from your fresh perspective!</em></p><p><strong>— — — — — — — — — here’s the LIST version — — — — — — — — — — — -</strong></p><h4>Navigating the organization</h4><ul><li><strong><em>Write everything down</em></strong></li><li><strong><em>Be relentlessly curious/inquisitive</em></strong></li><li>Get the <strong>who’s who overview</strong></li><li>Draw or get a <strong>desk map with names</strong></li><li><strong>Arrange 1:1</strong>’s</li></ul><h4>Learning the product(s)</h4><ul><li><strong>Get user-facing documentation</strong> (make notes)</li><li>Ask for <strong>internal documentation </strong>(make notes)</li><li><strong>Reference</strong> (ex. glossary, personas, client list, architecture diagrams, personas)</li><li><strong>Project tracking documents</strong></li><li><strong>Style guides</strong></li><li><strong>QA documentation</strong></li><li><strong>Access</strong> to Zendesk</li><li>If <strong>feature requests</strong> are collated, if not look at some</li><li>If <strong>support tickets</strong> are quantified, reported (also look at some)</li><li>Find out <strong>how/where to login to the product</strong> (with data)</li></ul><h4>UX-specific intell</h4><ul><li>Find out who <strong>advocates design</strong>?</li><li>Find out <strong>who talks to users </strong>in the company (field team, support, sales, client relationship people of all kinds) Then be friends with them.</li><li>Talk to <strong>devs/dev team leads</strong> and get the temperature for UX maturity</li><li>Ask (everyone): what keeps you <strong>up at night</strong> about your product?</li><li>Ask: Who are the <strong>UX personas</strong></li><li>Ask: what role does <strong>user-testing</strong> play</li><li>Ask: how does the design team <strong>work together</strong></li></ul><h4>Business context</h4><ul><li>Find out who are the <strong>main competitors?</strong></li><li>What share of the market does this product/service have?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/511/1*E50V4RtL_l2Ut4qnNAZ6Uw.png" /></figure><p>Download a pdf <a href="https://static1.squarespace.com/static/58d16fb3ff7c505812b22f2d/t/5b1946e7575d1ffecb66cfaa/1528383207290/Medium_Onboard_CearaCrawshaw.pdf">here</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12105d47b5c8" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/an-onboarding-todo-list-12105d47b5c8">Onboard yourself to a new UX job/gig</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Delight is great, but satisfying might be a whole lot more valuable]]></title>
            <link>https://medium.com/@CearaCrawshaw/delight-is-great-but-satisfying-might-be-a-whole-lot-more-valuable-57cf4fd18cd6?source=rss-8fa4899f7d71------2</link>
            <guid isPermaLink="false">https://medium.com/p/57cf4fd18cd6</guid>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ceara C]]></dc:creator>
            <pubDate>Thu, 20 Apr 2017 01:21:41 GMT</pubDate>
            <atom:updated>2017-04-26T17:13:59.096Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/544/1*sV646KEZtcDsgMwTGnm8NQ.png" /></figure><p>I go into Asana and mark a task as complete, all of a sudden a unicorn with a rainbow in its trail flies across the screen. Eyebrows go up, smile forms and high pitched ‘eeeeeeeee!’ Can be heard from across the open plan office. The elusive ‘delight’ has struck.</p><p>That’s pretty meta, a UX Designer (who <em>wants to be</em> a unicorn) squealing <em>because</em> of a unicorn while <em>experiencing</em> the unicorn UX described as ‘delight’.</p><p>I appreciate this moment of delight and realize that it is precious and intentionally/artfully crafted. But I’d argue that as UX Designers, we are so obsessed with delight that we downplay the value of creating satisfying and successful user experiences. This is hard to do, and we shouldn’t feel like that is sub-par in some way.</p><h4>Reasonable expectations</h4><p>It’s not that realistic to create a moment of sheer delight while someone is:</p><ul><li>working on crunching mortgage numbers (determining the financial future for a person),</li><li>diagnosing a person with a disease,</li><li>making sure a bridge is strong enough to support the weight of 30 cars (so that people don’t get crushed).</li></ul><p>People use software in a huge diversity of ways. Many of whom are trained on complex and powerful software and use it to make serious decisions. So the expectation that they would need or even want some delight thrown in there is a notion straight out of fairy land.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SAyaBsQKq7IeZRcaYQOQBA.jpeg" /><figcaption><strong>Out of context delight</strong>: when applying pressure to stop some serious bleeding, you gaze to the packaging and see a The Wizard of Gauze using his magic wand.</figcaption></figure><h4>A satisfying experience</h4><p>What about this. A smart and very busy person working at a company needs to use a piece of software to create a purchase order that will benefit their whole team. This is what their experience looks like:</p><ul><li>They easily find the software they need</li><li>The thing they need to do is called what it should be called</li><li>The form they need to fill out validates on the fly, giving instantaneous feedback in the fields</li><li>Fields that are easily populated by other available information are automatically filled out</li><li>The person knows how they are progressing through the overall process of purchasing</li></ul><p>This takes them a mere 25 minutes, where it used to take at least an hour, plus another week of emailing a contact person (somewhere in the company) to finally finish this process — sucking the life force from both our original user, and the contact person who had to answer the same question they have been asked 35 times this month.</p><h4>Elegant, satisfying and not detracting</h4><p>This is what I would describe as a satisfying experience. Our user didn’t encounter tricks, backwards logic or unpredictable patterns make them feel stupid or mad. <em>The effort suspended is in proportion to the task performed.</em> Compared to the alternative, this is an interaction that is seamless and shows respect and regard for people. Sure it didn’t have an ‘element of fun’, but does making a purchase order have to be fun?</p><p>As designers we have the power to remove that helpless, soul sucking software experience. We can do this by using consistent logic and ultimately creating a satisfying software experience that makes users feel smart, not lost.</p><p>That’s pretty powerful to me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57cf4fd18cd6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maturing as a designer (in 4 stages)]]></title>
            <link>https://medium.com/@CearaCrawshaw/maturing-as-a-ux-designer-db9db739ab26?source=rss-8fa4899f7d71------2</link>
            <guid isPermaLink="false">https://medium.com/p/db9db739ab26</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ceara C]]></dc:creator>
            <pubDate>Wed, 12 Apr 2017 00:41:04 GMT</pubDate>
            <atom:updated>2017-05-17T20:17:24.199Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7PvTOitXR_Dy8VzTf8AHZQ.png" /><figcaption>Growing as a designer, from seed onwards…</figcaption></figure><p>I’ve noticed that growing as a designer doesn’t happen on a linear path of Time VS Growth. Instead I see phases in those I’ve worked with (and myself) that do a better job of capturing this ‘growth/life cycle’. There are 4 phases:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/301/1*2NoaJ_mZ8CfEHhKz55ygVg.png" /><figcaption>Phase 1 — a sprouted seed</figcaption></figure><h4>Phase 1 — a sprouted seed</h4><ul><li>Total beginner</li><li>Doesn’t know their direct selection tool from their pointer tool</li><li>Loves a good brainstorm and has unbridled creativity and ideas, which are abstract and difficult to articulate</li><li>Lots of excitement, not a whole lot of scope or constraints</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/301/1*03K2VomIgW8Mkp-vG773vA.png" /><figcaption>Phase 2 — a budding plant</figcaption></figure><h4>Phase 2 — a budding plant</h4><ul><li>Much more proficient with the core design tool — knows much of the keyboard shortcuts and all the basic concepts in their chosen design program</li><li>Learns the technical ropes around print design or UI design</li><li>Has enough knowledge to deliver designs that look quite good and satisfy the technical specifications of the end product</li></ul><p>A key differentiator is how they start their work. <em>They often dive into visual design once an initial idea is identified but maybe not very developed.</em> A lot of the design happens (say 80%) throughout <em>the visual design process</em> which is incredibly time consuming. They often try to do <em>all of the things</em> simultaneously, which requires a lot of manual correction of previous choices.</p><p><em>They are prone to going off to fairy land*, exploring stuff wildly out of scope. This is partially a symptom not having a well defined concept when starting the visual design.</em></p><p>They can be difficult to collaborate with because their documents have a horrendous lack of organization. It’s not clear what technique they use in terms of grouping and segregating objects. Is it layers? Groups? Art boards? Where do the colours come from? How were the font sizes determined? What are they named?</p><p><strong><em>Because deliverables are pretty good, sometimes great, lots of us can stagnate here indefinitely, it’s only when you push past this that design becomes manageable, less manual and more enjoyable day-to-day.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/301/1*r6Dwm3vKXkxO_GYWnKOsEA.png" /><figcaption>Phase 3 — a growing plant</figcaption></figure><h4>Phase 3 — a plant starting to grow tall, with leaves</h4><p>They know their design tool inside out (power-user level). They’ve used every feature and know every common hotkey there is. They are gaining efficiency with their tool and overall approach.</p><p>They start design in a fundamentally different way. <strong><em>They’ve reversed the effort ratio of the idea stage to the visual design stage. </em></strong>Now, 80% of design is done before their design program is even launched, those sweeping changes described for phase 2 don’t happen anymore.</p><p>The previous idea gathering stage transforms into a more rigorous process, during which the core communication goals are determined. The core problem is discussed in detail. The final design deliverable is clearly the right choice. If you are a client or team mate involved with the project, this person has asked you 12 thousand questions to fully grasp the problem.</p><p><em>This is a designer who can clearly articulate why all of the design choices they’ve made.</em></p><p>When they do open their design program and get started. They build up the core bones of the document, based on the visual hierarchy. Then they layer on color, then shadow/effects, decoration. Pixel perfect icons, final spacing rules, all of the final details. In this way, the foundation is validated, then things are tweaked and perfected.</p><p>Their design documents reflect a method of organization where they could be shared and collaborators wouldn’t have to spend time rebuilding or interpreting their document.</p><p>The final 10% of refinement is still quite time consuming, but the process of getting there is a million times less frustrating and time consuming.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/301/1*wlzmv7HNzHxc_-qrkVgcxQ.png" /><figcaption>Phase 4 — full-on plant</figcaption></figure><h4>Phase 4 — a full grown, flowering plant with a thick healthy stalk and solid root system</h4><p>The distinctive aspect of this phase is the ability to speed up that perfection process. This is a seasoned designer, who can not just feel when something is a bit off, but can <em>figure out how to fix it quickly</em>. They don’t have to try five different ways to fix something, they narrow it to a couple of possibilities and execute it efficiently. Design never ceases to be a process of elimination that is messy and has a lot of experimentation, but they bring more solid process and technical know how than most people would think could be possible in design.</p><p>This ability makes them great to get feedback from, because <em>they can give specific advice and specific actionable feedback</em>.</p><p>Even at this level of maturity, this person can still embrace that phase one creativity, but can clearly articulate it and deliver something great.</p><p>Their design time is productive and efficient. Almost no fairy land involved.</p><h4>Conclusion</h4><p>In design, we level-up by gaining feedback from other designers (and users/audience). Feedback from other designers pushes you to become more professional, articulate your decisions better and refine your workflow. Users/Audience feedback questions how well you’ve translated your thinking visually and interactively (to people that don’t do what you do).</p><p>The distinguishing features of a mature professional (as I see it) are thoughtfulness and self-control. The tilting of time spent speculating wildly in design software vs upfront thought.</p><p><strong>Fairy land</strong> — Is that place where your eyes go big when you start bending your mind around a problem. Blue sky thinking. As creatives and general humans, we’re curious and use that imaginative side of our minds to not just find solutions to problems but also conceptualize abstract and complex problems. This is a great part of the job. However, the amount of blue sky scheming that we do can derail and scope creep our work and stress us out. We can’t solve every aspect of a meaty problem simultaneously, nor can we explore every single idea that pops into our head whenever we want. It’s a stressful approach that leaves you feeling like you’re waist deep in a rabbit hole and haven’t accomplished a thing.</p><p><strong>Am I talking crazy here? Have you noticed a similar path with yourself or colleagues? I’d love to hear what you think.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db9db739ab26" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Collaborative interaction documentation for UX, QA and Dev]]></title>
            <link>https://medium.com/theuxblog/collaborative-interaction-documentation-for-ux-qa-and-dev-2d3c8cb2c49f?source=rss-8fa4899f7d71------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d3c8cb2c49f</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[enterprise-software]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ceara C]]></dc:creator>
            <pubDate>Sun, 02 Oct 2016 21:31:33 GMT</pubDate>
            <atom:updated>2016-10-05T23:04:40.963Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8pw3vuU7qzS7p4qxNvB-8g.jpeg" /></figure><p>As complexity of interactions increase, so do demands on UX (<a href="https://en.wikipedia.org/wiki/User_experience_design">user experience</a>) designers to produce appropriate documentation to communicate this complexity. When you’re dealing with enterprise applications, this complexity is inevitable because users perform an especially complex set of workflows. As a result, the richness of the interaction rules you define increases.</p><p>If we put together our documents well it can ease implementation, inform QA and help technical writers. As each of these roles have different expectations, we often all use separate pieces documentation that are disconnected, but this means content is duplicated and compromised. For example, a QA might write separate test scenarios and a technical writer might jot down what they’ve read from Jira stories. As implementation of stories happens, things shift and details of a feature could be spread across 5 stories and that single source of truth becomes more and more important. Like the game telephone, the more you remove information from the home source, the more distorted it becomes. More than that, it seems like duplicated effort which most of us can’t spare.</p><p>So my dream solution is this: QA, Dev, UX, Tech writers all know, and contribute to a single place where all the details are kept which results in:</p><ul><li>better communication</li><li>better results for the user</li></ul><p>So how might this work? Let’s start with the interaction design process from the UX end: To deal with interaction complexity, UX designers use the power of scenario mapping. This can be high level (like, a customer walks into a Starbucks..) but also more specific (like, a user presses cancel after executing three over actions which haven’t been saved yet).</p><p>Detailed scenario mapping helps UX check and recheck the strength of our designs, seeing if our interaction model actually makes sense. This process helps us identify edge cases; those weird sequences of events that aren’t immediately obvious. However, try as we might, we never think of every single one.</p><p>This is where a QA (quality assurance) specialist shines. These are creative system breakers have a keen sense of how to follow of complex sequence of events in order to break your product. They are beacons of interaction thinking and can dazzle you with their scenarios, so why not leverage these brains and collaborate on interaction documentation?</p><p>They can take your edge cases just that little bit further and assist you in stress testing your design before any developer starts implementing. You can ask them what their test cases might be when the design is being implemented. This can be a great way to come up with different states and conditions you might not have realized existed, as well as help you think a little bit more like a QA. Collaborating with QA can also be a useful communication mechanism, so that when it comes to QA stage, you have well informed gate keepers to releasing the finished product.</p><p>QAs aren’t the only brains that can improve your documentation, developers, especially UX-minded ones can help you improve your documentation as well. These guys fundamentally know the product inside and out, they also likely have a different mind from yours, one that doesn’t miss a single colon or backslash. They typically work within Agile or other project management styles which grounded in frameworks which call out assumptions and have very clear acceptance criteria. They can also grill you on your expectations around weird edge cases.</p><h3>Benefits of Collaboration</h3><p>This sort of collaboration can be useful on a lot of levels. First and foremost, it helps to have absolute clarity on how your design/feature/widget should function. You are enabled to work out even further kinks because of their input, before the expensive implementation is in full swing. You can’t predict every single question that will arise, but you can certainly work out a lot of things before you’re put on the spot. This will reduce weird decisions that get made on the fly resulting in interaction patterns that don’t sit right. <br>You also get a great opportunity to take in information from team mates that is defined in specific parameters. Getting and giving feedback is an art, you have to be cognizant of how effective getting the right type of feedback from the right people is. Asking for input on things that people are knowledgable about is great, asking for input on everything as a blob is not.</p><p>Collaboration helps build a collective brain where important things are considered when making decisions. If you’re a half way good ux designer, you’re flexible and thoughtful about the interaction choices you make. You don’t always want the most difficult implementation because that’s how you imagined it, you’re willing to compromise for the smaller things and fight for the things that are most important.</p><h3>When do you collaborate on documentation?</h3><p>You’ve sketched and written a lot of things down, dismissing other options. You have put in enough thought that you have something real to discuss with your collaborators. Showing half thought out stuff won’t be a productive use of their time.</p><p>So, your idea is quite well developed but not finalized. You’ve validated need, use cases, and your approach to solving the problem has sound rationale. Now, you’re trying to push it as hard as you can and see if it gets crushed under the pressure of edge cases and detailed developer questions.</p><p>I usually start a design document that gets gradually more and more clear (from rough notes to detailed notes, tables, images etc). At the stage where I want to know if it makes sense to others I get them to check it out. Lots of UX stress tests have already happened, so you’re in a position where you’re hungry to iron out the granular details</p><h3>The Dream Document</h3><p>The dream document for a complex feature for example:<br><strong>Intro</strong>: need/problem, design rationale, basic description of how if would work l<br><strong>Rules:</strong> specific but important design rules that developers need to know ex. Multi select is not allowed, by default container is collapsed, etc. these rules are built by design and dev<br><strong>Interaction scenarios </strong>— these scenarios including basic CRUD and edge cases are built by UX and QA.<br><strong>Visual design</strong> — housed externally (url) or embedded.</p><p>The children documents, which are linked to in your source document include detailed documentation like: help text, user facing technical documentation, implementation details, any UX research/analytics.</p><p>We as tech people seem to always ask the question: how do we actually practice ux? How do we actually do it? Working in ways like this is how we get closer to an Agile, inclusive ux practice in our organizations.</p><p>Do you join together your documentation in a way similar to this? Or do you see a better way? Tell me what you think.</p><p><a href="https://powered.by.rabbut.com/p/yBBt?c=4">Subscribe to The UX Blog</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d3c8cb2c49f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/theuxblog/collaborative-interaction-documentation-for-ux-qa-and-dev-2d3c8cb2c49f">Collaborative interaction documentation for UX, QA and Dev</a> was originally published in <a href="https://medium.com/theuxblog">theuxblog.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Corporate organization: The healthy people ecosystem]]></title>
            <link>https://medium.com/@CearaCrawshaw/corporate-organization-the-healthy-people-ecosystem-6a5264886d02?source=rss-8fa4899f7d71------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a5264886d02</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <dc:creator><![CDATA[Ceara C]]></dc:creator>
            <pubDate>Sun, 17 Jul 2016 18:19:46 GMT</pubDate>
            <atom:updated>2016-07-17T18:19:46.397Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Corporate organization: The healthy people ecosystem</strong></p><p>Lately I’ve been reflecting about how organizations function, I can’t help but compare them to living things, communities and ecosystems. These things all function in a similar way. They have objects inside of them which function in specific ways and feed into the greater system; specific feedback is passed back and forth and around and through this system. Many of the pieces can block and inhibit the greater system, or facilitate it’s healthy functioning.</p><p>A company is a manufactured or artificial system that aims to function in a similar manner, but unlike natural systems, they need to consciously engineer the mechanisms which run the feedback and enable healthy functioning. We try to do this in official ways, which often slow down or inhibit the system and cease to recognize the ways that the agents in that system (human beings), function. Specifically, what drives us and what blocks us from running efficiently (that is being happy, inspired, motivated).</p><p><strong>How the manufactured ecosystem is built</strong></p><p>Let’s say most teams are made up specialists in a specific area, let’s take marketing as an example. You have a content writer, a sales cycle person, a designer and a leader who ties it all together. As a unit, they divide and conquer a marketing and sales enablement. That works pretty well as a complimentary combination of knowledge. Say roughly the same pattern persists throughout your organization, branching and clustering accordingly.</p><p>But to have a healthy functioning, you need a system of networks to feed forward to and back from one another. This usually happens between obviously related groups, say marketing and sales and support, but not every cluster.</p><p>So who exactly connects groups that aren’t obviously related? How do these groups exchange information between one another? The answer usually is: they don’t. Accounting has no idea what support is going, quality assurance has no idea what design is doing, and development has no idea what sales is doing. This creates common organizational problems like, interdepartmental beefs, lack of understanding of how others work, general bad morale and tones of lost potential for collaboration and efficient, healthy functioning.</p><p>But what if we could engineer these systems more effectively, creating mechanisms that form connections like neurons in the brain?</p><p><strong>Super-connectors</strong></p><p>I’ve noticed recently that single agents can function this way. There are people in organizations who have extensive knowledge in either one or more <em>job function</em> or one or more<em> areas of knowledge </em>in specialized subject matter. They are the types of people that you can throw a task at and they will accomplish it, regardless of their own knowledge base. You see people like this in startups but they exist elsewhere too. They manage to bridge between groups that don’t have an existing connection to one another and enable things to get done. These are people that have the knowledge to unlock and untangle convoluted ways teams work and help create real efficiency. They can find the potential to do things better because they are embedded, they know why we’re blocked and they probably know how to fix it.</p><blockquote>[super-connectors] can find the potential to do things better because they are embedded, they know why we’re blocked and they probably know how to fix it.</blockquote><p>I think of them as superconnectors. They are a rare breed, but we can create more of them, if we put in the right catalysts.</p><p><strong>Creating collective connections</strong></p><p>Take a scenario where you have a designer do a manual tedious task that they must do fairly regularly, despite their looming workload. A software developer is embedded into the marketing team that day, just to learn how designers work, with no agenda. The developer sees the designer clicking, copying, pasting, switching screens, losing their spot, copying, pasting again, and so on and so forth. The developer asks: hey do you just need to copy x, paste it into y and do a set third thing? The design says yes. The developer takes 20 minutes, writes a script to automagically do this task, and suddenly the designer gets to leave on time the days that they are charged with this particular task. As a result the developer feels ownership and pride about their solution and also has an understanding for how difficult design is. The designer feels that their repetitive days at work are lessened and appreciate the developers knowledge base to an extent they had never felt before.</p><p>Then you have a finance person embedded in the support team for a day, they see that there is a ton of time going back and forth with a customer because of a way that a certain button is worded on their third party payment screen. This finance this person knows that this can be changed because they were intimately involved with buying the third party app. Developers didn’t have time to investigate this, because they didn’t know there was a problem. With this small exposure to how others work, the collective knowledge can go straight into action.</p><p>Finance communicates this to dev, dev changes it in two seconds. This blocking screen then frees up the support team, customers easily pay for what they need, the entire business does better.</p><p>Suddenly temporarily embedding people has made your business function like a brain, or a forest or an immune system. Temporary exposure of unconnected groups crates permanent connections being constantly built, common ground constantly created and ownership and curiosity fostered amongst individuals. Ultimately the manufactured system works much more like a natural system. We have a network of super-connectors to start, then more start to grow, ultimately forming an efficient manufactured system that functions like a natural one.</p><p>The opportunity presented in these connections far outweighs the cost, as people share knowledge, they bring perspectives together, efficiency and are able to unblock each other in a multitude of ways we could never predict.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a5264886d02" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Significance of Creepy UX]]></title>
            <link>https://medium.com/@CearaCrawshaw/the-significance-of-creepy-ux-a7d1b0e2743c?source=rss-8fa4899f7d71------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7d1b0e2743c</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ceara C]]></dc:creator>
            <pubDate>Mon, 02 May 2016 01:32:25 GMT</pubDate>
            <atom:updated>2016-05-13T15:53:37.363Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*CVQpxvG5ND2LbOfwQYGQIg.png" /><figcaption>Recieved a couple of days after a made a booking, a hilarious example of creepy UX by Hotwire.com</figcaption></figure><p>This past week, I was lucky enough to attend uxi16, a conference which gets around 500 <a href="https://www.nngroup.com/articles/definition-user-experience/">user experience</a> (UX) enthusiasts together in one place for three days.</p><p><a href="http://microinteractions.com/about-the-author/">Dan Saffer</a> led a workshop on microinteractions, during which he challenged the group to think of some<em> ways to use data to solve interaction problems </em>or ease a task for the user.</p><p>He showed us an example of how data was used to make his life easier. The image was a screenshot of a text message, where his wife asked his preference between three flavours of pie. When he went to reply, the keyboard immediately popped up and presented three word suggestions, the three flavours she had mentioned in her question. Dan described this as both clever and creepy. Really creepy.</p><p>The room discussed a series of challenges around our tables. In response to the challenges presented to us, it dawned on me that all of our separate group (and myself included), had responded to these challenges with a suggestion that we say to the user: <em>‘…we noticed, you’re doing x, would you like to do y?’. </em>This, we thought would allow us to help the user accomplish their goals.</p><p>There’s a widespread assumption we had made: <em>the user will be more pleased that they have been empowered, than they are creeped out</em>. If we’re watching them in order to help them, they’ll be fine with it.</p><blockquote>…the user will be more pleased that they have been empowered, than they are creeped out.</blockquote><p>We didn’t question if it’s ok to intrude for the sake of easiness to the user. It almost feels like we assume they can’t decide things. We assume that because the user has signed the Terms of Service Agreement (TOS), that we don’t need to ask for further consent. Yes, this is technically true, but to me, this shows a glaring omission of what the user experiences emotionally throughout using our products.</p><p>Picture this: you’re using a travel app, you’ve come back to it a few times. One day as you’re using it to search for something, it shows you a dialog that says, <strong><em>‘we’ve noticed you tend you search for this city a lot, but haven’t been there yet! Can we help find a better way to get there?’</em></strong>. There’s an <strong>ok</strong> and <strong>no thanks</strong> button.</p><p>Then picture the same situation and same message, but it gives you a third option: <strong>‘don’t cache my searches’</strong> or <strong>‘manage privacy settings’</strong>, <strong>‘show what data you look at’</strong>, <strong>‘show how my data is managed and stored’.</strong> Now, how does that situation sit with you? How does the feeling in your stomach change?</p><p>For me, that feels a lot different. It feels like the message is less paternalistic, that me and the technology are interacting <em>with</em> each other, that there is real transparency in our exchange.</p><blockquote>///aside/// <strong>the significance of creepy </strong>—It’s called intuition, a gut feeling, or a spider sense. Like lots of our emotions this is a biological mechanism designed to help us stay alive and safe. This is the feeling that hits you and says that <strong>something is off</strong> about the current situation or person you’re interacting with. This feeling has helped us stave off predators of all descriptions throughout our time on earth.</blockquote><p>Is it enough that users sign a legal document up front, and there’s no significant further exchange about data? Does that make sense for building trust and accountability?</p><p>There’s something to me that feels immature about this style of interaction, that is: either using behaviour data and assuming what the next step is or showing that you’re watching behaviour and your interpretation of what that means. There’s very little nuance in ignoring the creepy feeling users will accumulate. It’s not that this happens one time ever, it’s that this happens over lots of apps in lots of situations. This feeling falls into the negative category, which us humans remember with great fervour (see The Significance of Creepy). Can this add up to engender a feeling of technological ambivalence?</p><h3>UX call to question</h3><p>We’re at the forefront of wearable tech and all manner of bionic tech, lots of which offers real value to users. All of which requires a significant amount of trust for widespread adoption. A trust that we might be taking for granted, or considering a given. So, I wonder, how can we temper this creepy feeling and create transparent, truly empowering systems in our work? How can we develop a more nuanced approach to using data to make UX great, while allowing users to know and choose? Seriously, I’m asking.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7d1b0e2743c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>