<?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 Dani Nordin on Medium]]></title>
        <description><![CDATA[Stories by Dani Nordin on Medium]]></description>
        <link>https://medium.com/@danigrrl?source=rss-e98e32f5af35------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*Rp0HN_wKBhTNN6NA_3l9Vg.jpeg</url>
            <title>Stories by Dani Nordin on Medium</title>
            <link>https://medium.com/@danigrrl?source=rss-e98e32f5af35------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:50:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@danigrrl/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[Maternity Prayer]]></title>
            <link>https://danigrrl.medium.com/maternity-prayer-38727e26244f?source=rss-e98e32f5af35------2</link>
            <guid isPermaLink="false">https://medium.com/p/38727e26244f</guid>
            <category><![CDATA[maternal-health]]></category>
            <category><![CDATA[womens-health]]></category>
            <category><![CDATA[reproductive-rights]]></category>
            <category><![CDATA[feminism]]></category>
            <dc:creator><![CDATA[Dani Nordin]]></dc:creator>
            <pubDate>Wed, 15 Nov 2023 19:58:38 GMT</pubDate>
            <atom:updated>2023-11-16T16:44:10.687Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A pregnant woman lies in a tub during labor." src="https://cdn-images-1.medium.com/max/1024/0*aZ9Yp4-1PnmwgFLH" /><figcaption>A woman bent over during labor in a birthing tub. Photo by <a href="https://unsplash.com/@diaduit?utm_source=medium&amp;utm_medium=referral">Rebekah Vos</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><em>So yeah… as part of my work as a professional UX researcher, I‘ve gotten to spend the last many months researching every aspect of how Women’s Health care is delivered. And it’s brought up some feels — which led to this poem. Enjoy.</em></p><p>They never told me that every sneeze would become an adventure.</p><p>See, when you’re born with a womb and you fill it, <br><em>like you’re supposed to,</em> <br>your organs move around to make room for the tiny being you’ve donated your body to gestate.</p><p>As the fetus evolves from blueberry <br>to avocado <br>to papaya <br>and then pumpkin — <strong><em>why are they always measured in produce? -<br></em></strong>abdominal walls cleave open to make room for your expanding uterus. <br>Your intestines migrate upward to your lungs,<br>making it hard to breathe and to sleep <br>and everything — I mean <strong>everything — pushes. on. your fucking. bladder.</strong></p><p>When finally the baby arrives <br>on a river of shit <br>and blood <br>and screaming, <br>for a moment, after they clean her off, you get to hold her — <br>this gorgeous little miracle you sacrificed everything to create.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TEBI6m-IY2RNNfPT" /><figcaption>My first miracle.</figcaption></figure><blockquote><em>See, we’re taught to focus on the </em>miracle<em> part.</em></blockquote><p>Never mind the padded underwear and ice packs you wear <br>for a week after delivery <br>while your uterus bleeds out and your body reels <br>from the trauma of having a tiny human torn out of it.</p><p>Pay no mind to the litany of changes your body and mind go through <br>during every stage of pregnancy and its aftermath — <br>and <strong><em>definitely don’t think about</em></strong> <br>the myriad of ways that being a pregnant woman <br>can actually kill you.</p><p>Just be grateful for the 12 weeks you get <em>(if you’re lucky)</em> <br>to get that mind and body back in working order once that baby is born,<br>because honey — your coworkers already resent you for taking the time off.</p><blockquote><em>See, we’re taught to believe that this is all natural, </em><strong>what a woman’s body is made to do </strong><em>— the ways in which it breaks us is all part of God’s plan.</em></blockquote><p>So our legislators make choices <br>like trying to outlaw ending a pregnancy, <br>no matter why a mother might need to.</p><p>We short-change postpartum care <br>and refuse to guarantee paid parental leave,<br>leaving mothers with depression, <br>chronic pain from poorly healed scars, <br>and the need to always bring an extra pair of underwear <br>in case we sneeze, <br>or jump,<br>or live our lives a bit too “out loud.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OOJcgN1BFiWZjs2j.jpg" /><figcaption>The “father of modern gynecology” teaching medical students using enslaved women as test subjects.</figcaption></figure><p><a href="https://www.pbs.org/newshour/show/alabama-artist-works-to-correct-historical-narrative-around-beginnings-of-gynecology">James Marion Sims carved the field of gynecology <br>into the bodies of enslaved women</a>, forcing them to endure <br>the earliest gynecological procedures— including C-Sections — <br>with no lube <br>and no anesthesia.</p><blockquote>We have birthed a legacy <br>of women’s suffering and pain<br>being minimized — <strong>if not ignored completely </strong>—<br> to such a degree that <a href="https://www.cdc.gov/nchs/data/hestat/maternal-mortality/2021/maternal-mortality-rates-2021.htm#Table">125 of every 100,000 live births in the United States <br>results in the death of a mother, and <strong>70 of those mothers are Black.</strong></a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*v2t9X7s5eikfcq__.jpg" /><figcaption>Michelle Browder’s amazing <a href="https://www.smithsonianmag.com/smart-news/mothers-of-gynecology-monument-honors-enslaved-women-180980064/"><em>Mothers of Gynecology monument</em></a><em> in Montgomery AL.</em></figcaption></figure><p>Now I will never regret the choice I made to give life to my two children.</p><p>But I will always be grateful that it was, in fact, <strong><em>my choice to make</em></strong>, <br>and that I could make it when I was ready — emotionally and financially— <br>to live with the outcome, even knowing the scars it would give me.</p><p>My prayer for you, my fellow Americans, <br>is to stop focusing on the <strong><em>miracle</em></strong> part <br>and to accept the reality that pregnancy and childbirth <br>is <strong>brutally <br>fucking <br>hard</strong> and that nobody —<br>No. <br>Body.<br><em>should be forced to live with a pregnancy that will break them.</em></p><h4>If you want to learn more about the dark side of gynecology and maternal health, visit these resources<strong>:</strong></h4><ul><li>PBS Newshour, <a href="https://www.pbs.org/newshour/show/alabama-artist-works-to-correct-historical-narrative-around-beginnings-of-gynecology"><em>Alabama artist works to correct historical narrative around beginnings of gynecology</em></a><em>. </em>February 2023.</li><li><a href="https://www.morethantours.us/"><em>More than Tours</em></a>, civil rights tours out of Montgomery AL featuring artist Michelle Browder’s amazing <em>Mothers of Gynecology </em>monument.</li><li><a href="https://www.cdc.gov/nchs/data/hestat/maternal-mortality/2021/maternal-mortality-rates-2021.htm">CDC’s 2021 statistics on maternal</a> mortality rates.</li><li>Cooper Owens, Deirdre. 2017.<em> </em><a href="https://www.amazon.com/Medical-Bondage-Origins-American-Gynecology/dp/0820351350"><em>Medical Bondage: Race, Gender, and the Origins of American Gynecology</em></a><em>.</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38727e26244f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Object Oriented UX in user research — it can be done!]]></title>
            <link>https://medium.com/athenahealth-design/using-object-oriented-ux-in-user-research-it-can-be-done-f4c484972032?source=rss-e98e32f5af35------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4c484972032</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[object-oriented-ux]]></category>
            <category><![CDATA[focus-group-research]]></category>
            <category><![CDATA[information-architecture]]></category>
            <dc:creator><![CDATA[Dani Nordin]]></dc:creator>
            <pubDate>Tue, 05 Jul 2022 17:05:34 GMT</pubDate>
            <atom:updated>2022-07-06T15:29:25.976Z</atom:updated>
            <content:encoded><![CDATA[<h3>Using Object Oriented UX in user research — it can be done!</h3><p>When designing complex software, it’s easy to forget that part of what we’re dealing with is content. The content a form is required to capture; the content available to a user to accelerate their work. Content, and its structure, as an essential component of the enterprise design process — and one that’s far too easy for designers to overlook in the pressure of getting design out the door for developers to work on.</p><p><a href="https://bootcamp.uxdesign.cc/introducing-orca-the-third-diamond-in-your-ux-process-23a1babb0389">Object Oriented UX</a> provides a way for designers and teams to align on structure and content before they start designing screens. By understanding the OBJECTS people need to interact with, the ATTRIBUTES that need to exist within them, and the CALLS TO ACTION they offer, we can have better conversations with our developers and set ourselves up for experiences we can iterate and evolve over time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SYpCr0X7tkXWO_8-I3aMeg.png" /><figcaption>An overview of the OOUX process, via Sophia Prater</figcaption></figure><p>One of the key outputs of OOUX is the <em>object map</em>, which outlines the objects in the system, along with their relationships and attributes. While this can be valuable for product and engineering teams, during a recent project we wondered if it could also be used for user research,</p><p>The answer, it turns out, is yes — kinda.</p><p>Setting the stage a bit, one of our designers, Kayla Huddell, has been working with her team to create a treatment plan for a specific type of specialist. The treatment plan is a core part of how these specialists work and captures <em>goals</em> for treatment, along with specific <em>objectives</em> and <em>interventions</em> they will take to get there. We knew through our user research that the plan needed to evolve along with the provider/patient relationship, and it had to be signed by multiple people, including the patient and the provider(s) involved with treatment. We also knew that there needed to be a way to capture progress against the goals of the plan, and that there was some way in which this plan needed to be involved with the provider’s progress notes — but we weren’t fully sure how that needed to work.</p><p>So you can see that going into this project, we already had a lot of research around what a treatment plan should be, how it might be accessed, and we had a solid sense of what should be in it. What we weren’t fully clear on was:</p><ul><li>how would practitioners need to interact with the treatment plan as they work with their patients? What information would need to be captured in the progress note for a session, and what could stay in the plan?</li><li>How do practices report on treatment plans? We had heard through interviews that some practices wanted to report on how effective common interventions were — does this mean that users might need some structured “starter content” for aspects of the plan?</li><li>how might other provides need to interact, or be attributed, within this treatment plan? We knew that multiple providers, or even social services, might be participating in someone’s treatment. While we knew that signatures from all these people were needed, did we also need to find a way to assign things to them from within the plan?</li></ul><p>Working through the OOUX process together, Kayla and I arrived at a set of core objects we believed existed within and alongside the treatment plan. For each object, we looked at the research to determine:</p><ul><li>how the objects related to one another</li><li>what calls to action they might offer</li><li>what information might be most important to collect and possibly report on.</li></ul><p>The result was an object map that looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EfwXoFHNIY_FfZtJyEehWg.png" /><figcaption>Our hypothesized object map for treatment plans</figcaption></figure><p>Now came the question of validating this with end users. We had already planned on joining the user group for our target specialty the following week to get feedback on our early design for treatment plans. Could we bring the object map, and get the feedback we needed to make sure we were creating something that would work <em>before we started creating designs</em>?</p><p>We decided to start by reaching out to a couple of our internal subject matter experts (SMEs) in this space. Zooming through the object map with them in Figma, we were able to get some reasonable feedback one on one — but it was easy to get tripped up trying to figure out where to navigate next on the big map as we were trying to ask our questions. We could tell that trying to do this in a big group of providers and EHR admins over a Teams call would be a recipe for disaster. But going through the exercise with these SMEs, we were able to get really clear on some of the questions we needed to validate:</p><ul><li>Were these the right objects? And did all of these things need to be objects, or could they be free text in the Treatment plan?</li><li>How, specifically, did Objectives and Interventions play together? Did providers need suggested content here, or did they always want to write it their own way?</li><li>What about our list of things someone could <em>do</em> to a treatment plan? We knew that these plans had a review cycle and had to be signed by the patient and providers; Did that mean the current plan was closed and a new one created? Or were we just capturing a snapshot in time?</li><li>How do provides need to track progress against the plan, and how did they expect that to show up in their progress notes?</li></ul><p>These questions in mind, we decided to break out our object map into a series of PowerPoint slides, which included:</p><ol><li>An overview of the OOUX process and what the different colored boxes on the object map mean</li><li>Our experience vision for the treatment plan</li><li>The first 3 objects we identified — treatment plan, goals, and diagnosis — and how we had defined them</li><li>A few of the critical CTAs we had identified, and some key questions we had about how the were expected to work</li><li>A handful of the important attributes we identified for treatment plans, with our questions on those</li><li>The specific sub-objects within the treatment plan — objectives and interventions — and our questions around how they were meant to work with each other, and within the context of the treatment plan itself.</li></ol><p>With these slides, we were able to engage the user group in a robust conversation over a 40 minute call. Keeping things at the object and attribute level helped us get to the core of what the treatment plan should be and do, without the baggage we often find when we try to validate more “finished” prototypes types. Even better, it gave participants the freedom to challenge and correct our assumptions, which helped us see aspects of the problem we hadn’t even considered before. Best of all, the participants loved it; feedback in the meeting chat suggested that they found it productive and engaging. And the user group lead, one of our internal SMEs, was overjoyed.</p><p>So the tl;dr on this? OOUX can absolutely be validated with users, when you structure the conversation thoughtfully. Some tips on making it work:</p><ol><li>Get really clear on the questions you have to answer based on the map. This will help you structure the conversation.</li><li>Pull out the specific attributes you have questions about, as well as the objects. It’s helpful to keep like attributes together on the same slide — meta with meta, CTAs with CTAs, etc.</li><li>Define your objects and how you think they relate to each other — and use part of the session to validate &amp; evolve your definition.</li><li>Provide an overview of what OOUX is, and how you will be working with it in the session. This doesn’t have to be comprehensive; ours was a single slide that took less than two minutes to explain. But it’s essential for grounding the conversation.</li><li>Treat the session like any other type of research session. We focused in on each slide, let participants absorb what, they were seeing, and drew out their feedback with targeted questions. Within a few minutes, we were having a lively conversation that helped refine our approach to the project — and the group was delighted that their voices were being heard so early in the process.</li></ol><p>All in all, we felt this process helped to deepen our understanding on what the treatment plan could be, while giving us rapid validation and refinement of our approach — just in time to talk through the backend architecture with our engineers, with on updated object map as a guide: 10/10 would recommend!</p><p>To learn more about object-oriented UX, visit <a href="https://ooux.com/">ooux.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4c484972032" width="1" height="1" alt=""><hr><p><a href="https://medium.com/athenahealth-design/using-object-oriented-ux-in-user-research-it-can-be-done-f4c484972032">Using Object Oriented UX in user research — it can be done!</a> was originally published in <a href="https://medium.com/athenahealth-design">athenahealth design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meditation as a Leadership Skill]]></title>
            <link>https://danigrrl.medium.com/meditation-as-a-leadership-skill-117dd36d22e?source=rss-e98e32f5af35------2</link>
            <guid isPermaLink="false">https://medium.com/p/117dd36d22e</guid>
            <category><![CDATA[meditation]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Dani Nordin]]></dc:creator>
            <pubDate>Sun, 14 Mar 2021 16:53:16 GMT</pubDate>
            <atom:updated>2021-03-14T16:53:16.753Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zu4WSW9GDY8EVhyaw03vwA.jpeg" /><figcaption>Our dog, Larry, is an excellent meditator.</figcaption></figure><p>A few months ago, I decided to start a daily meditation practice. Like so many of us, I was struggling with the weight of the pandemic, and the toll it was taking on my team, my family, and my work. Guided meditations didn’t seem to be working, so I decided one morn­ing to wake up early, sit in a cozy chair by a window, set a timer, and just meditate for 5 minutes.</p><p>5 minutes turned to 10. 10 turned to 15. By the end of a week or two, I was meditating for 20 minutes every morning, even on mornings when the kids were up and running around.</p><p>Within a few weeks, I noticed I was showing up differently, at home and at work. I was able to notice when I was about to get worked up in conversa­tion and calm myself down. I could approach conflicts from a place of curiosity instead of anger. I stopped multitasking in meetings. And now, three months into the practice, I can wake up early, energized and excited-to go down­stairs and do my meditation while the house is still asleep. So what, you may ask, does this have to do with leadership? Everything.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*pzeUNaay9XYM-3g3HS3BpA.jpeg" /></figure><p>As a leader, how you show up has a tremendous im­pact on both your team and your peers. As Fosslien and Duffy say in their book <a href="https://www.lizandmollie.com/"><em>No Hard Feelings</em></a>, “Emotional culture cascades from you.” When you show up stressed, frazzled, and snapping at your colleagues, that attitude percolates through the rest of the team — and leads to teams feeling stressed, frazzled, and distracted from delivering what’s expected of them.</p><p>Okay, sure, I hear you saying, “That’s great and all, but I’m super busy. Who has time to meditate?” That may be true; I didn’t have time to meditate either for years. In my experience, the 20 minutes I spend meditating has actually saved me at least an hour a day; an hour that I normally would have spent frustrated, rumi­nating on some argument I just had, or otherwise distracted from my priorities.</p><p>So, if you decide you want to get started, here’s a few tips that have helped me.</p><ol><li><strong>Pick a good timer.</strong> I like <a href="https://insighttimer.com/">Insight Timer</a>, personally. It has the best unguided timer I’ve used, and the guided meditations are also good. <a href="https://www.calm.com/">Calm</a>, <a href="https://www.headspace.com/">Headspace</a>, and <a href="https://www.simplehabit.com/">Simple Habit</a> are also fine.</li><li><strong>Pick the right time and the right spot.</strong> For me, it’s first thing in the morning, in a cozy chair surrounded by windows in my office. For you, it might be lying on the floor with your feet on a cushion before bed, or a meditation cushion during lunchtime. I’ve found that if you’re too precious about sitting in the perfect lotus position, it distracts you from actually doing the meditation. So just find a place that’s comfortable, where you can be undistracted for a while.</li><li><strong>Pick a mantra. </strong>Having a simple mantra can make it much easier to let go of stray thoughts while you’re meditating. For me, I start off by repeating the mantra “I’m [in-breath] here [out-breath]”, then move to a variation on <a href="https://positivepsychology.com/loving-kindness-meditation/"><em>metta</em> (loving-kindness) meditation</a> for myself, my family, and my team as I breathe through each chakra. Your mileage may vary here; for some people, a mantra like “I am” or “be calm” might be sufficient.</li><li><strong>Keep a notebook and pen handy.</strong> I am constantly finding that ideas come to me in the midden of meditation-either the solution to a problem I’ve been stuck on, or a way to reframe a conflict so I can move forward in a productive way. By keeping a notebook handy, I can jot those things down and get right back to meditating.</li></ol><p>In a world gone mad, all you can control is how you show up each day. Taking some time for yourself each day in meditation can make a huge difference in how you relate to your colleagues, your directs, and yourself.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=117dd36d22e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Storytelling as a UX superpower]]></title>
            <link>https://uxdesign.cc/storytelling-as-a-ux-superpower-d6519fd7f84c?source=rss-e98e32f5af35------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6519fd7f84c</guid>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[storytelling]]></category>
            <dc:creator><![CDATA[Dani Nordin]]></dc:creator>
            <pubDate>Fri, 07 Aug 2020 16:15:55 GMT</pubDate>
            <atom:updated>2020-08-20T22:33:51.300Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Note: This article is based on a talk that I gave at </em><a href="https://chicagocamps.org/events/2020/leadership-by-design-home-edition/"><em>Leadership by Design: Home Edition</em></a><em>. If you want to see the </em><a href="https://www.slideshare.net/thezenkitchen/storytelling-as-a-ux-superpower"><em>slides, they’re up on Slideshare</em></a><em>.</em></p><p>Many folks who know me publicly know me from some <a href="https://www.oreilly.com/search/?query=dani%20nordin&amp;extended_publisher_data=true&amp;highlight=true&amp;include_assessments=false&amp;include_case_studies=true&amp;include_courses=true&amp;include_orioles=true&amp;include_playlists=true&amp;include_collections=true&amp;include_notebooks=true&amp;is_academic_institution_account=false&amp;source=user&amp;sort=relevance&amp;facet_json=true&amp;page=0&amp;include_scenarios=true&amp;include_sandboxes=true">books and videos on Drupal and design I published for O’Reilly</a> several years ago. What people may not know is that while I’ve been doing design since 1995ish, I’ve been writing since 1991.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w9N7X0IxXc5RSrrRH6vWyw.jpeg" /><figcaption>30 years of journals dating back to my (very emo) high school years.</figcaption></figure><p>My first published piece was a short poem, published in my high school’s literary journal in 1992. It read,</p><blockquote>As I reach for a star<br>and pull,<br>the sky breaks<br>and I fall into<br>the abyss.</blockquote><p>What was remarkable about this moment wasn’t the attention I got from my classmates; it was actually published anonymously. But the school’s guidance counselor, who was on the committee for the journal, reached out to me after I submitted it to see if I was okay (tl;dr, I was 16 — of course I wasn’t). That, combined with the fact that I’d been doing theatre for a couple of years at that point, really cemented the idea that <strong>stories matter.</strong></p><p>Everything that we do, no matter how mundane, has a story. Stories are a fundamentally human way in which we make sense of the world, connect with other human beings, and share knowledge. And as we grow in our design careers, we understand this implicitly. The most usable and beautiful prototypes, backed by the most rigorous research, can not succeed if we can’t get our Engineers to build them, or our Product partners to prioritize the work. Stories play a critical role in that process; if you can tell a compelling story about the problem you’re solving, and how this particular solution addresses that problem, you can move meaningful work forward.</p><h3>It’s not just scenarios</h3><p>Often, when we talk about storytelling in UX, we’re focused on <a href="https://aycl.uie.com/virtual_seminars/designing_with_scenarios_putting_personas_to_work">design scenarios</a>, which help ground our designs in a particular experience we want to create for our users. An example from my work might be:</p><blockquote>A 20-year-old woman goes to see her OB for chronic pelvic pain due to endometriosis. After looking at her chart, the OB realizes that the patient has tried several interventions, including pain medication and hormone therapy, and nothing has worked. She decides to refer the patient to a surgeon for a consultation.</blockquote><p>It’s easy to see the value of scenarios, both in terms of setting the stage for detailed design work, and for driving a compelling vision of a new future. But stories are inherent to everything we do, beyond design scenarios. Stories live in:</p><ul><li>the metrics we choose to define success</li><li>the data we use to inform our decisions</li><li>the business cases we create for our work</li></ul><p>And most importantly, <em>stories need to live in the way we talk about our work with our colleagues and stakeholders.</em></p><h3>Pick a flavor</h3><p>In my experience, stories in UX come in three flavors:</p><ol><li><strong>Explain.</strong> These stories set the stage for a deeper conversation, by describing what exists today. Examples include usability findings, research insights, etc.</li><li><strong>Persuade.</strong> These are the stories we love to pay attention to. You’ve laid the groundwork in Explain, showed the current state, and now you’re contrasting that to a new, better, vision that people will buy into. These are your vision decks, storyboards, even the case studies you put in your portfolio.</li><li><strong>Align.</strong> These are the stories which, in my experience, don’t get enough attention. We’ve heard the explanation of the current state, we’ve bought into the story that persuades — now we’re capturing our alignment to what we’re actually going to execute on.</li></ol><p>While the first two types of stories are important to set the stage, <strong>Align stories are the most essential to moving work forward</strong>. They have the most longevity, and they’re the most ubiquitous of the three flavors. They’re also the most important to get right, because they’ll be told over and over again, each time you present your work — and they’ll evolve with the project.</p><h3>The structure of a story</h3><p>Now that we know about the different types of stories, let’s look at how to make the most of each type of story. The <strong>Elements, Tone</strong> and <strong>Altitude</strong> of a story are essential to its success.</p><h4>Elements</h4><p>Story elements are pretty easy to recognize; if you’ve read fiction before, you know them. You have a <strong>character</strong>, who’s in a <strong>situation</strong>; a <strong>conflict</strong> arises and the characters need to find a <strong>resolution</strong>, which has an <strong>impact.</strong> If we apply this to our scenario from earlier, it’s easy to see this pattern:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/508/1*b2QBDjKmWwfTBEIQ3ZYBgg.png" /><figcaption>A user scenario may follow a basic story pattern.</figcaption></figure><p>But the elements of the story may change depending on its complexity and purpose. For example, the scenario listed above may have a second act, that occurs as the specialist office tries to schedule the patient. In another type of story, such as a research finding, you may want to move elements around to make the story more compelling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*hHjGqrqvKScRnjjSewWpfw.png" /><figcaption>In this story, we lead with the Conflict and Impact, then move on to the Situation, its Resolution (a workaround), and the Impact of the Resolution.</figcaption></figure><h4>Tone</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d7DDwe9jCBxZk-64lm4hTw.png" /><figcaption>Tone can shift based on what type of story you’re focused on.</figcaption></figure><p>The <strong>tone</strong> of a story helps us create the emotional connection we’re looking for. In Explain, we’re keeping things Pragmatic and matter of fact, but bringing in some Sympathy, since we’re trying to convey user pain. In Persuade, we’re shifting to a more Visionary and Urgent tone, while bringing in a sense of Pride about how we solved the user’s pain (conveyed through Sympathy).</p><p>In Align, we bring things back to a mix of Pragmatic and Sympathy, but we add a sense of Optimism as we talk about the impact of our solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*Ou0-QcU2mhSigNnJdWfn8A.png" /><figcaption>An example business rationale for a product feature.</figcaption></figure><p>In the problem statement/business rationale above, we lead with sympathy, sharing a concise description of the character’s situation and conflict, then bring a pragmatic tone to our proposed resolution before making an optimistic statement of the impact we expect to bring.</p><h4>Altitude</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/1*LmU9Lzf8q12-70Y9WmkmFg.png" /><figcaption>Levels of altitude can help shape the perspective of your story.</figcaption></figure><p>Finding the right altitude for a story can make or break its effectiveness in the telling, and it’s where I see teams trip up most often. At 5 feet, you’re deep into the weeds. You might be talking about a usability finding, or debating an interface element. When you’re talking about findings from more foundational research or discussing an entire workflow, you want to move up to about 5,000 feet.</p><p>When you start getting to the 10,000 and 30,000 feet range, you’re starting to take a big problem space and break it out into easily understandable themes. This is where the magic happens, especially in Persuade stories; when you’re working on big, hairy problems, being able to simplify that complexity into a clear set of business or user problems is essential to helping teams understand how their work fits into the bigger picture.</p><p>As we saw with Tone earlier, Altitude tends to move up and back down as you move through the three-story flavors; in Explain, you’re ranging from 5ft-10,000ft depending on what level of thing you’re trying to explain; as you get to Persuade, you want to move up to 5,000–30,000 ft to drive excitement about the big picture. When you get into Align, you want to bring things back down. At 30,000ft, you’re aligning on the big problems in the space; at 10,000ft you’re breaking down the problem space into discrete features you’re going to execute on, and when you’re back at 5ft, you’re debating the execution details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/648/1*XlUDl-FyUTCOAmDPT6tXOQ.png" /><figcaption>In this Problem Statement example, we’re staying at about 5,000ft and using a fairly standard story architecture.</figcaption></figure><h3>Principles for better storytelling</h3><p>So how can you put these things into practice? In addition to the structural elements above, here are some guiding principles I’ve found useful for successful storytelling.</p><ol><li><strong>Know what kind of story you’re telling.</strong> Way too often, teams focus on either an Explain or a Persuade story when they should really be in Align mode. The impact of this is that the story sounds either like a matter-of-fact description of what is before we’ve aligned on things, or like they’re desperate to get people to agree with them every time they talk about the work. By knowing when you’re in Align mode and focusing your energy on reminding people of your shared understanding of the problem being solved, you can improve the conversations you have during the process.</li><li><strong>Don’t drown people in data.</strong> One of the biggest traps people fall into when telling stories is trying to throw every possible number or qualitative detail into their story. This makes the listener either tune out of the story, or worse — think you aren’t thinking strategically enough. Focus instead on identifying the overall theme, and choose just enough data to ground your thesis. Additional data points are most useful when you get questions about the main point.</li><li><strong>Lead with the human element.</strong> It’s tempting to depend on analytics to tell the story of outcomes. But if you can’t tie the story back to something a human can see or feel — or how this work will solve a human problem — the numbers are meaningless. Even with largely technical changes, you should be able to articulate how this work will set us up to better meet user needs.</li><li><strong>Have a clear point of view</strong>. Even when you’re in an Explain story, you need to share a compelling point of view on why this particular story matters. Without that, people will lose interest, and you won’t be able to move on to Persuade.</li></ol><h3>Wrapping things up</h3><p>I hope this article has given you some insight into how stories can shape our work in a multitude of ways, and some tools for success. Being thoughtful about how we structure and tell stories about our work can be critical to its success.</p><h4>For more on stories</h4><ul><li><a href="https://vimeo.com/209181822">Scenarios and Storyboards: Getting to Structure and Flow</a>, Kim Goodwin, Webstock ‘17</li><li><a href="https://pathosethoslogos.com/">Ethos, Pathos and Logos,</a> <a href="http://pathosethoslogos.com/">pathosethoslogos.com</a></li><li><a href="http://www.openculture.com/2014/02/kurt-vonnegut-masters-thesis-rejected-by-u-chicago.html">Kurt Vonnegut Diagrams the Shape of Stories in a Master’s Thesis Rejected by U. Chicago</a>, <a href="http://openculture.org/">openculture.org</a></li><li><a href="https://io9.gizmodo.com/the-22-rules-of-storytelling-according-to-pixar-5916970">The 22 rules of storytelling, according to Pixar</a>, Cyriaque Lamar, Gizmodo</li><li><a href="https://rosenfeldmedia.com/books/storytelling-for-user-experience/">Storytelling for User Experience:</a> <a href="https://rosenfeldmedia.com/books/storytelling-for-user-experience/">Crafting Stories for Better Design</a>, Whitney Quesenbery and Kevin Brooks</li><li><a href="https://www.duarte.com/resonate/">Resonate: Present Visual Stories that Transform Audiences</a>, Nancy Duarte</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*ZmQpeMnKcMQSnmm8" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6519fd7f84c" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/storytelling-as-a-ux-superpower-d6519fd7f84c">Storytelling as a UX superpower</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[The lean research memo]]></title>
            <link>https://medium.com/athenahealth-design/the-lean-research-memo-35ea62b2c022?source=rss-e98e32f5af35------2</link>
            <guid isPermaLink="false">https://medium.com/p/35ea62b2c022</guid>
            <category><![CDATA[methods]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Dani Nordin]]></dc:creator>
            <pubDate>Fri, 12 Apr 2019 02:07:53 GMT</pubDate>
            <atom:updated>2019-04-12T16:45:34.657Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qamksuUoTXIRDHDhoJSr2A.jpeg" /></figure><p>In graduate school, I learned usability testing in a very formal, considered way. Tests were planned over the course of weeks, recruiting was handled by a third-party, and test reports were lengthy Powerpoint decks with dozens of issues rated by severity.</p><p>Then I graduated, and joined an Agile product team as a UX team of one. There was no way they would deal with a lengthy Powerpoint presentation, or dozens of issues. So, I developed a format for <a href="https://medium.com/@danigrrl/usability-test-reporting-a-lean-approach-8b6b593e655b">lean test reporting</a>, which enabled me to plan, execute and report on studies within the same document. Having a templated format gave my colleagues something to expect as a deliverable, and helped me plan the study in a structured way. It also had the benefit of being short; instead of creating a long, involved presentation deck that people wouldn’t read, I could report the entire study in a 4–10 page Google doc, which could then be discussed with the team.</p><p>For the purposes of illustration; we’ll stick with a basic usability test as our example. At the end of the article, I’ll share a couple versions of the template for different types of studies.</p><h4>Phase 1: Goals and planning</h4><p>As with any research study, it’s important to define your goals. In the top section of the template, work with your team to align on:</p><ul><li>a brief description of the study;</li><li>a set of clear research objectives;</li><li>a list of the key screens, workflows, etc. that you want to test;</li><li>any recruiting or compensation logistics.</li></ul><p>An example is below. The highlighted text is placeholder text in the template.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rDFZYusFPN9FWwhwP23Rww.png" /><figcaption>Use the first part of the template alongside stakeholders in the kickoff meeting.</figcaption></figure><h4>Phase 2: Writing the protocol</h4><p>Based on what you established in the goals, walk through the key scenarios, and use that information to establish your tasks for the test. Add these to the template, and review with your stakeholders for feedback. I often like to add some foundational, persona-ish questions in the background section, to start things off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kJ43kW3s5Phzf0jT9qAVpA.png" /><figcaption>The script is created after the kickoff, and reviewed with stakeholders prior to running sessions.</figcaption></figure><h4>Phase 3: Synthesize findings</h4><p>As you finish up your sessions, start to synthesize your findings into the “Key Findings” section of the template. I’ve found it helpful to use bulleted lists for the findings, and to include at least 3–5 positive notes at the beginning of the report.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pMuZ-thAttx1zn45I1eRFA.png" /><figcaption>Keeping the findings in a bulleted list helps teams absorb the content more easily.</figcaption></figure><h4>Phase 4: Recommendations &amp; Reshuffling</h4><p>After the findings are complete, finish up the report with a set of recommendations, including some mockups if appropriate. As a final step, move the “Planning” section of the template into the Appendix. This allows you to keep the highest-value information up front, but give readers the ability to see the thought process behind the study.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y35nOMoCr11gZgVvlGQpBg.png" /><figcaption>The last step is to move the Planning section down to the Appendix.</figcaption></figure><h4>Adapting the format to other types of research</h4><p>While the basic format was created initially for usability tests, I’ve also found it easy to adapt to foundational research. The main sections are the same; the difference is largely in how you plan the study and how you display the findings.</p><p>Over the years, I’ve continued to use the structured memo format for planning and reporting research, alongside <a href="https://www.smashingmagazine.com/2013/04/rainbow-spreadsheet-collaborative-ux-research-tool/">Tomer Sharon’s Rainbow Spreadsheet</a> for note-taking. We’ve also adapted the format to help designers plan and report on concept validation and <a href="https://medium.com/athenahealth-design/establishing-a-design-quality-metric-to-build-design-credibility-61236b8a4567">design quality scoring</a>, two quantitative methods we use at athenahealth to evaluate design decisions.</p><p>If you’re interested in using the method, here are a couple of templates to get you started:</p><ol><li><a href="https://docs.google.com/document/d/10fq64-jxHfC-KKwwjs_Zpudh-ZDCuFedvE7dxYRDz1A/edit?usp=sharing">A template for usability tests</a></li><li><a href="https://drive.google.com/open?id=19S3vwql2zB5197m0Tj9R-g2amKNZFEwdNh50Q4J2Xdo">A template for interview or other foundational research</a></li><li><a href="https://docs.google.com/document/d/1b-4uqy-vrFe_-OaQOb-oRWx7nBv1Oz_jD5hgL4irPGA/edit?usp=sharing">A template for site visits/ethnography</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35ea62b2c022" width="1" height="1" alt=""><hr><p><a href="https://medium.com/athenahealth-design/the-lean-research-memo-35ea62b2c022">The lean research memo</a> was originally published in <a href="https://medium.com/athenahealth-design">athenahealth design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Increase your design influence by understanding your organization’s decision-making style]]></title>
            <link>https://medium.com/athenahealth-design/increase-your-design-influence-by-understanding-your-organizations-decision-making-style-507b9ae4068e?source=rss-e98e32f5af35------2</link>
            <guid isPermaLink="false">https://medium.com/p/507b9ae4068e</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[influence]]></category>
            <dc:creator><![CDATA[Dani Nordin]]></dc:creator>
            <pubDate>Tue, 30 Oct 2018 15:41:06 GMT</pubDate>
            <atom:updated>2018-10-31T13:39:25.304Z</atom:updated>
            <content:encoded><![CDATA[<p>As designers, we like to think of ourselves as makers. When we’re working on large, <a href="https://www.invisionapp.com/inside-design/untangling-wicked-digital-problems/">wicked problems</a>, the challenge is that “making” is no longer a solo endeavor; it’s something that requires a lot of people and functionality to make happen. This can leave designers feeling like we’ve had to compromise our standards to appease business or development stakeholders. It also inadvertently creates an us-versus-them mentality that actually makes it less likely that we’ll be successful in moving forward our vision of what’s possible.</p><p>So what does this mean for us? Simply understanding what your product’s users are dealing with isn’t enough. To make truly great products, you need to understand how people, organizations, systems and content play together. In this post, I’ll focus on some ways to help understand the organizational context you’re working within, and to adjust your approach to increase your success within those organizations.</p><h3>The Competing Values Framework</h3><p><a href="https://www.oreilly.com/library/view/diagnosing-and-changing/9780470650264/">The Competing Values Framework</a> (O’Reilly, 2011) was developed by researchers Robert Quinn and Kim Cameron to help managers understand and help shift their organization’s culture. The model focuses on four quadrants, mapped by <em>focus (internal vs. external)</em> and <em>risk tolerance</em> (flexibility vs. control).*</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TqnLHJOKwFLfCGZIm5YOug.png" /><figcaption>Figure 1. The Competing Values Framework (Cameron &amp; Quinn, 2011)</figcaption></figure><p>When applied to design challenges you may be dealing with, things tend to break down thusly:</p><ul><li><strong>Clan</strong>: Clans focus on collaboration and consensus in all things. When you’re working within a clan, it can feel like things never move forward because everyone wants to have a say in the work you’re doing. Signs you’re in a clan environment include feeling like nobody is willing to just <em>make a decision already,</em> or having people involved in your project say <em>why wasn’t I involved in that decision?</em> after a decision has been made.</li><li><strong>Adhocracy</strong>: Adhocracies like to focus on creating new and innovative things. While this can be a great thing, it can also lead to feelings of chaos and churn. You might be in an adhocracy if you come up against resistance to anything that sounds like “process,” or if you hear things like <em>that’s nice and all, but we need to ship [x].</em></li><li><strong>Market</strong>: Markets love numbers. If there’s a metric they can point to that tells them they’ve succeeded, they will follow that metric closely, and focus their attention primarily on moving it in the right direction. If you’re in a market situation, you may find that your stakeholders keep asking you for more and more data to back up your proposals, but qualitative data isn’t taken seriously.</li><li><strong>Hierarchy</strong>: Heirarchies focus on top-down leadership. As such, getting anything done generally requires buy-in from senior leadership. If you’ve ever experienced the executive “swoop and poop,” or felt like your priorities constantly shift based on whatever mood an executive is in that day, you might be in a hierarchy.</li></ul><h3>So startups are adhocracies, nonprofits are clans and enterprises are hierarchies. Right?</h3><p>Not… really. As designers, we often deal with multiple groups within the same organization as we try to get our work done. So while the organization as a whole might be one style, <em>the specific groups we work within</em> can be drastically different.</p><p>For example, let’s say that you’re a design leader overseeing several digital products across an enterprise. As such, you interact with multiple teams, e.g. Marketing, Engineering, Training. Your portfolio includes work that’s beholden to each group; however, there’s one group (e.g. Marketing) that has the final say on everything in the portfolio. Each of these groups has a distinct decisionmaking style, but the style prevalent in Marketing ultimately wins. Figure 2 shows what that may look like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iCnjqNVHXrnKaFOaUZRuWQ.png" /><figcaption>Figure 2. Different team structures require different approaches.</figcaption></figure><p>In this case, what you may find is that working with the Training group requires a ton of group meetings and 1:1 discussions to move any decision forward; meanwhile, engineering is focused on meeting immediate deadlines and trying to move everything forward as quickly as possible. Once a decision is finally made with the Training group, you have to bring it to Marketing, where a single executive could throw the whole plan out of alignment, requiring you to go back and start the whole process over with the Training group.</p><h3>Navigating the four types of cultures</h3><p>Once you’re able to recognize the different types of groups you’re working with, it becomes easier to see frustrating situations not as evidence that people “don’t get it,” but as a difference in decision-making style that requires a new approach. Here are some tips that can help you navigate the different types of environments more successfully.</p><h4>Help Clans see the big picture</h4><p>With Clans, the most important thing you can do is bring people along for the ride. Find ways to show your teammates how their ideas are helping to shape the vision, and make use of informal, 1:1 feedback sessions with people who might need a bit more help getting on board. Regular sharing sessions throughout the process are also helpful; start with sharing low fidelity work, and increase the level of fidelity as the work evolves. This helps team members see the design process in action, and prevents them from feeling like you’re “handing down” a finished design for them to implement.</p><h4>Bring Just Enough Process to Adhocracies</h4><p>Adhocracies love to move fast — which can sometimes translate to a resistance to planning, or statements like “<em>don’t let Process get in the way of Progress</em>.” Adhocracies are another area where you want to focus on lower fidelity deliverables; presenting something too “finished” can make teams feel like you wasted a bunch of time when they could have jumped straight to code. Focus your role on listening at the whiteboard, and be the person who synthesizes what everyone else is saying, helping to shape the next phase of work. Another trick is to find ways to add process without every calling it that; walking the team through <a href="https://www.daninordin.com/posts/maintaining-team-alignment-with-experience-briefs">an experience brief</a> at a project/feature kickoff meeting is a great way to keep them focused. Follow it up with referencing the brief whenever you talk about design.</p><h4>Help Markets see the “why” behind the “what”</h4><p>Markets tend to focus heavily on analytics, and pay close attention to what the competition is doing. Bring as much data to the table as you can to back up your decisions. If you have access to the analytics folks, work with them to identify anomalies in the numbers, and use those anomalies to kick off qualitative research, to get to the “why” behind those numbers. By showing how qualitative and quantitative data can work together, you can put yourself in a great position to shape the MVP, and identify ways that your team can differentiate from the competition.</p><h4>Cultivate sponsors within Hierarchies</h4><p>In a Hierarchy, executive sponsorship is key to success. The challenge is being able to engage with and cultivate executive sponsors without having to create design by HPPO (<em>highest paid person with an opinion</em>). Focus on creating higher-fidelity deliverables, including prototypes, journey maps and vision decks. Discuss these with your executives, and position yourself as a strategic partner. Listen attentively during meetings, and look for ideas, feedback, etc. that will actually make the design better — and tell the executive what you’re going to do with that feedback. Hierarchies are also one of the few cultures where confidently projecting your expertise is helpful. Being able to project that expertise without diminishing that of others will serve you well here.</p><h3>Being a designer means being a diplomat</h3><p>As much as we may dislike it, navigating office politics is an essential part of being a successful designer within any culture. By taking some steps to identify the type of situation you’re in, it’s easier to adjust your approach, and increase your influence within the organization.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=507b9ae4068e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/athenahealth-design/increase-your-design-influence-by-understanding-your-organizations-decision-making-style-507b9ae4068e">Increase your design influence by understanding your organization’s decision-making style</a> was originally published in <a href="https://medium.com/athenahealth-design">athenahealth design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a sustainable strategy for tackling product-wide UX debt.]]></title>
            <link>https://medium.com/athenahealth-design/creating-a-sustainable-strategy-for-tackling-product-wide-ux-debt-5542c6b028bd?source=rss-e98e32f5af35------2</link>
            <guid isPermaLink="false">https://medium.com/p/5542c6b028bd</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Dani Nordin]]></dc:creator>
            <pubDate>Tue, 21 Aug 2018 20:36:39 GMT</pubDate>
            <atom:updated>2018-08-27T20:54:43.797Z</atom:updated>
            <content:encoded><![CDATA[<p><em>athenahealth provides network-enabled services for healthcare and point-of-care mobile apps to drive clinical and financial results for its hospital and ambulatory clients — we employ 85+ designers globally to support those efforts. Collector, one of our core products, helps clients improve their financial performance by helping them reduce the heavy administrative costs associated with getting paid.</em></p><p>During the life of any software product, a certain amount of <a href="https://www.invisionapp.com/blog/design-debt/">design debt</a> is bound to accrue. New features are added, old ones are deprecated; as our design language, and understanding of our users, has evolved, some of the interfaces in the product need to be refreshed to incorporate the new thinking. Individual issues, taken on their face, can seem trivial and not a priority to fix. Taken in aggregate, these issues can lead to frustrated customers, inefficient workflows, and eroding trust in the product if not addressed.</p><p>On the Collector UX Team, we’ve been working on a strategy to catalog and pay down the design debt accrued over the years as part of our commitment to continuously improving the product experience for our users.</p><h3>First, let’s talk about what UX debt is — and is not.</h3><p>On our team, we define “UX debt” as any design issue that impacts the <em>accuracy, efficiency or discoverability</em> of a user’s work, or which impacts the <em>credibility</em> of our product to our users. It may come from inconsistent interaction or visual design, inadequate system messaging, or excessive cognitive load required to perform certain tasks.</p><p>To quote an <a href="http://uxpamagazine.org/ux-debt-in-the-enterprise/">article on the issue from UXPA Magazine</a>:</p><ul><li><em>The term “technical debt” was coined by Ward Cunningham as a metaphor used to describe the increased cost of maintaining technology due to shortcuts taken during the development process. Joshua Kerievsky later extended the metaphor to user experience design using the term “User Experience (UX) Debt.” Kerievsky explained that, like technical debt, UX debt will eventually come due, usually in the form of less customer satisfaction and possible customer defects.</em></li></ul><p>That said, all UX debt is not created equal. The universe of design problems can range from seemingly trivial fixes (fix some spacing, improve some system messaging) to entire workflows that require redesign. In most conversations, teams will take a one-or-the-other approach; UX debt is either a minor fix to specific UI elements, or it’s the need to redesign multiple entire workflows. This typical framing of UX debt creates problems with prioritization. The problem is either too small/trivial to prioritize, or it’s so big that the team doesn’t want to risk working on it.</p><p>With this in mind, we needed a structured way to:</p><ul><li>define the types and scopes of debt we were dealing with;</li><li>store and prioritize the backlog of debt alongside the rest of the product roadmap;</li><li>determine ways to track the “payment” of debt across sprints and releases;</li><li>focus conversations around constructive, manageable things we could fix, while also taking note of where larger redesigns were more appropriate.</li></ul><p>In other words, if the team is going to commit to paying down UX debt, the debt first needs to be clearly defined, catalogued, and prioritized — not bundled into an amorphous group of UX issues.</p><h3>Identifying UX debt by problem scope</h3><p>Through discussions with the team, we organized our definitions around two fundamental characteristics: scope (how hard/easy it is to fix) and locus (global vs. local). Each of these types of debt can then be treated in different ways, making it easier for teams to prioritize the work against the larger product backlog. These types of debt are listed below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*M3qYJNP59VYHypSxWHnzrA.png" /></figure><h4><strong>Quick win</strong></h4><p><strong>What it is: </strong>A UX issue that is relatively small in scope, with a clear fix that can be implemented by a developer and designer working together in a single sprint with minimal artifacts or upfront design required. Examples of this type of debt could include updating error messages or instructional copy, or making minor layout tweaks, such as spacing or a color definition.</p><p><strong>What we do about it: </strong>combine as many issues as possible that impact the same screen into a JIRA ticket that can be prioritized in the backlog.</p><h4><strong>Optimization</strong></h4><p><strong>What it is: </strong>A UX issue that is local in nature (impacts a single element or a piece of a single screen), has a clearly understood solution that will require a non-trivial amount of work by design or development to implement, but can be resolved within a sprint or two. Examples of this type of debt could include updating an old UI pattern to use a pattern from our Forge Design System, or changing a field of checkboxes to use a multi-select list.</p><p><strong>What we do about it: </strong>Clearly define the current state and the expected state, and add as a JIRA ticket that can be prioritized in the backlog.</p><h4><strong>Redesign effort</strong></h4><p><strong>What it is: </strong>The business problem is known and we have a functional but sub-optimal solution in place. The workflow/feature as designed has multiple issues across several distinct screens, and the most appropriate solution is not necessarily obvious. Improving the workflow will require significant research and design effort, including usability testing. Examples of this could include redesigning the way that users turn chart information into billable codes, or improving the way that chart information is displayed to coding users.</p><p><strong>What we do about it: </strong>Since these issues are bigger than a single JIRA ticket, and the solution isn’t immediately apparent, they are prioritized as design initiatives within a separate backlog.</p><h3>Our approach to tackling the debt</h3><p>Once we’d built a shared language around our types of debt, it was time to start finding and cataloguing it for prioritization. Taking a cue from <a href="https://medium.com/iq-design/how-to-effectively-address-the-usability-debt-within-your-product-6b8693e6e853">Catriona Shedd’s structure for defining design debt</a>, we started by identifying the high-level user goals and tasks. We then used <a href="https://capian.co/">Capian</a> to conduct an expert review of each workflow. In addition to the expert reviews, we started to sift through our existing user research archives, <a href="https://medium.com/athenahealth-design/establishing-a-design-quality-metric-to-build-design-credibility-61236b8a4567">design scoring feedback</a>, and notes from regular user feedback calls to start finding potential issues to address.</p><p>Then came the question of storing and tracking it all. Spreadsheets were easy to lose track of, or get cluttered with too much information. Adding every single issue to JIRA was a sure-fire way to torture the development teams. We ultimately decided on an approach that involves two key streams:</p><ul><li>JIRA to store and track issues that are well defined and ready to be worked on by the development team;</li><li>Trello to capture high-level issues that still need to be shaped, discussed, etc.</li></ul><p>This allows the development backlogs to stay focused on issues that are workable, while the UX team can keep track of the other issues, pulling them into the development queue as they’re shaped. We use labels within our Trello cards and JIRA issues to keep track of the various types of debt, and can run JIRA reports on those labels to see how we’re tracking against paying it down.</p><h3>Figuring it out along the way</h3><p>By undertaking this effort, we hope to achieve the following:</p><ul><li>An inventory of design debt within Collector that we can track and drive down over time. To paraphrase Peter Drucker, “You can’t manage what you haven’t measured.”</li><li>A robust process for identifying, cataloging, and addressing design debt going forward.</li><li>Visible improvements to the quality of the user experience for our clients.</li></ul><p>As we take on this effort, we’re actively taking input from our Product and Engineering colleagues about how it’s going and what we can do to make it as effective as possible.</p><p><em>Want to tackle and prevent design debt with us? We have a variety of design roles open in Boston, Austin, Bengaluru, Chennai and Pune. If you’re interested in working with us try </em><a href="https://www.athenahealth.com//careers/design"><em>here</em></a><em> and </em><a href="https://sjobs.brassring.com/SEOTGWebHost/athenahealth/jobs/jobcategory/userexperience/25409-5492-1033-26969-User%20Experience-1.aspx"><em>here</em></a><em> or get in touch via LinkedIn, Twitter etc.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5542c6b028bd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/athenahealth-design/creating-a-sustainable-strategy-for-tackling-product-wide-ux-debt-5542c6b028bd">Creating a sustainable strategy for tackling product-wide UX debt.</a> was originally published in <a href="https://medium.com/athenahealth-design">athenahealth design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maintaining team alignment with experience briefs]]></title>
            <link>https://uxdesign.cc/maintaining-team-alignment-with-experience-briefs-99f2d09a8c65?source=rss-e98e32f5af35------2</link>
            <guid isPermaLink="false">https://medium.com/p/99f2d09a8c65</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Dani Nordin]]></dc:creator>
            <pubDate>Wed, 11 Jul 2018 01:53:55 GMT</pubDate>
            <atom:updated>2019-05-05T20:09:32.202Z</atom:updated>
            <content:encoded><![CDATA[<p>Ah, the creative brief. At once the bane of the creative’s tortured existence and a North Star to guide teams along the path to delivering something great. During my years running a small design studio, I used briefs to help plan projects, and keep clients honest during the design process. Once I started going in-house, my habit of doing design briefs floundered a bit — mostly because my <a href="http://shop.oreilly.com/product/0636920020264.do">old project briefs</a> were, frankly, a bit heavy for the work I was doing.</p><p>A few years ago, I started noticing that my teams were suffering. Projects would go off the rails — approvals would take forever, we’d go through too many rounds of iteration and end up with a sub-par design before we ever got to development. Our designers were having trouble getting their teams and stakeholders on board with the work they were trying to do, and designs were compromised as a result. I needed a way to help us bring focus and clarity back to the work so we could move design through more effectively.</p><p>Enter <a href="http://shop.oreilly.com/product/0636920020264.do"><em>the magical short-form creative brief</em></a><em>, </em>made famous by Jared Spool on the UIE blog. Comprised of a few short sections and no more than a page or two long, the brief helps center teams around a concise, brief vision for what they’re trying to create. The basic structure has been adapted over the years, but the main sections include:</p><ol><li><strong>Design problem</strong>: a 2–3 paragraph description of the problem we’re trying to solve, and why it’s important to the business.</li><li><strong>Considerations/Constraints: </strong>a quick synopsis of any dependencies, business constraints, etc. we should pay attention to during the process.</li><li><strong>Goals: </strong>a set of clearly defined business goals for this design (if they’re measurable, even better);</li><li><strong>Key Personas: </strong>1–2 personas (see “Pre-Work” below) that are most relevant to the functionality we’re creating;</li><li><strong>Key Scenarios: </strong>3–5 <a href="https://jtbd.info/replacing-the-user-story-with-the-job-story-af7cdee10c27">job stories</a> applicable to the project;</li><li><strong>Key Principles: </strong>1–3 design principles (see “Pre-Work” below) that are most applicable to this project.</li><li><strong>Milestones and Deliverables (optional)</strong>: for larger projects, this section can be used to indicate the general scope of work, and key milestones along the way.</li><li><strong>Supporting Information:</strong> any information that isn’t covered by the above sections. In practice, this may include meeting notes, findings from user research sessions, or links to various competitive analysis.</li></ol><h3>Working through the brief: the project kickoff interview</h3><p>Done well, a solid brief is no more than a page and a half of printed text, and can be completed within the course of a 1-hour project kickoff. The key to doing it well is that it’s done <em>alongside</em> stakeholders and the team, preferably during the kickoff meeting. I like to treat the brief as a structured questionnaire, where my role is to listen, facilitate conversation, and reframe what I heard as the text of the brief, which I write in front of the team.</p><p>Doing it this way requires a certain amount of thinking on your feet, but the benefit is twofold. First, it creates transparency within the team, and shows that you’re listening. Second, it prevents anyone from arguing that doing a brief “slows down the process,” since it’s happening during a meeting that you’d be having anyway.</p><h3>Pre-Work to speed up the process</h3><p>In order to realize the true time-saving power of the short-form creative brief, it helps to have a couple of things squared away up front. Having a set of clear personas and design principles for your product gives you the opportunity to speed up these sections of the brief; instead of “guessing” which personas or principles apply to this project, you can revisit the whole set with your team, and decide which ones to include.</p><p><strong>Personas: </strong>A solid set of personas (which I like to think of as <em>characters</em>, <a href="https://indiyoung.com/the-squabble-over-personas/">to borrow Indi Young’s term</a>) not only helps speed up the brief-writing process, it helps align the team on a common set of users. Conduct a <a href="https://www.daninordin.com/posts/the-persona-character-sheet">Character Sheet Workshop</a> with your team to map out the different types of people your product serves. When creating personas, think not just about demographics and user roles, but the person’s context within your problem space.</p><p><strong>Design Principles: </strong>If your product or team doesn’t have a clear set of design principles, now is the time to create them. While it’s common for teams to come up with abstract design principles, such as “Clean” or “Intuitive,” I have found in practice that design principles work best as directives from our users to the team. “Make it easy to figure out what I have to do next” is more powerful/useful than “Intuitive,” particularly in an enterprise context.</p><p><strong>Create a template: </strong>As your team continues to create briefs for projects, it becomes much easier to create a template that you can grab and start filling out on the fly. <a href="https://docs.google.com/document/d/1RwH3WPTWL2sUzFXIYgM_cLMk8A4IWBza3JBOMPCAP0Y/edit?usp=sharing">Here’s one of mine that you can use</a>.</p><h3>Conclusion</h3><p>When it comes down to it, being a good designer requires much more than pushing pixels or learning the next interesting prototyping tool. You have to help your teams prioritize, reframe their problems, and stay aligned through the messy, thrilling process of creating something new. This makes the creative brief a small but incredibly powerful tool in your design arsenal.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%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/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99f2d09a8c65" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/maintaining-team-alignment-with-experience-briefs-99f2d09a8c65">Maintaining team alignment with experience briefs</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[#DrupalVote: Meet the Candidates Round 1]]></title>
            <link>https://danigrrl.medium.com/drupalvote-meet-the-candidates-round-1-b0458d1d9825?source=rss-e98e32f5af35------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0458d1d9825</guid>
            <category><![CDATA[drupal-association]]></category>
            <category><![CDATA[open-source-contribution]]></category>
            <category><![CDATA[drupalvote]]></category>
            <dc:creator><![CDATA[Dani Nordin]]></dc:creator>
            <pubDate>Sun, 06 Mar 2016 20:01:00 GMT</pubDate>
            <atom:updated>2016-03-06T20:01:00.953Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Voting for the Drupal Association Board begins March 7, 2016 and lasts until March 18. If you want more information about my work in the Drupal community, </em><a href="https://assoc.drupal.org/election/2016-director-large-election/candidate/danigrrl"><em>visit my candidate profile on Drupal.org</em></a><em>.</em></p><p>On February 24, me and several other Drupal professionals met to discuss our candidacies for the Drupal Association board. Below are some of the key questions asked, along with my answers.</p><blockquote>The term for members-at-large has been extended to two years; at the end of your two-year term, what would you like to say you got done?</blockquote><p>For me, what I love most is finding opportunities for people to work together and figuring out which people need to be in the room in order to get things done. At Drupalcon Austin, I was able to catalyze a consensus among front-end developers around the use of CSS classes in core templates by working with MortenDK to map out the different perspectives in play, and then finding people who shared these different perspectives to join the conversation. The result was the <a href="https://www.drupal.org/node/2289511">Drupal Frontend Consensus Banana</a> (don’t ask me why it’s called that), which brought the Stable and Classy themes to Drupal 8 core.</p><p>Another way I could see myself contributing to the board is by helping to organize design and UX sprints at Drupal events. To be effective, designers need context for the problem space they’re working in, and they need to understand who they need to work with — either to get the information they need to inform the design, or to gain approval for the final design. By creating a repeatable process for organizing design sprints, we could increase the number of design contributors by giving them a set of steps to go through to plan an event.</p><blockquote>Service on the Board is different than many of the roles you play in the community. It’s more strategic role, so you get to set a longer-term direction for how to move the community forward instead of focusing on the day-to-day. How do you see being a board member as different from being a community member?</blockquote><p>From the time I started contributing to Drupal, it felt more important for me to do drupal.org than Drupal itself. I’m an information architect and researcher, and I do UX strategy for large, content-heavy websites. I’m also obsessed with helping people get their work done and find the things they need to get it done. This makes my skills and interests particularly valuable for issues like community and process documentation, work on the tools the community uses, and other pursuits I’ve been part of. Being on the Board cements my involvement with the Drupal community beyond my current level of contribution, which mostly revolves around showing up at contribution sprints and asking, “how can I help?”</p><blockquote>What is it that the Association can do to be less Americanized? How can we embrace the range of cultures that make up the Drupal community.</blockquote><p>During my thesis research, when I was doing some research with the French Drupal community, one of the first things I noticed is that they have their own Drupal.org. This happens for a very specific reason — according to French law, any information that is provided to French citizens (or software sold to them) must be at least as understandable in French as in any other language. One of the easiest ways to clarify the global position of the Drupal Association is to make Drupal.org multilingual, and to ensure there are people across the world who are helping to translate its content.</p><p>In terms of whether each country/region should have its own Association, I don’t actually mind having different versions of the Association as long as the different groups communicate with each other. It’s really difficult for volunteer-driven organizations to manage effectively when they’re trying to work together in different regions. Each culture has its own unique needs, which are difficult to accommodate through a single organization.</p><blockquote>Last year, Drupal Association decided to fund Drupal 8 in a way they haven’t before with the D8 Accelerate program. Do you feel like there’s room for more or different types of programs like this?</blockquote><p>There were a lot of exceptional situations with Drupal 8. Prior to 8, we didn’t have Views or WYSIWYG in Core. We also completely changed much of the architecture, including the theme engine. All this work made a significantly better product, but also made the implementation of these changes infinitely more complex.</p><p>Most big modules are sponsored by one Drupal shop or another, and <a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=1&amp;cad=rja&amp;uact=8&amp;ved=0ahUKEwjVj-ushKbLAhWLKh4KHc_4D4sQFggcMAA&amp;url=http%3A%2F%2Fbuytaert.net%2Fthe-investment-case-for-employing-a-drupal-core-contributor&amp;usg=AFQjCNEZw7NGy3W06W7SFZq6w1q59pNSGg&amp;bvm=bv.115339255,d.dmo">we’ve made the case for shops to hire people to just work on core</a>. If we’re going to make that decision as a community, I don’t see why the DA can’t be part of that.</p><blockquote>Back in May, we released issue/comment credits on Drupal.org. It’s been exciting to get more clarity on what the community is doing, but there have been concerned about “gamifying” contribution. Do you think the system we’ve put in place is achieving the goal of increasing contributions by making contribution more visible? How can we do better?</blockquote><p>When you’re talking about gamification, generally people tend to assume that it’s badges, and they either get really annoyed or they really love it, because “badges!” The important thing is to be able to, from a macro level, demonstrate and understand the breadth of the ecosystem that contributes to Drupal, and it’s much larger than code commits.</p><p>It’s also important to recognize that a solely technological solution isn’t going to cut it. Most designers who do contribution aren’t doing their work in the Issue Queue; they’re having conversations with people at events, or collaborating over Skype. People who are running sprints and doing mentoring aren’t necessarily going to be hanging out in the Issue Queue; they’re going to be rolling up their sleeves at events helping other people get their work done. You have to find a technological solution and balance that with a human solution.</p><p><em>Voting for the Drupal Association Board begins March 7, 2016 and lasts until March 18. If you want more information about my work in the Drupal community, </em><a href="https://assoc.drupal.org/election/2016-director-large-election/candidate/danigrrl"><em>visit my candidate profile on Drupal.org</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0458d1d9825" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I’m running for the Drupal Assocation board… and why you should elect me.]]></title>
            <link>https://danigrrl.medium.com/why-i-m-running-for-the-drupal-assocation-board-and-why-you-should-elect-me-cbd27b8e08cc?source=rss-e98e32f5af35------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbd27b8e08cc</guid>
            <category><![CDATA[drupalvote]]></category>
            <category><![CDATA[drupal-association]]></category>
            <category><![CDATA[open-source-contribution]]></category>
            <dc:creator><![CDATA[Dani Nordin]]></dc:creator>
            <pubDate>Fri, 04 Mar 2016 20:11:00 GMT</pubDate>
            <atom:updated>2016-03-04T20:11:00.936Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Voting for the Drupal Association Board begins March 7, 2016 and lasts until March 18. If you want more information about my work in the Drupal community, </em><a href="https://assoc.drupal.org/election/2016-director-large-election/candidate/danigrrl"><em>visit my candidate profile on Drupal.org</em></a><em>.</em></p><h4>Why I’m running</h4><p>I have long been an activist — both in the Drupal community and outside of it. In high school, I spent summers canvassing for a national environmental group, and got involved in theatre and writing during the school year. During the early years of <a href="http://tzk-design.com/">my former design studio, the zen kitchen</a>, I focused my client base on non-profits and social entrepreneurs, developing expertise in sustainable print design, branding and marketing for non-profits, and socially responsible businesses.</p><p>Since joining the Drupal community in 2008, I’ve been a persistent and vocal champion for designers and other non-code-oriented professionals in the community, even going so far as <a href="http://www.amazon.com/Drupal-Designers-Dani-Nordin/dp/1449325041">writing books on project management and design for Drupal</a>. I’m passionate not only about expanding the variety of skillsets involved in Drupal contribution, but in helping more people learn how to use Drupal. Being part of the Drupal Association board will give me an opportunity to work with the community to achieve both of those goals.</p><h4>What I’ve done</h4><p>Since 2009, I’ve been a lead organizer of <a href="http://design4drupal.org/">Design 4 Drupal Camp Boston</a>, which brings together the brightest design minds in the Drupal community to share knowledge, talk shop and network with each other. In addition to leading the web team for three years running, I’ve been responsible for recruiting speakers, curating sessions, and (most important!) making sure that people at the Camp have plenty of coffee and a delicious lunch.</p><p>I’ve been contributing design and UX work to both the Drupal project and Drupal.org since 2010. Highlights include:</p><ul><li>Playing a key role in facilitating the <a href="https://www.drupal.org/node/2289511">Front-End Consensus Banana at Drupalcon Austin</a>, which resulted in the Stable and Classy themes in Drupal 8. This included both helping to outline the problem space for the people involved, and making sure the voices involved in the discussion included as much variety as possible.</li><li>Working with the community to <a href="https://www.drupal.org/node/2281763">redesign the Drupal.org user profile</a>. This included both creating an overall vision for the profile as a Drupal community member’s “Drupal resumé,” and creating a living, annotated prototype of the updated profile.</li><li>Conducting qualitative research into the experiences of Drupal contributors as part of my Master’s Thesis. The final research was <a href="http://tzk-design.com/tags/drupal-community-involvement-study">published on my blog</a>, <a href="http://tzk-design.com/engaging-ux-and-design-contributors">presented at DrupalCon Amsterdam</a>, and delivered to the Drupal Association.</li></ul><h4>Why you should elect me</h4><p>Being part of the Drupal Association Board gives me the opportunity to do what I do best — helping people from different disciplines reach consensus on issues that matter to them.</p><p><em>Voting for the Drupal Association Board begins March 7, 2016 and lasts until March 18. If you want more information about my work in the Drupal community, </em><a href="https://assoc.drupal.org/election/2016-director-large-election/candidate/danigrrl"><em>visit my candidate profile on Drupal.org</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbd27b8e08cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>