<?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 Justin Jolley on Medium]]></title>
        <description><![CDATA[Stories by Justin Jolley on Medium]]></description>
        <link>https://medium.com/@amiwebguy?source=rss-5dc7602b0ba8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*332jtoKZy56OFqBgTFm_jg.jpeg</url>
            <title>Stories by Justin Jolley on Medium</title>
            <link>https://medium.com/@amiwebguy?source=rss-5dc7602b0ba8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 12:46:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@amiwebguy/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[Thinking again: my path from transactional to transformational]]></title>
            <link>https://uxdesign.cc/thinking-again-my-path-from-transactional-to-transformational-935bdd131301?source=rss-5dc7602b0ba8------2</link>
            <guid isPermaLink="false">https://medium.com/p/935bdd131301</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Justin Jolley]]></dc:creator>
            <pubDate>Sun, 06 Jun 2021 09:58:15 GMT</pubDate>
            <atom:updated>2021-06-06T09:58:15.412Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Thinking again, my path from transactional to transformational" src="https://cdn-images-1.medium.com/max/1024/1*RyHJZY9HdA2aQr_w6DAHjQ.jpeg" /></figure><h3>An engineer’s mind</h3><p>It’s funny, growing up I didn’t think I had a particularly logical mind. I always enjoyed doing more creative things like drawing, reading, and writing and tended to not be terribly engaged with logic and math. I found though, that as I grew I learned to love repeatable patterns and consistency. As I found a love for creating websites I also discovered that I loved learning how to code.</p><p>The reliability that if you wrote these certain lines, then this would be represented in your browser. Yes, we have to eventually account for browser differences, but my world became to revolve around twiddling with 1’s and 0’s to build and connect to databases, structure pages, improve the interaction with JavaScript. I thrived on the predictability and reliability of code and action.</p><p>I think that possibly because so much of my personal life was beyond my control I sought the comfort of structure and stability and I loved what I did. I didn’t realize as I progressed throughout my career into management and leadership how big a change was awaiting me. What I didn’t realize is how hard the shift would be to move from an individual contributor role, tweaking code and design to build something to dealing with people that were much less structured, immutable with repeatable cause and effect. People are complicated and complex, emotions take over and logic flies out the window.</p><p>The old adage of what got you here won’t help you go further rang very true. The practice of promoting top performers within a technical environment is pretty widespread in our industry. This means as a manager you have no real managerial training or have learned how to lead people as you’ve been focused on how to design and develop better. I can easily look back over my career and name the great thinkers who were brilliant technical minds but on retrospection see how they lacked basic management skills.</p><p>I believe because technology is so fast-paced with a new language or product popping up so frequently that few technology leaders have time to learn or hone their management skills. It’s so easy to find online training or the latest JavaScript framework, but more difficult to find good resources for <a href="https://www.businessnewsdaily.com/6456-new-manager-tips.html">being a good manager</a>.</p><h3>Black and white, on or off</h3><p>I think because of my engineering mind many things seemed very black and white to me. There was a right way and a wrong way for things to be done. Either your code compiled or ran or it didn’t. There’s not a lot of gray area in development. This didn’t mean it was in absolute terms, but I had seen what worked and what did not. I tended to see things as those bits, on or off. Whether it was design, development, agile philosophies or what have you, I thought I had gathered a list of ways that worked best and those things that caused struggle and rework. If we only followed the path, executed on the known then thing would work out, right?</p><p>On the leadership path, I’ve come to realize how many other paths there are, very few things are black and white. There is more than one way to do something and very few people actually think exactly the same, especially as we reach out to more diverse audiences, and work with those in locations that are very different than ours.</p><figure><img alt="John Coltrane Jazz Musician" src="https://cdn-images-1.medium.com/max/406/1*_9GhAaQkJM_wf5oqaRGT8g.jpeg" /></figure><p>One way I’m trying to be more open-minded is by seeing the value in more than one approach. While I’ve never been a big Jazz music fan I was recently turned on to the difference between two musicians, <a href="https://en.wikipedia.org/wiki/Charles_Mingus"><strong>Charles Mingus Jr</strong></a><strong>. and </strong><a href="https://en.wikipedia.org/wiki/John_Coltrane"><strong>John William Coltrane</strong></a><strong>. </strong>In his early career, Coltrane was all about the regular tones, tempos and chord changes, while Mingus was more about improvisation.</p><p>You can easily notice the different style by listening to <a href="http://John Coltrane - I&#39;ll Wait and Pray - YouTube">I’ll Wait and Pray</a> and then <a href="https://www.youtube.com/watch?v=Rbdx-jR3a8U">The Shoes of the Fisherman’s Wife are Some Jiveass Slippers</a>. Both these artists brought some great fame to Jazz music even though their music could be very different.</p><p>I’m also reminded of the popular Hamilton play by <strong>Lin-Manuel Miranda </strong>where he shows the realization that the <a href="https://www.youtube.com/watch?v=BQ1ZwqaXJaQ">world was big enough for both Hamilton and Burr</a>. They fought so hard against each other, but how much tragedy could have been avoided if they would have just made room for each other’s thoughts and ideas.</p><p>Realizing you have a team of varied personalities with different life experiences, different approaches and different visions can help you realize things aren’t always as black and white as they may seem.</p><h3>Scaling by replication vs true growth</h3><p>Since I thought I had discovered the best or most optimal way of doing things fed by years of watching other leaders and managers do things I had put together in my mind the way I wanted things to work when I arrived there.</p><p>I was talking with a friend who nailed it on the head when he said as UX practitioners we search for the optimal solution or best design. We <a href="https://www.youtube.com/watch?v=gfHcnig8Lo4">hypothesize, test, design</a>, and then retest always striving to get better and ‘delight’ the customer. Because of this, we tend to be perfectionists and not rest, literally, until things are just so. When I say literally, I mean literally. I don’t know how many nights I’ve lost sleep retracing my steps in a discussion on research findings or thinking about ways to support my design choices.</p><p>I’ve come to learn though that trying to just recreate myself 15 times over won’t make a perfect team. Giving copious notes with directions on how everything should be didn’t lead to the optimal formation of a team. It didn’t lead to perfectly synchronized work either.</p><p>What went wrong? In the lines of one of my favorite bands, <a href="https://www.youtube.com/watch?v=MzGnX-MbYE4">People are People</a>. While you can always rely on a compiler creating code or your favorite design tool drawing a box with a flood-filled hex color, people are not cogs that you can set and forget. They’re not extensions of yourself complete with a Vulcan mind-meld that gives them perfect insight to your thoughts, emotions and experiences. Regardless of how well you think you’ve communicated your commander&#39;s intent there always seems to be something that gets lost in translation.</p><h3>My way and when to execute vs discover</h3><p>One thing that is a temptation when you are first a manager is to finally be able to implement or structure a team how you’ve always wanted it.</p><p>Another mistake that I made was to not communicate my thinking very well. For several designers as I brought them on I had been thinking for weeks or months on how these things should be implemented. Some projects may have been designed or research gathered in multiple iterations before. Without proper communication, it’s easy for you to think that someone can just come on and fulfill all the work that’s happened previously.</p><p>What more commonly happens is that people want to feel empowered and want to do the thinking by themselves. They don’t necessarily understand that you may have planned out how to implement a design system for multiple years and have been working with development as they pivoted through multiple technology stacks on the third iteration of your loyalty system.</p><p>This is something I’m still trying to come to terms with, people need to understand what projects are open for discovery and what projects do you need to have people come in and just execute on previous thinking. What do you need to do to communicate all this and get their buy-in seems to be the sticky part? I’m far from perfect on this and am always looking for help in better ways to do this.</p><h3>Code it again rather than build on someone else’s thinking</h3><p>If you’ve ever designed or developed something you’ll recognize the nearly impossible to ignore the pull to redo it yourself. It’s so much easier to design and develop from a fresh clean slate than to wade through the muck to understand existing spaghetti code or multiple iterations of designs. Very few times do people want to code on top of or extend a design. It’s difficult to understand the prior thinking and work and so many times we take the easier path which is to redo everything ourselves.</p><p>The struggle again is to know that given the current constraints in time, money, and other resources how much autonomy and greenfield thinking can people do?</p><h3>Dunning–Kruger effect</h3><p>One of the things that I found about myself I believe holds true for many designers and developers. We tend to be optimists and over-estimate our abilities. We see this over and over again show up when estimating. We over-estimate our ability to deliver something. We tend to forget all the difficulties we’ve had in the past to accomplish something and just boil it down to how long we think it will take us to do the work. We tend to forget all the other people involved, delays, difficulties and things that make our work take longer than initially imagined.</p><p>Because we have this sort of magical ability to create we tend to have an over-inflated evaluation of what we can do. We say things like oh yeah, I can do that, it’s just code. We also see designers for small mom and pop shops design FAANG level experiences for their teams when that organization doesn’t have the talent or resources to deliver the same experience. We’re not all Apple and Google, sometimes we’re just smaller shops who can’t achieve the same experiences as The big guys.</p><p>So we naturally have this tendency to feel that we know a lot about leading and managing individuals and teams. Since we’ve been part of one for so long we tend to think it’s easy and we can pull this off so easily. Rarely do we understand the intricacies of managing software licenses while we’re doing performance reviews during the push to finish up two major mobile applications and a website redesign unless we’ve done that before. We don’t realize the political drama that’s included or the interpersonal challenges that may appear, so we end up thinking managing isn’t all that difficult.</p><p>My amazing UX research counterpart told me about <a href="https://thedecisionlab.com/biases/dunning-kruger-effect/?adw=true&amp;utm_term=dunning%20kruger%20effect&amp;utm_campaign=Biases&amp;utm_medium=ppc&amp;utm_source=adwords&amp;hsa_kw=dunning%20kruger%20effect&amp;hsa_ver=3&amp;hsa_src=g&amp;hsa_mt=e&amp;hsa_cam=1044459117&amp;hsa_tgt=kwd-325492061008&amp;hsa_ad=293079632289&amp;hsa_net=adwords&amp;hsa_grp=51369231356&amp;hsa_acc=8441935193&amp;gclid=Cj0KCQjwnueFBhChARIsAPu3YkRD5cLU9xDCElYdYfqnIsz7j-670TKc0pgbo5SYJfwSyovb_AVRhb4aAuCuEALw_wcB">the Dunning-Kruger Effect</a> a number of years ago and we talked about it as we saw examples of it so often in young and new designers. Sometimes our optimism and confidence don’t quite match our capabilities.</p><blockquote>“<strong>Dunning</strong>-<strong>Kruger effect</strong>, in psychology, a cognitive bias whereby people with limited knowledge or competence in a given intellectual or social domain greatly overestimate their own knowledge or competence in that domain relative to objective criteria or to the performance of their peers or of people in general.”</blockquote><p>Adam Smith talks about the positive and negative aspects of this effect in his book <a href="https://www.amazon.com/Think-Again-Power-Knowing-What/dp/B08HJQHNH9/ref=sr_1_3?dchild=1&amp;gclid=Cj0KCQjwnueFBhChARIsAPu3YkTH4KzAWrYZTfQJyJvD97aHez78gJ44Mip_zJI8jN5zSljafRji3ZUaAq62EALw_wcB&amp;hvadid=492860974525&amp;hvdev=c&amp;hvlocphy=9029711&amp;hvnetw=g&amp;hvqmt=e&amp;hvrand=6711688120188167088&amp;hvtargid=kwd-1063487923426&amp;hydadcr=22567_10346631&amp;keywords=think+again+book+adam+grant&amp;qid=1622830717&amp;sr=8-3">Think Again</a>. It some instances it may lead to over-inflated egos, but at other times it may lead to people working harder to be more than what they believe they are.</p><h3>Imposter Syndrome</h3><p><a href="https://en.wikipedia.org/wiki/Impostor_syndrome">Imposter Syndrome</a> has been talked about a lot in the last few years as people. I never realized how wide-spread this was as I never took a job unless I felt I was qualified. It’s hard to get a job as a .net developer unless you can actually write C# .net code. Every job interview I had as a developer they asked you to actually write code. Likewise, it is difficult to get a designer job without a portfolio of your past design work.</p><p>I can see how this feeling might abound though for less technical jobs where it’s more difficult to prove previous experience or a job that you’re doing for the first time. To me management can feel a bit more like this as it’s more difficult to provide evidence of how you’ve grown other people, managed difficult situations and people.</p><p>This is especially true when moving from an individual contributor to a manager role. You’re going from a technical or creative focus to one more focused on people and it’s easy to see how you might not feel you’re qualified to handle all the different situations.</p><p>In Think Again, Adam Smith says for some people feeling like an imposter can drive people to work harder and more focused. Some people thrive on this situations and others crumble under the pressure. As a manager it’s important that we know our people well enough to help them in either situation.</p><h3>What is transformational</h3><p>As I have been learning to be a better manager, one of the concepts I’ve learned about and even wrote about was on becoming a transformational leader. I’m learning the <a href="https://uxdesign.cc/the-role-of-transformational-leadership-in-design-19ec9372e240">role of transformational leadership in software development and design</a>.</p><p>Looking back on how I wanted to lead my teams I realized how transactional I was trying to be, focused on replicating people within a certain prescribed processes.</p><p>We all are usually under some high pressure when we’re building out teams and trying to establish processes where we may hear things like, “Justin, we need to create 15 new teams in the next three months.” It’s easy at that point to let your natural tendencies take over and the path of least resistance take over. However, it’s precisely at these moments when we need to think about what’s the best way to scale our team and our process.</p><p>It’s at this time we learn how to serve as a role model without doing everything ourselves, but rather model good behavior. We think about how to inspire and motivate rather than just focus on what needs to be done. We show concern for each member of the team and try to communicate and understand their challenges and issues. We intellectually challenge our teams on how to discover the best way themselves rather than an overly prescriptive process to assure everyone is in lock-step.</p><h3>Asking rather than telling</h3><p>One of the biggest challenges I’m working through is to ask/challenge rather than tell. It’s so tempting, especially during those high-pressure, short schedule times to just tell everyone what to do. The challenge then becomes how do I change what I’m talking about in a way that challenges people to think for themselves and discover, possibly with subtle guidance the best way to execute.</p><p>You have to spend just as much time thinking about how to pose questions and on how things get done rather than just what needs to be done.</p><p>I find it’s also good to have those retro moments with yourself to think over how did I just handle that situation. Many times I end up kicking myself because I just went through a situation again that I didn’t behave the best. I fell into the trap of being transactional rather than thinking about how I should be transformational.</p><h3>Being the manager you want -Simon Sinek</h3><p>One of the best ways I’ve learned to stop and think again is from Simon Sinek who gave us the challenge to <a href="https://www.youtube.com/watch?v=Swa34BiA_Xg">be the manager that you would want to have</a>. Mother Teressa said, be the change you wish to see in the world. This is right along that same path, stopping to think about how you guide others to do the work. You’re literally switching your way of thinking from the execution to what helps your team and people transform?</p><h3>Think again, learning from being Wrong</h3><p>As I mentioned before, as a creative or technical person we have a drive to do everything perfect, no bugs, delightful experiences without pits. This built up a perfectionist tendency in my over the years and something I’ve tried to overcome as a manager. It’s not good to expect perfection from your team or expect them to deliver the same way you do.</p><p>An aspect of perfectionism we see is the hesitancy to be wrong. This one has my natural man alarm bells going off that ranks right up there with the “<a href="https://www.forbes.com/sites/sunniegiles/2018/04/30/how-to-fail-faster-and-why-you-should/?sh=555f7729c177">fail fast</a>” thought. It’s very difficult in this high-stress world to revel in, let alone think about being wrong. In Think Again Adam Smith researches a number of people who have flipped this thinking upside down. They truly enjoy being wrong because it helps them learn. He posits the idea that the only way that he can truly be sure he’s doing the right thing is if he’s wrong. It’s only by ruling out the possibilities that don’t work do you keep finding information that supports what is right.</p><p>I ask the designers on my team this all the time, if you don’t test, how do you know you got the design right? We’re not perfect, I mean what are the odds that we get every design exactly right every time? It’s non-existent, right? You have to go through iterations and discovery to test what works and what doesn’t to know if you’ve got a design that’s approaching right or meeting your definition of success whatever that may be for the myriad of different users (personas).</p><h3>I don’t have to do it all, know it all, or be perfect</h3><p>Another thing I’ve learned is that I don’t have to do it all or know it all. I don’t have to be perfect, I don’t have to be the first to volunteer for something, I don’t have the be involved with all the work. As a top performer doing creative or development work, you strive to be the best and involved in important things so we show we’re important and can contribute.</p><p>When we switch over to managing, instead of trying to do all the work ourself, it’s more about how can you align others with that work to give them an opportunity to learn and be successful. I find myself still fighting this impulse even though I’ve managed for a long time. There’s the old saying that if you want something done right you have to do it yourself, but there’s just not enough of you to do everything. You have to rely on others, give them opportunities to learn, and sometimes this learning comes through failing. After all your job now is to build others and not to do all the work yourself.</p><p>I hope some of this has been helpful and informative, I’d love to hear what your experience is going from an individual contributor to managing. What have your experiences been?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*qKOdL9ALPwReoGEv" /><figcaption>The UX Collective donates US$1 for each article we publish. This story contributed to <a href="https://www.wcd.school/">World-Class Designer School</a>: a college-level, tuition-free design school focused on preparing young and talented African designers for the local and international digital product market. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=935bdd131301" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/thinking-again-my-path-from-transactional-to-transformational-935bdd131301">Thinking again: my path from transactional to transformational</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 role of transformational leadership in design]]></title>
            <link>https://uxdesign.cc/the-role-of-transformational-leadership-in-design-19ec9372e240?source=rss-5dc7602b0ba8------2</link>
            <guid isPermaLink="false">https://medium.com/p/19ec9372e240</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Justin Jolley]]></dc:creator>
            <pubDate>Wed, 07 Apr 2021 11:20:14 GMT</pubDate>
            <atom:updated>2021-04-07T11:20:14.236Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Transformational Leadership" src="https://cdn-images-1.medium.com/max/1024/1*AbmlhsVuuCgnmaM5yG7kgw.png" /></figure><p>As my team has been focusing on elevating each team member, we’ve started looking at what makes a good manager and how we can train them.</p><p>My hope is to share with you some of my experience of things that I’ve found that worked well for me. We’ll cover a diverse set of topics from time management, career planning and 1:1’s, to evaluating your team, leadership and strategy in future articles.</p><p>One of the most transformational things for me to learn as a manager has been learning about transformational leadership. Coming up through the ranks as a designer and moving to senior designer, the focus was all on how to get better at everything I did — how to hone my craft and improve each interaction.</p><p>I learned that extending that took me to a transactional management style where I was focused on how many stories I could finish, how many designs I could complete, or how many interviews I could conduct.</p><p>If I were to take a transactional approach, then I would just try to teach everything I did to our team and have them implement everything just as I did. The problem is this only scales so far. If you try to keep that tight a rein on everything, it’s an exhausting and limiting process.</p><p>This is an ongoing process as my natural instinct is to jump in and manage the process. I love to organize and execute on projects as an IC but as a manager I have to try to step back and think of the big picture. It’s difficult because when you’re executing on a project you can see the changes in real-time, but with managing others you don’t have direct control and it’s a long-game, hands-off approach that’s going to work better.</p><p>It also changes from the focus on the projects to the people. Transformational leaders are generally energetic, enthusiastic, and passionate. I stumbled upon an article by VeryWellMind, an online resource that focuses on mental heath and finding balance that focuses on the <a href="https://www.verywellmind.com/what-is-transformational-leadership-2795313">benefits of Transformational Leadership</a>. “Not only are these leaders concerned and involved in the process; they are also focused on <a href="https://www.verywellmind.com/what-is-democratic-leadership-2795315">helping every member of the group succeed</a> as well.”</p><p>This also brings up another skill needed for this type of management, instead of orchestrating each movement it becomes more of a democratic style of leadership. I found that for me this can feel like you’re losing some control, but you end up with greater creativity as you partner with people in their growth and exploration of a project.</p><h3>Checklist</h3><p>Before we jump into this learning, I want to make it clear that what I’m trying to do is equip you with the tools that are commonly found amongst good leaders and managers. This isn’t a checklist that as soon as you complete it, poof, you are now a certified manager. Sure, there are management courses, degrees and certifications you can take to help prepare you, but you really won’t become a manager until you are one and struggle through your own path to become a manager.</p><p>Transformational Leadership is very applicable to UX and UX Management. The field is rife with various methodologies, processes and tools. What passes for UX practice in one company or even one department of a company can be vastly different from another.</p><p>Because of this, it’s important to decide on and train on your process, document it and train on it; then allow each member to practice it as it begins to make sense to them. As a manager, you can’t participate in every empathy mapping, stakeholder or customer interview, design exploration or interaction with every team unless you have a very small organization. Then even if you could it’s probably not a good idea to involve yourself at that level.</p><p>I’ve worked for various companies from the only UX person to a member of a global organization with studios around the world. If you are going to scale your practice and organization, you have to learn to lead from a transformational level in your UX rather than a transactional.</p><h3>What is Transformational Leadership</h3><p><strong>Transformational leadership, </strong>according to the Business Dictionary, is “a theory of leadership where a leader works with teams to identify needed change, creating a vision to guide the change through inspiration, and executing the change in tandem with committed members of a group”.</p><p>The best way I can explain it is moving from a process where you detail out each step of how to accomplish a task to where you teach people correct principle, help them know your intent/vision and then allow them to find their way through it. You can coach but not micro-manage. You provide direction but don’t supply all the answers.</p><p>Think of leaders or managers you’ve had in the past who have inspired you or sparked an interest where you dive into a topic with all you have and possibly spend much more time on it that if someone instructed you in every action. That is transformational leadership. They inspire, not insist; they encourage, not provide the exact path; they give commanders intent, instead of providing all the answers. It’s really allowing people to surprise you and come up with solutions that are beyond what you thought of and hoped for.</p><p>A number of years ago I saw a video that I loved right away and have referred to over the years. It was about what people needed to be engaged in a job. The top three answers were autonomy, mastery and purpose. Transformational leadership gives people autonomy over their specific jobs and allows for much more free exploration of their role and day-to-day actions.</p><p>Transformational leaders generally function under four distinct behaviors, also known as the four I’s. These behaviors are inspirational motivation, idealized influence, intellectual stimulation, individualized consideration. Let’s take a deeper look at each one:</p><h3>Components of Transformational Leadership</h3><blockquote><strong>Idealized Influence (II)</strong> — the leader serves as an ideal role model for followers; the leader “walks the talk,” and is admired for this. A transformational leader embodies the qualities that he/she wants in his/her team. In this case, the followers see the leader as a model to emulate. For the followers, it is easy to believe and trust in a transformational leader.</blockquote><figure><img alt="Google co-founder Sergey Brin. Source: Emaze" src="https://cdn-images-1.medium.com/max/1024/1*Ul4Bi0ien_HT6gxIJxMz_g.png" /><figcaption><em>Google co-founder Sergey Brin. Source: </em><a href="https://www.emaze.com/@AZFRRQWF"><em>Emaze</em></a></figcaption></figure><p>For someone to hold you in esteem enough to allow you to manage them, you need to be someone they can look up to. Many times this is through them being able to do the things they talk about. I’ve had leaders who were unable to perform the technical things that were a part of the daily job and their credibility was never sufficiently built to allow for respect to develop.</p><p>To manage or lead you have to be able to show that you have the knowledge and ability to model whatever you’re trying to teach.</p><p>Google co-founders, Larry Page and Sergey Brin were these type of leaders. While Google seems to have struggle as of late, their early years were marked by examples of how they wanted to <a href="https://iveybusinessjournal.com/publication/distributed-leadership-at-google-lessons-from-the-billion-dollar-brand/">change the world for the good and empower people</a> rather than just make money.</p><blockquote><strong>Inspirational Motivation (IM)</strong> — Transformational leaders have the ability to inspire and motivate followers through having a vision and presenting that vision. Combined, these first two I’s are what constitute the transformational leader’s charisma. A transformational leader manages to inspire the followers easily with clarity. The transformational leader convinces the followers with simple and easy-to-understand words, as well as with their own image.</blockquote><figure><img alt="Simon Sinek" src="https://cdn-images-1.medium.com/max/530/1*qsKgf7gteQiiZZ2KMKp3BA.jpeg" /><figcaption>Simon Sinek Source: Wikipedia</figcaption></figure><p>Think back to a coach, teacher or some other kind of leader who inspired you and was able to encourage and invite you to do things rather than force and use a carrot or stick? If so, then you’ve met someone who used aspects of Inspirational Motivation.</p><p>One of Simon’s quotes that I love is, “<a href="https://www.youtube.com/watch?v=Swa34BiA_Xg">be the leader you wish you had</a>”. This is something that I try to remember when I have a bad day or struggle with leadership that I’ve had.</p><p>In the UX field this could be a string of people from Jakob Nielsen to Jared Spool, Jeff Gothelf to Steve Krugg and Simon Sinek to Brene Brown and many others.</p><p>This can even be someone you work with. I have a great counterpart who leaders our user research where we worked together on a process for testing the effectiveness of an experience or feature redesign. We were working well together and found ourselves waking up each morning, eager to check on the data and chat about it. Is was very motivational and infectious to work this way.</p><blockquote><strong>Individualized Consideration (IC)</strong> — Transformational leaders demonstrate genuine concern for the needs and feelings of followers and help them self-actualize. This personal attention to each follower assists in developing trust among the organization’s members and their authority figure(s).</blockquote><figure><img alt="Sir Richard Branson" src="https://cdn-images-1.medium.com/max/1024/1*YKd4fO8AeuTz8HFB8zpbSw.jpeg" /><figcaption>Sir Richard Branson Source: Wikipedia</figcaption></figure><p>I’ve had a number of leaders and even a few managers that I felt excelled in the Individualized Consideration realm. Many times managers do not bother to be involved or they feign interest to try to build a relationship. However, there are those who truly connect with those they manage.</p><p>In order to build the trust needed, someone must be vulnerable enough to ask for help. You have to connect with them in this manner for the trust to exist.</p><p>One great example I’ve seen of this is Sir Richard Branson of Virgin companies. He’s a great champion of his people and is noted as saying, “<a href="http://that by taking care of employees at Virgin that everything else will take care of itself,">that by taking care of employees at Virgin that everything else will take care of itself</a>.”</p><p>At Virgin, a great leader must:</p><ul><li>Praise employees instead of criticizing them.</li><li>Genuinely love all people from the cleaning lady to the senior executives.</li><li>Be a great listener who not only hears the recommendations from employees but acts upon them.</li></ul><blockquote><strong>Intellectual Stimulation (IS)</strong> — the leader challenges followers to be innovative and creative, they encourage their followers to challenge the status quo. A common misunderstanding is that transformational leaders are “soft,” but the truth is that they constantly challenge followers to higher levels of performance.Elements of Transformational Leadership</blockquote><figure><img alt="Brene Brown" src="https://cdn-images-1.medium.com/max/798/1*H4dkdIUVKz2ggYowlYhIHg.jpeg" /><figcaption>Brene Brown Source: Wikipedia</figcaption></figure><p>I can still remember a teacher from the 4th grade that encouraged me to read fantasy books. She inspired something that sparked the fire in me to have a love of reading and writing that’s served me throughout my life.</p><p>I can also remember directors that taught me elements of coding that inspired me to learn more about software design patterns. Learning about MVC patterns helped me know how to best work with developers as I would design and implement the HTML and CSS for the front end.</p><p>The instances go on and on where I’ve had people that have stimulated me intellectually to learn all that I could about a topic or technology.</p><p>Brene Brown is a great example of this right now for me. In her Book <a href="https://daretolead.brenebrown.com/">Dare to Lead</a>, she has chapter after chapter that has given me insight into my own life and how it affects how I show up as a person and manager.</p><blockquote>“Leadership is not about titles or the corner office. It’s about the willingness to step up, put yourself out there, and lean into courage. The world is desperate for braver leaders. It’s time for all of us to step up.” -Brene Brown</blockquote><h3>How this Plays Out</h3><p>So how do we learn to become more transformational? Here is a list with some examples of how we can practice being transformational in our organizations and UX departments/teams.</p><p>Approach situations with a way in mind to encourage rather than give orders. This is very difficult at times when you may receive a mandate from three levels above you and you don’t really have a choice with how or when something gets done. This is something that is a challenge, but am learning how to do better.</p><ul><li>Focus on what intrinsically motivates people and focus on developing them individually</li><li>Highlighting priorities that are important to the company, you and the customer</li><li>Promoting co-creation and cooperation with feature teams</li><li>Using insights and persuasive story telling based on data</li></ul><p>Most companies have a corporate standard or philosophy they try to live by. We can make sure as leaders we help facilitate these as well as others like inclusive design or avoiding dark practices that can adversely affect those who use experiences we design.</p><ul><li>Raise awareness of moral and ethical standards</li><li>Help develop moral maturity in others</li><li>Creating an ethical climate (share values, high ethical standards)</li><li>Encouraging team members to look beyond their self-interests to the needs of others and groups</li><li>Appeal to the ideals of followers</li><li>Being authentic, consistent in their practice of UX</li></ul><p>As a manager it’s easy to have one process and try to follow that for each person, but that rarely works. Many times you need to adjust your approach to match the needs as well as the emotional and mental levels of those you lead. The more times you can find to provide choice based on their needs and interests the better off you’ll be.</p><p>I have a great friend who always said his father’s parenting style was to find out what his children wanted and then order them to do it. This might seem like the opposite of freedom, but then both win, right?</p><ul><li>Providing individual coaching and mentoring for team members</li><li>Allowing freedom of choice for team members</li></ul><p>According to <a href="https://hbr.org/2017/05/what-the-best-transformational-leaders-do">Harvard Business Review</a>, “Companies that claim to be ‘transforming’ seem to be everywhere. But when you look more deeply into whether those organizations are truly redefining what they are and what they do, stories of successful change efforts are exceptionally rare.</p><p>Becoming transformational as an organization is more difficult than doing it as an individual as we’ve seen by many of the leading companies. They did find a number of characteristics of leaders within these organizations that helped them achieve greater earnings and success.</p><p>These characteristics include:</p><ul><li>They don’t have insider knowledge of how things have always been to serve as a crutch. Instead they find new ways to be successful.</li><li>They don’t go down just one path, they try to change the core of the business while growing new areas.</li><li>They use culture changes going on in the org to enact their changes, trying to take more risks and exploring opportunities.</li><li>They create powerful narratives around future changes and effectively communicate them to the company.</li><li>They create a road map to help people understand how the organization will get there.</li></ul><h3>Put it Into Practice</h3><p>Let’s put what we’ve learned into practice. Here are a few scenarios. Think how you would respond to each of these in a transactional manner and then in a transformational manner.</p><p><strong>Scenario:</strong> Jim, a member of your team is having a difficult time following the process to check-in some work that he’s working on. How do you handle this situation?</p><p><em>Do you take him to task about following the process or do you show him the reasoning behind why it’s important to check-in work and let him come to the realization of the effects it has if he doesn’t follow the process?</em></p><p><strong>Scenario: </strong>Candice, a member of your team has a conflict with whether to skip a review of her work in order to meet a deadline or make sure the experience that is delivered provides value to the customer and definition of done. How would you coach her?</p><p><em>In your 1:1 with Candice do you bring up the fact that she hasn’t done a review in front of the team or do you show the team something you’ve been working on and model how to get a review of your work?</em></p><p><strong>Scenario:</strong> Steven, a member of your team is struggling with working remotely and finding a good work/life balance. How would you manage this interaction?</p><p>Do you try to understand his needs and then come up with a solution and to help him or do we ask him to communicate what he needs and what his solution would be given all the needs of the company, his teams as well as his needs.</p><p><strong>Scenario: </strong>John, a member of your team is looking at a process that you’ve always used on your team, but he thinks it could be done better. How would you interact with him?</p><p>Do we simply take everything a team member submits or complains about or do we help them understand all the issues and then see what solution they can come up with that takes into account everyone’s needs?</p><h3>Takeaways</h3><p>I’ve been to trainings and conferences where they provide a task to do after the training to put into action what you’ve learned. Let’s try that now. In the next few days or weeks pick a few of these transformational activities to try with your team(s).</p><ul><li>Communicate expectations to your team</li><li>Invest in your relationship with a team member</li><li>Lead on a project by example</li><li>Make others on your team feel safe to speak up, create the space for it</li><li>Be a patient and purposeful teacher on a topic</li><li>Challenge someone on your team to think differently on a new topic</li><li>Provide continuous but not over-bearing feedback to a team member</li><li>Show how you are accountable to others within your organization</li><li>Measure and reward team members performance</li><li>Connect each member of your team with a project that challenges them</li><li>Ask questions and seek the counsel from members of your team</li><li>Exude a positive attitude and energy to the groups you interact with</li><li>Make decisions and explain them to those they affect</li><li>Provide opportunities for team members to figure things out</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*G3U8mqkCZcsSvRVp" /><figcaption>The UX Collective donates US$1 for each article published on 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=19ec9372e240" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-role-of-transformational-leadership-in-design-19ec9372e240">The role of transformational leadership in design</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[Heuristic analysis is now “Experience Walkthrough”]]></title>
            <link>https://uxdesign.cc/heuristic-analysis-is-now-experience-walkthrough-141349c69d90?source=rss-5dc7602b0ba8------2</link>
            <guid isPermaLink="false">https://medium.com/p/141349c69d90</guid>
            <category><![CDATA[experience-walkthrough]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[heuristic-analysis]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Justin Jolley]]></dc:creator>
            <pubDate>Sat, 11 Jul 2020 22:33:04 GMT</pubDate>
            <atom:updated>2020-07-13T18:49:19.184Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Chicken Sexing" src="https://cdn-images-1.medium.com/max/1024/1*Hu2XJ8f8pwnlbMqm4dtRag.jpeg" /></figure><h3>Chicken Sexing</h3><p>I kid you not, this is a thing. There is a very valuable skill that allows someone to <a href="https://en.wikipedia.org/wiki/Chick_sexing">separate female and male chicks soon after birth</a>. The mystery is that when you look at the back end of a chick, some people just know which are female. It has proven nearly impossible to articulate why, so the Japanese figured out how to teach this inarticulable skill. The student would pick up a chick, examine its rear, and toss it into a bin. The master would then say ‘yes’ or ‘no’ based on his historically, often correct intuition. After a while, the student’s brain was trained to the masters level without quite understanding why.</p><p>Sometimes performing a heuristic analysis can seem like chicken sexing. My goal is to take some of the mystery out of practice and discussion and make it more easily articulated.</p><p>Remember, these words and phrases are not magical, canonical or holy. In fact take them, and change them, as the immortal Paula Abdul was so fond of saying, “Make them your own!” The point is to evaluate how you talk with your teams and people in your company. Then determine if you can make it more inclusive, co-operative and reduce the barriers for everyone to participate in the design of the experience.</p><h3>Heuristic Analysis</h3><p>This is one of my favorites. I always feel like I’m an important scientist when I get to talk about these. Like I have a white coat, wire-rimmed glasses and a clipboard methodically going over a design. Occasionally I noddle silently with disappointed eyes and a disapproving nod. So smug, like how could you have been so unaware? Did you really not know that there isn’t good proximity between that label and the input? I can see the whole telenovela worthy scene playing out in my head, can’t you? Egads, I’ve created a monster!</p><p>I think that’s part of the problem though. For years we’ve been getting these little dopamine sparks from sounding important and having “the” answer. The science and experience behind people who can do this effectively is a real skill, but in reality, we’re just walking through the suggested experience to see if it is a good one. Anyone can learn this with an open mindset, it’s not a noble birthright for the elect few. I can see it now, a Harry Potteresqe sorting hat…Slytherin…Hufflepuff…Heuristic Analyst! (The entire crowd erupts in hurrahs.)</p><p>We have mental models and best practices that have been shown to be most beneficial. People who have experienced testing things one way or relied on the feedback from the experts like NNg or Beymard can go a long way to calling out problematic designs. I can’t overvalue the great insight they have brought to our industry.This exploration doesn’t have to sound so complicated though. The approach can be much more humble, “you know, I’ve found that if we put the button next to the field where people interact with it they have an easier time using the application.”</p><p>We can think of the rules we use around the heuristic analysis and reframe our wording to be more inclusive and approachable.</p><p>This practice of heuristic analysis has been described as, “A detailed analysis of a product that highlights good and bad practices, using known interaction design principles as guidelines. Helps you visualize the current state of the product in terms of usability, efficiency, and effectiveness of the experience.”</p><h3>Walk Me Through It</h3><p>A good first step may be to use something like <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">NNg’s 10 heuristics</a>. Now there are dozens of others, but this is a good first step when working with new teams. Let’s deconstruct the first heuristic or guideline in a more user-friendly and co-creative way.</p><blockquote>#1: Visibility of system status</blockquote><blockquote>“The system should always keep users informed about what is going on, through appropriate feedback within a reasonable time.”</blockquote><p>A perfect illustration of this can be seen in this video from NNg on the <a href="https://youtu.be/cTtc90jCULU">Visibility of System Status</a>. Notice at the front how the complex jargon can be a bit confusing and even difficult to get out and effectively communicate what this is. However, when the focus switches to giving common examples in plain words, you start to understand where you’ve seen examples of this before. An example might be like in elevators, battery indicators or even button clicks.</p><p>Another great examples of this is the null state. When you are using an app/site that lets you create things, bookings, events, playlists, emails, etc. there is usually a starting or null state where you have an inbox which lists all your items. It’s good practice to help them along and have interactions where they are lead through creating their first widget.</p><p>You could say something like, “If I’m walking through this experience for the first time, I might not know how to create my first widget. What do you think about giving them some hints on how to do that?”</p><p>“I know I find it useful when I’m using a site to have clues that help me understand what’s going on and what I need to do.”</p><p>Now you might know the best way and even have a component in your design system, but it’s about co-creation too. Who knows when someone will have the next brilliant idea to upgrade or add a new feature to your component. The point is you’re working with your team to gather insight, have them take part in the discovery and do it in a way that uses human terms.</p><p>What’s best is that you didn’t have to talk about heuristics and design principles to make yourself sound all-knowing and like no one else knows anything about doing good design. The approach is inquisitive, like you’re all working together to find a good solution to the problem.</p><h3>You’re Not Alone, Say It One More Time, You’re Not Alone!</h3><p>What’s even better than going through and doing your “expert analysis” based on “heuristics” is walking through the feature as a team. Sometimes allowing the designer or developer to take a step back and walk through as a user or <a href="https://medium.com/@amiwebguy/personas-are-now-called-roles-4bc9e7f5a99">specific role</a>, you can get enough mental distance to have them say “oh yeah, I forgot x” or “how would I do y”.</p><p>Before we take the next step of testing with other users we can practice disassociating ourselves from knowing too much or being too close to the problem/solution. This is why we’re always told, “You are not the user.” You know too much and are too close to the situation. With a little practice though you can become better at putting yourself in the customers shoes. You’ll never be a perfect substitute for actual user testing, don’t fall into that trap, but you can become better at detecting issues before you show your work to the customer.</p><p>Something that may be helpful is to put together a set of rules based on your favorite heuristics that you can walk through as a team.</p><p><em>Did we check for the first time use?</em></p><p><em>Does a user know how to create a new widget?</em></p><p><em>Does the user have a good example in their real world where they use something like this?</em></p><p><em>Is there anything about this experience that feels like I lost control or couldn’t do something I wanted to do?</em></p><p><em>Do all the colors and components match the rest of the site or app? Having this conversation with PO’s and QA’s can be very helpful as they can be great advocates in the search to root out inconsistencies.</em></p><p><em>Did I get an error during the experience that we could have prevented or helped them through more efficiently?</em></p><p><em>Did we give our customers a way to figure out how to complete a task without having to remember an important detail?</em></p><p><em>Is the experience too cluttered or confusing or are there too many steps?</em></p><p><em>If an error happens how do we think the customer will feel and how can we help them get back on track?</em></p><p><em>What kinds of information or tools would be useful for our customers when they’re using this feature?</em></p><p>Having a checklist (either mental, paper or digital) with these types of questions that everyone can ask is an approachable way to have everyone do an experience walk-through. Not only are you enlisting others in the effort to fix issues, but you’re maturing the team’s capability by knowing what to look for without expecting them to be a UX mastermind.</p><p>Next Up: Competitive Analysis/Audit is now Competition Experience Comparison</p><h3>Competitive Analysis/Audit is Now Competition Experience Comparison</h3><p>My first though was something like competition snooping or corporate espionage; but in the end I’ve come back to Competition Experience Comparison.</p><p>Competitive makes it sound like you’re signing up for a race or possibly a soccer competition where the moms bring you Capri Sun’s and those little slices of oranges. An analysis feels like you’ve got lab work you’re going to have to wait for and even worse and audit makes it feel like the IRS (tax guys) are hot on your trail. None of those quite capture the fun that can be had during one of these exercises.</p><p>The more structured definition talks about, “a comprehensive analysis of competitor products that maps out their existing features in a comparable way. Helps you understand industry standards and identify opportunities to innovate in a given area.”</p><p>I have to admit this isn’t filled with a lot of jargon or techie phrases and does a good job at describing what happens during a competitive audit.</p><p>Experience Walkthroughs (formerly Competitive Analysis) are one of my favorite things to explore and I’ve provided some insight into doing an enterprise level competitive analysis that you may find useful.</p><p>Continue reading…(coming soon)</p><h3>Articles in this series</h3><p>This series seeks to reexamine the approach and vocabulary of<strong> UX design methodologies</strong> and translate them into <strong>experience practices</strong> (minus the UX and design terms) that help us to be more inclusive, align with our teams better and interact with the full spectrum of humans as we design experiences.</p><h3><a href="https://uxdesign.cc/how-to-discuss-experience-design-and-not-sound-like-an-arrogant-arse-b4dc76312164">How to discuss experience design and not sound like an arrogant arse</a></h3><p>Sometimes we struggle connecting with our teams and it may just be our approach and interaction.</p><h3><a href="https://uxdesign.cc/personas-are-now-called-roles-4bc9e7f5a99">Personas are now called “Experience Roles”</a></h3><p>Personas really look at the hats or roles that people play and the things they do that make them different from others.</p><h3><a href="https://uxdesign.cc/taxonomies-are-now-experience-organizations-1303643aa7ee">Taxonomies are now “Experience Organizations”</a></h3><p>In life, it’s important to learn how to organize things. Let’s look at how we can do this with our teams.</p><h3><a href="https://uxdesign.cc/is-hx-just-doing-ux-right-or-is-it-more-d7690063307e">Is HX simply about doing UX right, or is it more?</a></h3><p>Human experience design is a more holistic approach to experience design.</p><h3><a href="https://uxdesign.cc/how-co-designing-can-reduce-your-rejection-and-stress-levels-as-a-uxer-6b905a7d6a86">How co-designing can reduce your rejection and stress levels</a></h3><p>You’re not a magician, cowboy, ninja or superhero; stop trying to be one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*JMpR18oDaESs9L7X" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://twitter.com/uxminaspretas">UX Para Minas Pretas</a> (UX For Black Women), a Brazilian organization focused on promoting equity of Black women in the tech industry through initiatives of action, empowerment, and knowledge sharing. 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=141349c69d90" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/heuristic-analysis-is-now-experience-walkthrough-141349c69d90">Heuristic analysis is now “Experience Walkthrough”</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[Taxonomies are now “Experience Organizations”]]></title>
            <link>https://uxdesign.cc/taxonomies-are-now-experience-organizations-1303643aa7ee?source=rss-5dc7602b0ba8------2</link>
            <guid isPermaLink="false">https://medium.com/p/1303643aa7ee</guid>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[taxonomy]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Justin Jolley]]></dc:creator>
            <pubDate>Fri, 10 Jul 2020 11:42:20 GMT</pubDate>
            <atom:updated>2020-07-12T05:15:14.191Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Cows and organizing" src="https://cdn-images-1.medium.com/max/943/1*EnlsXHnfdRsU-K48I5Qo4Q.jpeg" /></figure><p>In life, it’s important to learn how to organize things. It’s important to know which type of animals produce milk and which ones do not. From a very early age we are taught how to differentiate things, organize them, create categories, tag them and all manner of ways to keep things straight. Doing this work can be called working with taxonomies, information architecture, or simply experience organizations.</p><p>As we start to look at how we talk about various experience design practices(methodologies) we can take a step back and rethink how we approach them to make sure we are really connecting with our teams and those around us on a <a href="https://uxdesign.cc/is-hx-just-doing-ux-right-or-is-it-more-d7690063307e">human level</a> and do it <a href="https://uxdesign.cc/how-to-discuss-experience-design-and-not-sound-like-an-arrogant-arse-b4dc76312164">without sounding like a know-it-all</a>.</p><p>Remember, these words and phrases are not magical, canonical or holy. In fact take them, and change them, as the immortal Paula Abdul was so fond of saying, “Make them your own!” The point is to evaluate how you talk with your teams and people in your company. Then determine if you can make it more inclusive, co-operative and reduce the barriers for everyone to participate in the design of the experience.</p><p>One of the definitions I’ve heard for taxonomies is, “an exploration around multiple ways to categorize content and data: topics in a news site, product categories in an ecommerce etc. Assists designers in defining the content structure to support the user’s and the organization’s goals.”</p><p>That one’s still a bit rough, how about this one, “Taxonomies are <em>systems</em> used to classify and organize things. So yes, when we talk about <a href="https://www.uxbooth.com/articles/introduction-to-taxonomies/">taxonomies</a> in the animal kingdom (remember <a href="https://www.mnemonic-device.com/biology/taxonomy/domain-kingdom-phylum-class-order-family-genus-species/">Kings Play Chess On Fine Glass Stools</a>?), we are talking about the same type of taxonomy that gets used to organize a digital property.”</p><h3>Test #1: Spelling</h3><p>Here’s the first clue; if you have to stop and think about how to spell a method or practice then there’s probably a better way to make this exercise more approachable for people. Granted, I’m not the best speller in the world, but for me this falls under the don’t make me think category. If I have to stop and think about how to spell the word then why not just go with something simpler to start with?</p><p>Of course I’ve always subscribed to the Mark Twain line of thinking in terms of spelling when he says, “Anyone who can only think of one way to spell a word obviously lacks imagination.” You may be gifted with the ability to spell all the hard words and ascend to the spelling bee championships, if so kudos!</p><figure><img alt="“Anyone who can only think of one way to spell a word obviously lacks imagination.”" src="https://cdn-images-1.medium.com/max/850/1*qN-_oecJCRgsH_qMa5Ygnw.jpeg" /></figure><h3>Test #2: Mental Model of the Word</h3><p>If you have to try to remember the word representing the work and the meaning of it, then that’s another case where we could probably simplify it. Taxonomies fall into this realm for me as it’s not a word I use naturally or have a mental association with. So when I want to talk about taxonomies, I have to stop and try to recall some association with the word and the meaning.</p><p>In his book, <a href="http://sensible.com/">Don’t Make Me Think</a>, Steve Krugg talks about this as a test if a design is good or not. I think Steve gives a great translation in the title. Instead of talking about the science about cognitive load and over-working the user’s memory he just says, “don’t make me think.” If the users have to stop and think about what to do with your experience, then something isn’t right.</p><p>Think of the cases where you’ve had an experience in real life or the digital realm and it was seamless; you didn’t think about it. It just happened! This is what we’re aiming for. I know Amazon get’s all the credit, but there have been several times where I’ve ordered something on Amazon and thought to myself, “did I just order that, it went too fast?”</p><h3>Specificity</h3><p>In all honesty I think both Taxonomies and Experience Organizations are too general and can benefit from having some additional clarity. We can talk about experience organization of our navigation or the organization of our product categories, this helps us provide more clarity into what we’re talking about focusing on.</p><p>This one is more of a struggle as the original word is both vague and specific. Taxonomies talk about the specific structure of the information yet are vague — as it doesn’t focus on any specific area within your app/site. I’m hoping this wording will evolve as we start to have these discussions with our teams more.</p><h3>What About IA?</h3><p>This is not AI or Artificial Intelligence where robots become our masters. This is IA, Information Architecture. Taxonomies are a part of the overall information architecture of a site or application.</p><p>Think of an IA as your house. The taxonomy helps identify which pieces of furniture belong in each room. After all, we wouldn’t want our oven in our bedroom or our bed in the bathroom. So there is a taxonomy or structure to the things that belong in each area (taxonomy) and a way that they are all connected and navigated through (IA). There is a hierarchy and all the pieces fit together.</p><p>A more relevant example in the digital world might be around an electronics store. Electronics can be categorized as home, auto and personal. Then further classified by size, color, price or style. These are all how we mentally and physically organize the pieces in our minds. The information architecture then becomes how do we use all that structure?</p><p>One of the sites that’s helped me with this is actually a .gov site, about the <a href="https://www.usability.gov/what-and-why/information-architecture.html">Information Architecture Basics</a>. Big shocker I know.</p><p>They have you think about four main areas that make up the information architecture of your site/app.</p><p>The first one is what we’ve been talking about… the taxonomy, or in their words, schemes and structures. In a scientific world these make sense, but to the rest of the world a scheme seems like something criminal and structure is something a construction company handles. That’s why I’m going with experience organization…of our menus and navigations.</p><ul><li><strong>Organization </strong><a href="https://www.usability.gov/how-to-and-tools/methods/organization-schemes.html"><strong>Schemes</strong></a><strong> and </strong><a href="https://www.usability.gov/how-to-and-tools/methods/organization-structures.html"><strong>Structures</strong></a>: How you categorize and structure information</li><li><strong>Labeling Systems</strong>: How you represent information</li><li><strong>Navigation Systems</strong>: How users browse or move through information</li><li><strong>Search Systems</strong>: How users look for information</li></ul><p>Labeling is also an important part of the information architecture or structure of the experience. We have to remember not to use too many acronyms, industry terms and abbreviations that those not in the know or new to the industry might not understand.</p><p>We should strive to make sure the labeling on forms and information is clear and uses as few words as possible.</p><p>Navigation is so important and why we test our taxonomies or experience organizations. Many times we structure the navigation by what makes sense to our business and product groups rather than to customers. Just like we know too much to do user testing, the mental model and organization of products in our minds usually don’t match those of the general public.</p><p>Search is usually the first interaction or last ditch effort to try to find something; so it’s vital to have a good search in our systems. Search helps us bypass all the structure and organization to get to just what we’re looking for. It’s a good idea to review your search logs to find out just how people are searching for your products and services. What words or phrases have stuck in their minds to help them associate ties to them?</p><h3>So Open Our Minds Fall Out</h3><p>My goal is not to “dumb everything down” or erode the advancements and work that have gone into our industry. I remember in college hearing the saying that we should have an open mind, but not so open that our minds fall out.</p><p>In fact, in the back of my mind I keep hearing this voice say, “make it clear that we don’t want to eliminate the technical jargon.” A surgeon, scientist or other technical person needs to be able to speak to their community with these technical terms. They just need that translation unit to be able to communicate to the rest of the world. We need to continue the maturation and rigor around our work within the right spheres;- but we need to be more inclusive and co-creative in order to be successful. In many cases that means translating our approaches, thoughts and words to something that can be consumed by everyone involved in the project.</p><p>Remember, the whole premise of this series is to help us talk to groups of people in a more human way to achieve our desired goals as a team.</p><h3>Co-Creation and Career Growth</h3><p>I offer up this transformation to co-creation as I’ve heard so many stories of <a href="https://uxdesign.cc/how-co-designing-can-reduce-your-rejection-and-stress-levels-as-a-uxer-6b905a7d6a86">rejection, frustration and disillusionment</a> that I wanted to provide hope. How do you move to a <a href="https://uxdesign.cc/is-hx-just-doing-ux-right-or-is-it-more-d7690063307e">more inclusive and human experience</a>?</p><blockquote><strong>“Design may have its greatest impact when it’s taken out of the hands of designers and put into the hands of everyone”.</strong></blockquote><p>Tim Brown, the founder of IDEO has a saying I’m growing to love and question at the same time. He said, “Design may have its greatest impact when it’s taken out of the hands of designers and put into the hands of everyone”.</p><p>As I’ve said, this sounds like you’re bringing your world down all around you (and we have enough of that going on already), but it’s really the opposite. It’s allowing you to grow in your career. It’s no longer just about having a hammer (UX and Visual Design) and screwdriver (UX Research), but about <strong>facilitating the solving of problems</strong>. Customers need solutions, not designs; and companies need to sell products, not just data and interfaces.</p><p>You’re also growing beyond an individual contributor and becoming more of a facilitator. You start to care about all the parts of the process and not just the research and design. If you want to advance in your career this is the path you need to step into. You’ll start to move up from individual contributor as a designer or researcher and start to lead and manager your teams. The next steps above that though are more concerned with the entire operation as you start to move from simple transactional leadership (short-term tasks) to transformational leadership (long-term vision).</p><p>You include more people, and get more insight and participation than ever before when you have this approach. There’s less infighting and frustration, fewer silos and happier people. This all leads to better products and happier customers who are having their needs and wants met more often.</p><p>Up Next: <a href="https://uxdesign.cc/heuristic-analysis-is-now-experience-walkthrough-141349c69d90">Heuristic Analysis is now Experience Walkthrough</a></p><p>This is one of my favorites. I always feel like I’m an important scientist when I get to talk about these. Like I have a white coat, wire-rimmed glasses and a clipboard methodically going over a design. Occasionally I noddle silently with disappointed eyes and a disapproving nod. So smug, like how could you have been so unaware? Did you really not know that there isn’t good proximity between that label and the input? I can see the whole telenovela worthy scene playing out in my head, can’t you? Egads, I’ve created a monster!</p><p><a href="https://uxdesign.cc/heuristic-analysis-is-now-experience-walkthrough-141349c69d90">Continue reading…</a></p><h3>Articles in this series</h3><p>This series seeks to reexamine the approach and vocabulary of<strong> UX design methodologies</strong> and translate them into <strong>experience practices</strong> (minus the UX and design terms) that help us to be more inclusive, align with our teams better and interact with the full spectrum of humans as we design experiences.</p><h3><a href="https://uxdesign.cc/how-to-discuss-experience-design-and-not-sound-like-an-arrogant-arse-b4dc76312164">How to discuss experience design and not sound like an arrogant arse</a></h3><p>Sometimes we struggle connecting with our teams and it may just be our approach and interaction.</p><h3><a href="https://uxdesign.cc/personas-are-now-called-roles-4bc9e7f5a99">Personas are now called “Experience Roles”</a></h3><p>Personas really look at the hats or roles that people play and the things they do that make them different from others.</p><h3><a href="https://uxdesign.cc/taxonomies-are-now-experience-organizations-1303643aa7ee">Taxonomies are now “Experience Organizations”</a></h3><p>In life, it’s important to learn how to organize things. Let’s look at how we can do this with our teams.</p><h3><a href="https://uxdesign.cc/is-hx-just-doing-ux-right-or-is-it-more-d7690063307e">Is HX simply about doing UX right, or is it more?</a></h3><p>Human experience design is a more holistic approach to experience design.</p><h3><a href="https://uxdesign.cc/how-co-designing-can-reduce-your-rejection-and-stress-levels-as-a-uxer-6b905a7d6a86">How co-designing can reduce your rejection and stress levels</a></h3><p>You’re not a magician, cowboy, ninja or superhero; stop trying to be one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*6mOmE4hll2n4jq5V" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://twitter.com/uxminaspretas">UX Para Minas Pretas</a> (UX For Black Women), a Brazilian organization focused on promoting equity of Black women in the tech industry through initiatives of action, empowerment, and knowledge sharing. 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=1303643aa7ee" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/taxonomies-are-now-experience-organizations-1303643aa7ee">Taxonomies are now “Experience Organizations”</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[Personas are now called “Roles”]]></title>
            <link>https://uxdesign.cc/personas-are-now-called-roles-4bc9e7f5a99?source=rss-5dc7602b0ba8------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bc9e7f5a99</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[personas]]></category>
            <dc:creator><![CDATA[Justin Jolley]]></dc:creator>
            <pubDate>Thu, 09 Jul 2020 11:11:46 GMT</pubDate>
            <atom:updated>2020-07-10T13:48:44.561Z</atom:updated>
            <content:encoded><![CDATA[<h3>Personas are now “Experience Roles”</h3><figure><img alt="Hats, roles and personas" src="https://cdn-images-1.medium.com/max/1024/1*_54iGneAGQ3oJ4-X-BFRXw.jpeg" /></figure><p>In life we wear a lot of different hats, play a lot of different roles. Sometimes when we get ready to do different jobs we put on different uniforms, gear, outfits and top it off with a hat. When we think about these <a href="https://www.youtube.com/watch?v=Stc0beAxavY">jobs to be done</a>, we can think about different experience roles that people play and the jobs they hire for. Instead of talking about these in terms of personas we can simple talk about what these experience roles are and what are they hiring for.</p><p>As we start to look at how we talk about various experience design practices(methodologies) we can take a step back and rethink how we approach them to make sure we are really connecting with our teams and those around us on a <a href="https://uxdesign.cc/is-hx-just-doing-ux-right-or-is-it-more-d7690063307e">human level</a> and do it <a href="https://uxdesign.cc/how-to-discuss-experience-design-and-not-sound-like-an-arrogant-arse-b4dc76312164">without sounding like a know-it-all</a>.</p><p>Remember, these words and phrases are not magical, canonical or holy. In fact take them, and change them, as the immortal Paula Abdul was so fond of saying, “Make them your own!” The point is to evaluate how you talk with your teams and people in your company. Then determine if you can make it more inclusive, co-operative and reduce the barriers for everyone to participate in the design of the experience.</p><p>I’ve heard personas described as, “A relatable snapshot of the target audience that highlights demographics, behaviors, needs and motivations through the creation of a fictional character. Personas make it easier for designers to create empathy with consumers throughout the design process.”</p><p>Let’s start off with the name Personas. Doesn’t this sound all mysterious and scientific, like the word <em>dossier</em>? Dossier doesn’t even look like it sounds. The definition is “a file containing detailed records on a particular person or subject.” I know, it has French roots.</p><blockquote>“French, bundle of documents labeled on the back, dossier, from <em>dos</em> back, from Latin <em>dorsum”.</em></blockquote><p>My point is the average Jessica/Joe wouldn’t talk about a dossier without feeling at least a little twinge of pretentiousness…and you probably have to say it several times with a really bad French accent, right?</p><p>Anyway, back to Personas. Even the definition of persona sounds pretentious.</p><blockquote><em>plural </em><strong>personas</strong> [New Latin, from Latin] <strong>: </strong>an individual’s social facade or front that especially in the analytic psychology of C. G. Jung reflects the role in life the individual is playing.</blockquote><p>Go ahead…read it through several times to really let it sink in. There’s no way you would use this definition to explain what a persona is, and if you have to explain what it is aren’t you already creating work that doesn’t need to be done?</p><h3>The Rest of the World Doesn’t Live in Your Mind</h3><p>I know sometimes it feels like there are a lot of voices in there, but hopefully there’s just one…okay two, — your mother berating you for all the bad things you do with your life. Just kidding, my mom is my biggest champion. She has everything I’ve ever written in a scrapbook and her favorites on her refrigerator door (I think she secretly only brings them out when I visit).</p><p>For years I told myself everyone, or at least <strong><em>most</em></strong> people understand what it is that I mean when I say persona. For instance, “let’s look at the personas” or “that’s the grandma persona” or “I don’t think the builder persona would do that.” I expected everyone I was talking about to have the same mental model of what a persona is and what they are meant for. You know what? They don’t! Not every developer or team member has the same understanding of how personas are developed, how they are attached to customer journey maps (now <a href="https://medium.com/@amiwebguy/ux-methodologies-are-now-experience-practices-b4dc76312164">Customer Experience Maps</a>) and how they can be useful in defining stories in agile backlogs.</p><p>If you were to talk about Pam, the manager of a store or Jim the sales agent and the fact that they represent various <strong>experience</strong> <strong>roles</strong>, we are much more likely to understand what it is we are after. After all, that is the purpose of all this, right? We want to understand what Pam is feeling when she does her job, what her environment is like, and how she interacts with various people, processes and technologies throughout the day. We need to know what her tasks are, what permissions she needs to a system, and what information and tools she needs at her disposal to help her do her job. She helps represent a certain set of needs that we should account for as we design and develop experiences.</p><h3>The Definition</h3><p>Let’s try to reframe our definition of what a Role is and what we need it for when we have these conversations with our PO’s, teams and stakeholders.</p><p>A Role is someone that represents a group of people, their backgrounds, the things they do, and what makes them do the things they do. It helps describe their routine tasks.</p><p>We create these experience roles so we can organize the research we’ve done to better understand them and have common words to talk about them with our teams.</p><p>They create people that represent the need for certain experiences and features, and help us make sure we can intelligently talk about them as we build experiences for them.</p><p>We can use them to help us get into character as we’re trying to understand their needs and environment as we research, do design work and create stories to bring our experiences to life with the developers on our teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G7iK1wCIQu4pZQCPs3Dwwg.png" /></figure><h3>Role + Goal = Experience (Scenario/Feature)</h3><p>I have to credit our Director of UX, Rob Thomas for this next piece of thinking as he helped me get here. I think it’s brilliant and indicative of what I’m trying to accomplish in this series of articles about how we approach designing experiences. It breaks down what can be complex and arduous work into a simple and approachable equation. He said, Role + Goal = Scenario. I looked at that and tried to make it a bit more approachable as we talk about building experiences and evolved it to Role + Goal = Experience.</p><p>Let’s take each part of the equation piece by piece. Role, this can be confused with a permission (user, admin, manager, etc.), but here we’re talking about what is the role of this type of customer in the <a href="https://uxdesign.cc/how-to-discuss-experience-design-and-not-sound-like-an-arrogant-arse-b4dc76312164">Customer Experience Map</a>? This Role is really their Persona. What unique attributes represent this section of your customer base that can help you identify needs as you seek to craft stories, designs, development? What value can be delivered to your customer through features or working code/products that help them achieve their goals.</p><p>Next is goal, what are the day to day (UCD) tasks does that Role play each day. Whether you like User Stories or Jobs to Be Done your identifying the needs of the customer, their wants, their desires, their goals.</p><p>Taking that Role and adding the Goal helps define what experience you are going to create. Call it a scenario, feature, app, micro-journey, whatever. Those first two pieces of Role + Goal help you empathize with the customer to define what experience you will build.</p><p>Remember that experience can be as small as interacting with the sound controls of Spotify, adding quantity to your Amazon order or adding a new photo in Instagram. Experience can also be the whole experience, but the point is the Role the customer plays plus their goals equals the experience you can design for them.</p><h3>How to Create Personas or Experience Roles</h3><p>There are endless resources on the web for how to create personas or experience roles. Again, that’s not my goal here. My goal is to help us change our approach in how we talk about this methodology/practice/activity with our team members and others we work with to be more inclusive and less prickly.</p><p>Here are a few of my favorites.</p><p><strong>NNg</strong> <br>-<a href="https://www.nngroup.com/articles/persona/">https://www.nngroup.com/articles/persona/</a><br>-<a href="https://www.nngroup.com/articles/persona-scope/">https://www.nngroup.com/articles/persona-scope/</a></p><h4>Next Up: <a href="https://uxdesign.cc/taxonomies-are-now-experience-organizations-1303643aa7ee">Taxonomies are now “Experience Organizations”</a></h4><p>In life, it’s important to learn how to organize things. I learned this from an early age and have enjoyed it throughout my life. I think this is one reason I love designing experiences. You take all these messy-middle thoughts and start to try to make sense of them, move the bits and pieces around until you can find a semblance of order. You can feel the pieces flow, you almost feel happier as each new piece falls into place like a puzzle nearing completion.</p><p>Taxonomies, Information Architecture (IA), Labeling, Search, all these are helping us to define the basic architecture of the experiences we build. Let’s explore more about these things as we <a href="https://uxdesign.cc/taxonomies-are-now-experience-organizations-1303643aa7ee">move from Taxonomies to “Experience Organizations”</a></p><p><a href="https://uxdesign.cc/taxonomies-are-now-experience-organizations-1303643aa7ee">Continue reading…</a></p><h3>Articles in this series</h3><p>This series seeks to reexamine the approach and vocabulary of<strong> UX design methodologies</strong> and translate them into <strong>experience practices</strong> (minus the UX and design terms) that help us to be more inclusive, align with our teams better and interact with the full spectrum of humans as we design experiences.</p><h4><a href="https://uxdesign.cc/how-to-discuss-experience-design-and-not-sound-like-an-arrogant-arse-b4dc76312164">How to discuss experience design and not sound like an arrogant arse</a></h4><p>Sometimes we struggle connecting with our teams and it may just be our approach and interaction.</p><h4><a href="https://uxdesign.cc/personas-are-now-called-roles-4bc9e7f5a99">Personas are now called “Experience Roles”</a></h4><p>Personas really look at the hats or roles that people play and the things they do that make them different from others.</p><h4><a href="https://uxdesign.cc/taxonomies-are-now-experience-organizations-1303643aa7ee">Taxonomies are now “Experience Organizations”</a></h4><p>In life, it’s important to learn how to organize things. Let’s look at how we can do this with our teams.</p><h4><a href="https://uxdesign.cc/is-hx-just-doing-ux-right-or-is-it-more-d7690063307e">Is HX simply about doing UX right, or is it more?</a></h4><p>Human experience design is a more holistic approach to experience design.</p><h4><a href="https://uxdesign.cc/how-co-designing-can-reduce-your-rejection-and-stress-levels-as-a-uxer-6b905a7d6a86">How co-designing can reduce your rejection and stress levels</a></h4><p>You’re not a magician, cowboy, ninja or superhero; stop trying to be one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*cZIhkZoke46-EXB-" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://twitter.com/uxminaspretas">UX Para Minas Pretas</a> (UX For Black Women), a Brazilian organization focused on promoting equity of Black women in the tech industry through initiatives of action, empowerment, and knowledge sharing. 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=4bc9e7f5a99" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/personas-are-now-called-roles-4bc9e7f5a99">Personas are now called “Roles”</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[How to discuss experience design and not sound like an arrogant arse]]></title>
            <link>https://uxdesign.cc/how-to-discuss-experience-design-and-not-sound-like-an-arrogant-arse-b4dc76312164?source=rss-5dc7602b0ba8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4dc76312164</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[customer-journey]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Justin Jolley]]></dc:creator>
            <pubDate>Wed, 08 Jul 2020 23:05:15 GMT</pubDate>
            <atom:updated>2020-07-10T12:58:08.706Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Donkey, Mule, Arse" src="https://cdn-images-1.medium.com/max/1024/1*EzWWlYyQpvbWO_x5gGBs7A.jpeg" /></figure><h3>UX Methodologies are now Experience Practices</h3><p>Restructuring our speech to be more inclusive and less technical, complicated and filled with jargon can go a long way. In this next series of articles, I’d like to explore how we could approach changing our talk from methodologies to more human terms with our teams.</p><p>The point of this article is not to teach you how to do each of these practices, but to change how we talk about them and to whom we talk about them with. In a previous article, I talked about how to reduce the rejection and stress levels in your life by changing your approach to UX design to a more <a href="https://uxdesign.cc/is-hx-just-doing-ux-right-or-is-it-more-d7690063307e">Human design (HX)</a>. This included changing from “<strong>UX</strong>” and “<strong>Design</strong>” language to “<strong>Human</strong>” and “<strong>Experience</strong>” language.</p><p>This focus makes us more approachable and inclusive in our design work. We can still talk about the methodologies to each other as we push the maturity of our industry into the future, but we need to start translating or employing a conversion or connector when talking with our teams. Talking in highly technical terms confuses, alienates and excludes the teams that we are striving to be part of.</p><p>So again, the purpose here is to make a switch in our brains as to how we talk about various UX methodologies or Experience Practices. We can drop the ketchup bottles and courtyard paths when we try to explain to everyone what UX is- and leave the “methodologies” to rocket scientists. We’re just going to work on the “<strong>experiences</strong>” we’re creating for our customers and “<strong>practice</strong>” how we do them to get better as a team.</p><p>Before we start, these words and phrases are not magical, canonical or holy. In fact take them, and change them, as the immortal Paula Abdul was so fond of saying, “Make them your own!” The point I’m trying to get across is that many times our approach as UX professionals is not compatible with the engineering efforts going on in many companies. If you are the exception, wonderful. I’d love to hear how you did it. In the mean-time, this is my effort to make sense of it to myself and to those I work with. Hopefully it may bring a new approach to how you’re helping your team design experiences.</p><figure><img alt="Male to male converter" src="https://cdn-images-1.medium.com/max/770/1*a8t5xV0fc3ayWXqpGYDZuw.png" /></figure><p>For most people, however, the analogy that I’ve heard that makes so much sense is that we (UX and the rest of the org) tend to come at things like two male plugs that don’t quite connect. We need someone to act as a connector, translator or conversion device. You know, like one of those Swiss Army knife contraptions you use when you travel abroad that pops out the multi-shaped prongs for different electrical standards. Imagine if we had some type of converter that translated our thinking and speech from a male plug to a male plug when doing experience design. You can be the translation device, — the piece in the middle of the teams that brings everything together to make it work harmoniously.</p><h3>Trigger Words</h3><p>Something that may be helpful is to listen to yourself for trigger words. In the past you may say, “user”, “UX design” or “UX” a lot to refer to the people or teams doing design. As part of the translation you can start to think about substituting these words. <strong>Customer</strong> instead of <strong>User</strong>, <strong>Experience Design</strong> instead of <strong>UX Design</strong> and <strong>team</strong> instead of <strong>UX</strong>. These are just a few of the words you can use in your mind and conversation to start changing how design is done in your organization. This will help you <a href="https://uxdesign.cc/how-co-designing-can-reduce-your-rejection-and-stress-levels-as-a-uxer-6b905a7d6a86">reduce your feelings of rejection and stress levels</a>.</p><h3><strong>Consumer Journey Map</strong> Becomes <strong>Customer Experience Map</strong></h3><figure><img alt="Train" src="https://cdn-images-1.medium.com/max/1024/1*g_Jqa-zkG6HXHC8NhuV-lg.jpeg" /></figure><p>A consumer or customer Journey Map is a diagram that explores multiple steps taken by customers as they interact with the various channels and services of your organization. It allows you to have empathy with a customer’s motivations and needs along each step of their interaction (experience) and design experiences that are needed for each step.</p><p>This is simply the process a customer goes through when they initially are introduced to your organization and all the places where they can interact with another human being, computer or other technology. This can be your website, mobile apps, customer service, brick and mortar stores, product shipping, returns, IoT, etc.</p><p>These are usually associated with a persona which we’ll call a role. It can be very useful as it allows you to see what the current experience is, test to set priority of areas to change and then focus on areas to improve the experience.</p><p>A great example of the value of a map is when a designer asked our team last week, if everyone could help him understand how the features they’re working on would interact with our notification process. I pulled out our journey maps, walked the process though of all the spots where a notification may have triggered interaction with a customer.</p><p>The main point is that we change <strong>consumer to customer</strong> as who know’s what a consumer is and that <strong>journey changes to experience</strong> because it better describes what is happening. Our customers are interacting with our customer success agents and having <strong>experiences</strong>. They are interacting with our websites and mobile apps and having <strong>experiences</strong>. You wouldn’t hear a customer in a store or online say, “I’m about to start a <strong>journey</strong> to interact with the company called Nike.” It’s much more common for people to talk about their good or bad “<strong>experiences</strong>” with someone in a call center or with ordering on line. This is our natural language and we all understand what these terms mean.</p><h3>Your Challenge</h3><p>Whether you’re involved in creating a Customer/Consumer Journey Map right now, or validating them or using them to explore a new/existing feature. Have this conversation with your team, both your UX team and your feature teams. Talk about how you could change the wording and approach of exercise or findings to be more inclusive in gathering the data and understanding it. How can you reframe the conversation so that everyone understands what the goal is (to get a better understanding of the customers experiences) and how you will use that information going forward (prioritizing experiences that need attention or walking through the maps to provide insight into existing/new features that you’re designing).</p><p>Next Up: <a href="https://uxdesign.cc/personas-are-now-called-roles-4bc9e7f5a99"><strong>Personas</strong></a></p><h3>Personas are Now Called Roles</h3><p>I’ve heard personas described as, “A relatable snapshot of the target audience that highlights demographics, behaviors, needs and motivations through the creation of a fictional character. Personas make it easier for designers to create empathy with consumers throughout the design process.”</p><p>This is from a <strong>foundational work</strong> originally appearing in Medium from the UX Collective on <a href="https://uxdesign.cc/ux-design-methods-deliverables-657f54ce3c7d">UX Design Methods &amp; Deliverables.</a> My intent is not to disparage anything they provided as it’s vital that we have an understanding of the work described here. My goal is to<strong> build on</strong> this and <strong>provide the translational layer for discussion</strong> around how to communicate these methodologies or activities/practices to a <strong>larger, more inclusive group</strong>.</p><p>I think it’s important that we’re able to speak both languages, the technical terms to advance the rigor around the science of experience design as well as the more approachable common terminology to communicate effectively to the larger group we work with.</p><p>A good analogy might be a medical doctor. When choosing someone to perform a double bi-pass heart surgery for your loved one you want someone who can both speak intelligently with the correct technical terms to the medical staff, as well as someone who can explain just what is going to happen during the surgery. You expect or at least hope that the doctor is mature enough to be the translator and communicate effectively with both groups.</p><p><a href="https://uxdesign.cc/personas-are-now-called-roles-4bc9e7f5a99">Continue reading…</a></p><h3>Articles in this series</h3><p>This series seeks to reexamine the approach and vocabulary of<strong> UX design methodologies</strong> and translate them into <strong>experience practices</strong> (minus the UX and design terms) that help us to be more inclusive, align with our teams better and interact with the full spectrum of humans as we design experiences.</p><h3><a href="https://uxdesign.cc/how-to-discuss-experience-design-and-not-sound-like-an-arrogant-arse-b4dc76312164">How to discuss experience design and not sound like an arrogant arse</a></h3><p>Sometimes we struggle connecting with our teams and it may just be our approach and interaction.</p><h3><a href="https://uxdesign.cc/personas-are-now-called-roles-4bc9e7f5a99">Personas are now called “Experience Roles”</a></h3><p>Personas really look at the hats or roles that people play and the things they do that make them different from others.</p><h3><a href="https://uxdesign.cc/taxonomies-are-now-experience-organizations-1303643aa7ee">Taxonomies are now “Experience Organizations”</a></h3><p>In life, it’s important to learn how to organize things. Let’s look at how we can do this with our teams.</p><h3><a href="https://uxdesign.cc/is-hx-just-doing-ux-right-or-is-it-more-d7690063307e">Is HX simply about doing UX right, or is it more?</a></h3><p>Human experience design is a more holistic approach to experience design.</p><h3><a href="https://uxdesign.cc/how-co-designing-can-reduce-your-rejection-and-stress-levels-as-a-uxer-6b905a7d6a86">How co-designing can reduce your rejection and stress levels</a></h3><p>You’re not a magician, cowboy, ninja or superhero; stop trying to be one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*oJdKrISDQQYvK-Ys" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://twitter.com/uxminaspretas">UX Para Minas Pretas</a> (UX For Black Women), a Brazilian organization focused on promoting equity of Black women in the tech industry through initiatives of action, empowerment, and knowledge sharing. 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=b4dc76312164" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-discuss-experience-design-and-not-sound-like-an-arrogant-arse-b4dc76312164">How to discuss experience design and not sound like an arrogant arse</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[How co-designing can reduce your rejection and stress levels]]></title>
            <link>https://uxdesign.cc/how-co-designing-can-reduce-your-rejection-and-stress-levels-as-a-uxer-6b905a7d6a86?source=rss-5dc7602b0ba8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b905a7d6a86</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Justin Jolley]]></dc:creator>
            <pubDate>Sun, 14 Jun 2020 02:35:17 GMT</pubDate>
            <atom:updated>2022-10-17T15:28:05.363Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="It takes a team to get the job done…that includes designing in the larger sense of the word." src="https://cdn-images-1.medium.com/max/1024/1*bRE-PD2eV5O5rH4iEJH2GQ.jpeg" /><figcaption>It takes a team to get the job done…that includes designing in the larger sense of the word.</figcaption></figure><p>You’re not a magician, cowboy, ninja or superhero; stop trying to be one. Unless you really are, that’s pretty exciting! Let’s talk. For the rest of us mere mortals, if you look at any of these stoic figures they appear to be standing out in front on their own. If you stop and think though, there are always so many others involved in the operations behind the scenes. Magicians have assistants and stage crews, cowboys have drovers, camp cooks, and branders, ninjas have sensei’s and the people that make those shoes with the pieces that go in-between your toes, and superheroes have sidekicks and the costume and gadget developers.</p><p>The point is that no person is an island and you can’t be all things as a UX professional. Even if you are a “full-stack” designer or wear black turtlenecks with wire-rimmed glasses, man-buns, lumberjack beards with wicked awesome flannel shirts or arm sleeve tattoos. Well, maybe if the flannel was super grungy and covered one of those Nirvana T-shirt with the smiley face. It’s really hard to tell in that case.</p><p>What sparked me to write this is that I just read an article about a UX designer who was expressing some frustrations about things they wish people would have told them about doing UX before they started. I really felt for this person and anyone else stuck in this stage. I wanted to write a response to give them hope and share how they might turn things around. There is a way of alleviating some of the frustration and burden they feel.</p><p>There is an old dad joke that goes something like this: (I’ll pause for the golf clap.).</p><blockquote>Doctor! Doctor! It hurts when I go like this…Well, don’t go like that!</blockquote><p>Many times as new UX practitioners we find ourselves in somewhat of a battle. We might be fresh out of a UX bootcamp or just completed years of training in which we are laser focused on 157 methods for empathizing with our customers. We may feel we have to justify our existence, prove we know what we’re talking about, fit in with the team, and make a name for ourselves. We do UX research, create incredible designs and work with developers to help deliver them all on a silver plate. We invested thousands of dollars, spent hundreds of hours fine tuning our skillset to know all the buzzwords about affordance, cognitive overload and what Henry Ford said about faster horses.</p><p>I’m here to tell you, if you keep going like that it’s just going to keep hurting. There is another approach.</p><p>It’s called participatory design. It’s also known as co-operative design or co-designing. I like co-designing because it sounds the most human, which is an important first lesson (we’ll talk about that later).</p><p>First though, let’s look at some good signs that will help you know if you could approach things a bit differently and alleviate a whole world of hurt for yourself and your teams.</p><h3>Rejection</h3><p>If you feel like you’re constantly getting rejection with your designs, there is another way. Stop designing. No seriously, stop designing. Drawing pictures should not be the only tool in your tool belt. I’ve heard people say things like, “I don’t think I realized just how routine rejection would become.” There is another way where there isn’t so much rejection and it’s not all on you.</p><p>This mindset can also be a trap. I used to ask designers in interviews, “what do you do if you show a design to a product owner and they say I don’t like it (rejection)? “ The hope was that they’d say something like, “in a non-confrontational manner I’d ask them what they didn’t like about it and then help them see the <strong>data</strong> that supported why I designed it that way. “ I wanted to know they were a team player, could resolve conflict and work to let data make the decisions.</p><p>I’ve since learned this whole approach is wrong. If you’re trying to pull magical designs out of your hat…or other place like some aesthetically gifted Criss Angel, you may be doing it wrong. I know, I know, the burst of elation in getting positive feedback from awestruck PO’s is a veritable Pavlovian bell. However, it’s leading you down the wrong path. It’s encouraging the Marlboro Man to come out, the Lone Ranger, the superhero archetype.</p><p>Instead of going off in a corner, doing the research, sketching, wire-framing, validating designs, doing visual designs, and <strong>revealing</strong> “the” answer to your PO. Why not <strong>bring the whole team along for the understanding and design</strong>. After all, it <strong>isn’t</strong> about how much notoriety and credit <strong>you</strong> can gain from creating amazingly user-friendly designs, or the number of times your artwork appears on the company fridge. It is about how much value you can create for the customer, company and your team. It’s an outward mindset kind of thing, or in other words how you can succeed as a team instead of by yourself.</p><p>Tim Brown the founder of IDEO, a design agency specializing in design thinking has few <strong>heretical quotes</strong> that just might shake up your design world. It may be the best thing for your career and your company though. I still shutter a bit every time I read this, and then in a reassuring inner dialog, I tell myself it is the best way forward.</p><blockquote>“Design may have its greatest impact when it’s taken out of the hands of designers and put into the hands of everyone” -Tim Brown</blockquote><p>Tim Brown argues that focusing less on the <a href="https://designthinking.ideo.com/resources/tim-browns-ted-talk">design of an object and more on design as an approach to problem-solving</a> will allow design to serve human needs most effectively.</p><p>There are a number of ways you can do this, a few of my favorites are simple brainstorming as a group and design sprints. I’ve had designers on my team do this with amazing results, and you know what, everyone loves them. The team no longer feels like order takers, they get to be involved with the sense-making and solutions -they have a say in how and when things are done and a ton of weight is taken off the shoulders of the designer.</p><p>The designer is learning other great skills when doing this too. Instead of just designing or researching, they become facilitators. They’re teaching the team the importance of understanding the customer and the business, bringing in subject matter experts and insight that they’d never have on their own. They are interacting and leading people. This elevates the designer and the whole group, not just around design thinking. They are interacting as human beings, designing software and delivering working products.</p><p>It’s the height of hubris to think an inexperienced designer fresh out of college/camp and new to an organization has all the wisdom, knowledge and experience to design a solution all by their lonesome. Do not take this pressure upon yourself and set yourself up for a career full of rejections. How could it be otherwise? You don’t know enough to not be rejected. It’s easy to lull yourself into thinking you have all the answers after you have a few successes; but it’s not what is best for you, your team or the company.</p><h3>The first Iteration Does Suck</h3><p>This should be pretty obvious as again, you don’t know everything. Nor should you be expected to as experiences are too complex. I just came across this quote from Ernest Hemingway that said, “The first draft of anything is shit.”</p><figure><img alt="The first draft of anything is shit -Ernest Hemingway" src="https://cdn-images-1.medium.com/max/1024/0*0stg8m6IwA_3WVmj" /></figure><p>Well as fun as this is to say, isn’t that pretty obvious? The goal is to not let your first or even third draft appear on the screen of your Jira board or presentation during a sprint planning meeting. Why would you do this? A better solution would be to work out all of the refuse quality designs together as a team.</p><p>During design sprints you do something called Crazy 8’s. Everyone on the team from the product owner to QA analyst draws eight designs in eight minutes. You have dozens of first drafts or iterations on possible solutions. Then everyone gets to explain and vote on the best approach and you then dive in again to fine tune that with a solution sketch.</p><p>You see what’s happening here. You’re getting so much valuable input that you’d never know if it were just you, your MacBook and Figma/Sketch/XD…other design tool. You have the benefit of the product owner who remembers from the talks with stakeholders that there are legal issues around this feature. You have developers who know that the current library of components only supports certain interactions. You have QA that might remind you that another team already developed a component that you could reuse. This way when you come to deliver the first draft to the light of day it doesn’t suck!</p><h3>Writer’s/Designer’s Block</h3><p>You never have to fear this again, you are not the soul source of creativity on your team or organization. You work <strong>together</strong> to come up with ideas. I can’t tell you how many times I’ve had different team members chime in and then hear a designer say something to the effect of, “oh yeah, I would have never thought about that. Great idea.”</p><p>You don’t have to sit and stare at a blank canvas, spend countless fruitless hours exploring Dribbble and Google for inspiration. You don’t have to feel heightened stress around presenting to the group on Monday morning, fear of feeling like a fraud or that you don’t have enough talent. The <strong>group</strong> should be working together in an agile manner to solve the problem. Just like you’d help the developers get the CSS colors right or the product owner write user stories and define the feature map. We each help each other to the best of our abilities on a daily basis and especially when we swarm to finish a feature.</p><h3>Experience, Intuition or Luck</h3><p>I don’t care how much experience you have, Sherlock Holmsian intuition or the luck of a slick Las Vegas gambler; you can’t on a consistent basis produce the best on your own. The burnout is real folks. Cast off the thoughts of relying only on yourself over and over and instead think about participatory design not only with your team but with your customers.</p><p>Another aspect of co-design is not just with your team, but with your customers. Going right to the horses mouth to get an understanding of how the customer does their business, uses the tools and interacts with their environment while you’re designing removes the need for experience, intuition or luck.</p><p>Whether you do this as a focus group, customer advisory board or a few zealous volunteers you got their contact information during your last global conference. Let the customers in, have them help, listen to what they say (don’t always follow it, trust but verify, right?) and have them help validate that together you created what they wanted and needed.</p><h3>Take off the Cape</h3><p>I know, I know, the first rule of super heroes is not to wear a cape. I’ll let Superman and Mr. Incredible fight that one out, but for the rest of us we don’t have to wear it or those restrictive tights. They chafe like crazy!</p><p>If you find yourself in any of the situations listed above, it’s time to evolve to a better way of doing UX. Here are some first steps to take.</p><h3>UX Language vs. Human Language</h3><p>It’s very tempting when you’re first trying to establish yourself with a company and team to make yourself sound educated or authoritative. Try to resist the urge somewhat, as it just serves to alienate you from your teams. At the very least chose the best times to use those cool UX-ey words.</p><p>If you’re giving a presentation, talking to the board of directors or addressing congress, it’s okay to bedazzle your speech a bit. However, for everyday work with Debbie the PO and Henry the developer, let’s just stick to plain old useful and well understood terms. The point of talking in these cases is to communicate. We do that best when we use language we all understand. Talk like you talk with your brother or sister…okay, maybe not that intimately, but you get the point. Just be human, fallible, vulnerable and don’t have all the answers.</p><p>In fact, there’s a whole evolution of experience design that is dealing with the human experience of things…but that’s <a href="https://uxdesign.cc/is-hx-just-doing-ux-right-or-is-it-more-d7690063307e">another topic for another time</a>.</p><h3>Don’t Weaponize UX</h3><p>Oooh, I love this one. I’ve done this so many times it’s embarrassing. During how many discussions have you pulled out a statistic on mobile usage, cognitive biases, quotes by seemingly famous demi-gods (Nielsen, Norman, Shaffer, Spool, etc.) to prove a point or win an argument? Just stop that.</p><p>I remember in college we learned about lies, damn lies and statistics. How many UXers worth their weight aren’t able to conjure up a survey, Google Analytics or a Hotjar session to support “their” way of how form validation should work? Don’t use the data to prove your or anyone else’s point. Data shouldn’t be used to further anyone’s agenda but to help us understand the customer.</p><p>Instead, let’s teach the whole team about the best methodologies for understanding our customers, qualitative, quantitative, behavioral. Our value is in helping our teams and organizations mature in their thinking and understanding of research. Our goal is to bring value to our customers, not build a fan club, right?</p><h3>Tri-Force Tension</h3><p>There is a natural tension in any agile feature/product/journey team between user experience design, product ownership and development. It’s easy to let this become adversarial and build up sides or kingdoms. Resist this urge as well, even though the power flowing through your veins is as intoxicating as the dark side of the force. Don’t give in. It’s so easy. It only takes a few times of someone introducing you as our “experience expert” or “usability ninja” and you’re hooked. The tension should be about protecting those areas of work and not making it personal.</p><figure><img alt="Tri-Force Tension" src="https://cdn-images-1.medium.com/max/478/1*cMk8r43VRF4Ap9KACWZOzw.png" /><figcaption>Tri-Force Tension</figcaption></figure><p>A great book on how teams should work together is, <a href="https://www.amazon.com/INSPIRED-Create-Tech-Products-Customers/dp/1119387507/ref=asc_df_1119387507/?tag=hyprod-20&amp;linkCode=df0&amp;hvadid=312045580796&amp;hvpos=&amp;hvnetw=g&amp;hvrand=15491158344739612075&amp;hvpone=&amp;hvptwo=&amp;hvqmt=&amp;hvdev=c&amp;hvdvcmdl=&amp;hvlocint=&amp;hvlocphy=9029688&amp;hvtargid=pla-387522764878&amp;psc=1&amp;tag=&amp;ref=&amp;adgrpid=60223809337&amp;hvpone=&amp;hvptwo=&amp;hvadid=312045580796&amp;hvpos=&amp;hvnetw=g&amp;hvrand=15491158344739612075&amp;hvqmt=&amp;hvdev=c&amp;hvdvcmdl=&amp;hvlocint=&amp;hvlocphy=9029688&amp;hvtargid=pla-387522764878">Inspired: How to create Tech Products Customers Love</a> by Marty Cagan.</p><h3>We Need Development to Deliver Experiences</h3><p>Sometimes we get so busy designing and testing amazing experiences that we forget that in order to make the designs reality (code) we must work through the current company development resources. You can’t design your way to production. One of the biggest mistakes we make is separating the work we do from that development flow. In a recent conversation with Dr. Eric Schaffer he said, “one of the biggest mistakes we’ve made in UX is providing a playbook.” This is because many times we try to set up practices to <strong>mirror</strong> development instead of <strong>merging</strong> with it. We forget that what we’re doing has a large engineering component that everything hinges on.</p><p>We’ve setup design ops just like dev ops. We saw the similarities and want to bring the structure and validation rather than become part of the flow. It’s understandable because it can be hard on both sides to see how “design” fit’s into the development flow and works nicely together. Many times we don’t have control or can’t get a seat at the table to merge our workstreams, so we create our own segment of the deployment train.</p><p>It’s okay to develop our playbooks. It just needs to be for the entire team to execute plays on instead of just a designer or the UX team. In order to do this we need to democratize it, make it consumable and understandable by the whole team. They can see a place where they can see themselves in it and what part they play. Provide simplified explanation, templates, training and guidance for everyone to join in the fun.</p><p>This takes a mindset change. You are bringing design thinking to the whole organization. You’re not protecting “your” field of study and “your” area of expertise, but opening up and sharing and helping the entire team understand the benefits of each methodology and execution of play in the playbook.</p><p>Some of the most fun I’ve had in my career was when we’ve had research going on that was conducted by the team, understood by the team, and then working together with PO’s and developers in the same projects to create pages as they come together. When you’re all working together in harmony and seeing the work progress, it’s exciting. Then working with the customers to iterate, fine-tune it and push it to production and see the usage take off all while achieving the company’s KPI’s/OKR’s is pure joy.</p><h3>Build Your Design System Together</h3><p>Build your design system together. Taking this action to make your language and components common is a great step. Build your components together, conduct workshops for research together and sit side-by-side as you develop prototypes. Life is more fun with a friend and so is work.</p><p>Pick the next item in your design system whether it’s a way to upload documents or your methodology for doing preference testing to work on. Set up a time for your PO and development lead to join you in defining how and when you’ll implement these pieces. It may seem scary at first or you may tell yourself they’re too busy. We’re all too busy, so who cares. One of the most important skills you’ll develop as a UX practitioner is developing relationships. Work on that. It won’t happen overnight. It may take some time for people to change, but they will. I’ve seen it happen.</p><p>Measure your successes by the small, incremental changes and improvements your team has this way. The systems you develop in this manner will have a greater chance of living beyond your time at the company and your team. There is an old African Proverb I like.</p><blockquote>If you want to go fast, go alone. If you want to go far go together.</blockquote><p>Go together.</p><h3>Design as a Team</h3><p>This is painful at first, I’ve had team members downright shut down mentally, emotionally and physically when you ask them to scribble down ideas on a piece of paper. This can be so foreign to them as they have been living and breathing in a different world. Bring them along slowly, some will dive right in but others will take time. Even if they just write words that represent designs at first, that’s wonderful. It’s about coming up with ideas and not an art competition.</p><p>Be patient with them and help them see the excitement you feel when you understand a customer’s pain point, the down right giddiness of the rise and fall of the line chart in your A/B test, the sense of serenity you feel when the colors and balance of a visual design align. These things that excite us about crafting user experiences are contagious. Showing a PO a session with a user rage clicking will turn on lightbulbs. Help developers deliver a feature by designing with a component that’s already in the design system and helps them increase their velocity by closing a ticket.</p><p>Co-designing is about working as a team and delivering working software, which is the true measure of the success of any team. It doesn’t matter how many designs you have in Figma, Abstract or InVision, if they never see the light of day they’ll never fulfill the measure of their creation and neither will you.</p><p>Life is hard enough without taking on more responsibility than you need. It’s time to let all the kids on the playground into the sandbox, work together and build something wonderful that you all can be proud of.</p><p>If this tickled your fancy, you might also enjoy this other read.</p><figure><a href="https://uxdesign.cc/is-hx-just-doing-ux-right-or-is-it-more-d7690063307e"><img alt="Is HX simply about doing UX right, or is it more?" src="https://cdn-images-1.medium.com/max/1024/0*P8RtS3Uka7QchhjI.jpeg" /></a><figcaption>Is HX simply about doing UX right, or is it more?</figcaption></figure><p>Is HX simply about doing UX right, or is it more?</p><p>From UX to CX to HX.</p><p><a href="https://uxdesign.cc/is-hx-just-doing-ux-right-or-is-it-more-d7690063307e">Yes, I’d love to read that!</a></p><h3>Articles in this series</h3><p>This series seeks to reexamine the approach and vocabulary of<strong> UX design methodologies</strong> and translate them into <strong>experience practices</strong> (minus the UX and design terms) that help us to be more inclusive, align with our teams better and interact with the full spectrum of humans as we design experiences.</p><h3><a href="https://uxdesign.cc/how-to-discuss-experience-design-and-not-sound-like-an-arrogant-arse-b4dc76312164">How to discuss experience design and not sound like an arrogant arse</a></h3><p>Sometimes we struggle connecting with our teams and it may just be our approach and interaction.</p><h3><a href="https://uxdesign.cc/personas-are-now-called-roles-4bc9e7f5a99">Personas are now called “Experience Roles”</a></h3><p>Personas really look at the hats or roles that people play and the things they do that make them different from others.</p><h3><a href="https://uxdesign.cc/taxonomies-are-now-experience-organizations-1303643aa7ee">Taxonomies are now “Experience Organizations”</a></h3><p>In life, it’s important to learn how to organize things. Let’s look at how we can do this with our teams.</p><h3><a href="https://uxdesign.cc/is-hx-just-doing-ux-right-or-is-it-more-d7690063307e">Is HX simply about doing UX right, or is it more?</a></h3><p>Human experience design is a more holistic approach to experience design.</p><h3><a href="https://uxdesign.cc/how-co-designing-can-reduce-your-rejection-and-stress-levels-as-a-uxer-6b905a7d6a86">How co-designing can reduce your rejection and stress levels</a></h3><p>You’re not a magician, cowboy, ninja or superhero; stop trying to be one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b905a7d6a86" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-co-designing-can-reduce-your-rejection-and-stress-levels-as-a-uxer-6b905a7d6a86">How co-designing can reduce your rejection and stress levels</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[If the Mandalorian showed value proposition to Disney+]]></title>
            <link>https://uxdesign.cc/if-the-mandalorian-showed-value-proposition-to-disney-ee69dd711d16?source=rss-5dc7602b0ba8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee69dd711d16</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[movies]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Justin Jolley]]></dc:creator>
            <pubDate>Tue, 02 Jun 2020 00:01:12 GMT</pubDate>
            <atom:updated>2020-06-09T17:16:14.159Z</atom:updated>
            <content:encoded><![CDATA[<h4>How would Din Djarin Use the Business Model Canvas</h4><p>I’m working with my team to document the process for using various experience design methodologies and I wanted a way to share with them how to provide the Value Proposition for a project/feature. So…knowing my audience, I wanted to put this in terms that they would appreciate.</p><p>If your teams are anything like mine there are waves of pop culture that surf through your organization. Star Wars, Marvel, LoTR, etc. One of those waves is now crashing upon our shores. You know that period before a meeting starts when you’re waiting for everyone to gather. There’s usually some light-hearted banter about this and that. Well, our (now virtual) team meetings are periodically kindled with excitement of the latest Mandalorian episode. I think Disney plus has been a hit by this measure alone. If we can combine learning a new concept Business Model Canvas (BMC) with something fun (Mandalorian) I think it helps things make more sense.</p><p>One way we can show the value proposition for a project or feature is by using the Business Model Canvas. The <a href="https://en.wikipedia.org/wiki/Business_Model_Canvas"><strong>Business Model Canvas</strong></a> is a strategic management tool, which allows you to develop and sketch out new or existing business models. It is a nine block visual model that represents parts of a business model. It can be useful in putting some thinking around your product and feature ideas.</p><p>Din must earn bounties in order to pay his expenses, maintain his ship and build a suit of armor. This is much like many of our companies today. We have expenses we have to pay, we have costs associated with maintaining our offices and products while searching to add additional features to our suite of products (suit of armor).</p><p>The nine sections are;</p><ol><li>Key Partners</li><li>Key Activities</li><li>Key Resources</li><li>Value Proposition</li><li>Customer Relationships</li><li>Channels</li><li>Customer Segments</li><li>Cost Structure</li><li>Revenue Streams</li></ol><p>Let’s take a look at the details of each of these sections. I’ll get you started on the first couple and you go through the exercise of defining these for the Mandalorian or your favorite fandom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1jLlYW1eUz6iDohu5pvAag.png" /></figure><h3>Key Partners</h3><p>Who are our key partners? This changes from time to time with Din as one minute someone may be helping with his quest and the next they may be trying to kill him.</p><p>• Baby Yoda<br>• Armorer<br>• Kuiil<br>• IG-11<br>• Cara Dune</p><p>Who are our key suppliers?<br>• Greef Karga supplies Din with work in collecting bounties.<br>• Jawas are suppliers even though they stole the parts from his ship.</p><p>Which key resources are we acquiring from partners?<br>• Beskar Steel<br>• Pauldron &amp; Cuirass (armor pieces)</p><p>Which key activities do partners perform?<br>• Connecting to bounties from clients<br>• Forging Pauldron armor from Beskar Steel provided from securing bounties</p><p>Motivations for Partnerships<br>• <strong>Optimization and economy</strong> -Din must partner with Greef to bring in bounties even though Greef attacks him for freeing Baby Yoda.<br>•<strong> Reduction of risk and uncertainty</strong> -Din partners with IG-11 in order to help fight his way into obtaining the child/Baby Yoda. Yet that relationship is complicated as well because he turns on him as well.<br>• <strong>Acquisition of particular resources and activities</strong> -Din needs activities (bounty hunting) in order to obtain particular resources (Beskar Steel/Armor).</p><h3>Key Activities</h3><p>What key activities do our value propositions require?</p><p>Customer relationships?</p><p>Categories<br>• Production -Hunting down bounties, converting Beskar into armor<br>• Problem Solving -how to get parts from the Jawas for his ship, driving off a band of Klatoonian raiders for lodging.<br>• Platform/Network -bounty hunting network of customers (Imperial connections) and bounty hunters.</p><h3>Key Resources</h3><p>What key resources do our value proposition require? <br>Our distribution channels? <br>Customer relationships? Revenue Streams?</p><p>Types of Resources <br>• Physical -Beskar, Food, Fuel, Armor, Bounty discs<br>• Intellectual (brand patents, copyrights, data) Bounty disc data<br>• Human -Key partners<br>• Financial -Credits and Beskar</p><h3>Value Proposition</h3><p>What value do we deliver to the customer?<br>Delivering bounties, baby Yoda.</p><p>Which one of our customer’s problems are we helping to solve? <br>Trying to find bounties, baby Yoda</p><p>What bundles of products and services are we offering to each customer segment?</p><p>Which customer needs are we satisfying? -Cost reduction, risk reduction, performance, customization. By hiring the bounty hunter (Din) one of the primary needs he is satisfying is “Getting the job done”. That’s why people come back again and again to the bounty hunters as they know they can get the job done.</p><p>• Newness<br>• Performance<br>• Customization<br>• “Getting the job done”<br>• Design<br>• Brand Status<br>• Price<br>• Cost Reduction<br>• Risk Reduction<br>• Accessibility<br>• Convenience/Usability</p><h3>Customer Relationships</h3><p>What type of relationship does each of our customer segments expect us to establish and maintain with them?<br>Which ones have we established?<br>How are they integrated with the rest of our business model?<br>How costly are they?</p><p>Examples<br>• Personal Assistance<br>• Dedicated Personal Assistance<br>• Self-Service<br>• Automated Service<br>• Communities<br>• Co-Creation</p><h3>Channels</h3><p>Through which channels do our customer segments want to be reached? How are we reaching them now? How are our channels integrated? Which ones are most cost-effective? How are we integrating them with customer routines?</p><p>Channel Phases<br>1. Awareness <br>2. Evaluation<br>3. Purchase<br>4. Delivery<br>5. After Sales</p><h3>Customer Segments</h3><p>For whom are we creating value?<br> Who are our most important customers?</p><p>•Mass Market<br>• Niche Market<br>• Segmented <br>• Diversified<br>• Multi-Sided Platform</p><h3>Cost Structure</h3><p>What are the most important costs inherent in our business model?</p><p>Which key resources are most expensive?</p><p>Which key activities are most expensive?</p><p>Is your business more<br>• Cost driven (leanest cost structure, low price value proposition, maximum automation, extensive outsourcing)<br>• Value Driven (focused on value creation, premium value proposition)</p><p>Sample Characteristics<br>• Fixed Costs (salaries, rents, utilities)<br>• Variable Costs<br>• Economies of scale<br>•Economies of scope</p><h3>Revenue Streams</h3><p>For what value are our customers really willing to pay?<br>For what do they currently pay?<br>How are they currently paying?<br>How would they prefer to pay?<br>How much does each revenue stream contribute to overall revenues?</p><p>Types<br>• Asset Sale<br>• Usage/Subscription Fee<br>• Lending/Renting/Leasing/Licensing<br>• Brokerage Fees / Advertising</p><p>Fixed Pricing<br>• List Price<br>• Product Feature <br>• Customer Segment<br>• Dependent, Volume</p><p>Dynamic Pricing<br>• Negotiation<br>• Yield Management <br>• Real-Time-Market</p><p>If we ask ourselves what is the purpose or the value of creating a value proposition we can sum it up by saying that a <strong>value proposition</strong> tells prospective customers why they should do business with you rather than your competitors, and makes the benefits of your products or services more clear from the initial discussion.</p><p>If we set the value proposition early on in a project whether we are trying to build a suit of armor or adding a new product or feature each member of our teams will have a better understanding of what we’re trying to accomplish and the value we provide to customers through designing and developing it. For experienced designers it is especially important to know so we can focus on what is setting us apart from our competition and what values are our customers expecting.</p><p>We can then create OKR’s or KPI’s around the values to see if what we are producing is increasing or decreasing our objectives. If Din’s goal is to gain a suit of armor, deliver bounties, rescue baby Yoda, then we can track that over time and measure to see if we are on track with our initial guidance for his team or if he needs to adjust something in order to provide actual value to his customers.</p><p>This really is an important step as I’ve heard it over and over from designers and developers, “Why are we building this?” or “How do I know if i’m building the right thing?”. It’s important to have this guiding document to make sure we’re pointing in the right direction as things shift and we need a fresh reminder to help us remember why we are doing what we are doing?</p><p>I’m reminded of this from listening to the sage advice from Mr. Simon Sinek. As <strong>Sinek</strong> puts it, “<strong>People don’t buy what you do</strong>. They <strong>buy</strong> why <strong>you do</strong> it.” Starting with “why” helps us deliver something of greater value to customers and organizations. If you’re struggling with filling out a basic business model canvas to determine your value proposition you may want to ask if this is really the most important thing for us to be working on.</p><p><strong>Other Reads You Might Enjoy</strong></p><figure><a href="https://uxdesign.cc/is-hx-just-doing-ux-right-or-is-it-more-d7690063307e"><img alt="" src="https://cdn-images-1.medium.com/max/200/1*Yb0WypIVeq8TFT_WdW-H8w.png" /></a><figcaption><a href="https://uxdesign.cc/is-hx-just-doing-ux-right-or-is-it-more-d7690063307e">Is HX simply about doing UX right, or is it more?</a></figcaption></figure><figure><a href="https://medium.com/swlh/your-johnny-cash-is-in-my-nirvana-why-designers-and-developers-should-be-friends-2f2b549120fd"><img alt="" src="https://cdn-images-1.medium.com/max/210/1*TtmHe0UFtTfuHcVahJAbkw.png" /></a><figcaption><a href="https://medium.com/swlh/your-johnny-cash-is-in-my-nirvana-why-designers-and-developers-should-be-friends-2f2b549120fd">Your Johnny Cash is in My Nirvana: Why Designers</a>…</figcaption></figure><figure><a href="https://medium.com/swlh/enterprise-ux-competitive-analysis-69d09a989bd7"><img alt="" src="https://cdn-images-1.medium.com/max/200/1*eoVoNmNtQ-7WfdrCfc5a4w.png" /></a><figcaption><a href="https://medium.com/swlh/enterprise-ux-competitive-analysis-69d09a989bd7">Enterprise UX: Competitive Analysis</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee69dd711d16" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/if-the-mandalorian-showed-value-proposition-to-disney-ee69dd711d16">If the Mandalorian showed value proposition to Disney+</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[Is HX simply about doing UX right, or is it more?]]></title>
            <link>https://uxdesign.cc/is-hx-just-doing-ux-right-or-is-it-more-d7690063307e?source=rss-5dc7602b0ba8------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7690063307e</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[hx]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Justin Jolley]]></dc:creator>
            <pubDate>Wed, 27 May 2020 20:20:27 GMT</pubDate>
            <atom:updated>2020-07-10T12:59:24.086Z</atom:updated>
            <content:encoded><![CDATA[<h4>From UX to CX to HX.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N1fdZt-gpzPuEAa1IhU2wQ.jpeg" /><figcaption>Not my mom…or me</figcaption></figure><p>When I was a young whippersnapper my mother took it upon herself to pass down to me the grand skill of playing the accordion. I know, you’re saying in your head, that’s my favorite instrument too!</p><p>Now we did not come from a long, proud heritage of people where this instrument was a part of our culture and DNA. For some odd reason though we had an accordion in our home growing up. When many children are forced to plunk out the keys of chopsticks and Mary Had a Little Lamb, I was introduced to the sweet cacophony of the sounds emitted from the accordion.</p><p>I learned the ins and outs of playing the keys while expanding and contracting the bellows. It was always amazing to me how far I could extend the device and really open it up, to expose new sounds. When you explored the full length of the instrument you really got to know more and see the fullness and the potential of your interactions. The device is deceptive and at first you think all you are doing is confined within a medium-sized, awkward, defined space. However, it’s when you extend yourself, put in the effort and explore further you can see that there is more. Oh so much more. This is Human Experience Design for me.</p><p>When I first heard about HX I started to wonder if this wasn’t just describing the right way to do UX. When I’ve heard HX or Human Experience Design described many times it seemed like it was putting too narrow of a definition on what UX is. However, thinking about it a bit more it doesn’t have to be a competition but rather a way to further describe how to do experience design well. Can we approach it with more rigor and maturity? It’s thinking more holistically about designing experiences that’s more inclusive, is involved much earlier in the journey, and is from a richer and multi-dimensional…a more real-world human perspective. It doesn’t put blinders or walls up to what your playbook addresses when interacting with people, it opens it up and includes all the messy pieces that are the reality of our lives.</p><h3>The Evolution and Maturity of the X’s</h3><p>Let’s dig into this more and look at the evolution from UX to CX to HX. These days there’s always a new X tacked onto the ends of words to talk about experiences. It’s funny too because as they talk about frameworks, methodologies, processes, and tools, it seems like at their core are many of the same things that always existed in the beginning of UX. I think this is to be expected as any general area of study is diversified, and the studies become more faceted and mature; they all build on a common core of human-centered design.</p><p>So just what is HX? Like many terms and titles in UX, it depends. It depends on who you ask. I’ve seen a number of interesting things pop up, but at the core they are all talking about the <strong>Human Experience</strong> of interacting with not only a product, but a brand and company in a larger way. The interactions are more complete and multi-dimensional and more fully represent how messy and complicated our work and time on this planet can be. I see it as a more holistic approach to the experience design where you consider not just the customer and end user, but all those who have come along and had an effect somewhere along in the journey.</p><p>To break it down further, let’s look at the evolution of experience design.</p><p>User Experience — User is the end user who uses the product or goes through an experience. This is the experience prime, the intended digital experience in the case of software design. This is the flow, interaction, layout, and visual design of the experience. This is the people clicking and tapping on the bits and pieces we have designed to accomplish their tasks.</p><p>Customer Experience -Customer is the one who purchases the product. This can reach beyond the digital and encompass all the touch points that a customer might interact with. Think of a journey and the digital and non-digital touch points that a person interacts with when becoming acquainted with a product or experience, researching it, getting recommendations, obtaining information about the product or experience, interacting with a website/store, purchase, delivery, customer support and post purchase interactions to name a few.</p><p>Sometimes the customer and the user are the same, but in many cases they are not. There are many instances when the end users of software or experiences are not the ones with purchasing authority or means. There are managers, directors and others who gather input at times, but are the ones controlling budgets, holding the corporate cards and making the purchase decision and may never use the product or experience.</p><p>Human Experience -Human experience is more holistic from my point of view. It’s looking at everyone involved in the creation of a product or experience from the design and development to the purchasing and usage of it. It’s a 360 degree view, more multi-dimensional than a simple customer journey. Think of a human experience journey map as having multiple interactions by a cross-functional group of actors instead of one actor stopping at points along the way. It’s more realistic as we are rarely entities unto ourselves. We have purchasing departments, accounting, customer services and countless other touch points of people that contribute to decisions being made around the lifecycle of experiences that make up a product.</p><p>Thinking from just the perspective of the customers (not just teams and people within your organization) you can start to see how other people may bring more realistic, multi-dimensional aspects into an experience map. This becomes less rigid and narrow of mapping of the true experience and better represents all the players and interactions that happen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vDcF4k4g4DDPqKMv" /></figure><h3>Who Is My Customer?</h3><p>What you do is consumed by more than just the end user. Human Experience Design has us thinking about all the people involved with what we do. I like this because it makes me a better, well-rounded professional. Not only am I looking at how I’m delivering value to the end customer, but all those I interact with along the way. When a designer designs a component, they have to gather research from customers, requirements from stakeholders, interact with a product owner, multiple discussions with developers and QA teammates, marketing, sales, product and more at times.</p><p>As a designer you could think about how an idea for a project originates and the people you interact with. Have you thought about evaluating your interaction with them, are you measuring OKR’s/KPI’s with your those relationships? Do you provide a design system that third-parties use, how can you improve the consumption of your system? How do you infuse the brand guidelines from marketing into what you do or work with the physical designers of products if you have them? There are so many people involved in what you do before you even approach a customer or user.</p><p>Then as you focus more inward, you can also start looking at how you interact with your team. How do you collaborate with a product owner to gather requirements and research, how do you involve the teams in the design of a product or experience (is it just you and your sketchpad coming up with solutions?), how do you work with developers and QA to communicate design and interaction, how do you interact with CAB’s, alpha and beta testers and customers in production? There are so many touchpoints you can think about beyond did I do a good heuristic analysis, gather quantitative and qualitative data and produce a product that delights the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/826/0*szxGu4jB5Y0xJtZZ" /></figure><p>This list is by no means meant to be exhaustive, but to help you stop and think of all the departments, teams and people you interact with as you produce the parts of the product and experiences within your organization.</p><p>One of my favorite worker champions, Sir Richard Branson has sound thinking, that if we take care of the employees, they will take care of the customers. He said, “Clients do not come first. Employees come first. If you take care of your employees, they will take care of the clients.” This has been sound business advice for the Virgin Group despite recent troubles. It does help you look at things from a different perspective and how affective it can be at looking at the whole human experience of our businesses.</p><p>Deloitte Digital has done some good work on what they call the <a href="https://www.deloittedigital.com/us/en/blog-list/2019/we-re-only-human--exploring-and-quantifying-the-human-experience.html">HX Quotient</a> to help quantify the human experience. Their <a href="https://www.deloittedigital.com/us/en/blog-list/2019/we-re-only-human--exploring-and-quantifying-the-human-experience.html">HX quotient</a> takes into account the customer, workforce and partner to produce insights into what they build.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*VtiVPGeGSaOC2yf9" /></figure><p>This speaks to me as I’ve seen organizations as they mature focus on the experience of various customer types as well as the employee. I’m grateful that many organizations are now turning the power of experience design on interaction with it’s employees. Should we only measure the NPS of our customers or should the temperature of our teams be measured with HR as well? Deloitt’s workforce component of the equation is a measure of this.</p><p>I think aligning our experience design strategy to be more inclusive like this has the benefits of human interaction and coming closer to delivering experiences that meet the needs of the obvious and not so obvious customers throughout the whole interaction of our journeys in a multi-dimensional approach.</p><p>Deloitte is a consulting firm and so it’s equally as important for them that the companies they partner with are happy and engaged as well. In my industry, we rely on thousands of entrepreneurs and distributors to sell our products. They are a customer, but not the customer in many cases and we need to think of them differently as their needs are not the same as someone buying a product or service. They are partners with us in building our business, when we succeed, they succeed and vice-versa. If we were just to focus on the end consumer of our products though we would be missing a great opportunity to provide data and tools for the distributors, our partners in business. We need to understand how they do their work and build their businesses as much as how the end consumer likes the physical products we make.</p><h3>HX Lends Itself to be More Inclusive</h3><p>I’ve recently had the privilege in talking with Dr. Eric Shaffer who founded the Human Factors International organization. He reminded me of something that I’ve been looking into further, and that’s how we can be more inclusive in our designs. As I’ve studied Design Thinking and Design Sprints, I’ve come to see the importance of having cross-functional teams participating in the design of our software. We don’t want our developers to become just order takers, we want them to be able to think and reason for themselves. We don’t want the onus to be solely on the product or experience owners to come up with what should be produced and when. We want the work to be done by the team. It’s also never good to have a designer making large design decisions without the team being involved.</p><p>Tim Brown from IDEO has a saying I’m growing to love and question at the same time. He said, “Design may have its greatest impact when it’s taken out of the hands of designers and put into the hands of everyone”. Part of me screams, yes, that’s the way it should be done! Then the designer in me goes oh, wait. Thinking it out further though, designers should become the shepherds and facilitators of teams thinking about design as a solution to problem solving, rather than off in a corner with Sketch/Figma twiddling with the pixels. This is a much greater and more fulfilling role. There is a greater contribution and opportunity to deliver value for our customers and organizations.</p><blockquote>“designers should become the shepherds and facilitators of teams thinking about design as a solution to problem solving, rather than off in a corner with Sketch/Figma twiddling with the pixels. This is a much greater and more fulfilling role. There is a greater contribution and opportunity to deliver value for our customers and organizations”</blockquote><p>I’ve been working on putting together training on design thinking and how it could be embraced better by our agile teams and not just the experience designers. Dr Schaffer reminded me of something from my background, and that is that UX should live outside of the efforts to design and develop software. It is an engineering endeavor and we need to be partners in that work. It should not be a them vs us situation but a scrum team doing just enough work to get the sprint across the goal line.</p><p>Most of my past was from the point of a designer/developer. I usually sat side-by-side with the developers, gathering insight from users, getting their input on the capabilities of our systems, and working to implement the design in our code. I wrote Perl, ColdFusion, PHP, C#, Java, and then a bit into modern JavaScript frameworks all the while shepherding the CSS base styles and component design.</p><p>My work never was separate from the teams work. We sat together and worked on the same features in the same sprints. Somehow we got off the tracks though and made the playbooks about a separate study and implementation of experience design work. Somewhere we gained our own Jira boards and streams of work. The upside was that we were a real team contributing to the understanding of our customers, the downside was that by doing that work outside of the team focus we often relegate all our great discovery and insight to be largely ignored. How many of us have found amazing insights into our customers but that understanding just sits in a report and is never consumed because it wasn’t in-line with a sprint? A teams cognitive load has a finite capacity and many times if research isn’t relative it can overload the team and not be consumed regardless of the amount of money that it can earn/save a company.</p><p>I think Human Experience Design can help us take a step back, make sure that the work we’re doing involves all the humans we work with and have the important work we do become an integral part of the understanding of our whole teams. We are humans and we work in the messy middle, in often complex environments where we struggle to find places to add value. If we look at this from how we as humans interact with those around us more, I think we can make the work we do more satisfying for us and more effective for those around us.</p><h3>Doing the Right Thing</h3><p>I have a great VP that I’ve had the pleasure of working with that always encouraged us to do the right thing. I also have a great designer on my team who is zealous about ethical design in UX.</p><p>I believe that Human Experience Design helps us to do the right thing more often than not. If we look at the outcomes more of what we’re doing we can better make sure that what we give to the customers is not only valuable for them now, but has their best interest at heart for their future. Are we sacrificing revenue this quarter for doing the right thing for our customers? Stopping to think about how what we design affects us as human beings can help us from falling into the trap of delivering something that may come back to haunt us in the future.</p><p>Along with all our OKR’s and KPI’s, do we have an acronym that measures the ability to do the right thing? Are we focusing on the life-time of our customers, their well-being or are we just focusing on the next quarter.</p><p>With the state of commerce, social norms and how people are interacting with each other having an eye out for the overall human experience is a good idea. The normal flow and interaction as well the need for basic human connection and trust of people has changed. Things they never stopped to think twice about are different now.</p><p>I believe it has heightened the two extremes. We see people who did not have an outward mindset continue to pull in and worry about themselves (basic self-preservation) feeling an ever growing discord that feeds fears and anxieties. On the other hand, we’ve seen others who were in-tune with people and their emotions become greater givers and nurturers focusing on the wellbeing of those they interact with in all walks of life from their families, church, work and other organizations and affiliations. These ties, emotions and drives should become part of our conversations when discovering motives, needs, tasks and desires that customers all around us are focusing on.</p><h3>In HX, Sometimes I Am the Customer</h3><p>One of the interesting bits that I’ve heard in the discussion of Human Experience Design is that we, at times, are the user.</p><p>I know, I know all my training, indoctrination and experience serve to remind me that I am not the user. In fact, on my old MacBook I had a Gandalf sticker where the Apple logo illuminated his staff. Directly above that I had my sticker from NNg certification that in a booming voice shouted, “You are not the user!” With as much force and gusto as Gandalf declared to the Balrog (please pardon my geeky moment) I’ve routinely echoed this to people in a satirical way. This should serve to say that I don’t say this with out a little trepidation and reserve.</p><p>If we’re on the employee journey however, we are at times consuming components built by us or others on our teams or using internal systems. We CAN be the users. This flies in the face of what we’ve always learned as experience design practitioners. We are too close to the system, we know too much, we can’t be the customers. Yet at times in places like employee stock purchases, employee product stores, users of our own design systems, we are the customers.</p><p>It also helps support the practical approach to UX as there are times when we don’t have the time and resources to test everything. Sometimes we have to stand on prior internal research, standards, external research and anecdotal experiences to do some work. We would always prefer to have better insight, but in the real world there are politics, heightened deadlines, pivots and the like that inhibit our ability to do perfect UX work.</p><p>There are also times when we just need to update a component to add a new feature that we don’t have the ability to do ethnographic studies, create a prototype, conduct a usability study and synthesize all the data from around the globe. Sometimes we do work outside a discovery sprint where we just have to use what we have to make decisions and us as human beings can be the customer.</p><p>In looking at Human Experience Design I think this isn’t just another acronym or iteration on UX or CX, but a better way of looking at what we do in each of those. Approaching it from a more realistic and inclusive way.</p><p>There are a number of aspects that i’ve put forth so far, including:</p><p>Evolution and Maturity of UX has brought us to HX.</p><p>We can benefit from asking who are our customers, beyond the person buying our products?</p><p>How can I be more inclusive in my design efforts and mature the team as I learn.</p><p>Do the right thing, long-term for our customers and companies internally and externally. This will become more important in a time of heightened social stress.</p><p>Sometimes I am the customer and have great insight.</p><p>So the next time you are building out a persona, exploring a journey map, discussing the requirements for a feature, take a step back. Expand the accordion of your mind and think of all the other personas, strike that, humans that are involved in the production and see if you can change your interaction just a bit. If this helps or works for you, I’d love to hear about it.</p><p>Head ’em up, move ’em out!</p><h3>Articles in this series</h3><p>This series seeks to reexamine the approach and vocabulary of<strong> UX design methodologies</strong> and translate them into <strong>experience practices</strong> (minus the UX and design terms) that help us to be more inclusive, align with our teams better and interact with the full spectrum of humans as we design experiences.</p><h3><a href="https://uxdesign.cc/how-to-discuss-experience-design-and-not-sound-like-an-arrogant-arse-b4dc76312164">How to discuss experience design and not sound like an arrogant arse</a></h3><p>Sometimes we struggle connecting with our teams and it may just be our approach and interaction.</p><h3><a href="https://uxdesign.cc/personas-are-now-called-roles-4bc9e7f5a99">Personas are now called “Experience Roles”</a></h3><p>Personas really look at the hats or roles that people play and the things they do that make them different from others.</p><h3><a href="https://uxdesign.cc/taxonomies-are-now-experience-organizations-1303643aa7ee">Taxonomies are now “Experience Organizations”</a></h3><p>In life, it’s important to learn how to organize things. Let’s look at how we can do this with our teams.</p><h3><a href="https://uxdesign.cc/is-hx-just-doing-ux-right-or-is-it-more-d7690063307e">Is HX simply about doing UX right, or is it more?</a></h3><p>Human experience design is a more holistic approach to experience design.</p><h3><a href="https://uxdesign.cc/how-co-designing-can-reduce-your-rejection-and-stress-levels-as-a-uxer-6b905a7d6a86">How co-designing can reduce your rejection and stress levels</a></h3><p>You’re not a magician, cowboy, ninja or superhero; stop trying to be one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7690063307e" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/is-hx-just-doing-ux-right-or-is-it-more-d7690063307e">Is HX simply about doing UX right, or is it more?</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[Enterprise UX: Competitive Analysis]]></title>
            <link>https://medium.com/swlh/enterprise-ux-competitive-analysis-69d09a989bd7?source=rss-5dc7602b0ba8------2</link>
            <guid isPermaLink="false">https://medium.com/p/69d09a989bd7</guid>
            <category><![CDATA[data-wrangling]]></category>
            <category><![CDATA[competitive-analysis]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Justin Jolley]]></dc:creator>
            <pubDate>Sat, 03 Aug 2019 02:01:01 GMT</pubDate>
            <atom:updated>2019-12-17T18:38:10.009Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Enterprise UX Methodologies Series: Wrangling the Data of Competitive Analysis</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mdau9ho8MHmb8NwscrP8hg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/77/1*I17qn6avK3bptGcDT8tgGA.png" /><figcaption>Competitive Analysis</figcaption></figure><p>Sometimes integrating modern UX into a corporation can feel like wrangling a herd of cattle, you have to keep your eye on so many different moving pieces. Some processes fit nicely in with the business. Others have to be corralled and prodded into working in the organization, with the ultimate goal being able to deliver value to the customer by representing them and their experience accurately. I believe competitive analysis is in this state right now and the more I read the more there appears to be a glaring hole. There seems to be a lack of ability to align the UX practices with the research done during the competitive analysis. I have browsed a number of sites with recommendations and “easy steps” to create them, but I just haven’t seen any that take the approach from a UX design perspective.</p><blockquote><strong>Are you considering:<br>-Devices &amp; User Journeys<br>-Personas<br>-Regions &amp; Markets<br>-Product Lines &amp; Brands<br>-Product Lifecycle<br>-Assumptions</strong></blockquote><p>Now you may say to yourself, “self I do competitive analysis all the time”. If you’re going through a prescribed process with rigor and structure then great, please let me know about it. However, too many times I’ve seen this done more as an ad-hoc, unstructured process where people <strong>‘look at what Amazon is doing’</strong> and make their decisions based on that. I don’t want to kick dirt on that process because it is a good start and better than nothing, but I think if we just look a little more critically and apply a few steps to the work we can get even better thinking and results out of it that better represent our customer’s needs.</p><p>As I’ve had the chance to work with big name, high dollar companies that have fancy templates, the data seems to predominantly fall short when it comes to the research. Even though we repeatedly review our business model, customer journeys and personas these important areas always seem to fall down and not be represented when the findings are presented.</p><p>In all fairness, this information isn’t always readily available, but if we at least mentally plod through it as a mental exercise I know we can gain insight by putting our empathy to good work and try to understand how we can best serve the customer. In the end, this is what takes your organization to the next level. By not settling for what’s readily available by just browsing, you are already setting yourself apart from the run of the mill practitioners and agencies.</p><p>Let’s dive in then and think about the different methodologies, process and tools we use for UX and how we can apply those to competitive analysis.</p><h3>Devices &amp; User Journeys</h3><p>As any good evaluation of user’s needs, we need to understand the context of use in order to design a solution. Part of this is understanding our customers journey through our entire system as well as through the features we’re trying to refine or design. In this day and age, we surely all understand that users rarely have an experience completely on a single device. Many times, users start out on a mobile device, move to a tablet, dive deeper into their exploration on a desktop and then possibly back to other devices for final action or purchase.</p><p>This tells me that any true evaluation of our competition must also follow those same principles. We need to explore the experiences on mobile, tablet, laptop and desktop and see how the experiences differ and what the transitions may be like.</p><p>It’s not uncommon in today’s world of responsive and adaptive designs to have an experience that differs according to the device. This is always something I push for as a designer, that we don’t simply make our buttons wider and allow more text when moving from mobile to larger devices. One of the main purposes behind the mobile first thinking is to distill down what the essence of the feature would be, and then as space allows, improve the experience.</p><p>We need to understand what the hand-off might be and try to reduce the cognitive load or barriers that would prohibit people from moving from device to device. If we check for these opportunities in our competition it will help us see what is and isn’t there, and put ourselves in the shoes of someone going through that process so we can better see and feel what the experience <strong>should</strong> be like.</p><p>Having your user journey maps readily available can help you think through the journey you’re evaluating, and compare not just that feature, but the points pre and post, to see how you can make better entry, and exit into that feature.</p><p>I’m a big fan of the Heath brothers, and in their book <a href="https://heathbrothers.com/the-power-of-moments/">The Power of Moments</a>, and they talk about ending on a peak or high note. While reviewing your journey, you can see if this is a good spot for creating one of those moments. In order to create something that stands out, you must provide an experience that reaches beyond the norm or of what people expect. If you look at your competition through this lens, then it will help you think about how you can exceed the norm and truly design something that will delight the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PrA9I2NAjk51t1LlazxDFg.png" /></figure><h3>Personas</h3><p>If the exploration of devices leads us down the customer journey path and the devices at each touchpoint, likewise we need to explore the various personas associated with any feature. Just as we’d take into account the needs and requirements for various users when designing we need to have our exploration of competitive analysis keep those same personas in mind.</p><p>Simply presenting a review of an experience or design from one dimension doesn’t give us an adequate representation of what we’re competing against. Providing the search results experience or any other feature we’re comparing is the same for all users, and defeats the purpose of all the work we put into creating personas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/866/1*aVwws9T4kVkD3KPw7RwS3Q.png" /></figure><p>Surely, we can see how search results could be different for a casual customer vs a repeat customer. The experience should be different for non-authenticated user’s vs logged in members. In this day of social media surely the needs of a customer who’s simply browsing for their own consumption vs someone who is a brand affiliate and wants to share product imagery, description, FAQ’s and a myriad of other information would want a different experience a set of tools available for them on a search results page.</p><p>For these reasons whenever we look at the competition, we need to evaluate how our different personas experience their site and how should they be experiencing ours? What are the <strong>tools and information</strong> that each of our personas need and are we or our competition currently meeting or exceeding those needs?</p><h3>Regions &amp; Markets</h3><p>For an enterprise this is another important factor to take into consideration; the competition and market leaders may differ from region to region. Amazon may be one of the sites you look at, but is that the leading e-commerce platform in Asia or Europe? This is especially true for more boutique type product lines. There are generally more niche players that vary from market to market.</p><p>It’s probably helpful to have a matrix of the competition for each of the markets your company sells in. This may necessitate that you use different research agencies if you’re outsourcing these type of research activities, but you can’t make the error of thinking that the research that’s done for one market will suffice for all others. This is pretty much table stakes for any global organization but it bears repeating as I’ve had research done that only takes one region into account.</p><p>Again, I can understand why it’s difficult for a small company, researchers or agency to have the touch points and insight into all markets. Having UX resources in various global offices can help provide this information.</p><p>If you don’t have those resources in place there are some tools that can help with this type of research. Take for instance <a href="https://app.buzzsumo.com/research/content">Buzzsumo</a>, great name, right? <a href="https://app.buzzsumo.com/research/content">Buzzsumo</a> allows you to see top performing content around the globe.</p><figure><a href="https://app.buzzsumo.com/research/content"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cnVastmLVWTX-lTn2pSdEA.png" /></a></figure><p>Tools like <a href="https://www.similarweb.com/">SimilarWeb</a> and <a href="https://www.alexa.com/siteinfo">Alexa Rankings</a> also allow you to look at competitors and similar websites by similarity or rank with global results.</p><figure><a href="https://www.similarweb.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*97wHk4U6gwhj0nzeGASmcA.png" /></a></figure><h3>Product Lines &amp; Brands</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*_MYN7koKZ676dNZMDCD43w.png" /></figure><p>Another aspect is to organize these competitors along your product or brand lines. Often times there are multiple dimensions that you may be competing in and various competitors may align in one dimension and not another.</p><p>You may have competitors that compete with you along brand lines and others along experience lines. You may have competitors that are direct competitors in your industry while others are more indirect. With the explosion of the gig economy it may be competitors that align with your same business opportunity.</p><p>This is another level of intricacy, but I’ve rarely found a company that has the same business and content strategy for all their product or brand lines. This will be something you’ll want to work on with the marketing or sales team, but it will be helpful to align with these teams to know what are better understand the efforts currently being put into each of these?</p><h3>Product Lifecycle</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/558/1*ZiIrMGdzHT413eCp4YpEBw.png" /></figure><p>Additionally, it may be helpful to evaluate where we and our competitors are in a product lifecycle. A company with a product in the introduction and growth stage may have features and experiences that are completely different from that same product when it’s in a more mature state or even in decline. The number of features, and level of experience can all vary depending on where that product is in the lifecycle. Ask yourself if the feature on your competitors’ site is in that introductory or growth state, and what the opportunities or exclusions you’re going to make with your products in that same phase?</p><p>Possibly you’re in the growth phase of your product while others are in the maturity phase and you want your feature set and experience to be different. Many companies are great at this, as they don’t want to bring their best feature set to the game at the beginning of a product lifecycle. They wait for others to take that first step into the pasture and see what prairie Frisbees they step in. They learn from others mistakes and improve on them. Apple is a great example of this. They aren’t always the first to market, but they’ve built a reputation for seeing the pitfalls and coming to market with a better experience.</p><p>This brings to mind a few ideas that can converge. One of Lean UX and one from one of my favorite speakers Simon Sinek and his talk on <a href="https://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action?language=en#t-653840">Start with Why</a> where he talks about the <a href="https://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action?language=en#t-653840">Law of Diffusion of Innovation</a>.</p><p>With the proliferation of companies employing agile methodologies and we may not know if a certain competitor feature is a simple MVP with the major features coming in future sprints. Also with concepts like <a href="https://jeffgothelf.com/">Lean UX from Jeff Gothelf</a> are we sure that we’re not seeing the competitors skateboard or scooter version of a feature? Without taking these into account we don’t know where our competition may be with their development cycle. Any insights we may be able to glean or think about in advance can help us when applying this same thinking to our own design and development processes.</p><p>Moving on to Simon, he makes the point about “<strong>People</strong> don’t <strong>buy</strong> WHAT <strong>you do</strong>; they <strong>buy WHY you do</strong> it”. If you haven’t heard this talk go listen to it, it’s a great one. In there he talks about the <a href="https://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action?language=en#t-653840">Law of Diffusion of Innovation</a> that explains how, why and at what rate new ideas and technology spread.</p><p>This is important because of the need for UX designers, researchers and strategists all to realize the reason why they are doing work, which is to help the company meet the customer needs. If we’re not in a partnership and trying to understand how to solve the problem behind the problem for the business, then we’re not helping the company succeed. I’d much rather designers focus on adding customer value this way than being seen as the people who ‘<em>make it look pretty</em>’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W1YMJB196yz60Frs-cvtKw.png" /></figure><p>So yes, this is making things very complicated but if we’re not seeking to understand the whole business case, can we really fully help the business to the full potential?</p><h3>Assumptions</h3><p>I give credit to this next point to my colleague and buddy, Phil Burgess, who is a UX Research wizard and always reminds me of this when we’re doing competitive analysis.</p><blockquote><strong>“How do you know feature x is working for customer y?</strong> “</blockquote><p>You don’t know if you’re viewing part of an A/B test or if what you’re seeing is working for your competitors. That may be a sore spot for the company, but they’ve never had the time to fix it.</p><p>A good illustration of this is how often we hear, “well Amazon is doing it”. Yes, Amazon has a bazillion dollars and is doing a lot right, but according to many evaluations they may not only be the leader in that area, but their solution is only acceptable as shown here in the <a href="https://baymard.com/ux-benchmark/case-studies/amazon">Baymard evaluation of Amazon’s search functionality.</a></p><figure><a href="https://baymard.com/ux-benchmark/case-studies/amazon"><img alt="" src="https://cdn-images-1.medium.com/max/452/1*Vuzw0193fYo__dRyPGz5yA.png" /></a><figcaption>Baymard Benchmarks</figcaption></figure><p>This brings up NNg’s <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">10 Usability Heuristics for User Interface Design</a>. We can’t simply take competitors sites for face value, we have to look at them objectively and say yes, they may be one of the largest companies in the world, but is that right for us? Is this company following standards and good practices for this feature? Are our customers Amazon’s customers or Apple’s customers? If they are then great, you can employ <a href="https://www.nngroup.com/articles/end-of-web-design/">Jakob’s Law of Internet User Experience</a>, “Users spend most of their time on other sites”. You can then use this as a standard for your site, but if they are not the same demographic then maybe they’re not the perfect yard stick to be measuring by. All of this needs to be taken into consideration as we’re evaluating the competitive analysis data.</p><p>To wrap everything up like a hog-tied beast, make sure that when your producing a competitive analysis or receiving one from your UX research team or an agency that you don’t forget all the great UX processes and methodologies you’ve amassed, and don’t forget to use them in your analysis.</p><blockquote><strong>Are you considering:<br>-Devices &amp; User Journeys<br>-Personas<br>-Regions &amp; Markets<br>-Product Lines &amp; Brands<br>-Product Lifecycle<br>-Assumptions</strong></blockquote><p>Happy Trails…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69d09a989bd7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/enterprise-ux-competitive-analysis-69d09a989bd7">Enterprise UX: Competitive Analysis</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>