<?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 Carien Moolman on Medium]]></title>
        <description><![CDATA[Stories by Carien Moolman on Medium]]></description>
        <link>https://medium.com/@carien?source=rss-d25a0d79e797------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1WdWwVirLRqkPGKQUy6SBg@2x.jpeg</url>
            <title>Stories by Carien Moolman on Medium</title>
            <link>https://medium.com/@carien?source=rss-d25a0d79e797------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:21:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@carien/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[You really like this, don’t you?]]></title>
            <link>https://uxdesign.cc/you-really-like-this-dont-you-4713a811aa7d?source=rss-d25a0d79e797------2</link>
            <guid isPermaLink="false">https://medium.com/p/4713a811aa7d</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Carien Moolman]]></dc:creator>
            <pubDate>Sun, 18 Aug 2024 21:34:00 GMT</pubDate>
            <atom:updated>2024-08-31T19:14:54.127Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why <em>should</em> user researchers avoid questions like “Do you like it?” Why does this question or one of its close siblings keep on making an appearance? What are the biases to be aware of during user research? Why are open-ended questions better? Let’s talk about it.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zv8xvgYbaQISM6jmvzkAJg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@uxindo?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">UX Indonesia</a> on <a href="https://unsplash.com/photos/woman-in-blue-robe-using-macbook-Rf6lwwbsZB4?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><p>Many many years ago, I had the opportunity to attend a Google-sponsored Masterclass about Human-Centred Design (HCD) in Cape Town, the beautiful city I call home. It was an intense 2-day experience where we were shown the phases of <a href="https://www.nngroup.com/articles/design-thinking/">the HCD process</a>: discovering needs, defining problems, ideation, prototyping, and improving. We were given a light optional exercise to do on our own to drive the concepts home. At the end of day 1, all of us had sketchy hand-drawn mobile prototypes attempting to solve well-defined problems.</p><p>The facilitators recommended that we put our prototypes in front of one or two people (obviously, not necessarily our target audience but at least other, non-product human beings) that evening or early the next morning, and to listen and observe. We could then bring these observations back and see how they might help us improve or pivot our products.</p><p>Jokingly, one facilitator called out to the room: <strong>“And remember: don’t put words into your users’ mouths. Keep your questions open-ended!”</strong></p><p>She picked up a sketchy prototype that was lying around, held it up to us, and said with a smile: “So you can’t ask people things like<strong> ‘You really like this, don’t you?’</strong>”</p><p>There was laughter all around. No self-respecting user researcher would ask something silly like that! <em>Right?</em></p><p>Right..?</p><p>It’s almost 20 years later. Today, in my experience, user researchers continue to ask users that question during in-person, qualitative research, reporting on the answers gathered and making design decisions based on this dubious data. <em>Why?</em></p><p>Every Product Designer knows <a href="https://www.nngroup.com/articles/leading-questions/">that bias must be accounted for and leading questions minimised during user research</a>. We know that we must ask open-ended questions. We know that we are not selling our products during user research, but observing people with interest and curiosity to learn what they might do with our designs (or ideally, the designs of other designers!) when we’re not around.</p><p>Despite this, I still regularly come across user researchers who ask research participants the “Do you like it?” question during qualitative, one-on-one user research. They might change the wording slightly, but these are all problematic when asked by a researcher from a participant:</p><ul><li>how would you rate your experience of this?*</li><li>how easy is this to use?*</li><li>do you understand the content?*</li><li>how likely are you to recommend this to your friends or family?*</li><li>how empowered does this product make you feel?*</li><li>did you like it?*</li></ul><blockquote>*Researchers often add short lists of answers or Likert scales to these questions. These may be good (and necessary!) for quantitative data collection methods. During in-person interviews, however, these answers might just exacerbate the problem. The thinking goes: “If I add a list of answers and the answer selected is negative, I can ask the user ‘why?’” Unfortunately, the moment your participants discover that a negative answer means that they need to provide more explanation, they are likely to veer towards positive responses with even greater fervour.</blockquote><p>Research participants are highly unlikely to answer any of these questions honestly. They might even be <a href="https://www.cambridge.org/core/journals/judgment-and-decision-making/article/on-the-psychology-of-selfprediction-consideration-of-situational-barriers-to-intended-actions/2BED02612316051AC194A3C8655F5D47#"><em>unable</em> to</a>. Suppose a research participant is sitting with a researcher or the designer of the product being evaluated. In this case, <strong><em>the participant is highly likely to give a biased response whenever a question allows because participants want to please the researcher</em></strong>. This bias is powered by three factors:</p><p>1. <a href="https://onlinelibrary.wiley.com/doi/abs/10.1002/9781444316568.wiem02057"><strong>Social Desirability Bias</strong></a>: Participants are likely to provide higher ratings because they feel a sense of obligation or want to be seen favourably by you, the researcher, or the organisation you represent.</p><p>2. <strong>Fear of Negative Consequences</strong>: If participants believe their feedback could negatively impact their relationship with you or your organisation, they are likely to avoid giving low ratings.</p><p>3. <strong>Lack of Anonymity</strong>: When feedback isn’t anonymous, participants may be less honest, leading to skewed data that doesn’t accurately reflect user sentiment. Even if you reassure your research participants that their feedback will remain anonymous, they are not anonymous to you.</p><p>If people think that you or your friends designed a product and you ask them about it, they are likely to tell you what they think you want to hear. The same goes for participants who are incentivised to take part in the research. They might want to be invited to take part in research again.</p><p>In my experience, <strong>this effect becomes magnified when there is a power imbalance between researchers and participants</strong>. If you are part of the organisation for which you are doing research, and your organisation is big and renowned, or the driving force behind a product or service that your research participants truly need, the three factors — social desirability bias, fear of negative consequences, and lack of anonymity — will skew your data like a wrecking ball. I have taken part in research for organisations as a consultant and have done my best to introduce myself as such: it’s hard to tell whether people clearly differentiate between a “person researching her own organisation’s product” and a “person researching another organisation’s product”. I suspect the two often mush together in people’s minds.</p><p>Am I saying that we can’t ask people how they feel about a design or what they think about it? Not at all. If you are sitting right next to your participant and observing them getting increasingly frustrated with a task or getting hopelessly derailed, you should <em>absolutely</em> be asking open-ended questions. The responses will still be vulnerable to bias, though, and your <a href="https://www.nngroup.com/articles/first-rule-of-usability-dont-listen-to-users/">observations are likely to be more reliable</a>.</p><p>A classic scenario that every user researcher has experienced is this: a participant (let’s call her Alice) is given a task to complete. Alice struggles her dear heart out to get the task done. She clicks on buttons that shouldn’t exist and goes down rabbit holes that surprise even you, and after 10 minutes or more, she completes a task that should have taken her 30 seconds. You ask: “How was that?” Alice replies with a fleeting expression of worry: “Easy! Yes. It’s <em>really</em> user-friendly.”</p><p>To reduce this bias, it’s often better to gather quantitative data. Look at task success rates and durations analytically, and gather user satisfaction feedback through anonymous surveys or third-party tools that can objectively collect user responses without the direct involvement of the product team. Satisfaction ratings and NPS scores (if this is the metric your organisation prefers) gathered in this way are more likely to reflect genuine user feedback and provide more reliable data for decision-making.</p><p>The bottom line? If you’re doing in-person research, <strong>don’t ask people “Do you like this?”</strong> Don’t ask people questions where the answer is likely to be a wrecking ball in terms of its reliability for future design decisions.</p><p>In-person qualitative user research is incredibly valuable if it is done well and if the findings are combined with insights gained from quantitative methods. In-person qualitative user research is also very expensive. Use your time with people wisely. Empathise. Observe. You are not trying to prove that a product or an idea is great. You are discovering how people might interact with it and uncovering surprising behaviours and motivations.</p><p>I wanted to leave this post right here, but there is more to be said. There is a good reason why researchers, despite knowing that this is wrong, keep on asking “Do you like it?” questions in qualitative interviews. It’s often because stakeholders demand it. They want to know if people will like a product or a feature before investing in it too much.</p><p><strong><em>Side note</em></strong><em>: Interestingly, we can devise a trustworthy and reliable research method to find out how many people like a product or feature. But liking something does not mean that people will use it or buy it. You would be better off determining how many people </em><strong><em>need</em></strong><em> it. And this is a blog post for another day.</em></p><p>As the user researcher on the team, a big part of your job is to help your stakeholders to articulate their needs better. When your stakeholders ask you to find out whether people will like the new design, it’s your job to ask, with polite curiosity, “Why do you want to know this?” and to figure out whether they aren’t, in fact, hoping for an indication of <em>the number of people who are likely to use or buy the new design</em>.</p><p><strong>Asking a team to do user research to lower the risk of investing too heavily into a new design that not enough people will use/buy is a good thing to do.</strong> From a business perspective, user research exists for this very reason. Let’s say your stakeholders are happy with this as a research question: “How many people in our target audience are likely to use the new design?”</p><p>Now <em>this</em> is the kind of question that User Research exists to answer. It is a question that <em>can</em> be answered with a well-planned combination of <em>both</em> quantitative and qualitative research activities, depending on the product type. <em>None</em> of these activities will involve user researchers approaching people and asking: “Will you use this?” People are notoriously bad at predicting their future behaviours and <a href="https://www.muledesign.com/blog/research-questions-are-not-interview-questions#:~:text=Your%20research%20question%20is%20simply,and%20methods%20available%20to%20you">research questions are not interview questions</a>, and we must not confuse these. Once again, this phenomenon deserves a blog post on its own!</p><p>If you have read all the way to this closing paragraph, then thank you. I hope this is of some value to you. Please share your stories as a user researcher! I would love to hear them.</p><p>I’ll conclude with <a href="https://designthinking.ideo.com/">words that are not my own</a> but that resonate deeply, and speak to why I believe we need to spend one-on-one time with the people we are designing for:</p><blockquote>The designer’s mindset embraces empathy, optimism, iteration, creativity, and ambiguity. And most critically, <strong>design thinking keeps people at the center of every process</strong>. A human-centered designer knows that <strong>as long as you stay focused on the people you’re designing for — and listen to them directly — you can arrive at optimal solutions that meet their needs</strong>.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4713a811aa7d" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/you-really-like-this-dont-you-4713a811aa7d">You really like this, don’t you?</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[It takes a village to do human-centred design]]></title>
            <link>https://uxdesign.cc/it-takes-a-village-to-do-human-centered-design-e856a9163fa2?source=rss-d25a0d79e797------2</link>
            <guid isPermaLink="false">https://medium.com/p/e856a9163fa2</guid>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[lean-ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <dc:creator><![CDATA[Carien Moolman]]></dc:creator>
            <pubDate>Sat, 03 Jun 2023 06:53:05 GMT</pubDate>
            <atom:updated>2023-06-06T06:44:17.766Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Laptop, sticky notes, and sketches on a desk, with three people gesturing" src="https://cdn-images-1.medium.com/max/1024/0*23H0Y0jQzxbTXlKA" /><figcaption>Photo by <a href="https://unsplash.com/pt-br/@uxindo?utm_source=medium&amp;utm_medium=referral">UX Indonesia</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Human-Centred Design is not a solo mission. It never was and never will be. It is a collective effort. HCD is an inclusive and co-creative process that relies on the combination of many kinds of expertise. It was <a href="https://web.mit.edu/jrankin/www/engin_as_lib_art/Design_thinking.pdf">made to solve wicked problems</a> and fully embraces the <a href="https://en.wikipedia.org/wiki/Dusty_Baker">Dusty Baker</a> quote:</p><blockquote>“Everybody knows something, and nobody knows everything.”</blockquote><p>HCD requires a culture of openness, rigorous experimentation, and empathy, and a team of people working collaboratively towards a clear goal or set of goals that are prioritized in a human-centred way.</p><p>If you are a User Experience designer or Product designer working alone, receiving briefs and producing deliverables (whether these are wireframes, designs, product specifications, usability testing debriefs, synthesized insights from user research in reports, analytics, designs, or prototypes), but your team and organization aren’t involved in your research and problem-solving process, your efforts to build a human-centred product are likely to be ineffective. For human-centred design to do its magic and result in products/services that solve real human problems in a way that is engaging and kind, you need a team of people who understand and embrace a few principles:</p><ul><li><strong>Ideas are fallible.</strong> And even great ideas can fail because of poor execution. Rigorous experimentation is how you prevent this from happening.</li><li><strong>People often don’t behave in the way that we imagine they will.</strong></li><li><strong>Ideas need to be tested with target users</strong> to see how they respond to them (quantitatively) and why they respond in the ways that they do (qualitatively).</li><li>Findings from responses must be <strong>central</strong> in determining whatever is designed or built next. (This is why it’s called human-<strong>centred </strong>design).</li><li><strong>The faster &amp; cheaper the team can learn from experiments, the better</strong> for the business (read <a href="https://theleanstartup.com/book">Eric Ries’s legendary book</a> for a <em>very</em> powerful illumination of this).</li><li><strong>HCD begins with empathy.</strong> Empathy means <strong>spending time with your users, in order to feel and think what they are feeling and thinking</strong>. It needs to be evenly distributed amongst your team members, and not be the domain of a single team member or function.</li></ul><p>From the good folks at <a href="https://designthinking.ideo.com/faq/whats-the-difference-between-human-centered-design-and-design-thinking">IDEO</a>:</p><blockquote>Human-centered design is about cultivating deep empathy with the people you’re designing with; generating ideas; building a bunch of prototypes; sharing what you’ve made together; and eventually, putting your innovative new solution out in the world.</blockquote><p>Experimentation means that you need to plan and facilitate experiments, regularly. It means that you need to recruit groups of target users and run unbiased interviews or usability tests with them. Or you need to create cohorts of users and keep a close watch on specific analytics in specific versions of your product. Both of these kinds of experiments require planning and collaborative execution to deliver value. It simply isn’t a one-person job. The learnings from the experiments (or research activities) must be shared and taken to heart by those responsible for the design and development of the next round of experiments.</p><p>If your organization is not ready and able to experiment, or for whatever reason, is not ready or in a position to take user feedback to heart and respond by solving the problems discovered, your human-centred design efforts will fail. Your business or team needs the:</p><ul><li>Capacity (process and resources), <strong>and</strong></li><li>Willingness (culture) to respond to users’ issues.</li></ul><p>Consider whether both of these — the capacity to respond and willingness — are there. Are you in a position to influence either of these, if they are not there? Can you influence the way that your teams are structured, the kinds of roles and skills people are employed for, the way that processes are managed, and how work is prioritized? Is there an opportunity for you to change the way that people in your business think about their users? Do you have allies who will support you if you try to introduce a more human-centred way of working? Do people in your company care about their users’ well-being at all, (or is there an almost overwhelming focus on user engagement purely for the sake of profitability?) Has your team or organization already given HCD a go in some way or form, or are you the trailblazer? Are you a natural trailblazer?</p><p>If your answer is mostly “no”, and you are the UX Designer in an organization that doesn’t want to listen to its users or to the synthesized findings of user research, and/or doesn’t have the capacity to respond to those findings, you need to reconsider your position and your role.</p><p>The success or the failure of the products you are working on depends on how rigorous and efficient your team’s experiments are, and how regularly you make improvements based on each experiment you run. It requires a team effort and intense collaboration.</p><p>The success or failure of your products does not depend on your capability as a designer to produce deliverables on time. It’s a fine skill set to have, but you need an empathetic team working together to ensure product success over time.</p><p>There are successful products and services that have been designed and built without any formal user experience discovery phase preceding the first Sprint. This is sometimes cited as a reason to abandon qualitative user research altogether. In my experience, a product discovery phase that is well-planned and executed in as Lean a way as possible, always adds value. But it can be replaced with a different kind of discovery phase, where the first real version of the product or a functional prototype “is” the experiment. Entrepreneurs, who are often more optimistic and less risk-averse than most people, will often prefer to go this route. But once that first version of the product is launched, you will be faced with a multitude of improvements to make and requested features. Your backlog will need to be prioritized in some way, and this is where HCD is a business’s friend, *if* it is part of the team’s way of working and of thinking about the product being built. If the findings from regular, well-executed, qualitative user feedback are not taken into consideration, then the role of the UX Designer is diminished, and might be better described as a UI Design and/or Wireframing role — also a demanding and specialized position, but certainly not one that can be held responsible for the success of the product.</p><p>I have often seen talented UX Designers in this position, some becoming extremely frustrated and disillusioned. I have been there, and it’s a tough place to be, especially if you don’t consider all the external factors playing a role in the success or failure of your work. If this is you, pause. Consider your role and your organization’s culture, mindset, and resources.</p><p><strong>Do what you do to the best of your abilities and have a kinder view of where your responsibilities end, or are allowed to end.</strong> Reach out to people in your team, be brave, and include them in your early design process as much as possible. Or find a different way of working that complements your organization’s capacity and culture. If you do, share it with the rest of us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e856a9163fa2" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/it-takes-a-village-to-do-human-centered-design-e856a9163fa2">It takes a village to do human-centred 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[Five Essential Qualities of Kindness and how to Design for them]]></title>
            <link>https://uxdesign.cc/kindness-in-product-design-9516407439ee?source=rss-d25a0d79e797------2</link>
            <guid isPermaLink="false">https://medium.com/p/9516407439ee</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[editor-picks]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Carien Moolman]]></dc:creator>
            <pubDate>Thu, 29 Sep 2022 14:35:38 GMT</pubDate>
            <atom:updated>2022-09-30T07:53:52.283Z</atom:updated>
            <content:encoded><![CDATA[<h4>Kindness is empathetic, inclusive, beautiful, sees suffering, and reflects kindly. But more importantly: it is powerful. Here are some thoughts about kindness in Product Design and how we might build kinder products.</h4><figure><img alt="A picture showing 5 ellipses with the words: Kindness is empathetic, is inclusive, sees suffering, reflects kindly, and is beautiful." src="https://cdn-images-1.medium.com/max/1024/1*3ZjQbt6uKKYkmdGgrrRxaQ.png" /><figcaption>Essential parts of Kindness in Product Design</figcaption></figure><p>I was an anxious child. It didn’t help that by the time I went to Grade 3, I was in my third primary school. My parents moved around a lot. They both worked full-time, which was unusual for the neighbourhoods we lived in. As was being in after-care. I was not as well-groomed as the other kids in my class, and I knew it.</p><p>But I had this 2nd-grade teacher. One day she walked past me after school and asked how I was doing. I didn’t know how to respond to a grown-up who seemed to just want to talk to me, and blurted out: “3rd grade is so much harder than 2nd grade! I can’t keep up!”. She didn’t smile or laugh. She just looked at me, very seriously, and said: “Yes, you can. You <em>can</em>.”</p><p>It was a moment of kindness. It was a little strange. Quite frankly, she was a little strange. But I’ll never forget it.</p><p><a href="https://www.nytimes.com/2022/07/21/nyregion/werner-reich-dead.html">Werner Reich</a> was a holocaust survivor &amp; magician and said this:</p><blockquote><strong>“If you ever know somebody who needs help, if you know somebody who is scared</strong>, <strong>be kind to them</strong>. If you do it at the right time, it will enter their heart, and it will be with them wherever they go, forever.”</blockquote><p><em>“It will be with them wherever they go, forever.” </em>Sounds like a pretty low-energy, high-yield exercise to me.</p><p>I think we all have these kinds of stories. Stories where we’re feeling low, somehow, and then someone reaches out unexpectedly, without standing to gain anything, and gives us words of encouragement. Or a gift. Or a smile. Or teaches us a card trick. Or a song.</p><p>Kindness is powerful. It sees all of us but it focuses on the best in us. Kindness directs our attention to what we already are. It’s encouraging and uplifting. It makes us better human beings. Kindness recognises pain and wants to make it better.</p><p>Kindness is mysterious and illogical and beautiful.</p><p>I’ve been designing products — websites, platforms, desktop and mobile apps, dashboards and solutions — for the last 20 years. I’ve always felt a simmering dissatisfaction with my work. For a long time I put it down to the usual Product/UX Designer frustration: delivering things with a diverse team, tight deadlines, and every kind of constraint <em>is</em> challenging. It’s especially hard if you’re a bit of a perfectionist — as most designers are. We know it’s challenging. It’s why we’re so attracted to the work. Product Design is <em>never</em> boring.</p><p>But I realised that there is something else that’s bugging me: I want the things that I design to be <em>kind</em>. It’s something I’ve always pushed for, but it only revealed itself to me in the last few years. I looked at all of the frameworks I had been given as a Product Designer and I felt frustrated. Some of them come close to prioritising kindness — <a href="https://designthinking.ideo.com/faq/whats-the-difference-between-human-centered-design-and-design-thinking">Human-Centred Design</a>, <a href="https://www.bbc.co.uk/rd/projects/digital-wellbeing">Values-Centric Design</a>, and <a href="https://mitpress.mit.edu/9780262039536/">Value Sensitive Design</a>. But many of the popular frameworks seem to be all about business-centered values.</p><p>Why kindness? Why not design for love or compassion? The reason is this: I think love does not concern itself with boundaries or fairness. Design will always have boundaries. And when I think of compassion, I imagine physical, practical help being given to someone in pain, and I’m not sure I can achieve that with the kinds of products I design.</p><p><strong>Kindness, on the other hand, <em>is</em> attainable.</strong></p><p>The Dalai Lama says:</p><blockquote><strong>“Be kind whenever possible. It is always possible.</strong>”</blockquote><p>We can <em>and must </em>design tech to be encouraging, empathetic, inclusive, and optimistic about human nature, and to foster deeper and more authentic connections between people and nature. Without kindness, we are lost. We build addictive products that grow exponentially and disrupt industries, but often damage people.</p><p>I’ve studied kindness and it’s not a simple thing to define. I realised that there isn’t really even a word for it in my first language (Afrikaans). It’s big and amorphous, but when it comes to Product Design, we can simplify it a little bit.</p><p>Here is what I believe are five essential qualities of kindness:</p><ol><li>Kindness is <strong>empathetic</strong></li><li>Kindness is <strong>inclusive</strong></li><li>Kindness <strong>sees suffering</strong></li><li>Kindness <strong>reflects kindly</strong></li><li>Kindness is <strong>beautiful</strong></li></ol><h3>Kindness is empathetic</h3><p>Without empathy, without deeply understanding the people we are designing products for, what their lives are like, what their stress levels are, how healthy they are, how chaotic their environments might be, and what their capabilities and vulnerabilities are, we <em>cannot</em> deliver kind products. Without empathy, the help we provide is probably not empowering and it might not even be helpful at all. It is often charitable, but I believe that charity that doesn’t actively seek to empower people, often leaves them disempowered.</p><p>I recognized very early on in my career that spending time with your users, watching them use your products, and listening to them with as open a mind as possible, is <em>the</em> most valuable thing you can do as a designer. If you’re lucky enough to be in an environment where this is recognised and your team pays attention to primary user research, be grateful! You’re probably not working in a startup. :)</p><p>Without empathy, we often build products for ourselves. We convince ourselves that it’s for an end-user, but without knowing that person, we’re very quick to build a pseudo-persona of what that person is like, who is <em>kinda like us, but just a little bit different</em>.</p><p>How to empathise?</p><ul><li><strong>Meet your end-users (in real life, ideally), observe them, and listen. </strong>We need to meet the people we are designing and building products for. Ideally, we need to observe them in their normal, everyday environment (if this is the environment we imagine them in while using our designs, of course!). We need to listen to them without steering the conversation and hear what it is that they <em>need</em> (not what they want!). And we need to get as close as possible to understanding why they have this need. Yes. I believe that contextual, qualitative research is still the ultimate tool for building empathy.</li><li><strong>Share your findings with your team (or get them to join in a bit of research).</strong> We need to share our findings with the bigger product team in such a way that they also <em>feel</em> what our end-users are feeling, and get an understanding of how they think. And remember, <em>empathy is both about the affective (feeling what others are feeling) and the cognitive (knowing how others are thinking).</em></li><li><strong>Observe people using your product</strong>, and ask “why?” a lot. There is nothing quite as powerful for building empathy as a user test where you watch people struggling with your product in ways that you had never imagined. Or using your product in ways you didn’t foresee. And yet — this is what you will experience whenever you do user testing the right way. And when it happens — when people do those unpredictable things with your product — remember to ask them “why?” Without understanding why people do things, we assume we know, and assumptions can be risky.</li></ul><h3>Kindness is inclusive</h3><p>I come from South Africa. We’re famous for Nelson Mandela, beautiful beaches, incredible wildlife, and natural diversity. Our country is also known for the system of <em>Apartheid</em>. I grew up in a segregated society (officially until I was 10, but unofficially until much later). The damage that <em>that</em> kind of exclusion does — both to the excluder and the excluded — is profound. It will not be healed during my lifetime or that of my children or grandchildren. Apartheid was an extreme kind of exclusion, admittedly.</p><p>The kind of exclusion we often build into our designs is much more subtle and often unintentional. Of course, inclusion is not only the absence of exclusion. It’s the opposite of exclusion.</p><blockquote>“When we design for inclusion, we are designing for our future selves and our ever-changing abilities. It’s designing how the next generation will treat and care for us. It’s making solutions to uphold the human connections that are most important in our lives. <strong>Our dignity, health, safety, and sense of being at home.”</strong></blockquote><blockquote>~ <a href="https://www.linkedin.com/pulse/inclusion-designing-future-kat-holmes/">Kat Holmes</a>, Author of <a href="https://katholmesdesign.com/the-book">“Mismatch: How Inclusion Shapes Design”</a></blockquote><p>My idea of inclusive design is something like this: products should be designed in such a way that they don’t exclude people based on their physical abilities, race, culture, religion, gender, education, nationality, age, or physical environment. It’s about proactively looking for points of exclusion and addressing them. It’s an ideal to work towards rather than an end goal. It’s something I strive for in my work and that I am hard on myself about, especially when it comes to the simpler guidelines around accessibility, and the use of language.</p><p>We have all the tools at our disposal to easily determine sufficient contrast and text sizes for different devices, yet we keep building products with low-contrast, tiny text that can’t be resized. You will truly feel the frustration caused when you begin working with people older than 40. And when <em>you</em> hit 40, you’ll realise that <em>everyone</em> (including yourself!) is temporarily able-bodied. We need to get over ourselves and build products that resize text gracefully.</p><p>We also keep on using bewildering jargon in our designs (not only technical jargon but often the jargon of wherever our subject matter expertise lies). At best, we lose engagement, but at worst: we make people feel anxious, frustrated, confused, or spoken down to.</p><p>I spoke about this to my husband — the poor man has to listen to many of my ramblings about these things. He thought about it and said: “But what about all the things that are exclusive by nature? Luxury cars and yachts and things?” We will always have luxury brands and experiences with us, I suppose, but I don’t consider exclusive luxury products kind, or concerned with creating a kinder world. I’m not really concerned with them. My attempt to put together a new framework for designing products is not universally applicable — only to products and services that are concerned with kindness.</p><p>Fortunately, amazing progress has been made in the last few years towards designing and building products that are more inclusive, but I still think that we need to take care that we don’t view inclusive design as a luxury add-on to our designs — something we’ll give attention to once we start getting traction and investment.</p><p>How to build inclusive products?</p><p>There is an ocean of resources that have been created over the last few years about inclusive design and how to do it. I’m going to shamelessly draw from <a href="https://humanebydesign.com/principles/inclusive/">humanebydesign.com</a> because I feel that the site has eloquently put down the 3 most important things we need to pay attention to if we’re really serious about inclusivity:</p><ul><li><strong>Build diverse Product teams</strong>, because diverse teams bring diverse experiences and ideas together and you will end up with more inclusive designs. Or at least, your team will have more lively debates about design decisions and consider inclusive practices more often.</li><li><strong>Design for disabilities first. </strong>Gosh. I am yet to find a team that does this, but it’s certainly something to aim for. We’re often under so much pressure to get some kind of workable, non-buggy MVP out into the world, that designing for disabilities is the last thing on our minds. The great news is that there are tons of platforms and methods that are freely available to us to make this easier, <em>should</em> the team consider it.</li><li><strong>Give people control.</strong> Allow people to experience your Product with higher contrast settings, bigger text sizes, or screen readers. Don’t disable these options. Disabling them sends a very unkind message. At best it says: “We don’t care about you.” At worst it says: “You don’t exist.” As I write this, I’m helping out a startup Product Team who has already released a product that does exactly this. They are a kind bunch of people and yes, under a lot of pressure to release features. I empathise. It seems to me that inclusive design is something that often has to be built into the DNA of a product from the beginning, or it will never be achieved. But I also believe that it’s better for a Product from a business perspective (yes, profitability) in the long run. It’s just a little more expensive to work it in later.</li></ul><blockquote><strong>“Inclusive design is a win-win for customers and businesses. </strong>It expands your product’s reach, sparks innovation, and helps your company take on a position of social responsibility.”</blockquote><blockquote>~Lillian Xiao, <a href="https://uxplanet.org/6-principles-for-inclusive-design-3e9867f7f63e">6 Principles for Inclusive Design</a></blockquote><h3>Kindness sees suffering</h3><p>Kindness sees suffering and wants to alleviate it. Kindness cares. It wants to make people feel better. It’s encouraging and empowering. It is polite and considerate at the least.</p><p>It doesn’t aim to give people who are suffering a fleeting moment of relief, after which they return to a state of suffering. Kindness wants to see people build their health, wealth, and happiness.</p><p>We know that tech is committing untold harm to humanity. Only, <a href="https://ledger.humanetech.com/">the harms aren’t really untold anymore</a>. Peer-reviewed research shows us that in many cases, badly designed tech:</p><ul><li><a href="https://jamanetwork.com/journals/jamapediatrics/fullarticle/2722666">Causes developmental delays in our children</a>, especially in terms of language and literacy</li><li>Makes our young people <a href="https://jamanetwork.com/journals/jamapediatrics/article-abstract/2737909">depressed</a>, anxious, and <a href="https://journals.sagepub.com/doi/abs/10.1177/2167702617723376?journalCode=cpxa">suicidal</a></li><li>Makes us angry and <a href="https://www.pnas.org/doi/10.1073/pnas.2024292118">divides us</a></li><li>Damages our ability to think, focus, solve problems, and <a href="https://srcd.onlinelibrary.wiley.com/doi/abs/10.1111/cdev.12822">be present with our loved ones</a></li><li>Makes us feel <a href="https://www.liebertpub.com/doi/10.1089/cyber.2019.0744">stressed</a> and lonely</li><li>Is often addictive, with levels of addiction correlated with a reduction in gray matter in the amygdala, similar to the type of cell death seen in cocaine addicts</li></ul><p>If we care about people and about the alleviation of suffering, we need to recognise that this is true and <strong>stop building tech that causes suffering in the first place</strong>.</p><p>We also need to be more mindful and intentional with our designs.</p><ul><li><strong>Consider the intentions of your products and services</strong> — are they trying to alleviate suffering? Be careful not to confuse greater efficiency and speed with the alleviation of suffering. Just because I can apply for a product more easily and quickly, or buy something with fewer clicks, or complete a form without thinking about it (because I’ve been given convenient default responses), I am not necessarily on the receiving end of kindness.</li><li><strong>Recognise suffering (where possible) and respond appropriately</strong>, at the very least. Depending on the kind of product you are designing, your users may have more transparent or more opaque, and more severe or more trivial forms of pain that they’re dealing with. But I’ve seen work done at many enterprise-sized businesses where products for funeral insurance and disability cover are treated like children’s savings accounts. A Product Design machine with templates and guidelines is put into motion, and nobody feels empowered to question it.</li><li><strong>Language is important</strong> if we want to encourage people. Recognise effort. Say please. Say thank you. Say “well done!” Use the simplest language possible, so people feel understood, and that they can make the best decisions for themselves with the information you’ve provided.</li><li>Most importantly: <strong>don’t measure the success of your product by the amount of attention it receives</strong>. Measure its success by the positive impact it is having on people’s lives.</li></ul><h3>Kindness reflects kindly</h3><p>Being kind means perceiving people as they are — with all their flaws, vulnerabilities, insecurities, and marvelously imperfect humaneness, and reflecting that back kindly. Showing people the good they have inside of them, but perhaps also shining a light on their inner critic and showing it for what it is: often a very unnecessary and illogical voice we carry with us. Kindness assumes positive intent.</p><p>How often have you worked with a product team and heard one of the following phrases:</p><ul><li>Our users are stupid!</li><li>We need to make this idiot-proof.</li><li>Dumb it down a bit.</li></ul><p>I think we’ve <em>all</em> heard these or versions of these. We might even have said these to ourselves (Especially if you’ve been in tech support, and in that case, I forgive you!). The thing is: people are not stupid or dumb or idiotic. They’re just…people. The best experiences I’ve worked on were the ones where the team understood and appreciated people’s vulnerabilities.</p><p>Richard Thaler, the well-known behavioural economist and co-author of <a href="https://www.amazon.com/Nudge-Improving-Decisions-Health-Happiness/dp/014311526X">”Nudge</a>”, wrote about <a href="https://www.researchgate.net/publication/344119977_Econs_vs_Humans_An_Introduction_to_Behavioral_Economics_Social_Education_832_p_94-99">Humans versus Econs</a>. Econs are beings that carefully weigh the costs and benefits of alternatives before making decisions. They are analytical, reflective, effortful, deliberate, and patient. In Economical Theory and in Product Design, humans are often thought of as Econs. But they are not! Thank <em>goodness</em>. What an utterly boring world it would be. Psychologists have always known this.</p><p>Daniel Kahneman writes in <a href="https://www.amazon.com/Thinking-Fast-Slow-Daniel-Kahneman/dp/0374533555">“Thinking, Fast and Slow”</a>:</p><blockquote>“To a psychologist, <strong>it is self-evident that people are neither fully rational nor completely selfish, and that their tastes are anything but stable.</strong> […]</blockquote><blockquote><strong>Their view of the world is limited </strong>by the information that is available at a given moment, and <strong>therefore they cannot be as consistent and logical as Econs</strong>. <strong>They are sometimes generous and willing to contribute to the group to which they are attached</strong>. And they often have little idea of what they will like next year or even tomorrow.”</blockquote><p>Basically, humans are marvelously messy. As Product Team members, we need to embrace some understanding of this, so we can take advantage of what is marvelous, and support (and <em>not</em> exploit) what is messy.</p><p>How to reflect kindly:</p><ul><li><strong>Stop assuming that people are Econs. </strong>Know that they will sometimes behave irrationally, illogically, and inconsistently. Embrace it, and design and build for it.</li><li><strong>Be forgiving when people make mistakes.</strong> Everyone makes mistakes. And we make more of them when we are stressed and emotional and tired. Stop seeing mistakes as something negative and rather prepare for them and build your design to eliminate them completely, where possible. Mistakes are wonderful: they are how we learn and progress and grow — if we are given the opportunity to learn. Enough has been said about error handling in design. Take the guidelines to heart: <a href="https://www.nngroup.com/articles/slips/">prevent errors where possible</a>, and where they can’t be prevented, <a href="https://www.nngroup.com/videos/usability-heuristic-recognize-errors/">provide helpful error messages</a>. Assume positive intent: People don’t make mistakes on purpose.</li></ul><h3>Kindness is beautiful</h3><blockquote>“A thing of beauty is a joy forever:”</blockquote><p>~John Keats, Endymion</p><p>Close your eyes, take a few deep breaths, and then picture the face of kindness. I’m serious. Do it. There is no right or wrong here: whatever that face looks like for <em>you</em> is your truth.</p><p>Perhaps the face of kindness is the face of a mother? Or a deity? Perhaps it is a philosopher or thought leader? It might not be a human face at all. But to you, the face of kindness will be beautiful.</p><p>We know that people are more forgiving towards products when they are beautiful. We associate kindness with beauty — sometimes disastrously! But I think that often (not always!) beautiful designs have been given more attention.</p><blockquote>“Form follows function.”</blockquote><p>~Louis Sullivan, Chicago Architect</p><p>Stefan Sagmeister and Jessica Walsh created a beautiful book, called <a href="https://sagmeisterwalsh.com/work/all/beauty/">“Beauty”</a>, where they argue (and have convinced me, at least) that Beauty = Function. The Product world is sometimes obsessed with minimalist, functional design. Stripping things down to what is necessary, only. But beautiful objects and experiences that bring us joy, are often not “functional” at all.</p><figure><img alt="Sagmeister and Walsh’s book, “Beauty”, on a purple velvety fabric" src="https://cdn-images-1.medium.com/max/1024/1*uhWbQuE3Zaaql0XgASusFA.png" /><figcaption>Beauty, by Stefan Sagmeister and Jessica Walsh</figcaption></figure><p><a href="https://aestheticsofjoy.com/about/">Ingrid Fetell Lee</a> has been researching the Joy of Aesthetics for more than a decade, and found that humans find universal joy in these 10 aesthetics:</p><blockquote>“<strong>Energy</strong>: vibrant color and light</blockquote><blockquote><strong>Abundance</strong>: lushness, multiplicity, and variety</blockquote><blockquote><strong>Freedom</strong>: nature, wildness, and open space</blockquote><blockquote><strong>Harmony</strong>: balance, symmetry, and flow</blockquote><blockquote><strong>Play</strong>: circles, spheres, and bubbly forms</blockquote><blockquote><strong>Surprise</strong>: contrast and whimsy</blockquote><blockquote><strong>Transcendence</strong>: elevation and lightness</blockquote><blockquote><strong>Magic</strong>: invisible forces and illusions</blockquote><blockquote><strong>Celebration</strong>: synchrony, sparkle, and bursting shapes</blockquote><blockquote><strong>Renewal</strong>: blossoming, expansion, and curves”</blockquote><blockquote>~Ingrid Fetell Lee, “Joyful”</blockquote><figure><img alt="The cover of the book “Joyful: the surprising power of ordinary things to create extraordinary happiness”, by Ingrid Fetell Lee." src="https://cdn-images-1.medium.com/max/1024/1*vCIlVER1aiGG2CRdYQLeJA.png" /><figcaption>Joyful, by Ingrid Fetell Lee</figcaption></figure><p>Notice the lack of Functionality, Usability, and Minimalism. These are good principles to follow if we want to help people with workable tools. But if we want to step into kindness, we often need more.</p><p>Don Norman wrote his famous book — “The Design of Everyday Things”. It’s a classic and it changed the way people think about usability and design.</p><figure><img alt="Cover of “Emotional Design: Why We Love (or Hate) Everyday Things”, by Don Norman" src="https://cdn-images-1.medium.com/max/1000/1*EaRPqH-QeNnqWiHq_fL8xA.jpeg" /><figcaption>Cover of “Emotional Design: Why We Love (Or Hate) Everyday Things”, by Don Norman</figcaption></figure><p>It was followed up by <a href="https://www.nngroup.com/books/emotional-design/">“Emotional Design”</a>. He realised what Sagmeister and Walsh say with a lot of passion and swearing: functionality is important, but beauty is just as important — and in many cases, beauty doesn’t need to be functional at all. Beauty = Function.</p><p>This is almost a confession, but more importantly and beautifully a declaration:</p><blockquote>“In the 1980s, in writing “The Design of Everyday Things”, I didn’t take emotions into account. I addressed utility and usability, function and form, all in a logical, dispassionate way — even though I am infuriated by poorly designed objects. But now I’ve changed. Why? In part because of new scientific advances in our understanding of the brain and of how emotion and cognition are thoroughly intertwined. We scientists now understand how important emotion is to everyday life, how valuable. <strong>Sure, utility and usability are important, but without fun and pleasure, joy and excitement, and yes, anxiety and anger, fear and rage, our lives would be incomplete.</strong></blockquote><blockquote><strong>Along with emotions, there is one other point as well: aesthetics, attractiveness, and beauty. </strong>When I wrote “The Design of Everyday Things”, my intention was not to denigrate aesthetics or emotion. I simply wanted to elevate usability to its proper place in the design world, along with beauty and function. I thought that the topic of aesthetics was well-covered elsewhere.”</blockquote><blockquote>~Don Norman, “Emotional Design”.</blockquote><p>How to make your designs beautiful?</p><ul><li><strong>Consider context. Beauty is context-specific</strong>, so consider the context of your designs and the people who will be using them. See “Kindness is Empathetic”.</li><li><strong>Take time to craft your Products before and after they are functional.</strong> Your users will appreciate it and they will be more likely to forgive the bugs, and more likely to show your Product to other people.</li><li><strong>Invest in professional creatives. </strong>Too often, I have come across Product Teams with the best developers, architects and managers, but where visual design was handed to a junior person, or worse: not considered at all. It breaks my heart when this happens with B2B products that serve personnel who have no choice about the tools that they use. They are given functional solutions that are ugly — and often pretty low on usability as well. The message sent, as with non-inclusive designs, is not kind. We shape our products and our products shape us, in turn. If our designs communicate that kindness is unimportant, it will become unimportant to the people using them.</li></ul><h3>Conclusion</h3><p>If you made it all the way to the conclusion of this piece, we should probably meet up and have coffee sometime. :)</p><p>Kindness is empathetic, inclusive, beautiful, sees suffering, and reflects kindly. But more importantly: it is powerful. It carries people through difficulties as nothing else can, and our world is full of difficulty right now.</p><p>Digital Products are powerful too. They are made once and then appear on countless, infinite screens. Replicated infinitely. They are making our children sick, damaging our relationships with one another, and are being used by some pretty unkind powers to make people more divided and extreme in their views.</p><p>But what if our Products could be a force of Kindness? What if our Products were built to provide an unexpected lift for people when they need it most? What if we could be the kind teacher telling the anxious child who’s feeling a little lonely, and worried about her place in the world and whether she’ll be able to cope: “Yes, you can. <em>You</em> can.”?</p><p>With the global mental pandemic in full swing, and political turmoil and war and uncertainty, a lot of grownups are feeling a little lonely, and worried about their place in the world and whether they’ll cope. The world is in need of kindness. And I believe that Product Designers are in a privileged position to play a powerful role.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9516407439ee" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/kindness-in-product-design-9516407439ee">Five Essential Qualities of Kindness and how to Design for them</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[Kinder product design]]></title>
            <link>https://uxdesign.cc/kinder-product-design-782cb6da2daa?source=rss-d25a0d79e797------2</link>
            <guid isPermaLink="false">https://medium.com/p/782cb6da2daa</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[humane-tech]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Carien Moolman]]></dc:creator>
            <pubDate>Sun, 03 Apr 2022 20:56:15 GMT</pubDate>
            <atom:updated>2022-04-05T20:04:25.002Z</atom:updated>
            <content:encoded><![CDATA[<h4>Have we lost something essential in our desire to build new, innovative, profitable, desirable products?</h4><figure><img alt="A bit of graffiti saying: Kindness is a Superpower." src="https://cdn-images-1.medium.com/max/1024/1*CpPAQgoVm18_OTKFcR1eIw.jpeg" /><figcaption>Kindness is a superpower. Photo by <a href="https://unsplash.com/@athornebrooke?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Andrew Thornebrooke</a> on <a href="https://unsplash.com/s/photos/kindness?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Have we lost something essential in our desire to build new, innovative, profitable, desirable products? Have we forgotten to be <strong>kind</strong>? I’d like to explore how we might bring kindness back into our work as Product Designers in the next series of posts.</p><p>A few days ago, I had a provocative conversation with a friend and colleague. He is an energetic optimist and founder of a number of ventures, and a qualified neurologist and statistician to boot. We were talking about designing for behavior change and how it’s probably one of the most interesting challenges in Product Design (thinking about it, designing for behavior change <em>is</em> Product Design). He jumped in with a bold statement: “Actually, it’s all very simple. There are <em>only two things</em> that determine people’s behavior: the fear of death, and insightful learnings.”</p><p>To which I replied, perhaps a bit too quickly: “With all due love &amp; respect: you don’t know what you’re talking about!”</p><p>And then the conversation exploded into a rather technical lecture about the structures of the brain and how, from an evolutionary perspective, our base instinct as a species is to survive and procreate and how we become more successful in this as we grow our knowledge and skills. Of course, as always, he was right. If we really look at the very root driver of human behavior, it’s possible to trace all of it back to a very basic desire to survive.</p><p>The thing is — this isn’t a very useful behavioral model if one is trying to make decisions regarding the design of an app, for instance. How the flow of a digital experience should go, which features to build, how to prompt actions (“You’re about to die. Do something!”), and how such an experience might encourage people to establish better and healthier habits.</p><p>It got me thinking about the different design frameworks and models I have come across and applied to all sorts of designs over the last 15 years or so. <em>All</em> Product design is designing for behavior change to a greater or lesser extent, and so — all of these frameworks and models describe, in some way, how humans behave in one moment and how they might behave given a newly designed solution. If we are not designing for behavior change, we’re not designing at all, are we? We’re moving bits and pieces around for the sake of the appearance of productivity.</p><p>And so, I thought of these frameworks and models:</p><p><em>Disclaimer: This is simply a list of models/frameworks that have made some impact on me and that I’ve tried out, in practice.</em></p><h3>HCD</h3><p><a href="https://en.wikipedia.org/wiki/Human-centered_design">Human-Centred Design (HCD)</a> tells us to begin with empathy, focus on a well-defined problem, ideate, experiment, and learn. I don’t think I’ll ever be able to turn my back on this process. It’s experimental and it says you need to get your stuff in front of real human beings before you jump in and build things. I am yet to come across a method that beats it at cutting BS out of the process.</p><figure><img alt="A picture of the stages of Human-Centred Design, starting with Empathise, then Define, then Ideate and finally: Build." src="https://cdn-images-1.medium.com/max/1024/1*_CR0oqZTJD68M1ZzChPXrQ.png" /><figcaption>The phases of Human-Centred Design</figcaption></figure><h3>Jobs To Be Done</h3><p>Jobs To Be Done (JTBD) tells us that people hire our products to do jobs and that we need to identify what the job is and how other products may already be doing the job well enough. If our product <em>doesn’t </em>do the job well enough, it will be fired.</p><p>Alan Klement, author of <a href="http://www.whencoffeeandkalecompete.com/">“When Coffee and Kale Compete”</a> gives JTBD another spin:</p><blockquote>“Customers struggle when they try to make their life better but don’t know how. We call this struggle a <strong>Job to be Done</strong>.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cyIgcZsriVvWPlqK2094Dg.png" /><figcaption>Push and pull factors in Jobs To Be Done (from: <a href="http://www.whencoffeeandkalecompete.com/">http://www.whencoffeeandkalecompete.com/</a>)</figcaption></figure><h3>UX Honeycomb</h3><p><a href="https://semanticstudios.com/about/">Peter Morville</a>’s value model says that Products are valuable to people if they are findable, desirable, useful, usable, accessible, and credible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/440/1*8Hn781tTY7SiFpGxg-CYaA.jpeg" /><figcaption>Peter Morville’s UX Honeycomb (thanks &amp; credit to <a href="https://semanticstudios.com/user_experience_design/">Semantic Studios</a> for this pic)</figcaption></figure><h3>Usability Heuristics</h3><p>Don Norman and the clever people at the Nielsen Norman Group also follow an experimental approach, adhering to the stages of the HCD methodology, but with a strong focus on <em>usability. </em>They<em> </em>have <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">10 beautiful usability Heuristics</a> we can use as a measure of our designs — visibility of system status, match between the system and the real world, user control and freedom, consistency and standards, error prevention and helping people with recovery, recognition over recall, minimal (visual) design, and solidly documented help when needed. I’m a big Don Norman fan and, like most UX Designers, I think <a href="https://www.nngroup.com/books/design-everyday-things-revised/">The Design of Everyday Things</a> and <a href="https://www.nngroup.com/books/emotional-design/">Emotional Design</a> changed my life.</p><p>Then there has been the inevitable rise of the Behavioralists. They have certainly changed the landscape of Product Design.</p><h3>System 1 and System 2</h3><p>If we want to design and build products that shape people’s behavior, we must learn to understand the fascinating strangeness of how people behave by default and how they are biased subconsciously by their environment and subtle suggestions. Daniel Kahneman says it so well:</p><blockquote>Our thoughts and our behavior are influenced, much more than we know or want, by the environment of the moment.</blockquote><p>Thinking of the people we design for as beings with an intuitive, emotional System 1 that they rely on most of the time, and a deliberative, calculating System 2 that they access when needed, and that is easily exhausted, has been <em>tremendously</em> helpful to me over the years. If we’re designing for people in mentally draining or highly stimulating environments, it’s often best to design for unthinking actions, presenting as few choices as possible and pre-selecting smart defaults. If, on the other hand, our users are likely to be using our designs in quiet, focus-friendly environments, doing tasks that need careful thought and subtle analysis, the approach changes.</p><h3>B=MAP</h3><p>Another behavioralist that springs to mind is <a href="https://www.bjfogg.com/">the loveable BJ Fogg</a> with his perfect set of white teeth and his <a href="https://behaviormodel.org/">B=MAP model</a>. In his own words:</p><blockquote>Behavior (B) happens when Motivation (M), Ability (A), and a Prompt (P) come together at the same moment.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eE8fyMs3cD6T5ESLv3t9ng.jpeg" /><figcaption>The Fogg Behaviour Model (from <a href="https://behaviormodel.org/">https://behaviormodel.org/</a>)</figcaption></figure><p>This is a powerful picture to sketch and <em>keep</em> on the war room whiteboard. Stakeholders tend to overestimate user motivation and capability (and those stakeholders include the designers on the team!). They also tend to underestimate the impact of small usability issues on people’s ability to move to action.</p><h3>The Hook Model 😬</h3><p>Then there’s <a href="https://www.nirandfar.com/about-nir-eyal/">Nir Eyal</a> and the <a href="https://www.nirandfar.com/hooked/">Hook</a>.</p><figure><img alt="A picture of Nir Eyal’s Hook Model: Trigger, Action, Variable reward, Investment" src="https://cdn-images-1.medium.com/max/1024/1*8eh1-0hYoqnQg9SMRwUd4Q.png" /><figcaption>The Hook Model (Thank you, <a href="https://www.productplan.com/glossary/hook-model/">https://www.productplan.com/glossary/hook-model/</a>).</figcaption></figure><p>I’ve always felt uncomfortable with the Hook Model. It’s obviously massively successful and powerful but it seems to exploit human frailty. It’s just too close to a flow chart of the typical rodent’s behavior in a Skinner Box, and feels like <a href="https://creativegood.com/blog/21/losing-faith-in-ux.html">the thing Mark Hurst wrote about </a>— UX becoming an acronym for User <em>Exploitation</em> rather than User Experience. It seemingly aims to get us addicted to products (both “good” and “bad”) rather than encouraging us to be thoughtful about our electronic servants and how they can (and should!) remain exactly that — <em>servants</em> of humans. Having said that, the Hook Model has been valuable to me over the years by reminding me to consider:</p><p>(1) variable explicit rewards, and</p><p>(2) <em>anticipation</em> as a motivator.</p><h3>The Elephant and the Rider</h3><p>Another model I love is the Heath Brothers’ model as described in <a href="https://heathbrothers.com/books/switch/">Switch</a>, with the elephant, rider, and path. They’ve kinda taken Daniel Kahneman’s model and created a bit of a Segway for it, where the elephant is your System 1, the rider is System 2 and the path is your environment.</p><figure><img alt="A picture of a man on an elephant, following a path. Text: direct the rider, motivate the elephant, and shape the path" src="https://cdn-images-1.medium.com/max/1024/1*RQsvYp3QNLWP5pKFBIhp7g.jpeg" /><figcaption>The elephant, rider and path. (From Switch: How to change things when change is hard).</figcaption></figure><p>Switch says: take a careful look at the problem you’re solving. Is it a problem of motivation? Is it a process problem? Or is it perhaps an environmental problem?</p><h3>Predictable Irrationality</h3><p><a href="https://danariely.com/">Dan Ariely</a> has to be mentioned, with his wildly popular and simplified explanations of how we might make use of <a href="https://danariely.com/books/#book-predictably-irrational">predictable human irrationalities</a> (really, biases) to steer behavior. His stories of real behavioral experiments are powerful and memorable.</p><p>There are countless others. I just described the ones I’ve had the opportunity to apply in practice or that I like for some quirky reason.</p><h3>Movement towards Ethical and Humane Design</h3><p>More recently, of course, there has been a tremendous move towards <a href="https://www.humanetech.com/technologists">humane tech</a> and ethical design. I feel incredibly lucky to have had a rather intense conversation with <a href="https://cennydd.com/">Cennyd Bowles</a>, author of <a href="https://nownext.studio/future-ethics">Future Ethics</a>. He convinced me that user-centered design isn’t only <em>not</em> good enough anymore — it’s short-sighted and because of that short-sightedness, it is a risky approach. We need to think of the possible future consequences of the products we are designing now. We need to think about what our products can enable in a future world if they land in the hands of evil people. More importantly, we need to think of what a wildly successful product’s unintended effects might be on its ecosystem.</p><p>There is <em>so much</em> we have to consider as Product Designers. Ethics, <em>future</em> ethics, mental health, accessibility, inclusivity, usability, usefulness, forgiveness, profitability, feasibility, desirability, sustainability, credibility, heuristics, readability, value, privacy, transparency, community, economics, analytics, consistency…the list goes on.</p><p>And we have all these models and frameworks to help us design Products with these things in mind.</p><h3>What about Kindness?</h3><p>But I find myself wondering: whatever happened to <em>Kindness</em>? Is there a framework or a sounding board or evaluation technique that can help us judge whether our designs are in fact <em>Kind</em>?</p><p>I started looking for research into digital product design and kindness, and came across the work of <a href="https://www.jamesrdotymd.com/">Dr. James Doty</a>. He founded <a href="http://ccare.stanford.edu/">CCARE</a> — the Center for Compassion and Altruism Research and Education. This is a group at Stanford University that does rigorous research into the effects of compassion and altruistic behaviour, amongst other things. I somehow managed to convince Dr. Doty to have a short conversation with me: he <em>certainly</em> believes that tech has a significant role to play in the space of compassion, which he defines as empathy <em>plus</em> a desire to help in some way.</p><p>I have to admit, my internal definition of empathy in the context of Human-Centred Design has always included the need to help people. I empathise with my users <em>in order to design products that serve them better and remove pain</em>. So perhaps Design Thinking has always been an intrinsically compassionate process? (I know of many people who wouldn’t agree.)</p><p><a href="https://jonyablonski.com/info/">Jon Yablonski</a>, the author of <a href="https://jonyablonski.com/articles/2020/laws-of-ux-book/">The Laws of UX</a>, has made great inroads into what I believe is kind design. He puts down <a href="https://humanebydesign.com/">7 principles describing humane design</a>. He says: humane design is empowering, finite, inclusive, resilient, respectful, thoughtful, and transparent. I adore his work and am yet to figure out a way of applying it to my designs in a systematic way.</p><p>But I feel like being humane isn’t <em>quite</em> what I’m gunning for. And designing digital products and services that are somehow <em>loving</em> is on the crazy side-love does not concern itself with profitability. But perhaps somewhere between those two — being humane and being loving — is a measure of kindness. It’s about designing products that care about people and the world. Products that have good intentions from the beginning. It’s about products that say “please” and “thank you” and try to use the simplest language possible so that no one feels spoken down to or mystified. It’s about providing options. It’s also about being honest without being brutal, and about seeing all the imperfections that make us human, and dealing with them, well, kindly. It’s about making the machines do the hard &amp; repetitive work, so people don’t have to. It’s about making people feel just a little bit better.</p><p>This is how my journey into Kinder Design begins. Perhaps somebody has already figured it out, but I’d like to explore some more.</p><p>And who knows? Maybe kindness is evolutionary. Maybe it <em>is</em> simply another way for people to avoid death and learn more quickly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=782cb6da2daa" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/kinder-product-design-782cb6da2daa">Kinder product 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[How to survive a design career and avoid burnout (Part 3)]]></title>
            <link>https://uxdesign.cc/how-to-survive-a-design-career-and-avoid-burnout-part-3-a2cb87135cb6?source=rss-d25a0d79e797------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2cb87135cb6</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[burnout]]></category>
            <category><![CDATA[self-compassion]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <dc:creator><![CDATA[Carien Moolman]]></dc:creator>
            <pubDate>Mon, 03 Jan 2022 20:38:50 GMT</pubDate>
            <atom:updated>2022-01-04T20:15:17.973Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A beautiful scenic picture of the northern lights." src="https://cdn-images-1.medium.com/max/1024/1*kCFYvyVIV5hAebCkKjBWgg.jpeg" /><figcaption>Norwegian landscape with northern lights. Photo by <a href="https://unsplash.com/@lightscape?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Lightscape</a> on <a href="https://unsplash.com/s/photos/norway?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Early in 2021, I found myself in my dream job as a UX Designer and well on the way to burnout. I did something I had never done before: I resigned without knowing what I would do next and took time off. I decided to call up friends in the Product Design community to try to get to grips with this question: why do some Product Designers (and related roles) flourish in harsh working environments, while others (yes, like myself) tend to struggle &amp; burn out?</p><p>I had conversations with three people I admire and trust. This piece is based on the third conversation with a friend in Norway — Anouk. The other two conversation posts are available<em> </em><a href="https://uxdesign.cc/how-to-survive-ux-design-and-avoid-burnout-d410a9e14c1a"><em>over here</em></a><em> </em>and<em> </em><a href="https://uxdesign.cc/how-to-survive-a-design-career-and-avoid-burnout-part-2-3f3957e33fd0"><em>here</em></a>.</p><p><em>A bit of a detour:</em></p><p><em>As I’m writing this, it occurs to me that I’ve spoken to </em><strong><em>many</em></strong><em> more than the three people I’ve dedicated posts to. A lot of Product Design people have shared wonderful pieces of wisdom and some very personal stories. I have been showered with tales of burnout by designers from all over the world. It made me realise: everyone is having a hard time or has had some pretty hard times at some level, especially in the last two years with the global pandemic. Yes, even those amazing, successful people who one admires and finds inspirational because they seem to always be doing well. We’re all human. And we’re all in this together.</em></p><h3><strong>My third conversation</strong></h3><p>Anouk studied psychology and found her way to UX Design in a pretty meandering way in South Africa. We met at a Google UX Masterclass in Cape Town and we just hit it off. She is empathetic, smart, and incredibly funny, often inappropriately so. A few years after we met we started working together as UX consultants at a big corporate, doing projects for banks, investment managers, and the like.</p><p>At some point in time, she moved to Norway. We’ve stayed in touch. She is the kind of person who is fun to keep in touch with because she loves people and there are <em>very</em> few boring moments in her life. She has overcome incredible challenges and continues to do so. She is now a senior UX Specialist at a biggish startup in Oslo.</p><h3><strong>Advice</strong></h3><p>I called her up, post-resignation, to talk about how she does it. How does she keep moving upwards and onwards as a UX Designer? And this, despite having very little in terms of social support and having to design in a very recently gained third language. Her first response was not advice. Her first response was to look serious and ask how I was <em>really</em> doing.</p><p>Now. We all have friends who are psychologists, therapists, or counselors. They sometimes seem incapable of accepting a positive response to the question: “How are you?” You’ll reply: “I’m fine!” And then they’ll lean in and say, with a slightly concerned expression: “But how are you, <em>really</em>?”</p><p>This is not Anouk. She demands a non-flippant answer straight off the bat, so she can have a proper conversation. She doesn’t tolerate superficiality.</p><p>She listened as I told her about the things that I struggled with as a UX Designer, as a member of a team that had to make the dramatic shift to remote work, the challenge of working from home with two lively toddlers in a house that doesn’t allow me to work behind a closed door, and my utter failure at staying cool and calm when my partner’s anxiety levels shot through the roof because of all of the same challenges.</p><p>Her advice was two-fold.</p><blockquote>“You need to <strong>move to Norway</strong>. Things are so different here! The government really looks after its people. They don’t live to work. They <em>live</em>. And they really value getting out into nature. They even have a word for it: <a href="https://www.nationalgeographic.com/travel/article/how-norways-friluftsliv-could-help-us-through-a-coronavirus-winter"><strong><em>friluftsliv</em></strong></a>. Oh! And I worked overtime once or twice and got into trouble for it. It’s really not okay here.”</blockquote><p>Her second piece of advice felt more like an admonishment:</p><blockquote>“And you need to<strong> learn some self-compassion</strong>. Your children look up to you and they need to see that you value your own mental health.”</blockquote><h3><strong>Move to Norway!</strong></h3><p>This piece of advice, which was a little tongue-in-cheek but also quite serious, got me thinking about our environments — specifically our working environments — and the impact it has on our performance and general well-being as Designers. She referred to two environments in one go:</p><ol><li>The countries we live in,</li><li>The companies we work for,</li></ol><p>and how they impact us.</p><h3><strong>Consider the country you live in</strong></h3><p>Just to clarify — I’m not planning on moving to a Nordic country any time soon or advocating that everyone should. I would love to <em>visit</em> Norway if only to experience what it feels like to be in a place with <a href="https://worldhappiness.report/ed/2021/happiness-trust-and-deaths-under-covid-19/">the 8th happiest population on earth</a>, little crime, a working healthcare system, and almost zero poverty. Anouk and I are both from South Africa. South Africa doesn’t have any of those. I love my country. It is breathtakingly beautiful and diverse, but it is a developing country with the kinds of challenges developing countries face: poverty, corruption, rolling blackouts (our electricity supply is unpredictable), a broken healthcare system, and high unemployment and crime rates.</p><p>Looking at <a href="http://hdr.undp.org/en/countries">the UN’s Human Development Index numbers</a> and comparing Norway to South Africa (a little bit):</p><blockquote>Life expectancy (years): 82.4 vs 64.1</blockquote><blockquote>Expected years of schooling: 18.1 vs 13.8</blockquote><blockquote>Employment ratio (% of population 15 and older): 61.7 vs 40.2</blockquote><blockquote>Population earning less than $1.90 per day (%): 0.3 vs 18.7</blockquote><blockquote>Homicide rate (per 100,000 people): 0.5 vs 36.4</blockquote><blockquote>Internet users (% of population): 96.5 vs 56.2</blockquote><blockquote>Skilled labour force (% of labour force): 84.3 vs 52.2</blockquote><p>I’ve been lucky enough to travel a bit. When you walk the streets of a developed nation’s capital city (like Helsinki, Barcelona, or London) late at night and realize you feel relatively safe and free to move around, it dawns on you how subliminally stressful life can be in a country like South Africa. We have coping mechanisms in place to deal with things like crime (stay in safe areas and be vigilant), broken healthcare (pay for expensive private medical care, <em>if</em> you can afford it), and rolling blackouts (buy a generator or a battery system, also if you can afford it). But then you add a global pandemic and political instability to the mix. This is a recipe for a pretty stressed population. High unemployment rates make people (including UX Designers) in South Africa more likely to tolerate non-ideal company cultures, <em>even though experienced UX Designers are in high demand</em>, because of a skills shortage and a <a href="https://www.fdiintelligence.com/article/79638">burgeoning tech industry</a>.</p><p>It’s worth spending a bit of time thinking about the country you find yourself in and how it is having an impact on your well-being. Designers are often introverted. We tend to focus on internal factors to find solutions to the challenges we face. The thinking goes: “What am I doing wrong and how can I fix this?” On the one hand, this is great, because our emotions and responses are arguably things that we have a measure of control over. But sometimes our bigger environment is playing a far greater role than we care to admit. And maybe it’s a healthy thing to pause and think about this for a moment.</p><p>I worked at a wild digital ad agency in Jo’burg (the business capital of South Africa) for a few roller-coaster years. Our teams were diverse, and timelines were typically quite tight, so collaborating was key. On the same project team, we would have fashionistas driving to work in shiny Audi TTs from the leafy suburbs around the corner, as well as interns and single moms juggling taxis, trains, and buses from the townships, 50 kilometers away. People would sometimes arrive at work a bit shaken — either from experiences in traffic or because they had witnessed or been the victims of crime. We made a conscious effort as an organization to be sensitive to these experiences, but living in a stressful environment <em>will</em> have an impact on you and your team’s ability to perform at your best.</p><h3><strong>Consider your working environment</strong></h3><p>This brings us to the second kind of environment to become more aware of: the company you work for, including the company’s culture and the way it shapes processes. I cannot recommend “<a href="https://www.oreilly.com/library/view/accelerate/9781457191435/">Accelerate</a>” (by Nicole Forsgren, Jez Humble, and Gene Kim) enough.</p><figure><img alt="The cover of “Accelerate”, a book about building and scaling high performing tech organizations" src="https://cdn-images-1.medium.com/max/1024/1*ERdkcEEZ_rncEigrS9KBKw.jpeg" /><figcaption>Accelerate: Building and Scaling High Performing Tech Organizations</figcaption></figure><p>Their words:</p><blockquote>“As in other fast-paced, high-consequence work, software and technology is plagued by employee burnout. Technology managers, like so many other well-meaning managers, <strong>often try to fix the person while ignoring the work environment, even though changing the environment is far more vital for long-term success.</strong> Managers who want to avert employee burnout should concentrate their attention and efforts on:</blockquote><blockquote>- Fostering a respectful, supportive work environment that emphasises learning from failures rather than blaming</blockquote><blockquote>- Communicating <strong>a strong sense of purpose</strong></blockquote><blockquote>- Investing in employee development</blockquote><blockquote>- Asking employees what is preventing them from achieving their objectives and then fixing those things</blockquote><blockquote>- Giving employees time, space, and resources to experiment and learn.”</blockquote><p>Forsgren et al then go on to describe the organizational factors that are most strongly correlated with reduced burnout risk. I’m not going to go into all of these — I really, really recommend you read the book. The very first factor they mention is <strong>Organisation Culture</strong>.</p><p>For me, a company’s culture is its values made visible <em>and</em> how those values are experienced by the people inside the company. The strongest company cultures I’ve experienced are the ones that result from visionary leadership. The leaders in these companies are optimists in <a href="https://www.amazon.com/Thinking-Fast-Slow-Daniel-Kahneman/dp/0374533555">the way Daniel Kahneman describes them</a>:</p><blockquote>“Optimistic individuals play a disproportionate role in shaping our lives. Their decisions make a difference; they are the inventors, the entrepreneurs, the political and military leaders — not average people. They got to where they are by seeking challenges and taking risks. They are talented and they have been lucky, almost certainly luckier than they acknowledge. They are probably optimistic by temperament; […]. Their experiences of success have confirmed their faith in their judgment and in their ability to control events. Their self-confidence is reinforced by the admiration of others. This reasoning leads to a hypothesis: the people who have the greatest influence on the lives of others are likely to be optimistic and overconfident, and to take more risks than they realize.”</blockquote><p>These kinds of leaders have a vision that they want to make real. Usually, it’s something utterly impossible but irresistibly inspiring. It’s something that resonates with the people who work at the organization. One of my all-time favorite passages that speak to this comes from a book written by one of the original Mac developers, Andy Hertzfeld, in his memoirs about the early Apple days, <a href="https://www.oreilly.com/library/view/revolution-in-the/0596007191/"><em>Revolution in the Valley</em></a>.</p><figure><img alt="Cover of a book by Andy Hertzfeld: Revolution in the Valley" src="https://cdn-images-1.medium.com/max/1024/1*9X7gvFXbEp0RfZowM132Rw.jpeg" /><figcaption>Revolution in the Valley: The Insanely Great Story of How The Mac Was Made</figcaption></figure><p>Hertzfeld writes how Bud Tribble, his manager, described Steve Jobs:</p><blockquote>“Well, it’s Steve…The best way to describe the situation is a term from Star Trek. Steve has a reality distortion field.”</blockquote><blockquote>“A what?”</blockquote><blockquote>“A reality distortion field. In his presence, reality is malleable. He can convince anyone of practically anything. It wears off when he’s not around, but it makes it hard to have realistic schedules.”</blockquote><p>Just to clarify — Andy Hertzfeld’s stories about Steve Jobs are quite frank. He tells the stories as they are, and Jobs was not an easy person to work with! But the man made a dent.</p><p>Visionary leaders have reality distortion fields. When they do it right, their teams buy into that distorted reality and work towards it in <em>whatever</em> it is that they do. Team members are encouraged to do work and to work in ways that complement the crazy vision. And people are discouraged when they don’t. This, to me, is what shapes the true spirit and culture of an organization.</p><p>I’ve had the opportunity to do UX Design at businesses led by engineers, creatives, and UX designers. The engineers mostly built solutions that were functional and powerful and scalable, but on the less usable and beautiful side of the spectrum. The creatives built heart-stoppingly beautiful, fun things with little value other than generating the right kind of noise (which is a completely valid and worthy goal if you’re into marketing!). The UX designers built simple solutions to real humans’ problems: not perfectly crafted creative portfolio pieces, but things that <em>just made sense to people</em>.</p><p>The other two kinds of culture that I’ve experienced are what I can only describe as a weak culture, and a culture based primarily on the pursuit of profit. Weak cultures happen when there is a disconnect between leadership and their teams. The leaders might have a vision, but teams don’t know what the vision is, don’t understand it, or don’t connect with it. Cultures based primarily on the pursuit of profit are everywhere. These kinds of businesses are often very hierarchical and encourage competitiveness, meeting ambitious targets, pre-defined project outputs, and on-time delivery.</p><p>In most organizations, Product Designers are not the most empowered group of people. We have a voice, and if the organization has a listening kind of culture, that voice might be heard, but it also might not have any significant impact on the organization’s culture. So I think it’s important for us, as UX Designers, to consider the culture of the companies we find ourselves in. If your role description at the company does not have a prefix like “Chief”, “Head” or “VP”, chances are that you will have very limited influence on organizational culture. You’ll have a better time and deliver better work if you feel that your goals and values are aligned with the goals and values of the place you work for.</p><p>I tend to believe that most good UX Designers are an empathetic bunch of people. After all, empathy is where Design Thinking begins. We want to understand people’s pain points and solve for them. We want to solve these kinds of problems in surprising, creative, and beautiful ways. We want to build <a href="https://www.nngroup.com/articles/usability-101-introduction-to-usability/">usable</a> (forgiving, efficient, memorable, easily learnable) products. We want to play a part in making the world an easier and better place to live in. We want our designs to be ethical, accessible, and sustainable.</p><p>I don’t think that there are many organizations that want all of these things. Building usable, beautiful, creative, surprising products that solve real people’s pain points is hard. It takes time. It demands a particular kind of mindset that includes words like customer-centric and experimental. I realize that it might seem as if I’ve jumped from culture to process, but I believe that one determines the other.</p><p>Good designers want to build <a href="https://www.humanetech.com/">humane technology</a>. If your company isn’t all that interested in a more humane world and even asks you to design products that are harmful and unethical, you are going to have a hard time. If your company <em>is</em> interested in a more humane world, but clueless about the processes that need to be in place to design things in a human-centered kind of way, you are also in for some interesting times.</p><p>If you are not in a position to change your company’s culture or its processes, and they clash with your goals or your value system, you have some tough choices to make. Whatever you decide to do, be honest with yourself about:</p><p>(1) what you want to achieve in your career over the long term,</p><p>(2) whether you believe you will achieve some part of your goal in the organization you find yourself in, and</p><p>(3) how much influence you have on your company’s culture.</p><p>If the answer to (3) is “Not much” and you find that you are spending most of your time doing work that doesn’t set your soul on fire in some way, it might be time to move on. If you’re not ready to move on, remind yourself on a daily basis that a lot of your unhappiness as a designer stems from a culture that clashes with your value system, rather than some kind of personal deficiency.</p><p>One of my biggest frustrations at a company I worked for was that I felt as if I was often the bottleneck in the process. The developers wanted me to deliver detailed specs for them to build. I insisted that we needed to prototype things — together, as a team — usability test these with real people, and then build them iteratively. This takes a lot longer than simply specifying a solution and building it, but one removes the risk of building something expensive that nobody wants.</p><p>I had a conversation with a friend who is now the Head of Product Design at a payment solution company and I told him about my intense frustration at feeling like the bottleneck. His response, with a big smile on his face, was: “I <em>love</em> being the bottleneck! That’s what we do, isn’t it? We stop people building stupid sh*t that doesn’t make sense.” Maybe he’s right. In a world where more than 99% of consumer apps fail, we clearly need more people saying: “Wait but why?” Or at least: “How about we prototype and test that first?”</p><p>Depending on your company’s culture, your questions will be welcomed and responded to or you will be shut down. You are the only person who can judge whether this is something you can live with or not.</p><p>UX Design is not easy. The world is constantly changing, people’s behavior is changing, the way businesses operate is changing, and tech changes all the time. As a UX Designer, you are slap-bang in the middle of all of those and your job is to design solutions while the carpet is moving underneath your feet. It’s very exciting and incredibly interesting, but it is hard. No UX Design project is the same, even if the same tools and frameworks are used. You need people who understand this around you.</p><p>This brings us to the next piece of advice my friend, Anouk, shared: <strong>learn a bit of self-compassion</strong>.</p><h3><strong>Develop self-compassion</strong></h3><p>Designing and building well-made digital products is hard.</p><p>Stakeholders provide vague briefs and expect high-quality solutions to be delivered at speed, without necessarily providing a definition of how “high-quality” is defined. Designers often work in isolation, delivering designs that are impossible to build within any realistic timeframe. Developers are put under pressure to build designs that have been signed off by stakeholders with little understanding of the complexity of the design. Product Managers and Scrum Masters all seem to adopt their very own flavor of Agile or Scrum, which makes the process a bit confusing for new members joining the team. Existing architecture sometimes means that front-end and back-end are too tightly coupled, making what should be simple front-end changes ridiculously complex. Building good software is expensive, which often puts pressure on everyone to deliver too ambitious results in too little time. The challenges are endless. The point is: building good tech is hard. Many books have been written about it. We are still figuring it out.</p><p>I have the pleasure of working with an incredibly communicative and people-oriented front-end developer. We recently spoke about chemistry checks with people applying for development positions. I mentioned that it must be difficult for him because he likes <em>everyone</em>. His response surprised me. He said: “I like people, but you have to look at this person, figure out if they have the right skills, and then ask yourself if you want them in the trenches with you.”</p><p><em>In the trenches</em>. Those were his words, and my first reaction was to agree. A war-making analogy! Because things get stressful in Product, right? And when things get hard, you need people you can rely on and who you feel comfortable with.</p><p>But it’s also a little crazy. We feel as if the work we’re doing is like going to war. This means that we need to be like soldiers. We have to sacrifice ourselves for the greater good. We have to fight.</p><p>Wait a minute.</p><p>Maybe it’s time to sit back and realize that product development is <em>not</em> a war. No one’s going to die**. Maybe it’s time to appreciate that everyone in the team: designers, managers, scrum masters, developers, architects, owners, and whoever else, has a piece of complexity to deal with. Perhaps it’s time to learn to appreciate and respect everyone’s skills and efforts — including our own. As Designers, we often underestimate the value we bring. This doesn’t help when you are the Designer working late nights to get the job done.</p><p>To some degree, this is where self-compassion comes in. Here’s <a href="http://ccare.stanford.edu/research/wiki/compassion-definitions/self-compassion/">a formal definition</a>:</p><blockquote>“<strong>Self-compassion</strong> has been recently defined by Kristin Neff (2003) as having three interrelated components that are exhibited during times of pain and failure. Each component has two parts, the presence of one construct and the negation of another. These three concepts are: (a) being kind and understanding toward oneself rather than being self-critical, (b) seeing one’s fallibility as part of the larger human condition and experience rather than as isolating, and (c) holding one’s painful thoughts and feelings in mindful awareness rather than avoiding them or over-identifying with them.” (Barnard &amp; Curry, 2011).</blockquote><blockquote>Barnard, L., &amp; Curry, J. (2011). Self-Compassion: Conceptualizations, correlates &amp; interventions. <em>Review of General Psychology, 15</em> (4), 289–303.”</blockquote><p>When my friend told me to learn self-compassion, my first reaction was a bit of a scoff. It felt like she was expressing pity — only, Anouk is not one to pity others. Neither am I. Pity is not helpful.</p><p>But self-compassion is not about self-pity. It’s also not about self-indulgence or a sense of entitlement. Self-compassion does not imply that your work should be painless and easy, or that you should never give more than you expected to. Having self-compassion means that you:</p><p>(1) <strong>Are kind to yourself</strong>,</p><p>(2) <strong>Realise that you are human</strong>, just like all the other humans around you, who all make mistakes and struggle at times</p><p>(3) Are open to all of the emotions and thoughts you may be experiencing, especially the “war-zone” emotions, but you also <em>don’t over-identify with them</em>.</p><p>The best thing is: self-compassion is something we can all cultivate within ourselves. It’s a skill. Thinking about the three points here, self-compassion is cultivated when you:</p><p>(1) Recognise that you have a pretty unkind &amp; critical inner voice that makes a noise when you make mistakes. Consciously listen to that voice whenever you make mistakes and think what you would say to a good friend who told you about a similar mistake that they made.</p><p>(2) Reach out to people when you’re suffering. Realize that everyone is suffering on some level. Don’t allow your struggles to isolate you. We’re all human.</p><p>(3) Do solid mindfulness meditation. Allow your thoughts and emotions to surface, observe them, and move on. Don’t suppress them. Don’t over-identify with them. Watch them, both the good and the bad, come and go.</p><p>A lot of UX Designers suffer from perfectionism. We want the details to be right. We want the design system to be adhered to. We like alignment and beautiful proportions and perfect grammar and experiences that flow. We want our designs to be usable <em>and</em> desirable. But the problem with perfectionism is that it’s often pathological. From Brené Brown’s book <a href="https://brenebrown.com/book/the-gifts-of-imperfection/">“The Gifts of Imperfection”</a>:</p><blockquote>“<strong>Research shows that perfectionism hampers success. In fact, it’s often the path to depression, anxiety, addiction, and life-paralysis</strong>. Life-paralysis refers to all of the opportunities we miss because we’re too afraid to put anything out in the world that could be imperfect.”</blockquote><p>She goes on to describe how self-compassion helps us to overcome perfectionism, and how self-compassion leads to compassion, which in turn extends to the people around us and creates a space where they can be their authentic selves.</p><p>This brings us to the best thing about compassion in organizations, and why businesses should be paying attention to the work coming out of the likes of CCARE (<a href="http://ccare.stanford.edu/">The Center for Compassion and Altruism Research and Education</a>) at Stanford University: <a href="https://www.researchgate.net/publication/254109420_Effects_of_Positive_Practices_on_Organizational_Effectiveness">organizations with more compassionate cultures, are more productive and profitable</a>. Let me just repeat that, for good measure: <strong>more compassionate organizations tend to be more successful</strong>.</p><h3><strong>Last words</strong></h3><p>There is so much more to say on these pieces of advice, but here they are in a nutshell:</p><p>(1) <strong>Consider your greater living environment</strong> and its effect on you and your team.</p><p>(2) <strong>Consider your work environment</strong> and if it’s making you unhappy, change it if you are in a position to change it. Or move on.</p><p>(3) <strong>Develop self-compassion</strong>. Try mindfulness meditation. It’s super trendy right now. I recommend giving <a href="https://wakingup.com/">Sam Harris’ app, Waking Up</a>, a go.</p><p>All the best. Here’s to making the world an easier place to live in in 2022.</p><p><em>** I realize that many designers work in settings where people might actually die. I’m referring to the design of consumer apps, where the greatest loss might be a bit of time, money, or frustration. If you’re designing for healthcare workers and pilots, the conversation changes.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2cb87135cb6" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-survive-a-design-career-and-avoid-burnout-part-3-a2cb87135cb6">How to survive a design career and avoid burnout (Part 3)</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 survive a design career and avoid burnout (Part 2)]]></title>
            <link>https://uxdesign.cc/how-to-survive-a-design-career-and-avoid-burnout-part-2-3f3957e33fd0?source=rss-d25a0d79e797------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f3957e33fd0</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[burnout]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Carien Moolman]]></dc:creator>
            <pubDate>Sat, 17 Jul 2021 21:43:41 GMT</pubDate>
            <atom:updated>2021-07-19T14:41:05.588Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi, people in the UX Design and Product world. This post is <a href="https://uxdesign.cc/how-to-survive-ux-design-and-avoid-burnout-d410a9e14c1a">the second in a series</a> I’m writing, based on conversations I’ve had with Product and Experience Designers and leaders in the field, who prosper <em>despite</em> working in some really harsh environments. And when I say “harsh”, I’m talking about business environments that are pretty volatile and where the UX Designer* role is often <strong>ambiguous, overloaded or in conflict</strong> with the roles of other team members, these 3 factors being strong predictors of burnout.</p><p>In Part 1 of this series, I wrote about a conversation with a friend who works as the Design Director at a commercial bank in South Africa. You can read the entire post <a href="https://uxdesign.cc/how-to-survive-ux-design-and-avoid-burnout-d410a9e14c1a">over here</a> if you are that way inclined. For most of the readers, who don’t have yet <em>another</em> 15 minutes to spare, his advice centred around 3 things:</p><ul><li><strong>A crew</strong>: you need <strong>team members who have your back</strong> and will happily fail with you</li><li><strong>A rocket</strong>: you and your crew need to share the same clear <strong>vision</strong> of what it is you are trying to achieve</li><li><strong>A trail of destruction</strong>: you need to accept that <strong>destruction is necessary</strong> if you want to make change happen</li></ul><p>This second piece is based on a chat I had with Jen**, who is the Chief Experience Officer at a pretty big digital agency in South Africa. In contrast with the advice given by my friend in Part 1, her advice looked more inward.</p><p>Jen and I worked together years ago.</p><p>She’s the kind of person I’d have a nonchalant conversation with about aliens visiting humans, giants walking the earth back in the day and how we’re all living in an endless spectrum of possibilities that are playing themselves out simultaneously in every moment. And then about the best new coffee places in Melville (in Jo’burg), or how Jen’s freakishly large canary is always bullying the smaller one. We would also have fun talking about nerdy UX things like progressive disclosure and the right content types for a particular customer’s website, or <em>exactly</em> how to visualise individuals’ financial wellness on a dashboard.</p><p>Jen is not someone I’d describe as narrow-minded.</p><p>She has also <em>totally</em> prospered in a frenetic agency environment, where she really stands out for being the calm in the storm. When I think of her, the likeness that jumps to mind is Venus’s expression in the famous Botticelli: completely calm and focused on a future the rest of us can’t see. Yet.</p><figure><img alt="Detail of Venus’s face in the Birth of Venus by Botticelli" src="https://cdn-images-1.medium.com/max/1024/1*u3c1DHJ18X0onka2rg8FLg.jpeg" /><figcaption>Botticelli’s Venus</figcaption></figure><p>In highly charged situations with silly deadlines and wildly different personality types, she would be the person focused on the next steps and how to make it happen.</p><p>Jen and I met over Zoom this time, on a Friday afternoon. I was grateful that she had made time for me. I’m pretty sure her calendar looks like a bad Tetris game nearing its end. Case in point, towards the end of our hour, she had to excuse herself to get to her <em>next</em> work-related meeting, at 6 pm on a Friday.</p><p>I told her that I was feeling a bit burnt out and disillusioned with UX Design and needed to understand how she did it. How did she keep up the Venus look-and-feel? How did she convince heavily immovable big businesses to change their direction and veer towards customer centricity, all amidst the insanity of ad agency life? Jen had two broad pieces of advice for me that I’d like to share: know yourself and know when to let go. They sound unrelated, but it turns out they’re completely connected.</p><h3><strong>Know Yourself</strong></h3><p>Jen first reminisced a bit about our time working together years ago. She then said that she suspected that my personality type lent itself out to burnout and that this was something for me to ponder. From anyone else, these would have felt like harsh words, but coming from her, they settled down gently.</p><p>She spoke about her current team, whom she clearly adores. They had all completed the same personality type assessment (a version of the <a href="https://www.myersbriggs.org/my-mbti-personality-type/mbti-basics/">Myers-Briggs Type Indicator</a> or MBTI for short) and had spent a good amount of time talking about each team member’s type and how they might work together better. She recommended this kind of exercise for any team I might find myself in.</p><p>I’ve never been a particularly big fan of the MBTI or any personality or psychometric tests as guides for important life decisions. I believe (together with <a href="https://en.wikipedia.org/wiki/Walter_Mischel#">Walter Mischel</a>) that our personalities aren’t quite as static or as dependable a predictor of our behaviour as we might think. Our environments and situations play a much bigger role than we care to admit. Also, neuroscience has shown that we are able to <a href="https://www.linkedin.com/pulse/energy-economics-cost-paying-attention-/?trackingId=yKR8/DTSo9MpNmGYCsBQTQ==">consciously reprogram how we respond to events and thoughts</a>. We can train ourselves to have healthier default reactions to stressors over time by practising mindfulness, as an example.</p><p>I also think <strong>we are epically bad at assessing ourselves</strong> and the world around us. This is why another objective and professional human being (like a therapist, coach or counsellor) might be a better call. I love this Daniel Kahneman quote:</p><blockquote><strong>The world in our heads is not a precise replica of reality</strong>; our expectations about the frequency of events are distorted by the prevalence and emotional intensity of the messages to which we are exposed.” ~ Thinking, Fast and Slow</blockquote><p>Basically, our experiences and expectations are based on odd personal distortions of reality, and knowing yourself might help you to see what your very own personal distortion eyewear is doing.</p><p>Getting back to the MBTI, it’s well-known that the statistical and test validity of the MBTI has been the subject of a <em>lot</em> of criticism, with some of the harsher critics even <a href="https://www.newyorker.com/magazine/2018/09/10/what-personality-tests-really-deliver">comparing MBTI type descriptions to horoscopes</a>. But I think <strong>the strength of the MBTI lies in how it might help you and your team to discover something about yourselves that you weren’t actively aware of, and therefore not consciously considering</strong> while going about your day, designing and building digital products under stressful conditions.</p><figure><img alt="Cover of the novel Mostly Harmless, by Douglas Adams." src="https://cdn-images-1.medium.com/max/301/1*2M2IPY-ObHoiZjJFsiacKQ.jpeg" /><figcaption>Mostly Harmless, by Douglas Adams</figcaption></figure><p>Douglas Adams, bless his galactic backpacking soul, said it well:</p><blockquote>“In astrology*** the rules happen to be about stars and planets, but they could be about ducks and drakes for all the difference it would make. <strong>It’s just a way of thinking about a problem which lets the shape of that problem begin to emerge. </strong>The more rules, the tinier the rules, the more arbitrary they are, the better. It’s like throwing a handful of fine graphite dust on a piece of paper to see where the hidden indentations are. It lets you see the words that were written on the piece of paper above it that’s now been taken away and hidden. The graphite’s not important. It’s just the means of revealing the indentations. So you see, astrology’s nothing to do with astronomy. <strong>It’s just to do with people thinking about people.” </strong>~ Mostly Harmless</blockquote><p>***and personality type assessments :)</p><p><strong>Two more strengths of the MBTI are its popularity and simplicity.</strong> I was always surprised when people rattled off their four-letter Myers-Briggs type, but having done a version of the assessment myself, I get it. Once you understand what the four letters mean, you won’t forget them, and people <em>just adore</em> sharing and comparing theirs with yours. It’s like being in a global club of 16-personality-typers.</p><p>I’ve spoken to a few other considerate Product and UX people in the last while, and it seems as if many product businesses have done <em>some</em> kind of personality or strength-and-weakness assessment to help people understand themselves and their teammates a little better, ultimately to perform better.</p><p>For some of the designers I spoke to, the assessments might help in as basic a way as knowing who will sincerely appreciate and warmly respond to a genuine “How <em>are</em> you?” and who would love to skip the fuzzy bits and hit those bullets in the meeting agenda <em>right away</em>.</p><p>Thinking about the natural and never-ending cycle of product design and build, it’s also probably good to know who in your team is going to be energised by certain exercises and who might enjoy it, but need breaks in-between and a nap afterwards. And it’s not as easy as looking at the classic Design Thinking Process and mapping all the extraverted people to the divergent sections and the introverted people to the convergent parts.</p><figure><img alt="The Design Thinking Process as a double diamond. The first diamond contains divergent empathy and convergent definition (of a problem). The second diamond says we diverge by thinking of many solutions and then converge on one or two to take forwards and test." src="https://cdn-images-1.medium.com/max/1024/1*ZjyQzeuMwMm8CNu5CgqKnw.png" /><figcaption>The Design Thinking Process Double Diamond</figcaption></figure><p>I’m an introvert, but running one-on-one usability tests and customer interviews is one of my <strong>favourite things in the world</strong>. And after about four of them on one day, I’m <em>shattered</em>. On the other hand: give me a prototype to get built, and I’ll keep going until somebody or <em>something</em> stops me. We can still enjoy doing things that deplete us, but we need to be clever about this.</p><p><a href="https://blog.neurozone.com/human-energy-is-economical">We’re all finite</a>. We have a finite amount of mental energy, with some activities energising us and others depleting us. We need the collective to temper, encourage and combine the right ideas and activities at the right times.</p><p>When we know ourselves and the people in our Product teams and we know what kinds of tasks</p><ul><li><strong>need intense group work or hours of individual focus,</strong></li><li><strong>need more gut-feel decisions vs concrete choices</strong>,</li><li><strong>need structured thinkers and which need free thinkers</strong> and who those people are,</li><li><strong>need a more empathetic or a more analytical response </strong>and who the empaths and analysts in the team are,</li></ul><p>we’re more likely to perform well together, be happier and find a sense of personal meaning in our work. This has definitely been the case for Jen’s team.</p><p>Not everyone trusts the MBTI. Some swear by <a href="https://en.wikipedia.org/wiki/Big_Five_personality_traits">the Big Five</a> or <a href="https://www.enneagraminstitute.com/how-the-enneagram-system-works">the Enneagram</a> or some other assessments that may involve other teammates assessing you (which helps for those of us who tend to assess ourselves more or less favourably than we should).</p><figure><img alt="The 9 basic personality types of the Enneagram." src="https://cdn-images-1.medium.com/max/1024/1*We5xmhcZOYkiHtYt8uEMZQ.jpeg" /><figcaption>The Enneagram says that there are 9 basic personality types (Picture from: <a href="http://www.ciphermagazine.com/articles/2018/2/7/the-nine-types-of-people">http://www.ciphermagazine.com/articles/2018/2/7/the-nine-types-of-people</a>)</figcaption></figure><p>Perhaps the best thing anyone can learn from these myriad assessments is this: <strong>you are finite</strong>, and some things energise you and others deplete you.<strong> </strong>Just like everyone else in your team. So it’s probably good to get comfortable with your vulnerabilities and to help everyone to play to their strengths, including you.</p><h3><strong>Let Things Go</strong></h3><p>The second part of Jen and my conversation was about the notion of meaningful work and knowing when to let go of things, rather than trying to control all the moving parts of a digital Product team.</p><p>Jen told me how she had learned over the years to set boundaries with clients and that she had started giving one day of her work week to support worthy startups in a consulting role. She said something that stayed with me (paraphrased from memory):</p><blockquote>“You have to learn to not always be in control of the outcome of your efforts. You give something of yourself, and then you have to let it go. You kind of send your energy out into the world, like ripples in a pond, and then you have to trust the universe to pull everything together in the right way.”</blockquote><p>I shared her words with another UX friend, who immediately wanted to know what Jen was on because it’s obviously the good stuff. I suppose the ripples in the pond part <em>does</em> sound a bit…spiritual, but I thought about it again. And again.</p><p>I identify very strongly with my work, as most designers do. We put ourselves into the things that we make, and even the most thick-skinned and experienced designers feel <em>some</em> pain when their work is criticised or unkindly evaluated or turns out to be flawed somehow (as it always is). If we’re good designers, we set out to design solutions and not to do harm, right? It takes years of practice to listen, to <em>think</em> (unemotionally), and to respond sensibly to less favourable feedback. I’m <em>almost</em> there.</p><p>But there’s a next level that I need to work on. And I don’t think I’m unique in this.</p><p>For me to feel good about myself, I need to deliver work that I am proud of and that I feel makes a positive change in the world, <em>however small that change might be</em>. This is a dangerous place to be in if you’re part of a team — and just about all UX Designers are. Allowing one’s sense of well-being to be tied up with the outcome of a group’s effort is pathological. Let’s say you are part of a Product team where everyone is aligned in terms of values and goals and measures quality in the exact same way. This is rare, but hypothetically it’s possible. The thing is, even if this is true of your team and everyone is perfectly aligned and has the same idea of what success looks like, other stakeholders and managers and externally determined deadlines and technical constraints and revenue (!) will impact what the outcome of the team’s effort is.</p><p>In Product Design, <strong>there will always be forces that are out of your control.</strong> So you need to figure out what your best effort looks like and how you can best support all the members of your team to deliver <em>their</em> best. And then you need to allow the work to happen. And sometimes, it’ll be the outcome you had hoped for, but sometimes, technical and financial realities and constraints will take what’s due to them and the outcome of all of your (and your team members’) efforts might not be the ideal user experience you had in mind.</p><p>It is what it is.</p><p>The good news is that every now and then the universe will play along and the outcome will be something that’s good for the world.</p><p>And finally, as a compassionate and wise friend keeps on saying to me:</p><blockquote>Everything is connected.</blockquote><p>Knowing when to let go of the outcome of your work is inextricably tied up with being aware of who you are. In <a href="https://www.16personalities.com/articles/finding-authenticity">this article</a>, the author writes beautifully about Practical and Pure Authenticity. Basically, we can’t always be 100% true to ourselves (that’s the one called Pure Authenticity). Sometimes we have to practice Practical Authenticity, where we change our behaviour and our expectations for the sake of the greater good. You are the only person in the world who will know when you’ll have peace of mind in letting go.</p><p>***</p><p>And there you have it! Two beautifully simple things to ponder, if you’re fighting the good fight in the world of Product Design or UX Design. Know yourself. Let things go.</p><p>For anyone who wants to <em>really</em> get into the part about knowing yourself better, I can <em>truly</em> recommend grabbing a copy of <a href="https://www.amazon.com/How-Will-Measure-Your-Life/dp/0062102419">“How Will You Measure Your Life?”</a>, written by none other than the legendary <a href="https://claytonchristensen.com/"><em>Clayton Christensen</em></a>, as well as James Allworth and Karen Dillon. Read it right to the end, and do the exercise in the last chapter. It has changed my distortion eyewear a bit.</p><p><strong>Some footnotes:</strong></p><p>*UX Designer or Product Designer, Customer Experience Designer, Service Designer, UI Designer, UX/UI Designer, Product Manager, Interaction Designer or any of the roles involved in building great and thoughtful digital products for fragile human beings.</p><p>**Jen is a pseudonym for a real person, who really looks a little bit like Botticelli’s Venus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*Ah-AAUt6EFuVk0Pf.png" /><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=3f3957e33fd0" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-survive-a-design-career-and-avoid-burnout-part-2-3f3957e33fd0">How to survive a design career and avoid burnout (Part 2)</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 survive a design career and avoid burnout]]></title>
            <link>https://uxdesign.cc/how-to-survive-ux-design-and-avoid-burnout-d410a9e14c1a?source=rss-d25a0d79e797------2</link>
            <guid isPermaLink="false">https://medium.com/p/d410a9e14c1a</guid>
            <category><![CDATA[burnout]]></category>
            <category><![CDATA[neuroscience]]></category>
            <category><![CDATA[t]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Carien Moolman]]></dc:creator>
            <pubDate>Tue, 08 Jun 2021 06:49:02 GMT</pubDate>
            <atom:updated>2021-06-09T09:41:38.092Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi, all you UX Designers, UI Designers, UX/UI Designers, Product Designers, Product Managers, Interaction Designers and Design Engineers out there. This post is basically for everyone who feels like they belong in this picture (by <a href="https://odannyboy.medium.com/">Dan Saffer</a>, re-visualised by Thomas Gläser).</p><figure><img alt="A beautiful Venn diagram of the disciplines that overlap with what we call UX Design, including architecture, visual design, information architecture, human factors and ergonomics, interaction design, motion design and communication design." src="https://cdn-images-1.medium.com/max/596/1*jc89_MQjqPOAKtW1BHuTdQ.png" /><figcaption><a href="https://visual.ly/community/Infographics/computers/disciplines-user-experience-design">The Disciplines of User Experience Design</a> by Dan Saffer, re-visualised by Thomas Gläser</figcaption></figure><p>I recently experienced a bit of burnout. Burnout is no fun at all. You really aren’t your best self. It takes tremendous effort and the love and support of other humans to regain your empathy, to care about anything related to work again, and to remember what it is that you have to offer the world. One also loses one’s sense of humour.</p><p>I have a theory. I think that many UX Designers will tend to burn out at some point in their career, somewhere around their 10th year in the profession, and I’d like to make people aware of what burnout is and how to prevent it. I’ve gathered wisdom and advice from people in the industry who I know and admire. I would like to share their thoughts.</p><p><strong>I always knew burnout existed in a theoretical kind of way. </strong>Especially during my time working at an ad agency, I <em>regularly</em> saw what I thought of as burnout: characteristically highly detailed-oriented, enthusiastically creative and discerning people would stop caring about the quality of their work, seem perpetually exhausted from working too many late nights, and at the same time only <em>just</em> meet their deadlines. Or they would apathetically watch them whoosh by.</p><p>I became one of these folks in 2015. I remember reaching a point where I needed to urgently excuse myself from boardroom meetings to be sick in the nearest bathroom. Nope, I wasn’t pregnant. For a couple of months, I had been working 16-hour days, 7 days a week, eating in front of my computer, not seeing anyone besides work people and downing coffee at an alarming rate. At the time, I told myself I just needed to push through and that the next project would be better.</p><p>Fast forward to 2021, and despite making <em>profound</em> changes to my lifestyle (I quit drinking and smoking, get at least 7 hours of sleep a night, eat healthy food, exercise regularly, and feel like I’m basically a <em>poster child</em> for <a href="https://www.youtube.com/watch?v=O4SzvsMFaek&amp;ab_channel=Radiohead-Topic">Fitter Happier</a>) here I am again.</p><figure><img alt="The lyrics of Radiohead’s track, Fitter Healthier, turned into a beautiful poster by Stacey Sexton." src="https://cdn-images-1.medium.com/max/1024/1*O9ucALv5u-ldiMxQqvMqag.jpeg" /><figcaption><a href="https://staceysextondesign.com/Fitter-Happier">Fitter Healthier by Stacey Sexton</a></figcaption></figure><p>Sigh. This time around, though, I have two beautiful toddlers who deserve a parent who is not cynical, tired and physically ill much of the time. They saved me in a sense. Children give us perspective and courage as nothing else can.</p><p>For the first time in my life, <strong>I quit my job without knowing what I’d do next.</strong></p><p>Friends congratulated me, my husband breathed a sigh of relief, and my parents looked a bit worried and asked if I was okay. For about 5 seconds I felt victorious, and then the panic hit me: what do I do now? Will my brain deteriorate? Will I <em>ever</em> find fulfilling and meaningful work? Will my skills become outdated? Will I be forced to return to some heartless corporate to afford my children’s school fees? <em>WTF? </em>Who am I?</p><p>Adding to my extraordinary levels of anxiety at the time was the occasional doubt that I was, in fact, suffering from a scientifically recognised condition, rather than some imaginary mental construct I had invented to make me feel better about <em>quitting what I had believed to be my dream job</em> and becoming financially dependent.</p><p>The occasional doubt is slowly dissipating, though.</p><p>You see, I’m lucky. I’ve been able to speak to a few <em>really</em> smart and empathetic people, including a sweet psychologist, a brilliant neurologist and a bit of a whacky general practitioner who has a lot of experience in dealing with patients who suffer from burnout. I also spoke to two friends who admitted to burning out themselves and shared their stories. If it weren’t for all of these people, I would still be listening to that merciless inner voice telling me to “Just harden up and pull yourself together, damn it!”</p><p>Also — it’s 2021 now. In 2019 burnout became an internationally recognised phenomenon. Here is <a href="https://icd.who.int/browse11/l-m/en#/http://id.who.int/icd/entity/129180281">how the ICD-11 describes it</a>:</p><blockquote><strong>“Burnout is a syndrome</strong> conceptualized as resulting from <strong>chronic workplace stress that has not been successfully managed</strong>.</blockquote><blockquote>It is characterised by <strong>three dimensions</strong>:</blockquote><blockquote>&gt; feelings of energy depletion or exhaustion;</blockquote><blockquote>&gt; increased mental distance from one’s job, or feelings of negativism or cynicism related to one’s job; and</blockquote><blockquote>&gt; a sense of ineffectiveness and lack of accomplishment.</blockquote><blockquote><strong>Burn-out refers specifically to phenomena in the occupational context</strong> and should not be applied to describe experiences in other areas of life.”</blockquote><p>Sound familiar?</p><p>There are various diagnostic tools that have been developed to determine whether one has burnout and if so, how severe it is — <a href="https://en.wikipedia.org/wiki/Maslach_Burnout_Inventory">The Maslach Burnout Inventory</a> being one of the most reliable. I was provided with some of these tools by my whacky GP. The results were as conclusive as they can be.</p><p><strong>Now for the thing that really jumped out at me</strong> while I was reading up on burnout and made me think of us as a community of UX Designers (and related positions).</p><p>In 1974 <a href="https://en.m.wikipedia.org/wiki/Herbert_Freudenberger">Herbert Freudenberger</a> (who was friends with Abraham Maslow) published one of the first journal articles on burnout. He went on to author three books on the subject. According to him, <strong>three predictors of burnout</strong> are:</p><ol><li>role conflict,</li><li>role ambiguity and</li><li>role overload.</li></ol><p>When I read this, it really shook me. I read it again. And again. <em>And again.</em> These three things — <strong>role conflict, role ambiguity and role overload</strong> — are common amongst physicians, teachers and people in social services.</p><p>I would like to add UX Design to that list of professions.</p><p>If you call yourself a UX Designer, UI Designer, UX/UI Designer, Product Designer, Product Manager, Interaction Designer or Design Engineer or <em>whatever</em>, I am willing to bet that you’ve been in a situation or two where people expected you to do much more or much less than you believed you had to, or you were expected to do things outside of what you think of as your domain. (Luckily or perhaps <em>un</em>luckily, people who decide to dedicate themselves to any of the UX Design-related roles are typically also people who love to learn new things and neglect their boundaries).</p><p>Perhaps you’ve found yourself delivering work only to find that another team member had already done it or had made decisions regarding the direction of the product that nullifies or damages your contributions. I bet every UX Designer has been in this kind of scenario: you expected to be involved in the design and build process from the get-go, but instead, you are asked to do UX “magic” once all the fundamental design decisions had already been signed off by stakeholders.</p><p>If Freudenberger was right, and role conflict, ambiguity and overload <em>are</em> predictors of burnout, many of my UX peers must be burned out already or well on their way.</p><p>I decided to call up people who I love, respect and admire in the UX design world, and who seem to be flourishing and to ask them how they felt about their work.</p><p>I want to understand how some people seem to not only survive UX Design, but <strong>prosper</strong> and overcome truly difficult circumstances to deliver real value to end-users and do work that they themselves are proud of.</p><p><strong>My conversations have been special and surprising and I want to share them. </strong>Maybe, just <em>maybe</em>, this will help other UX Designers not only to <em>not</em> hit rock bottom but to flourish and be the joyful people they deserve to be in their work. After all, we get into UX Design because we want to make the world a better place for our end-users. And that’s a worthy and meaningful goal.</p><p>So here goes. I’ve decided to dedicate one post to each conversation I’ve had so far, starting with these three:</p><ol><li>Stanley*, Design Director at a commercial bank</li><li>Jen*, Chief Experience Officer at a digital agency</li><li>Anouk*, Senior UX Specialist at an ambitious Norwegian startup</li></ol><p>*I’ve decided to give them aliases because I’d like the real Stanley, Jen and Anouk to stay friends with me and not get fired.</p><h3><strong>Your Crew, your Rocket, and your Trail of Destruction</strong></h3><p>I’ll begin with my conversation with Stanley. I can’t give away too much about the man, because it would then be pretty easy to identify him. Let’s just say that he’s a guy with a mind like a diamond and a sense of humour that hits home. I’m still not sure how he ended up in digital design. He is impressively qualified in a domain that’s pretty non-related.</p><p>We worked together for a while about 5 years ago, directly and indirectly, in a corporate consulting environment. Corporate restructuring happened one too many times and he left for the banking world, and I left to join a startup.</p><p>We met over Zoom. I live in Melkbosstrand and he works in Johannesburg, about 1200 km apart. Stanley was in a collaborative office space, so not at home and not at the bank.</p><p>We had the usual chat about Covid and adjusting to remote work. Stanley asked if I had read the research on how we are able to trick ourselves into becoming more focused by only doing specific tasks in specific places or while sitting in certain chairs. I hadn’t. But the conversation stayed with me and I’ve played with the concept. There’s something to it.</p><p>We also spoke about our children and the incredible cuteness of little humans learning to speak.</p><p>He asked if I was looking for work, which I wasn’t. I told him I was just talking to people because I needed to understand how some UX designers seem to survive and prosper. I’ve done project-based work in the bank where Stanley is, and I’ve seen how some people behave towards one another there. It can get pretty rude and aggressive. I remember a specific incident one day about 4 years ago. I was still a consultant and assigned to a project at the bank where he had moved to.</p><p>Stanley joined our project team in a boardroom and was drawing and explaining a process concept on a whiteboard. One of his colleagues, tall, beautiful and slim, dressed in a tailored dress suit, clicked in on high heels, rudely interrupted the session and then claimed the rest of the meeting for herself. Without skipping a beat. I mentioned the incident to him, and he smiled and thought for a moment before replying.</p><p>Here’s the advice, which I am paraphrasing from memory.</p><blockquote>“You see, you need a crew in these difficult environments. And you need to understand that you won’t make changes happen quickly. Your crew is important…You need a vision. And you almost need to strap yourselves into this vision, like a rocket ship, and leave a trail of destruction behind you. And when things go wrong, it’s fine, because you have one another, right? And you can have a few drinks together and move on. And over time, you see change happening.”</blockquote><p>I giggled a bit. And we spoke about the future and where we picture ourselves in the next few years and promised to chat again (which I know we will). Then we said our goodbyes. (I sent him this piece in the meantime to sanity check it!)</p><p>I thought about what he had said a lot:</p><h3><strong>You need a Crew</strong></h3><p>You are not an island. Hopefully, there’s nothing surprising here, right? Trying to make change happen on your own, no matter how skilled or talented you are, <em>especially</em> if your job title has the word “designer” in it, is an exercise in futility.</p><p>Perhaps you’re part of an organisation where your team and your leadership understand what UX Design is, your processes make way for it and provide time for user research and checking that your product or service is having a positive impact on the world. Then you’ll also recognise the joy of collaboration and recognition of every team member’s contribution to the end product. It’s a lovely place to be in, and a rare one.</p><p>I think that more commonly UX Designers work on their own or in a siloed department. And they work really hard and craft their contributions in solitude, believing that the best creative work is done in a kind of a safe zone, removed from the rest of the business. There’s this notion of working independently and being rewarded for crafting original ideas on your own or with other “creative” souls like yourself.</p><p><strong>If this is you, you need to reach out.</strong> A great deal of research has been put into the concept of neuroplasticity — how our brains are continually reshaping themselves and growing new pathways. What is becoming increasingly clear is that <strong>social interactions and relationships, especially those that we experience as deeply meaningful, have a profound effect on how our brains rewire themselves</strong>. Your brain is not only closely connected to your entire body, but also to the minds around it. Considering this, our relationships have an impact on our physical well-being, building up or breaking down our resilience to stressful environments, but also impacting our immune systems and our ability to think creatively.</p><p>You need a good crew to stay mentally and physically healthy.</p><p>(I would love to take a deeper step into this and talk about theories around our minds not being able to even <em>function</em> in isolation, but we’ll keep that for another day. For now: your brain needs other high-performing brains and a sense of Social Safety to perform well, which includes bonding with your crew and having a sense of belonging with a wider community. <a href="https://youtu.be/fGKLO_ZaOT8">Here’s a great video about it.</a>)</p><p>As UX Designers in harsh environments, we won’t survive (very long) if we don’t connect with our team members — and that includes <em>everyone</em> impacted by or who has an impact on the experiences we design. Not only investors, developers, product people, copywriters, testers and visual designers, but also the teams delivering customer support, training (if you have a training department), selling the product and marketing it.</p><p>Right now, digital ethics is also a hot topic, and people like <a href="https://cennydd.com/">Cennydd Bowles</a> would recommend that you get a moral ethicist or a couple of philosophers on board, or provide Product Managers with frameworks for ethical decision making.</p><p>As far-fetched as that might sound, the truth is that our world is full of complex, interdependent systems and problems. Unintended harm is being committed at scale. Coming up with creative, digital, <em>ethical</em> solutions and building anything worthwhile requires a team effort. But designers are <em>still often left to themselves</em>, and expected to make deliverables that can be handed over.</p><p>We’re still solid horizontal bars with a hard beginning and end in a Gantt chart, somewhere. Argh!</p><p>We need to learn to speak up, run ad hoc workshops, make a noise and surface our work and ideas and questions, no matter how incomplete they are, to our team members. <strong>We need to stop the handover madness. </strong>We need to build real connections with a core group of people, who we can support and who we can rely on to support us.</p><p>Optimistic, compassionate, funny people who will have a drink (or coffee, in my case) with us when things go wrong or when we feel overwhelmed.</p><p>Human beings are wired for connection.</p><p>There is no way around this. You need a team to who you feel connected.</p><h3><strong>You need a Rocket</strong></h3><p>Stanley spoke about strapping yourself and your crew to a rocket. It’s a hilarious analogy but it works. Rockets are meant to travel to the stars, which we know ain’t happening any time soon, right? And just like interstellar travel, a worthwhile vision is unattainable. It’s something we’re always working towards, but that we’ll never quite achieve.</p><p>World peace. Equality. An end to human suffering and global warming. Freedom. Respect. “Imagine all the people…”.</p><p>Being strapped together to the <em>same</em> rocket is important. If the people in your crew have different North Stars, things are going to diverge in a bad way.</p><p>Your product vision has to be set (I believe) by a strong, well-spoken and optimistic leader. In my experience, it’s best for leaders to be loud, very talkative and clear about what they want. And a little idealistic and mad. Thinking about your leader should conjure up the undeniable mission that your team is on. When decisions are made or projects are tackled, the team should be able to imagine the leader walking in and know whether she/he will get excited, nod serenely or have a WTF reaction.</p><p>The team has to buy into the vision and be motivated to achieve it. Some of us are designers, some of us are managers, some are builders and makers, others are communicators or administrators or creative thinkers or carers. <em>Whatever</em> we do, if we all do the thing we’re good at, we should be working towards the same vision. And it’s up to each team member to judge whether the piece of work she is putting effort into, is contributing mostly toward the collective goal, or mostly towards a personal goal.</p><h3>You need to see a Trail of Destruction</h3><p>The last part Stanley mentioned to me really emerged from a question I posed to him. At a certain point in time, the bank where he serves decided to do the innovative thing and establish a design team in a beautiful working space physically separated from the bank. This is a common approach large corporates take when they crave imaginative solutions and finally realise that it might be easier to build a creative environment <em>outside</em> of their usual hierarchical and cubicle-filled office spaces, rather than importing creatives into the cubicle ocean and distilling a sense of corporate bureaucracy into them, so that they either lose all sense of creativity and experimental spark, or simply leave.</p><p>The bank established such a space, which I visited a few times. It was <em>so</em> joyful and fun! As a consultant, one gets to choose how much time one will spend at headquarters and how much you’ll spend at the client. When we did consulting work for this particular department at the bank, I spent the maximum allowable time over there.</p><p>The department didn’t make it, though. It made a noise and produced some epic, mindful and just plain <em>good</em> work for a year or two, and passionately criticised a lot of the work coming from the mothership. Then it was shut down, for no discernible reason other than a global partnership that went awry. And the creative souls either left or were absorbed. I asked Stanley what on earth had happened there. I might have imagined a flicker of pain on his face, but his answer was that you have to make peace that you will leave <em>a trail of destruction</em> as you make change happen in a large organisation.</p><p>He left it at that and I didn’t probe any further.</p><p>I thought about it, though. I’m not a trail-of-destruction kinda person, so this part of his advice didn’t sit well with me. Surely, I thought, it’s possible to persuade people to change their ways of working without conflict? To do that magical thing where you tell people what the theory is and what the research says and then <em>they realise for themselves that they need to adopt a different process</em>? Surely.</p><p>Maybe.</p><p>I’m not too sure about this anymore. I think Stanley is right. Let’s say you step into a business where:</p><ol><li><strong>UX Design happens in a department</strong> somewhere, with other designers, or</li><li><strong>You are the only UX Designer</strong> in a sea of developers, or</li><li><strong>UX Design is equated to Visual Design</strong> and people speak about it being sprinkled on top somewhere towards the end of the process, or</li><li><strong>Nobody cares</strong> deeply about the well-being of end-users and therefore usability tests simply don’t happen.</li></ol><p>To change such an organisation to be <em>Human</em>-Centered requires the destruction of <em>something.</em> It might be the current way of working, including how projects are prioritised and scoped. It might be the way teams are structured and what the leadership looks like. It might mean a cultural shift. It will almost certainly entail the destruction of the way that people in the business speak about design and how they speak about their customers and end-users. Organisational change will leave a few bruised and broken egos in its wake. The existing leadership and some team members would have built a particular way of working and be invested in it and proud of it. And it’s hard to let go of something you’re proud of.</p><p>So seek and cherish these three things: <strong>your crew, your rocket and your trail of destruction.</strong> They are lifelines, and your crew is the most important one. Without a sense of social safety the vision of your organisation, however grand and meaningful it is, will not help you. Digital work is not a solo mission. And grand and meaningful missions demand change, which demands a trail of destruction.</p><p>As a friend reminded me the other day, good design <em>has</em> to be revolutionary:</p><blockquote>Design, if it is to be ecologically responsible and socially responsive, must be revolutionary and radical.</blockquote><blockquote>—Victor Papanek</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*t4oDGqWo3FoZebZo" /><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=d410a9e14c1a" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-survive-ux-design-and-avoid-burnout-d410a9e14c1a">How to survive a design career and avoid burnout</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 the UX designer in an Agile product team]]></title>
            <link>https://uxdesign.cc/the-role-of-the-sole-ux-designer-in-an-agile-product-team-497afa8d04ff?source=rss-d25a0d79e797------2</link>
            <guid isPermaLink="false">https://medium.com/p/497afa8d04ff</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Carien Moolman]]></dc:creator>
            <pubDate>Tue, 19 Jan 2021 21:43:38 GMT</pubDate>
            <atom:updated>2021-01-26T19:51:34.662Z</atom:updated>
            <content:encoded><![CDATA[<h4>2020 was a hard year. It drove home something I’ve always known but had been taking for granted: good UX Design relies on an environment, process and team that support good UX Design. If the environment, process and team aren’t quite in place, I would argue that it’s the job of the UX Designer to speak up and take part in shaping them.</h4><p>This is a big and challenging task. Especially if you’re an introvert and a maker rather than a manager at heart. I recently stumbled across this quote in <a href="https://www.forbes.com/sites/stevebaltin/2020/10/06/remembering-a-guitar-god-a-2009-conversation-with-eddie-van-halen/?sh=487f3923309f">an article about Eddie van Halen</a>:</p><blockquote>“If it’s your passion and it’s from the heart, you just keep playing, playing, and playing and eventually somebody’s gonna notice.”</blockquote><p><strong>Not true</strong> in UX Design and probably not even true in the music industry. Eventually, someone might <em>not</em> notice and you would have played your heart out to an empty stage or an audience who just doesn’t get it. You need to be in the right place, playing the right tune, and you need the right band members.</p><p>I would like to share my 2020 experience as the sole UX Designer in an Agile Product Team. I’ll share some of the blunders I made and some of the opportunities I missed, and add some thoughts on a more productive way to go about doing UX Design in a business that’s flourishing and no longer a startup, and together with that success rapidly outgrowing a startup way of working.</p><p><strong>Towards the end of 2019, I joined a locally successful startup building a solution for field sales teams </strong>— a <em>very</em> special crowd of people, believe me. I was <strong>so</strong> excited. I dreamed of being part of a Product Team that would blow minds with its understanding of the behaviour and needs of our target audience. We would follow field salespeople around and observe them in their natural habitat. We would build and test crazy prototypes and argue energetically about them. We would come up with extraordinarily <a href="https://www.nngroup.com/articles/usability-101-introduction-to-usability/">usable</a> designs that fit seamlessly into our customers’ world and <strong>make their lives so much easier.</strong> The product would start selling itself and become an exponential disruptor (Dah Dah Dummmm). We would speak at conferences about how <a href="https://www.mckinsey.com/business-functions/mckinsey-design/our-insights/the-business-value-of-design#">designing for real human beings makes business sense</a>. About how becoming a customer-centric business had not only made us an outperformer in terms of revenue but had saved lives by eliminating lifetimes wasted on unnecessary admin. We would speak about how all of our customers had watched their sales soar.</p><p>It didn’t quite pan out that way.</p><p>2020 was friggin’ hard. Mistakes were made. I underestimated many of the challenges that come when a business is scaling up and also kinda scaling sideways into new economies and cultures. Covid-19 hit us — and with it, the <em>killer</em> Zoom-Slack-Email Combo of Distraction. Deadlines whooshed by. Projects were descoped. Communication and cohesion suffered. Team members lost touch with each other, emotionally and professionally. Embarrassing user experiences were shipped. People resigned. I cried, a <em>lot</em>.</p><p>One morning my 4-year-old daughter stood in front of me, looked up, and said (quote-unquote): “Mama is complicated.”</p><p>And that’s the moment I realised that I had pretty much reached a low point in my work and personal life: questioning my methods and abilities, my purpose, my skills as a parent <em>and</em> a designer, floundering between old and new tools, trying to herd cats in big ideation workshops delivering stupendous ideas with zero budget for any of them, unsuccessfully advocating for the establishment of a design system, and seeing months of team effort go to waste.</p><p>But as Buster Moon said to Eddie Noodleman (in <a href="https://youtu.be/5JTjesbU0zk">Sing</a>, which all parents of 4-year-olds will know):</p><blockquote>You know what’s great about hitting rock bottom? <strong>There’s only one way left to go, and that’s up!</strong></blockquote><p>So let’s do this thing and move onwards and upwards in 2021. And for me (and for the sake of my family’s sanity) an important first step is to find some clarity on this question:</p><p>What is the role of a UX Designer in an Agile Product Team? (And what is a Product Team, anyway? For the purposes of this post, the Product team is a team made up of a PO, PM, UX Designer, Dev Team leads and Developers.)</p><h3><strong>So, what exactly is the role of a UX Designer in a Product Team?</strong></h3><p>Where do the UX Designer’s responsibilities begin and end? I used to be very sure about this. As the UX Designer, my job is to do customer research (and <em>empathise</em>), share insights from that research with the Product Team, identify customer needs and pain points, ideate to find solutions with the Product Team, prototype ideas, test them with real users, learn from mistakes, and then ship a product or a solution and keep on improving.</p><p>This is not a process I dreamed up. I wish it was because it’s pretty darn powerful. It’s good old <a href="https://designthinking.ideo.com/">Design Thinking</a>. It’s been around for a very long time — since <em>1978</em> — and it’s been tweaked and adapted for different kinds of problems. It just makes sense. It’s iterative so it’s meant to be put on repeat, in cycles of learning and improving until your product is as extraordinary as you need it to be. I trust the process, as do <a href="https://www.thegeniusworks.com/2017/05/design-thinking-in-action-35-great-examples-of-companies-using-design-thinking-to-drive-innovation-and-growth/">some of the most successful tech companies in the world</a>: think Apple, Uber, Airbnb, Google and IBM. It’s a good process and looks a bit like this (<a href="https://www.nngroup.com/articles/design-thinking/">thanks, NN Group</a>):</p><figure><img alt="The Design Thinking Process as pictured by the Nielsen Norman Group" src="https://cdn-images-1.medium.com/max/1024/1*hq1gvvV3gJl_-PsiPJp3Mw.png" /></figure><p>From <a href="https://designthinking.ideo.com/">IDEO</a>:</p><blockquote>“Design thinking uses creative activities to foster collaboration and solve problems in human-centered ways.”</blockquote><p>As a team, we did a fair bit of this in 2020. We spent time talking to customers and observing them, and thinking together about our customers and what they need. We came up with some very creative solutions. We made prototypes and usability tested them. We learned from mistakes in our prototypes, ditched a lot of ideas and refined them.</p><p>And then things fizzled out. What we built was not what we designed.</p><p><strong>So what went wrong? </strong>How might we do better? How might<em> I </em>do better?</p><p>At our business, the Product Team process has been split into two stages:</p><ul><li>Discovery, and</li><li>Delivery</li></ul><p>In the Design Thinking visual at the top, the Discovery stage includes the first 5 activities (Empathise, Define, Ideate, Prototype and Test) and the Delivery stage is the last one. The purple rocket labelled “Implement”.</p><p><strong>When our process switched from Discovery to Delivery, concepts were scoped down to such a tiny subset of features that the delivered solution bore little resemblance to the design.</strong> Compromise between design, tech and business is normal and healthy. This pic, right? (Thanks <a href="https://designthinking.ideo.com/">IDEO</a>):</p><figure><img alt="The place where desirability, viability and feasibility come together" src="https://cdn-images-1.medium.com/max/858/1*eLigVGKRNHP9pjPKB3BH2g.png" /></figure><p>Any designer with a few years of experience will know that what can be imagined, can’t be built if you have limited time and resources. I know this and <strong>I welcome the compromises because it means that something <em>real</em> is happening</strong>. There are few things sadder than a solution designed in all of its adorable, pixel-perfect glory, the result of <em>weeks</em> of a talented designer burning the midnight oil a corner somewhere, that never gets built <em>because it isn’t viable or feasible</em>. This is why I welcome collaboration and compromise.</p><p>This quote from Milton Glaser says it well:</p><blockquote>There’s no such thing as a creative type. As if creativity is a verb, a very time-consuming verb. It’s about taking an idea in your head, and transforming that idea into something real. And that’s always going to be a long and difficult process. <strong>If you’re doing it right, it’s going to feel like work.</strong></blockquote><p>But what <em>we</em> delivered, was functional at best and confusing or distracting to end-users, at worst. Usability testing the shipped features was an exercise in futility (and an expensive one, at that) because the team had moved on to the next feature. Any findings that came out of usability testing were interesting but nodded at politely.</p><p>The train had left the station.</p><p>The truth is: if we want to follow an iterative process of failing fast, learning and improving, then our process needs to allow people to fail fast, learn and improve. We made no room for failure in 2020. A feature was specified, built and shipped. We skipped two pretty important steps: learning and improving. <strong>The first live version of a solution is guaranteed to have problems.</strong> This is the way experience design (and life) works. <strong>No first solution is perfect.</strong> Even if a few versions of a prototype have been usability tested, testing can only be qualitative and not done with a statistically significant number of people. Add to this an interesting quirk of our particular field sales solution: it is aimed at a very broadly defined user base, using the solutions in all sorts of unique ways and with highly variable levels of comfort with tech.</p><p><strong>Unknown usability and technical issues will arise after go-live and the process must plan for it, and plan for people and time to fix those issues</strong>. Our business would ship code and leave the Customer Support team to deal with issues — usability and otherwise. The thinking went: the User Experience might be a little bad, but a new feature is live and somewhere on a feature list, a checkmark can be made and a few prospects can be re-introduced to the solution. I would argue that this is not the noblest way of building a product. It certainly doesn’t get you to extraordinary.</p><p>Our process was also too choppy. It went from Discovery (by the UX Designer, with a bit of input from the rest of the team), followed by Delivery (hypothetically by developers working from spec docs that the UX Designer had produced).</p><p>The UX Designer can’t necessarily code and Developers can’t necessarily facilitate unbiased interviews and user tests with customers. Both roles must remain engaged during Delivery and Discovery, and add their voices.</p><h3>7 challenges we faced and some thoughts on each</h3><p>There are a few things that I want to highlight and address in the story I just told — 7, to be precise. Here they are with some ideas on how you (if you find yourself to be the sole UX Designer on an Agile Product Team) might do better than I did.</p><ol><li><strong>There was an expectation that the UX Designer (that’s me) would be delivering a blueprint</strong> of what needs to be built and hand this over to the team. I’m sorry to say that I utterly failed to deliver on this expectation, to the great frustration of many team members! You see: experience has taught me that this is a risky and inefficient way of working. Risky because the UX Designer doesn’t understand the technical implications of a solution, especially an original/conceptual solution, and inefficient because detailed specification documents take a lot of time to produce and are guaranteed to change once development begins. In my experience, it’s best for a team to have a prototype and style guide to refer to, with detail specifications added into tickets by the team, as part of individual user story descriptions. If necessary, the content of user stories can be saved to serve as documentation for reference purposes. As the UX Designer, I should have spoken up early in the process and pointed out that experimentation and figuring out the details need to be a part of our team’s activities.</li><li><strong>The Product Team wasn’t sufficiently involved in customer research and conceptual design</strong>. This means that there is a lack of buy-in from the team, which leads to projects being brutally de-scoped. If a Product Team isn’t convinced that the value of the solution matches the effort involved in building it, they will try to get the minimum requirements met, so they can move on to something they feel is more valuable (or less challenging). The entire team needs to meet or at least observe the people they are building things for. The developers can’t be left to feel that they’re in a world of ones and zeroes when they are the architects of thousands of people’s lives. As the UX Designer, I should have pulled them into research more often.</li></ol><p><strong>3. The process didn’t plan for failure (and improvement). </strong>It planned for features to be shipped and assumed that they will be successful by <em>some</em> <em>measure</em> (other than customer happiness), and for the Product Team to move on to the next feature, rather than learning and improving. This mindset is problematic. “Shipped is better than perfect” is a wonderful motto to have. Seth Godin (gotta love the man) is famous for it, even though he said it a little differently. He said:</p><blockquote>“Step by step, page by page, interaction by interaction. As you start moving, you can’t help but improve, can’t help but incrementally find yourself getting back toward your north star. You might not end up with perfect, but it’s significantly more valuable than being stuck. Don’t just start. <strong>Continue. Ship. Repeat.”</strong></blockquote><p>Continue. Ship. <strong>Repeat.</strong></p><p>If you’re shipping <em>without</em> repeating, you’re shipping incomplete things. Your Product Team (and your UX Designer) will become progressively more unhappy. People want to ship things that they’re proud of. <strong>The process must make room for testing and improvement.</strong></p><p><strong>4. Usability testing was a checkbox exercise</strong> to be nodded at and findings noted in a list, somewhere. Usability testing is a Product Team’s friend. Done right, it is the entire business’s friend. But it needs to be paid attention to. Done on prototypes, it saves the business massive amounts of money by showing what <strong>not</strong> to build. Done on shipped code, it helps the Product Team focus on what needs to be fixed <strong>before</strong> customers start calling the Support Team. However, if there is no time made to respond to the findings of usability testing, it’s wasted effort. If your UX Designer tests a piece of your product with 5 randomly chosen customers and every one of them gets stuck, your product has a problem. Usability testing doesn’t need to be performed on statistically significant numbers of people to be valid. Pay attention to the findings. Fix things.</p><p><strong>5. Timelines were too stringent.</strong> My father-in-law was an eccentric and mildly successful businessman and used to say: “In business, there are three variables: time, cost and quality. You can own <em>two</em> of those, but not all three.” He seems to have bastardised a thing called the <a href="https://en.wikipedia.org/wiki/Project_management_triangle">Project Management Triangle</a>, which is <em>totally</em> something that he would do. In the world of a Product Team, you can also only own two of those. If you have a fixed number of people with a certain skill set (your cost) and you give them a fixed time to get a piece of work done, the only variable left to play with is quality (I admit this needs a post on its own). If timelines are too stringent for the team assigned to the work, the quality of the outcome will suffer. If you want to own quality, team members and timelines need to bend.<br><strong>Closely related to this is that UX Designers need to get better at building business cases for their work. I need to get better at this. </strong>I tend to believe that good UX Design means happier customers, which I correlate with more sales and less churn. It’s an easy conclusion to jump to, but we need to be very careful as Designers that we quantify “more sales” and “less churn” into a Dollar amount. This is hard to do, but it needs to be done if you want to have a sensible conversation with the team about scope.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hMy8cV9QFdECpmsvNVlxkw.jpeg" /><figcaption>The Project Management Triangle (Thank you, <a href="https://www.oreilly.com/library/view/building-enterprise-javascript/9781788477321/6b79cd5a-cd3d-476b-95f9-c7b767e7c02d.xhtml">O’Reilly</a>)</figcaption></figure><p><strong>6. There were too many balls in the air. </strong>There are at least three streams of work happening at any one time in Product Development: building new features, improving or maintaining existing features and designing the future. One Product Team can conceivably work on all three simultaneously. But it’s not a wholesome or efficient process. Shifting focus requires effort. If the Product Team has never been involved in the design process, they will gravitate towards the thing they feel most comfortable doing — which is coding. Or they will gravitate to whatever seems most urgent, which is usually fixing bugs for grumpy customers or customer support folk. The same goes for the UX Designer on the team. Doing customer research, prototyping and testing new ideas, specifying new features and improving existing features <em>all at the same time</em>, is bound to lead to some balls being dropped and in my case, a bit of burn-out. I believe that a clear plan, keeping these three streams of work in mind, will result in fewer balls being dropped, a happier team and a more extraordinary outcome. It’s tricky, but not impossible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/770/1*SsJVRlBCiPF5RrInTxhO1Q.png" /><figcaption>Agile iterations need careful planning if improvements and future design happen as you build (<a href="https://www.process.st/process-flexibility/">Image source</a>)</figcaption></figure><p><strong>7. We didn’t have a design system.</strong> <strong>A good design system</strong> makes rolling out new features faster, makes for a more consistent experience and should save the team masses of time that would otherwise be spent on reinventing interaction and visual design details. A startup can get away with not having a design system. A growing business that has developers working from home and living in different countries and timezones needs a living design system. <a href="https://www.nngroup.com/articles/consistency-and-standards/">Consistency and standards</a>, allowing for <a href="https://www.nngroup.com/articles/recognition-and-recall/">recognition over recall</a> and aesthetic and minimalist design are all <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">key heuristics of usability</a>. A Product Team, especially a dispersed one, needs a design system to have a fighting chance at getting this right. The UX Designer needs to get this in place.</p><p><strong>Daniel Kahneman would probably say that 2021 will be better,</strong> simply because 2020 was a heartbreaking year for many of us and natural regression says it must get better. He wrote:</p><blockquote>“We are far too willing to reject the belief that much of what we see in life is random.”</blockquote><p>Human beings need to explain things. We are wired to try and make sense of our experiences, both good and bad, and to create a coherent story with causes and effects.</p><p>This is me, being true to that humanness, and trying to pick up the pieces of 2020 to put them together in a story that makes sense. I’m not sure that I’ve succeeded, but I’ve certainly had a moment to pause and think about things. And as I wrote this piece, I realised a few things that surprised me. I hope you enjoyed reading this and that it helps you and your Product Team, whatever your role is. Oh, and let me know your thoughts. I would love to hear from <strong>all you talented people out there, trying to make the world an easier place to live in</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*jmlngNemdDyu536K" /><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=497afa8d04ff" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-role-of-the-sole-ux-designer-in-an-agile-product-team-497afa8d04ff">The role of the UX designer in an Agile product team</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[Why I prefer interviews over surveys for Customer Experience feedback]]></title>
            <link>https://carien.medium.com/why-i-prefer-interviews-over-surveys-for-customer-experience-feedback-274110abfe96?source=rss-d25a0d79e797------2</link>
            <guid isPermaLink="false">https://medium.com/p/274110abfe96</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[surveys]]></category>
            <category><![CDATA[interviews-and-insights]]></category>
            <dc:creator><![CDATA[Carien Moolman]]></dc:creator>
            <pubDate>Tue, 21 Jul 2020 05:21:01 GMT</pubDate>
            <atom:updated>2020-07-21T05:21:01.577Z</atom:updated>
            <content:encoded><![CDATA[<p>When it comes to gathering customer feedback, I’m not a fan of surveys. I prefer one-on-one interviews, where it’s possible to ask people to tell their story in their own words and for me to look them in the eye, to see that flicker of confusion, uncertainty or irritation as they share their experiences. I want to see what their office space, home space or workspace looks like and how often they are interrupted, by bosses, children, emails, phone calls and colleagues.</p><p>I want to see how an idea or service or product fits into their life and how small it really is. I want to see people use a service or product and feel their frustration as they struggle to find something or do something, while telling me how much they love this thing.</p><p>Interviews allow me to ask “why?” a lot, and with every “why?” I ask, I unearth <em>unknown</em> pain points and misunderstandings between the businesses and the customers. Interviews have taught me to be humble when it comes to gathering Customer Experience feedback. They make me realise that the very long list of questions I want to ask people, often makes very little sense to them.</p><p>The problem with a survey is that it often forces people into providing a “yes” or a “no”, when they really want to say: “I dunno?” or “Maybe, sometimes…” or “Huh?” It also doesn’t allow people to say: “Actually, I don’t care about any of these things you’re gathering feedback about. I just want <em>[this unknown thing that’s really easy to solve], </em>but I’m doing this survey because I’m hoping to win a voucher.” So while your survey might provide you with clear-cut data that translates into beautiful graphs and metrics, those graphs and metrics are not telling the full story and <em>might</em> be telling the wrong story entirely.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=274110abfe96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why your UX/UI Designer job post drives real UX Designers away]]></title>
            <link>https://carien.medium.com/why-your-ux-ui-designer-job-post-drives-real-ux-designers-away-697e6486651b?source=rss-d25a0d79e797------2</link>
            <guid isPermaLink="false">https://medium.com/p/697e6486651b</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-interface-design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Carien Moolman]]></dc:creator>
            <pubDate>Fri, 20 Dec 2019 11:47:32 GMT</pubDate>
            <atom:updated>2019-12-21T07:56:17.390Z</atom:updated>
            <content:encoded><![CDATA[<h4>Despite all that has been written and blogged and said and vented about on this topic, there still seems to be a misunderstanding of the disciplines of UX Design and UI Design in the world. I’ve engaged on the topic with many people over many years and by now I usually steer clear of it, but a few recent experiences highlighted the unintentional harm that can be done because of this misunderstanding. And so, I felt I needed to re-engage.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AGkjW3UjyFqZiD4FZ3pxSQ.jpeg" /><figcaption>Where UX Design and UI Design fit into the design process</figcaption></figure><p>LinkedIn is littered with job ads for UX-slash-UI Designers and it drives UX Designers <em>nuts</em>! It wastes people’s time when they apply for a position that doesn’t match their experience and skill set. It creates unnecessary friction in the workplace when people expect UI Designers to do what UX Designers are trained to do, and vice versa. It annoys experienced UX Designers and UI Designers that the roles are referred to interchangeably because they are completely different.</p><p>I’m going to repeat this because people seem to feel uncomfortable saying it: <strong>UX Design and UI Design are completely different.</strong></p><p>If you are looking for someone who will:</p><ul><li><strong>wireframe</strong> features and user flows,</li><li><strong>create and apply style guides</strong>,</li><li>define and refine <strong>interface layouts</strong>, keeping different devices and screen sizes in mind,</li><li>ideate and<strong> create conceptual and detailed visual designs</strong>,</li><li>be comfortable with the <strong>interaction patterns of different digital devices</strong> and operating systems,</li><li><strong>understand UI components</strong> and their behaviours in detail, and</li><li>own visual details such as corner radii, component animations and interaction states, <strong>then you are looking for a UI Designer.</strong></li></ul><p>In a nutshell: UI Designers design User Interfaces. UI Design assumes that the solution is digital and focuses on making the things that happen on a screen make sense, look good and feel right to people.</p><p>If, on the other hand, you are looking for someone who will:</p><ul><li><strong>spend time with your customers</strong> in their environments to understand their behaviour and pain points across devices and real life,</li><li><strong>identify and define different types of customers</strong> based on their unique behaviours, skill sets and mental models of the world,</li><li><strong>come up with lots of solutions to those pain points in collaboration with key business stakeholders</strong>, and then prototype them (where possible),</li><li>map out how <strong>digital solutions fit into the bigger customer journey</strong> and their dependencies on the greater ecosystem,</li><li>understand<strong> the people, processes and tools that enable an improved customer journey</strong>,</li><li><strong>test ideas</strong> (including proposed new solutions) by putting prototypes in front of people, observing them and asking the right kinds of questions,</li><li><strong>gather insights from your customers</strong> and convert those insights into new solutions or improvements, and</li><li>save your software company buckets of money by not building things that people won’t use, <strong>then you are looking for a UX Designer.</strong></li></ul><p>In a nutshell: UX Designers design User <em>Experiences</em> and most of the time the experience includes some form of digital interaction.</p><p>The UX Designer and UI Designer <em>might</em> collaborate during conceptual prototyping if a style guide has been established or the kinds of questions that need to be answered by user testing demands high-fidelity prototypes. In my experience, the lighter a prototype is, the easier it is to discard, and the less likely it is that the rest of the team will fall in love with a flawed design. Paper prototypes or unrefined, partially clickable prototypes communicate to the people who come in to test it that the idea is just an idea, which makes them more likely to give valuable feedback. People are more likely to ask: “Why do I need to do [something that they misunderstand]?”, rather than: “Why is the button pink?” The first question is valuable. It tells us that people need more information or that the action we want them to perform in our design doesn’t fit their mental model of what they believe is necessary. The second question adds very little value*.</p><p>Once a prototype has been shown to solve the right problem for people and usability problems have been identified and the solution has been refined, the UI Designer, UX Designer and the development team will work closely together to make that prototype (or at least, a compromised version of it) become a reality. Once it is a reality, a UX Designer will run usability tests on the launched live digital solution, identify more detailed pain points, work with the team to find solutions to those pain points, and refine the solution. This is iterative design, with a repeating cycle of design and <strong>testing with actual end-users</strong>.</p><p>That last bit, about iteratively designing and testing with actual end-users, is ultimately what makes a UX Designer a UX Designer. The UI Designer participates in this iterative process by defining &amp; refining how the interface behaves and what it should look like, given the solutions that have been described by the UX Designer.</p><p>Yet another way of putting it is like this:</p><p>UI Designers embrace human-interface guidelines and interaction patterns and visual consistency. UX Designers embrace the predictable irrationality of human behaviour** and try to find the place where it meets business goals and technical feasibility. Sometimes, one will find a person with both skill sets, but these precious people are few and far between and I truly believe that UI Design and UX Design require different ways of thinking to solve their different kinds of problems. The unicorns who are able to do both, know how to make the mind shift and know when they need to do it. They also know that the companies who demand both skill sets from the same person, probably need to employ two.</p><p>*Except if you have broken a standard interaction pattern by making the button pink.</p><p>**Or as a friend of mine would say, the f***ed-upness that is the human race.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=697e6486651b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>