<?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 Brittany Sumarsono on Medium]]></title>
        <description><![CDATA[Stories by Brittany Sumarsono on Medium]]></description>
        <link>https://medium.com/@bnsumarsono?source=rss-6ea1f7f701f8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*wC1cCkQ9sUvdf-FxlKF45w.jpeg</url>
            <title>Stories by Brittany Sumarsono on Medium</title>
            <link>https://medium.com/@bnsumarsono?source=rss-6ea1f7f701f8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 12:01:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bnsumarsono/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 4 “Rs” that set apart great UX designers]]></title>
            <link>https://uxplanet.org/the-4-rs-that-set-apart-great-ux-designers-1731223d8de9?source=rss-6ea1f7f701f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/1731223d8de9</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[soft-skills]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[interviewing]]></category>
            <category><![CDATA[early-career]]></category>
            <dc:creator><![CDATA[Brittany Sumarsono]]></dc:creator>
            <pubDate>Tue, 15 Mar 2022 09:07:19 GMT</pubDate>
            <atom:updated>2022-03-15T09:07:19.598Z</atom:updated>
            <content:encoded><![CDATA[<h4>Soft skills that make all the difference (and how to showcase them)</h4><figure><img alt="4 Rs" src="https://cdn-images-1.medium.com/max/1024/1*WtQe97Ew4gVUsPFcA6SPIA.jpeg" /></figure><p>The core ingredients needed to be a successful UX designer in 2022 have not changed much over the decades: you need <a href="https://www.nngroup.com/articles/sympathy-vs-empathy-ux/">customer empathy</a> (not sympathy), you need to <a href="https://blogs.intuit.com/blog/2019/07/23/design-for-delight-how-to-fall-in-love-with-your-customers-problems-and-not-the-solution/">fall in love with the problem</a> (not the solution), and of course, you need some level of proficiency in <a href="https://www.coursera.org/articles/essential-skills-for-ux-designers">UX skills</a> (not coding… unless you want to). These are the bare bones, table stakes requirements to get started in UX.</p><p>But in a sea of portfolios, case studies, competing candidates, and overall awesome designers, how do you stand out from the crowd?</p><p>The answer is not to collect more UX certifications or create more dribbble-worthy UI GIFs, but rather to showcase the more intangible qualities that ultimately make for someone we all want to work with.</p><p>Great designers can distinguish themselves by demonstrating these 4, surprisingly rare, but very important attributes:</p><ol><li>Resourcefulness</li><li>Responsiveness</li><li>Reliability</li><li>Ready with reasons (and ready to be wrong)</li></ol><p>These attributes can be tricky to showcase, but I’m going to break down some ways you can make the intangible, tangible through either your portfolio, your interview, or your day-to-day job.</p><h3>1. Resourcefulness</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cEdP0ODSaHmn_P1P2APBSg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I3SnBi_CcS30Gvvbxg0Nsg.jpeg" /></figure><p>“Resourcefulness” is <a href="https://www.google.com/search?q=resourcefulness&amp;oq=resource&amp;aqs=chrome.0.69i59j69i57j0i433i512j0i67j46i199i291i512j0i67l2j0i433i512j46i175i199i512j0i433i512.1267j1j7&amp;sourceid=chrome&amp;ie=UTF-8">the ability to find quick and clever ways to overcome difficulties</a>. Anyone who has ever tried to implement every phase of the design process (and ultimately had to skip or reorder a step or two) knows that resourcefulness and flexibility are key to getting a project done. In the real world, you will rarely have enough of every resource — time, money, people, stakeholder buy-in, etc. I always love to see what designers do to creatively work within constraints.</p><p><strong>How to showcase:</strong><br>Presumably, at least one of your portfolio case studies involves limited resources. The most common instance of this I see is lack of access to user testing. Instead of saying “I didn’t have users to test with”, spell out what assumptions you made in order to move forward, and how you would validate those assumptions in a perfect world. You can also utilize secondary research (Google is your friend) or imperfect, <a href="https://en.wikipedia.org/wiki/N_of_1_trial">N of 1</a> research (use a real friend, or friend of a friend). Anything that demonstrates you’ve thought of an alternative to the prescribed path forward.</p><h3>2. Responsiveness</h3><figure><img alt="An email with a notification" src="https://cdn-images-1.medium.com/max/1024/1*usUUJKk52neyUyowgf0-qA.jpeg" /></figure><p>This one is easy — respond to your emails (or Slacks)*. A developer is asking for an SVG? Export and send. Your PM is asking when designs will be done? Give them a date. It sounds easy, and it is. But whether or not someone utilizes this hidden-in-plain-sight superpower makes all the difference. I once heard a story of a very wise person who had access to high levels of leadership at a very young age. She was asked, “How did you get to be on such good terms with [insert important name here]?” Her response? “I respond to every email within 24 hours.” While much of the <a href="https://blog.superhuman.com/inbox-zero-method/">inbox zero</a> philosophy revolves around productivity, another understated benefit is that quick responses also quickly build trust on a team.</p><p><strong>How to showcase:<br></strong>Just respond! If you’re interviewing, don’t let a message from the recruiter or hiring manager sit in your inbox for more than a day. If you had to recruit research participants for one of your portfolio pieces, show your communication methods for reaching out and following up (a powerful skill in its own right). Another bonus skill I love to see is when designers treat their email/slack responses with the same care they give to their designs — organized headings, artful use of emojis — all with the purpose of serving up a great communication experience to the end-user.</p><p><em>* But if you’re on vacation, tell people, then turn those notifications off</em></p><h3>3. Reliability</h3><figure><img alt="A trust fall with" src="https://cdn-images-1.medium.com/max/1024/1*-vTlhlvTaqk88IUaYY4zrQ.jpeg" /></figure><p>“Reliability” is tightly related to “responsiveness”, but with a twist: instead of just<em> saying </em>something in a timely manner, <em>doing</em> something in a timely manner. The people I trust most in my life have a high say-do ratio, meaning they follow through on what they say they’ll do. As a designer, your PM relies on you to help them shape the vision of a product. Development relies on you for the specifications they need to build the product. Designers have the unique ability to immediately back up their words with action by (you guessed it) designing.</p><p><strong>How to showcase:<br></strong>If you’re interviewing, a great way to show that you have follow-through is by setting out goals at the beginning of your project. At the end of your case study, follow up on those goals. Take the interviewers back to the beginning and remind them of how you were able to meet (or even not meet) the objective of your design. In this case, demonstrating that you can follow through on completing a task you set out to do — no matter the actual outcome — goes a long way. If you’re working at a company, try to <a href="https://www.ideou.com/blogs/inspiration/learn-more-before-you-invest-more">never attend a meeting without a prototype</a>. Instead of saying, “We should improve the onboarding experience”, just start improving the onboarding experience. Prototypes don’t have to be fancy or perfect, they just have to show that if this project is started, you can be relied on to finish the work.</p><h3>4. Ready with reasons (and ready to be wrong)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RlbZmXm6TW7QEeJlvHc24w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IqgyzfuXSB3dQMAb8377Rw.jpeg" /></figure><p>As a designer, you will be asked “Why?” more times than you can count in response to design decisions you make. Being ready with responses to these “why” questions will show your team members or interviewers that you’ve thoroughly thought through every aspect of the user experience. However, being prepared with answers is only half of the equation. The other half involves being able to engage in healthy debate, and conceding to the best rationale in the end — no matter who it came from. Letting the best idea win involves setting aside your ego in order to put the user experience first. However, having reasons to begin with is a prerequisite for healthy debate. So, armor up, but also be willing to drop your weapons.</p><p><strong>How to showcase: <br></strong>Prepare in advance (either mentally, or by writing things down) for what questions might come up in response to your design. It’s ok to miss something in the experience, or not to cover every possible use case. But never just leave your response to an interviewer’s “why” question as “I don’t know”. If you created the design, no one else is going to know the answer but you. So if you don’t know, and offer no potential solutions, that puts a big dent in your team’s confidence. If you truly don’t have a reason (it happens), not all is lost. Humbly take that as a note to improve upon next time.</p><p>It goes without saying that no designer (or human) is perfect at all 4 of these things. We all have our good and bad days. But in my experience, great designers demonstrate these traits more often than not. There are many different ways to set yourself apart from the crowd in this industry, but those who focus on developing soft skills will be better off in the long run.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1731223d8de9" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/the-4-rs-that-set-apart-great-ux-designers-1731223d8de9">The 4 “Rs” that set apart great UX designers</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[Is your idea worth it?]]></title>
            <link>https://uxplanet.org/is-your-idea-worth-it-d7a56790ae3a?source=rss-6ea1f7f701f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7a56790ae3a</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Brittany Sumarsono]]></dc:creator>
            <pubDate>Tue, 08 Dec 2020 08:57:03 GMT</pubDate>
            <atom:updated>2020-12-08T08:57:03.166Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to quickly test the market for your solution with a dry wallet test</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jbt9ucVHV1cFafXnisJ0FA.jpeg" /></figure><p>So, you have an idea for a new product offering. And presumably, you think it’s a good one. Here is a surefire way to prove that you’re right (or find out that you’re horribly wrong).</p><p>The “ideation” phase of a project — which happens before anything is designed, tested, or developed, and often before the project is funded — is full of crazy-making abstractions and “what if” questions. In this phase, a new product idea is vulnerable to the rightly-placed skepticism of corporate stakeholders or potential investors who want to know:</p><ul><li>Is this a big enough customer problem?</li><li>Will customers pay to solve it?</li><li>And if so, how much will they pay?</li></ul><p>Sometimes designers get uncomfortable talking about money. Discussions about designing for monetization often lead to talk of <a href="https://darkpatterns.org/">dark patterns</a> or other forms of user trickery. But determining willingness to purchase is none of those things.</p><p>Instead, a willingness-to-purchase test, sometimes referred to as a “dry wallet” test, aims to determine if there is a market for your idea, without using any manipulation or coercive tactics. You are simply posing a straightforward, no-nonsense question to your potential customer: “Do you want to buy this product?” And when it comes to testing new ideas, there really is no better currency than, well, currency.</p><h3>What is a dry wallet test</h3><p>According to <a href="https://learningloop.io/plays/dry-wallet">Learning Loop</a>, A dry wallet test is a simulated <em>“purchase now” experience in the form of a simple e-commerce checkout or a pricing page leading to a “We are not ready yet” page, “out of stock” message, a letter of intent, or a similar elegant way of letting the user finish without actually billing them</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vAasRL-53V3o8u24VxG59w.jpeg" /></figure><p>In our case, the simulated “purchase now” experience and consequent let-down message were facilitated face-to-face, over Zoom, with the help of our Sales team. Later on we’ll talk about how to determine whether you should facilitate your fake sale in-person (meaning, over Zoom in the Covid era) or via an online, e-commerce channel.</p><h3>When to run a dry wallet test</h3><p>If you’re working on a new product or service, it is best to run a dry wallet test after<em> </em>you’ve done some initial customer interviews and user testing. Customer interviews will tell you <em>if </em>there’s a problem to be solved, a dry wallet test will tell you <em>how big</em> the problem is. The size of the problem will help inform the size of your available market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SGOxqmeRDpDmhToMrv3y8Q.jpeg" /></figure><p>Another reason to do user testing before your dry wallet test is that you will have some snazzy, validated mock-ups to include on your landing page when it comes time to market your not-yet-real product.</p><h3>Who you will need to run it</h3><p>Running a monetization test is a lot like marketing a real product, only with quite a bit more smoke and mirrors. In order to run a test like this, you will need people with the following skill sets:</p><ul><li>Someone with a vision for the product</li><li>Someone to design and deliver an end-to-end purchase experience</li><li>Someone to analyze the results of the test</li><li>Someone to either develop or facilitate the transaction</li></ul><p>This could look like any number of roles within your organization. Look for those folks around you who are good at wearing multiple hats. If you don’t have a Marketing or Finance person at your disposal, don’t be discouraged. You can always do some quick competitor research to ballpark appropriate pricing and messaging. As the product team, it is still your responsibility to determine if you even have a product or not.</p><p><strong>This is what our small but mighty team looked like:</strong></p><ul><li>1 Product Manager</li><li>1 Product Designer (me!)</li><li>1 Researcher</li><li>3 Sales Consultants</li></ul><h3>In-person sales vs e-commerce</h3><p>The composition of our team reflects our need to test enterprise software, where customers expect a Sales call or live product demo before making a purchase decision. In our case, the “live product demo” involved some images from Figma in a Google Slide deck. This sort of high-touch transaction won’t work for every customer type, especially if the product being sold is a low-cost commodity.</p><p><strong>However, the in-person dry wallet test works great when:</strong></p><ol><li>You are selling enterprise software (or an otherwise expensive product)</li><li>You need to test something fast, and you want to avoid the complexities of billing systems</li><li>Or, you want an artificially high barrier to entry to prove that this is a significant customer pain point (i.e. “10 customer out of 100 bought our productivity app over the phone… in 2020!”)</li></ol><h3>How to design the experience</h3><p>If you are planning on conducting an in-person dry wallet test, you will still need to market the product online. Our funnel looked something like this:</p><figure><img alt="In-product notification &gt; Landing page &gt; Confirmation email &gt; Self-scheduler &gt; Product demo" src="https://cdn-images-1.medium.com/max/1024/1*pZHTbKKbt6vYWsf7ZY_SJg.jpeg" /></figure><p>It is best to create a single landing page with one main value proposition. It can be tempting to want to A/B test different messages at this point, but remember that there will always be time to refine the messaging once you’ve proven that your idea is viable. For now, focus on brevity and clarity — laser focus on the problem you’re solving.</p><h3>How to measure success</h3><p>Measuring success can be tricky in any endeavor, but it is especially tricky with a new product. Our team went through the struggle of how we would define success. We ended up landing on a two-fold definition.</p><p><strong>We will be successful if:</strong></p><ol><li>We validate that our product idea <em>interests</em> customers</li><li>We validate that our customers <em>would pay </em>at least N amount for the product</li></ol><p>To measure this, we decided to use landing page conversion rate as a proxy for <em>interest</em> (i.e., the number of form submissions / the total unique viewers of the landing page), and we would use purchase rate as a measure of <em>willingness to purchase </em>(i.e., the number of customers who agreed to have their credit card charged / the total number of customers who received a product demo).</p><p>As for numerical targets, half of the team wanted to stick to modest numbers that aligned with industry standards, while the other half of the team wanted to set the bar high, aiming to beat those averages by more than 10x. Sticking to historical data might be the safest way to define success in terms of aligning with probable outcomes, but I learned that it’s not the best way to define the success of a new product. We wanted something truly differentiated rather than incremental.</p><p>We compromised on a conversion rate goal of 5x the average and kept the purchase rate goal modest. We ended up beating both goals by nearly double.</p><h3>How to let ’em down easy</h3><p>One moment of the test that caused my people-pleasing insides to churn was the moment after a closed sale, when our Sales Consultants had to inform our newly acquired customer that the product they had just decided to buy was not available for purchase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ulIK-98lMOIMM5DXPwqSeA.jpeg" /></figure><p>Much like a breakup, it is best to deliver the bad news in person — particularly if you are conducting an in-person test. After they had agreed to have their credit card on file charged, we wanted to let them know quickly and definitively that their card would <em>not</em> in fact be charged because the product was not available for purchase yet.</p><p>Now, I won’t promise that your customers won’t get mad. Some will. But I was surprised to find that the overwhelming majority of customers were OK with being told that the product was not available for purchase at this time, as long as we could keep them updated as we progressed in development. We also left our die-hard fans with a parting gift — an interim, prototype solution in the form of a Google Sheet. Whenever you can, always aim to give your customers something of value in exchange for their time.</p><p>A dry wallet test is a scrappy way to validate your assumptions up front before getting too far down the road. Plus, with the right team, they’re a lot of fun.</p><p>***</p><p>Here is a list of tools that helped us design our end-to-end experience:</p><ul><li><a href="https://mailchimp.com/?ds_rl=1276838&amp;gclid=CjwKCAiAwrf-BRA9EiwAUWwKXmNLLBRqZbXXnQPO3Mxw-77in6kt2BD09JcIq5b3VGruX5X48u8JqhoChiQQAvD_BwE&amp;gclsrc=aw.ds">MailChimp</a> — For automated emails</li><li><a href="https://calendly.com/?&amp;utm_campaign=brand-exact&amp;aw_adgroup=calendly-exact&amp;aw_version=c&amp;gclid=CjwKCAiAwrf-BRA9EiwAUWwKXhNQYHSLLtFbD32hXRwPxZJoir8Bc2dIUS7PCKjYTRyuc-S5Hf4uehoC_nUQAvD_BwE">Calendly</a> — For self-scheduling</li><li><a href="https://unbounce.com/">Unbounce</a> — For the landing page</li><li><a href="https://zoom.us/">Zoom</a> — For remote everything</li><li><a href="https://www.figma.com/">Figma</a> — For product design</li><li><a href="https://www.google.com/slides/about/">Google Slides</a> — For the presentation</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7a56790ae3a" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/is-your-idea-worth-it-d7a56790ae3a">Is your idea worth it?</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[The power of visualizing process]]></title>
            <link>https://uxplanet.org/the-power-of-visualizing-process-8f7c7f7a91be?source=rss-6ea1f7f701f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f7c7f7a91be</guid>
            <category><![CDATA[flowchart]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[diagrams]]></category>
            <category><![CDATA[service-blueprint]]></category>
            <dc:creator><![CDATA[Brittany Sumarsono]]></dc:creator>
            <pubDate>Thu, 07 May 2020 09:12:46 GMT</pubDate>
            <atom:updated>2022-03-10T19:40:56.508Z</atom:updated>
            <content:encoded><![CDATA[<h4>A guide to process mapping</h4><p>When it comes to blueprints, diagrams, flowcharts, and maps, there’s no question that designers and product managers alike have plenty of frameworks to choose from when visualizing processes. Does it matter which one you choose?</p><figure><img alt="Abstract picture of a mix of diagrams" src="https://cdn-images-1.medium.com/max/1024/1*20u4PNSDIPnBGhkiR48uIQ.jpeg" /></figure><h3>What is “process mapping”?</h3><p>“Process mapping” is exactly what it sounds like — mapping out workflows (whether they be user, business, or technical) that underlie the customer experience. Process mapping is both a powerful communication tool, and a great way to identify experience gaps for customers, employees, and partners alike.</p><p>I am intentionally using the word “process mapping”, and not “journey mapping”, “service blueprinting”, “architecture diagramming”, or even the non-offensive “flowcharting” because I often find that none of those prescribed formats usually gets at the full picture of what I want my audience to know. “Process mapping” is just a catchall phrase for the above frameworks, and more.</p><p>In short, it doesn’t matter what framework you use as long as you are designing for your audience. At the end of the day, you want to produce an artifact that is <em>used</em> by your cross-functional team — not stowed on a digital shelf. So don’t be afraid that you’re “doing it wrong” — start with a few templates, then Frankenstein the pieces you need together to create a framework that’s right for your team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dpWiHwDsc0JGfd18FL08nA.jpeg" /></figure><p>In my experience, journey mapping often focuses too exclusively on the customer, while blueprinting focuses mainly on the business-to-consumer touch-points. Don’t get me wrong, both are amazing tools. And as <a href="https://www.nngroup.com/articles/service-blueprints-definition/">NNG points out</a>, these two frameworks are best used in tandem. But while both frameworks together communicate the business and consumer needs, they neglect (or at least, de-emphasize) the technical layer that can have an equally great impact on the user experience.</p><p>My end-game is always to produce a mapping mashup that both developers and business stakeholders alike can reference to have a clear picture of what is happening at every level. But again, no two audiences are the same. Knowing who you’re talking to will help determine the scope of your artifact.</p><h3>Getting started</h3><p>At the beginning of your journey, you’ll feel more like a historian or an investigative reporter than a designer. Start by interviewing the stakeholders and partners needed to build out your ideal process map. This should include product managers, engineers, product marketers, and customer care representatives at minimum. The archeological digging will pay off in two ways: 1) You’ll learn so much more about how your product or company works, and 2) You’ll be able to start laying down some swim-lanes and boxes without holding a 20-person inter-organizational meeting.</p><p>The reason I advocate for some initial heavy-lifting on the designer for this effort stems from efficiency as well as empathy: the only person who fears a blank canvas more than a designer, is a non-designer. And that is exactly whose help you will need in order to create this thing. Throw your stakeholders a bone by doing the leg work to collect the information and build an MVP flow ahead of time, before ever hosting a workshop.</p><p>As with user testing, it’s easier to give people something to react to than to hand them a pen and say, “tell me how you want it to look.”</p><h3>When to call for help</h3><p>Once you have something for an audience to react to, then you can bring cross-functional partners together to review, refine, and identify opportunities. NNG has great additional resources that address <a href="https://www.nngroup.com/articles/blueprint-fails-fixes/">fails and fixes for this process</a>.</p><p><strong>Warning:</strong> this workshop will get messy, and you will get some things wrong. If you’ve created a flow diagram with connected boxes and arrows, editing them on the fly is going to cause some major nervous sweats. I would recommend writing the adjustments you need to make on sticky notes (either digital or physical) and then set aside some time to make the edits later, after the meeting.</p><p>The most difficult part of this process is doing something with the opportunities you identify. It is easy to point out experience pitfalls, places to improve the customer communications, or technology stacks that you should replace, but it is much harder to actually do those things.</p><h3>Why it’s powerful</h3><p>Process mapping can catalyze stakeholders to actually <em>want </em>to make changes once everything is laid out clearly in front of them. Much like data visualization is useful for revealing insights in big data, process mapping can reveal insights in big companies. In today’s world, there is growing complexity that comes from increasing integration and collaboration. If we don’t lay it out in a way that makes sense, we’ll never get the chance to be told what we can’t do (and then find a way to do it anyway).</p><h3>Tools to get started</h3><ul><li><a href="https://www.lucidchart.com/">LucidChart</a> my is a personal favorite because of its flexibility and share-ability</li><li><a href="https://www.omnigroup.com/omnigraffle/">Omnigraffle</a> is a classic for information architecture and flow diagrams</li><li><a href="https://overflow.io/">Overflow.io</a> is great for UI heavy flows (not as much for process)</li><li>Or go analog: <a href="https://www.amazon.com/sticky-notes/s?k=sticky+notes">sticky notes</a> and pens also work!</li></ul><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&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a7ecd953714a6022a3456ca263d5f43b/href">https://medium.com/media/a7ecd953714a6022a3456ca263d5f43b/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f7c7f7a91be" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/the-power-of-visualizing-process-8f7c7f7a91be">The power of visualizing process</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[Learning data visualization as a UX designer]]></title>
            <link>https://uxplanet.org/learning-data-visualization-as-a-ux-designer-c2427df7d32a?source=rss-6ea1f7f701f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2427df7d32a</guid>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Brittany Sumarsono]]></dc:creator>
            <pubDate>Mon, 28 Oct 2019 16:52:08 GMT</pubDate>
            <atom:updated>2021-09-07T23:07:19.643Z</atom:updated>
            <content:encoded><![CDATA[<p>Try and remember the first graph you ever created. Was it a bar graph, or maybe a pie chart? Was it drawn on graph paper with pencil, or generated by PowerPoint?</p><p>If you’re like me, you were not taught “data visualization” as a separate discipline in school. It was woven in and out of our education through math and science classes, and it certainly was never covered as a part of art or design.</p><p>I recently completed a <a href="http://Data Visualization with Tableau Specialization">Data Visualization with Tableau Specialization</a> through Coursera. I wanted to share a few light bulb moments I had while taking the course from a distinctly design perspective.</p><h4>💡User research tells you what data the user needs, visualization principles tell you how to get it to them</h4><p>“I’m an accountant…just give me a number!” said one of our accountants during a user test.</p><p>She was responding to a bar graph that intended to communicate how much of our product she had purchased versus how much she had used during the previous year.</p><p>After taking the data visualization course, I realized that it was not necessarily the presence of a graph that upset the accountant, who is a “numbers person” by trade. It was the incorrect way the graph leveraged both information hierarchy and <a href="https://www.interaction-design.org/literature/article/preattentive-visual-properties-and-how-to-use-them-in-information-visualization">pre-attentive attributes</a> that was causing confusion.</p><p>Let me break that down.</p><p>The data visualization principles for information hierarchy offered by <a href="https://en.wikipedia.org/wiki/Ben_Shneiderman">Ben Shneiderman</a>, otherwise known as the “Shneiderman mantra”, are as follows:</p><ol><li>Overview</li><li>Zoom and Filter</li><li>Details on Demand</li></ol><figure><img alt="Bar graph" src="https://cdn-images-1.medium.com/max/466/0*ZyXgvyf7v6uXd78h" /><figcaption>Old experience</figcaption></figure><p>The bar above graph showed the amount purchased, but only once she “demanded” the details by hovering over the bar. A contextually labeled bar graph would’ve provided a sufficient overview, but instead, the data label was treated as a minor detail.</p><p>Knowing what users are looking for will allow you to determine the appropriate information hierarchy for your data visual. In the case of the accountant, she wanted to know how much she had purchased <em>and</em> how much she had left to use at the overview level.</p><p>Secondly, while length is a pre-attentive attribute because we can process what it is communicating subconsciously (i.e. the longer the bar, the greater the amount), it is being misused in the scenario of a part-to-whole relationship.</p><p>In a part-to-whole relationship where what is “used” is a part of the whole (i.e., what is “purchased”), length can be better leveraged as a horizontal bar graph. Furthermore, the color green (rather than blue and purple) can be used to communicate that the greater the usage is, the better the progress toward using everything you purchased.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jpASjSWyWmny1_s_JTW5cw.png" /><figcaption>New experience</figcaption></figure><p>So while our accountant above “just wanted the number”, a number plus a good visual would be able to provide that clarity quicker, just as <a href="https://www.nngroup.com/articles/icon-usability/">text plus an icon is best practice for labels in user experience design</a>.</p><p>Minimalism should never come at the expense of clear communication. Getting to know your user through research will distinguish your overview from your details.</p><h4>💡<strong>You’ve heard “know you users”, now you must also “know your data”</strong></h4><p>As in software development, Subject Matter Experts (SMEs) are invaluable, and help prevent you from inadvertently misrepresenting the truth through your design.</p><p>How do I know this? Simple — when working on my capstone project in the data visualization course, I didn’t have a SME to rely on.</p><p>For our final project, we were tasked with applying everything we had learned in the course: getting the data, cleaning the data, analyzing the data, and presenting the data to our intended audience, all in accordance with our design plan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O8UdOX_8InHbjUw5udhLKg.png" /><figcaption>Publicly available government dataset</figcaption></figure><p><em>Gulp</em>. I decided to leverage one of the publicly available government datasets out there, and settled on the Consumer Financial Protection Bureau’s (CFPB) Consumer Complaint Database (I know, thousands of complaints against financial institutions, so fun!).</p><p>But here’s the thing, I knew nothing about the data. Where did it come from? How was it collected? Had the data collection methods changed over time? Who are these people reporting the data? Fortunately, the CFPB had pretty good documentation of their data, <a href="https://cfpb.github.io/api/ccdb/index.html">replete with API documentation, release notes, and field notes</a>.</p><p><em>(</em><strong><em>Side note:</em></strong><em> In data, design, development, and basically everything, documentation is king.)</em></p><p>Now all of this may sound non-design-y, but a big part of our job as designers is to be effectual <em>and</em> ethical storytellers. British economist <a href="https://en.wikipedia.org/wiki/Ronald_Coase">Ronald Coase</a> once said, “If you torture the data long enough, it will confess.” Similarly, if we cram our data into an aesthetically pleasing visual design at the expense of objective data representation, we neglect our responsibility as ethical storytellers.</p><p>If you’re delving into data visualization for the first time, find yourself a data SME, or at the very least some well-documented data on a subject you’re familiar with. That will allow you to focus on what you do best — storytelling through design.</p><h4>💡<strong>Storytelling is the best way UX designers can help shape the presentation of data</strong></h4><p>While the experience of learning to clean and analyze data was super insightful for me during this course, I don’t expect to be doing this in my day job anytime soon.</p><p>Just as learning the basics of HTML and CSS helps designers to better communicate with developers, learning about data collection and analysis will allow designers to better communicate with data and business analysts to create more effective visuals.</p><p>According to communication expert <a href="https://www.duarte.com/">Nancy Duarte</a>, author of <em>Datastory: Explain Data and Inspire Action Through Story</em>, every good story contains a “who”, a “what” and a “how” in service to a big idea.</p><p>As user experience designers, we are already experts in the “who” — we do contextual inquiries, user tests, journey maps, and persona documents, all to better empathize with and understand our customers’ needs and pain points. If we sense that access to data would resolve our users’ need or pain point (the “what”), then it is up to us as designers to determine how to bring that to life through visualization (the “how”).</p><p>It doesn’t take much more than some well-documented data, and a visualization tool (that could be Tableau, or even Excel if you’re brave) to start getting your feet wet in storytelling through data. If you have the skills to design effective experiences, data visualization is just one more avenue to apply them.</p><h4>💡<strong>At the end of the day, data visualization is still user experience design</strong></h4><p>Don’t get me wrong, data visualization does require learning a few new tools and best practices and it requires you to understand a new medium (data instead of code). But your design training in empathy and visual communication will serve you just as well in data visualization.</p><p>User experience design is not about creating pretty pictures, and neither is data visualization. To paraphrase Ben Shneiderman, it’s about allowing our users to both make and leverage insights that affect their day to day lives.</p><p>If you’re looking for a place to get started, and you don’t have a user problem that requires data visualization, start by helping out your company. I guarantee you they have data to present, whether that be to VCs, clients, executives, or any number of stakeholders. Are you presenting user research anytime soon? Start there. The best thing to do is look for opportunities to practice, and soon enough, they’ll be there.</p><p><strong>Looking for data?</strong> <a href="https://www.data.gov/">Data.gov</a> has hundreds of thousands of datasets to choose from.<br><strong>Looking for inspiration?</strong> Check out <a href="https://public.tableau.com/en-us/gallery/?tab=viz-of-the-day&amp;type=viz-of-the-day">Tableu Public’s viz of the day</a>. <br><strong>Looking for inspiration for what <em>not</em> to do?</strong> Check out <a href="https://viz.wtf/">WTF Visualizations</a>.</p><p>***<br><em>If you want to check out my capstone data visualization project, you can do so </em><a href="https://public.tableau.com/profile/brittany.sumarsono#!/vizhome/ConsumerreportonfinancialinstitutionsCFPB/Consumercomplaints"><em>here</em></a><em>.</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=c2427df7d32a" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/learning-data-visualization-as-a-ux-designer-c2427df7d32a">Learning data visualization as a UX designer</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>