<?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 Antonia Horvath on Medium]]></title>
        <description><![CDATA[Stories by Antonia Horvath on Medium]]></description>
        <link>https://medium.com/@antonia-horvath?source=rss-5dc5553f6d0a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7Nak2s9BUq_316A7RORL9Q.jpeg</url>
            <title>Stories by Antonia Horvath on Medium</title>
            <link>https://medium.com/@antonia-horvath?source=rss-5dc5553f6d0a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:50:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@antonia-horvath/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[Feeding Your Inner Fire: Find More Joy in Your Work by Understanding What Gives You Energy]]></title>
            <link>https://medium.com/better-humans/feeding-your-inner-fire-find-more-joy-in-your-work-by-understanding-what-gives-you-energy-cb0554d9aea7?source=rss-5dc5553f6d0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb0554d9aea7</guid>
            <category><![CDATA[self]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[success]]></category>
            <category><![CDATA[work]]></category>
            <dc:creator><![CDATA[Antonia Horvath]]></dc:creator>
            <pubDate>Thu, 06 Jul 2023 08:32:14 GMT</pubDate>
            <atom:updated>2023-07-06T08:32:14.629Z</atom:updated>
            <content:encoded><![CDATA[<h4>Run a simple 30-minute work-life energy audit and design experiments to boost your motivation at work.</h4><figure><img alt="Abstract, colourful  collage of a woman‘s face generated by AI" src="https://cdn-images-1.medium.com/max/1024/1*DIMCYMgmEK6WQygirRO4CQ.jpeg" /><figcaption>Image from <a href="https://stock.adobe.com/at/images/abstract-modern-art-collage-portrait-of-young-woman-trendy-paper-collage-composition-generative-ai/568580949">Adobe Stock</a>, by ink drop, generated by AI</figcaption></figure><blockquote><em>“You bring an infections energy and excitement into every room</em>.”</blockquote><p>Sparking magic is one of my superpowers, and that‘s not by chance. Over the last decade, I have cultivated this capacity by observing what gives me energy at work and doing more of whatever that is. That way, I foster an authentic, contagious enthusiasm for my work.</p><figure><img alt="An illustration of an abstract figure that reaches for a star" src="https://cdn-images-1.medium.com/max/1024/1*XwgQkL0F4X4hKq0RqNJ4fw.jpeg" /><figcaption>Image from <a href="https://stock.adobe.com/at/images/quirky-abstract-creatures-cute-funny-characters-with-eyes-doodle-shapes-hands-legs-cartoon-contemporary-style-isolated-elements-design-templates-hand-drawn-modern-vector-illustration/598590541">Adobe Stock</a>, by Dariia</figcaption></figure><p>In the demanding dance of our work lives, understanding what gives us energy is like discovering a secret stash of fireworks. Some tasks just set our hearts aglow. By auditing our work for those energy givers and energy drainers, we can unlock a dazzling enthusiasm, turning our day into an intriguing adventure rather than a monotonous grind.</p><h3>Work Has Become More Pleasant. Or Has It?</h3><p>From a European perspective, work has become safer and more pleasant over the last decades for almost any profession. Work hours decreased. Breaks, time off work, and paid sick time are anchored in the law thanks to Workers’ Unions.</p><p>While physical demands have decreased, psychological stress has increased. Sick time off work for mental health reasons has increased in recent years (see the <a href="https://de.statista.com/statistik/daten/studie/254192/umfrage/entwicklung-der-au-tage-aufgrund-psychischer-erkrankungen-nach-geschlecht/">2022 Statista report</a> on how days off work due to mental illness in Germany have increased since 1997). While we know of the severe consequences that long-term stress has on our health, mitigation doesn‘t (yet) come as a structural approach, it‘s still up to the individual to manage <em>their</em> stress.</p><p>On average, we work 90,000 hours over the course of our lifetime, so why not be deliberate about making it worth our while, not just financially but on a human level? How do we feel at work? When are we most energised? Reflecting on those questions is the first step towards intentional change.</p><h3>A Simple 30-Minute Work-Life Energy Audit</h3><p>The work-life energy audit is a practice for self-discovery for anyone working in any industry or job. It is equally helpful for other parts of life. Whenever I run the exercise, I end up mixing work and life, and that’s ok. If you‘re not yet literate about your feelings, you might appreciate <a href="https://allthefeelz.app/feeling-wheel/">Gloria Willcox‘s <em>Feeling Wheel</em></a> as a vocabulary boost.</p><p>I like to grab a blank piece of paper and a pen and reflect:</p><p>⇢ 10 min: map activities that give you energy<br>⇢ 10 min: map activities that drain your energy<br>⇢ 5 min: explore how to do more of the things that give you energy<br>⇢ 5 min: ideate how to redesign the tasks that drain your energy</p><p>Perhaps you‘ll appreciate a <a href="https://miro.com/miroverse/work-life-energy-audit/">neat Miro template?</a></p><figure><img alt="Screenshot of a Miro template, showing the energy audit workshop" src="https://cdn-images-1.medium.com/max/1024/1*0kN2BnLxNPJS4pPyQlkCGA.jpeg" /><figcaption>Image designed by the author</figcaption></figure><h3><strong>All the small things: finding the branches and twigs</strong></h3><p>I like to think I have an inner fire. It has taken me time to realise that big chunks of wood aren‘t necessarily what makes it crackle and blaze best. It‘s the consistent addition of little branches and twigs that keep it cosy.</p><p>Have a look at the branches &amp; twigs that fuel my inner fire:</p><figure><img alt="Screenshot from a Miro board, from sticky notes containing the things that give the author energy. For example: “Help people do their best thinking collaboratively”, “Taking an ambiguous situation / a complex problem, bring clarity to it and define a way forward”, “Driving creative culture in an organisation; helping people find and leverage their creativity”, and so on." src="https://cdn-images-1.medium.com/max/1024/1*JXuqsBPSN5QTwdubn35f7A.jpeg" /><figcaption>Screenshot from the author‘s Miro board</figcaption></figure><figure><img alt="A collection of photos of things that bring the author energy: brewind fresh coffee, a train window with nature outside, a collection of sticky notes with illustrations on them, the author in a workshop settingm a little lego plane, the author while drawing a persona on a flipchart …" src="https://cdn-images-1.medium.com/max/1024/1*_YoSUbhieOhX9PtTH2Zbcw.jpeg" /><figcaption>Photos by the author</figcaption></figure><p>What would your life look like a year from now if you spent a bit of time doing more of the small things that give you energy daily? Imagine that fire.</p><h3>Small Experiments to Improve Our Work-Life</h3><p>Now we’ve discovered what gives us energy and what drains it. What’s insight without action? As a software person, I think big change best comes in small increments framed as experiments. Based on insights from the work-life energy audit, I prepare experiments to more proactively design how I feel at work. I like to use this syntax:</p><blockquote><em>“I believe that by [action], I will be able to achieve [outcome]”.</em></blockquote><figure><img alt="Screenshot of a Miro template, to set up an experiment" src="https://cdn-images-1.medium.com/max/1024/1*W8bKJzTT5WDc7C4Rf3gWpg.jpeg" /><figcaption>Image designed by the author</figcaption></figure><p>Lastly, I think about how I might measure progress and commit myself to a date when I‘ll revisit my experiment.</p><h3>Example Experiments</h3><p>Of course, everyone’s experiments will look different. By sharing my most recent experiments, I hope to inspire you to take action for yourself:</p><h4><strong>Exploring why my work matters</strong></h4><p>Who’s life is changing due to my work? How? Everyone’s <em>why</em> looks a little different. Gaining clarity about why my work matters helps me show up every morning with a smile: My <em>why</em> is to design a digital future that improves human life. I currently do this by helping teams learn how to design and develop meaningful software — while making their workdays a bit more fun.</p><p>If looking for your <em>why</em> is a topic that resonates with you, I recommend investigating the concept of <a href="https://www.japan.go.jp/kizuna/2022/03/ikigai_japanese_secret_to_a_joyful_life.html"><em>Ikigai: The Japanese Secret to a Joyful Life</em></a>.</p><figure><img alt="An infographic of the japanese concept of “Ikigai”, showing how Ikigai is the sweetspot that occurs when passion, mission, vocation and profession are unified" src="https://cdn-images-1.medium.com/max/1024/1*hdXbJWauSGdZtX4iQDIS4w.jpeg" /><figcaption>Image designed by the author, based on the concept of <a href="https://www.japan.go.jp/kizuna/2022/03/ikigai_japanese_secret_to_a_joyful_life.html">Ikigai</a></figcaption></figure><h4><strong>Taking back control over my time</strong></h4><p>Observing when I am most productive and adjusting deep work and critical conversations accordingly helped me increase my impact. By inventing a personal prioritisation system, I can now more objectively judge what to spend my time on. By adding deliberate time to deal with unforeseeable urgent things like escalations, I ensure they don‘t always push back crucial strategic work. Plus: adjusting the definition of done for my work based on the criticality &amp; impact helped me settle for “good enough” for less impactful things.</p><h4><strong>Meaningful human connection</strong></h4><p>I discovered that the 1:1 conversations that leave room for explorations beyond immediate work that are paramount for my sanity as a mostly remote person don‘t just happen by chance. I need to seek them out regularly and proactively to build lasting relationships. Having a background in user research, I am naturally curious about how other people experience the world. I learned to listen with the intention of having my mind changed.</p><p>If you‘re looking for inspiration to deepen your conversations, you might be surprised by the originality of <a href="https://www.theschooloflife.com/shop/100-questions-work-edition/"><em>100 Questions: Work Edition</em></a><em>.</em></p><h4><strong>Facilitating human collaboration</strong></h4><p>I’m fortunate to have a job that allows me to be in person with my team and customers regularly for strategic moments of collaboration. I like to design and facilitate workshops, and planning for a week <em>on the road</em> once every one or two months keeps the momentum up for the project and myself. When designing engagements with customers, I factor in travel budgets accordingly. I started training as a facilitator while at IBM iX in Berlin, where I later travelled the world teaching people Design Thinking.</p><p>If you’re curious about facilitation, I recommend looking at IBM’s free <a href="https://www.ibm.com/design/thinking/page/courses/Practitioner"><em>Design Thinking courses</em></a> and their <a href="https://ac-gm-static-files-server.lahgrqm5xee.au-syd.codeengine.appdomain.cloud/cloud/architecture/files/design-thinking-field-guide.pdf"><em>field guide</em></a>.</p><figure><img alt="Two images: left: four books: The Workshopper Playbook by AJ&amp;Smart, the book Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days, two booklets by IBM about Design Thinking. Right: a workshop kit with sticky notes, pens, voting dots and a poster, saying: “What problem are we solving together?”" src="https://cdn-images-1.medium.com/max/1024/1*ajhrprUysMZfuxgPnTi42Q.jpeg" /><figcaption>Photo by the author</figcaption></figure><h4><strong>Actively seeking inspiration to keep on learning</strong></h4><p>Another experiment I ran was creating dedicated time in my week to research, meander and look for inspiration. This almost sounds like a contradiction to point 2, optimising my time, but it isn‘t. Without getting inspired, what can we tap into when we need to be creative? I took on a role where projects rotate every couple of months so that I get to wrap my head around new challenges, customers and industries frequently because I know my mind is hungry to learn new things. What’s that comfort zone for anyway?</p><p>If you haven‘t yet, I recommend watching Carol Dweck‘s talk <a href="https://www.youtube.com/watch?v=hiiEeMN7vbQ&amp;ab_channel=StanfordAlumni"><em>Developing a Growth Mindset</em></a>, a celebration of the fact that our skills and intelligence are not something fixed but can be expanded over time.</p><h4><strong>Looking for the good and creating small wins</strong></h4><p>People tell me that I smile a lot and show up with positive energy, and it‘s true: I like to look for the good in things. I cultivated celebrating big and small wins within my team regularly and try to orchestrate work for incremental progress. According to <a href="https://hbr.org/2011/05/the-power-of-small-wins"><em>The Power of Small Wins</em></a><em>,</em> making progress in meaningful work is the single most important ingredient for a positive inner work-life and, subsequently, one’s performance.</p><p>I recently attended three workshops by The School of Life that helped me recognise the beauty in setbacks: <a href="https://www.theschooloflife.com/workshops/adaptability/"><em>Adaptability</em></a>, <a href="https://www.theschooloflife.com/events/resilience/"><em>Resilience</em></a> and <a href="https://www.theschooloflife.com/events/how-to-fail/"><em>How to Fail</em></a>.</p><blockquote><em>“If you stumble, make it part of the dance.”</em></blockquote><figure><img alt="Screenshot from the author’s notes from workshops by The School of Life" src="https://cdn-images-1.medium.com/max/1024/1*qOr660jCJLJ0H1cVOqGY5A.jpeg" /><figcaption>Screenshot from the author‘s notes from workshops by The School of Life</figcaption></figure><h4>Creating something every week</h4><p>With a background in design, making beautiful and fun things matter to me, so I started to challenge myself to <em>create</em> something every week. That might be <a href="https://miro.com/miroverse/profile/antonia-horvath/"><em>workshops</em></a>, <a href="https://antonia-horvath.medium.com/"><em>articles</em></a> or <a href="https://drive.google.com/file/d/1Hht85sjJDbvcYDswi505YiLtKDPAUios/view?usp=sharing"><em>talks</em></a>. One thing I recently rediscovered for myself is <a href="https://www.smashingmagazine.com/2014/11/how-to-get-started-with-sketchnotes/"><em>sketchnote</em></a> journaling: I document insights from books I read as scribbles. The new habit helps me to get inspired while creating something beautiful at the same time.</p><figure><img alt="Seven pages of sketchnotes by the author, condensing insights of the book “Unreasonable hospitality”." src="https://cdn-images-1.medium.com/max/1024/1*lwaSlQ_9zLsT3cCYJ46-0Q.jpeg" /><figcaption>Photos by the author</figcaption></figure><p>For the weeks that I just don‘t feel like I have it in me to create something more substantial, I put a box of LEGO next to my desk, so that, if nothing else, I can create a quirky LEGO monster.</p><figure><img alt="A photo of a box full of lego bricks" src="https://cdn-images-1.medium.com/max/1024/1*h1lN0mQrz3VZ7qi9LlEzAw.jpeg" /><figcaption>Photo by the author</figcaption></figure><h3>What‘s Your First Experiment?</h3><p>By learning to recognise what gives us energy and experimenting with implementing small changes to our work subsequently, we can craft our unique formula for success that yield the capacity to make us dance merrily through our work weeks.</p><p>What experiment might you run this week to redesign your work towards the things that give you energy?</p><h3>A Compass to Navigate Our Careers</h3><p>Few of us have the luxury of suddenly laying down all the work we don’t enjoy. However, applied consistently, the work-life energy audit is a reliable compass that can help us navigate our careers towards the energy-givers in the long run, like brewing the magic potion of tasks that light us up from within.</p><figure><img alt="A retro, black and white illustration of a compass, one arrow pointing towards the words “More of”, the opposite arrow pointing towards the words “Less of”." src="https://cdn-images-1.medium.com/max/1024/1*kkLC7yRKgt828IO9IXp1cQ.jpeg" /><figcaption>Image from <a href="https://stock.adobe.com/at/images/antique-engraving-illustration-of-vintage-compass-black-and-white-clip-art-isolated-on-white-background-compass-of-travel-and-sea-way/284990120">Adobe Stock</a>, by channarongsds</figcaption></figure><h3><strong>Credits</strong></h3><p>Nothing is written out of a vacuum. I was inspired by the perspectives of</p><ul><li>A special thanks goes to <a href="https://www.linkedin.com/in/nickstreet/"><em>Nick</em></a>, my former manager at VMware Tanzu Labs, who introduced me to the <em>work-life energy audit</em> exercise for the first time in a 1:1</li><li>Thank you, <a href="https://www.linkedin.com/in/andreanagel/">Andrea</a>; you recently called out my ‘infectious energy and excitement’ and inspired me to reflect more and write about the topic</li><li>Numerous conversations with colleagues and friends about their inner fire, including someone who has recently had to step away from work due to burnout</li><li>The book <em>Why has nobody told me this before</em> by Julie Smith</li><li>The book <em>Ikigai: The Japanese Secret to a Long and Happy Life</em> by Héctor García and Francesc Miralles</li><li>The School of Life with their <a href="https://www.theschooloflife.com/shop/100-questions-work-edition/"><em>100 Questions: Work Edition</em></a>, as well as their fabulous workshops on <a href="https://www.theschooloflife.com/workshops/adaptability/"><em>Adaptability</em></a>, <a href="https://www.theschooloflife.com/events/resilience/"><em>Resilience</em></a> and <a href="https://www.theschooloflife.com/events/how-to-fail/"><em>How to Fail</em></a></li><li>Gloria Willcox‘s <a href="https://allthefeelz.app/feeling-wheel/"><em>Feeling Wheel</em></a>, a vocabulary boost for your feelings</li><li>Carol Dweck‘s brilliant talk about <a href="https://www.youtube.com/watch?v=hiiEeMN7vbQ&amp;ab_channel=StanfordAlumni"><em>Developing a Growth Mindset</em></a></li><li>Articles in the <em>GEO magazine, health edition</em> (in German), particularly the issues <a href="https://shop.geo.de/de_AT/einzelhefte/einzelausgaben/geo-wissen-gesundheit-17-2021/2011651.html">What strengthens the soul</a>, <a href="https://shop.geo.de/de_AT/einzelhefte/einzelausgaben/geo-wissen-gesundheit-22-2023/2096890.html">The healing power of physical movement</a></li><li>Article: <a href="https://hbr.org/2011/05/the-power-of-small-wins">The Power of Small Wins</a>, Harvard Business Review</li><li>Article: <a href="https://www.smashingmagazine.com/2014/11/how-to-get-started-with-sketchnotes/"><em>How To Get Started With Sketchnotes</em></a>, Smashing Magazine</li><li>IBM‘s free <a href="https://www.ibm.com/design/thinking/page/courses/Practitioner"><em>Design Thinking courses</em></a>, as well as their <a href="https://ac-gm-static-files-server.lahgrqm5xee.au-syd.codeengine.appdomain.cloud/cloud/architecture/files/design-thinking-field-guide.pdf"><em>field guide</em></a>, also <a href="https://www.workshopperplaybook.com/book-choice"><em>The Workshopper Playbook</em> </a>by AJ&amp;Smart and the book <a href="https://www.thesprintbook.com/book"><em>Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days</em></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb0554d9aea7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-humans/feeding-your-inner-fire-find-more-joy-in-your-work-by-understanding-what-gives-you-energy-cb0554d9aea7">Feeding Your Inner Fire: Find More Joy in Your Work by Understanding What Gives You Energy</a> was originally published in <a href="https://betterhumans.pub/">Better Humans</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nine ideas to inspire more meaningful conversations at work]]></title>
            <link>https://medium.com/better-humans/nine-ideas-to-inspire-more-meaningful-conversations-at-work-4ba089526d46?source=rss-5dc5553f6d0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ba089526d46</guid>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[conversations]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[relationships]]></category>
            <dc:creator><![CDATA[Antonia Horvath]]></dc:creator>
            <pubDate>Mon, 03 Oct 2022 13:32:24 GMT</pubDate>
            <atom:updated>2022-10-03T13:32:24.829Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An abstract illustration of a crowd of people — their silhouettes all have a different colour" src="https://cdn-images-1.medium.com/max/1024/1*a7Gnc327hkGmmAwDlwVSRg.jpeg" /><figcaption>Image by Dedraw Studio— stock.adobe.com</figcaption></figure><h3><strong>Nine Ideas to Inspire More Meaningful Conversations at Work</strong></h3><h4>A leadership guide for understanding the type of conversation you need have—and how to have it effectively</h4><p>As a leader, 90% of my job is getting people to work together to solve problems. The magic of people collaboratively designing something no individual could have created alone gets me out of bed every morning.</p><blockquote>“No matter how it looks at first, it’s always a people problem.” — Gerald Weinberg, in his book The Secrets of Consulting</blockquote><p>Over the years, I came across a handful of concepts and ideas that fundamentally changed the way I interact with other humans. As a result, I was able to strengthen relationships and ultimately create more meaning in my work. I hope this collection yields inspiration for you, too. I added a list of training, books and videos that inspired this article at the end.</p><h3><strong>1. The shared pool of meaning</strong></h3><figure><img alt="An abstract, colourful illustration a round jugsaw. Three hands add three jigsaw pieces" src="https://cdn-images-1.medium.com/max/1024/1*CsfOSumlW8FpcNfW3qMDqQ.jpeg" /><figcaption>Image by paul_craft — stock.adobe.com</figcaption></figure><p>Whenever we’re having a conversation, two or more realities meet and create something new. Every fact, perspective, idea, experience and emotion that we and the humans we’re talking with contributing to a conversation form a pool of shared meaning. It’s unique to every conversation and can only be filled when everyone feels safe contributing. It’s our common ground, paramount to moving forward constructively. I love the appreciative way of thinking about a conversation. It helped me be more intentional about what I contribute and how I do so.</p><h3><strong>2. How to spot crucial conversations</strong></h3><figure><img alt="An abstract, colourful illustration of roots vegetables growing out of the soil: an onion, three beetroots and a carrot" src="https://cdn-images-1.medium.com/max/1024/1*NnW7sNjf1kybLZRPQOJYfQ.jpeg" /><figcaption>Image by Евгения Крупель — stock.adobe.com</figcaption></figure><p>At work, we tend to have surface-level conversations about content like daily to-dos, objectives, the project or the next quarter. It’s easy to speak about those. It’s not like content conversations aren’t valuable. But if we’re only ever having content conversations, we’re missing out on deepening our relationships at work in a meaningful way.</p><p>Occasionally, we have more crucial conversations. With high stakes and opposing opinions. With the potential for strong emotions. They’re the conversations that strengthen our long-term relationships and have the potential to solve our more fundamental challenges that are deeper rooted.</p><p>If we feel nervous, uncomfortable, anxious, or the sort before a conversation, chances are it’s not a pure content conversation. It’s not just about the “what”. Instead, we might want to address the underlying pattern or relationship issue and get behind the “why”.</p><blockquote><em>“Anytime you find yourself stuck, there’s likely a Crucial Conversation you’re either not holding or not holding well.”</em> — from the training handbook Crucial Conversations</blockquote><p>I recently learned about the concept of content, pattern and relationship conversations, with their different levels of depth. Let me share an example:</p><h4><strong>Content</strong></h4><p>Robin is your team member. Robin was meant to send a follow-up email to the customer after a workshop until the end of the week. They share on Friday afternoon that they won’t be able to send the email in time. — This sounds simple, doesn’t it? You have a conversation with Robin and find a solution to this particular instance.</p><h4><strong>Pattern</strong></h4><p>It’s been three times that Robin committed to sending follow-up emails but didn’t get to it in time. You start to wonder why this keeps happening. Not that simple anymore, is it? — This will likely be a conversation requiring more exploration of the <em>why</em>. You can’t just focus on the most recent incident but will need to address the pattern.</p><h4><strong>Relationship</strong></h4><p>It’s been three times that Robin missed sending follow-up emails, and the emails aren’t the only thing that Robin doesn’t follow through on. Their behaviour starts to damage the client relationship and reflects poorly on you. You begin to wonder whether Robin was, in fact, the right candidate for the role you hired them for two months ago. — Not easy anymore, is it? This situation might include all sorts of emotions like disappointment, resentment or regret. — This conversation will likely be a relationship-based conversation where you’ll get to the bottom of what the pattern does to your relationship.</p><p>I started to identify crucial conversations by reflecting: where and with whom do I feel some negative emotions at work? What keeps on annoying me? Where am I not being heard? Where am I not expressing what I think/need/feel? Those are the crucial conversations that we all should prioritise.</p><h3><strong>3. We’re all imaginative storytellers, and that’s not helpful</strong></h3><figure><img alt="An abstract, colourful illustration of someone’s head in a cage, referencing to being prisoner of our own minds" src="https://cdn-images-1.medium.com/max/1024/1*xtV08pQxnKEzl2hjucMKvw.jpeg" /><figcaption>Image: collage of work by paul_craft and ONYXprj — stock.adobe.com</figcaption></figure><p>We like to think that imagination is one of our most valuable assets. But unfortunately, the stories and speculations we tell ourselves about other people’s intentions aren’t helpful.</p><p>Let me explain: let’s say your colleague Sam continues to answer your questions with a simple yes or no. That’s a fact that you and others can observe and hear. What we don’t have evidence for is <em>why</em> they do this. The wild thing about our minds is that we like to <strong>make things up in the most negative ways</strong> in the absence of factual evidence. And we’re pretty good at convincing ourselves that these stories are facts.</p><p>Let’s say you had a disagreement with Sam yesterday. What stories might you tell yourself? “Sam is still angry with me.”? Your mind will try to put Sam’s reaction into context — making stuff up that may or may not be accurate.</p><p>Why is it so dangerous when we are <strong>anticipating </strong>things? It’s quite simple. When we assume the worst, our actions, body language and tone of voice will <strong>reflect this</strong>. And that’s perhaps just what the other person needed to confirm their constructed story about us. So it’s a <strong>downward spiral</strong>.</p><p>How can we break the downward spiral? By questioning our own emotions. Are they <strong>tied to a story</strong> we’re telling ourselves about the other person? What <strong>actual evidence</strong> do we have?</p><p>The tricky bit is that sometimes, our narratives<em> are</em> true. We may have a good intuition as to what people’s motives are. So it’s even more critical to curiously investigate our emotions and what has led us to feel them. For example, by asking ourselves: What did I hear or see that makes me think this?</p><p>Ultimately, we like to tell ourselves stories to not have to act. We like to portray ourselves as victims, “It’s not my fault”, the other person as the villain, “It’s all their fault!” or retreat to a state of helplessness: “There’s nothing I can do!”. Neither of these black-and-white patterns is helpful to move forward with any challenge or relationship issue.</p><h3><strong>4. Expressing ourselves — in a nonviolent way</strong></h3><blockquote><em>Isn’t it odd that when it matters the most, we often communicate our worst?</em></blockquote><p>It’s essential first to address emotional needs in any conflict to be able to move forward to the facts part. For this, I love the format <em>Nonviolent Communication.</em></p><figure><img alt="An abstract, colourful illustration that show the words “Obervation”, “Feeling”, “Needs” and “Requests”." src="https://cdn-images-1.medium.com/max/1024/1*MhnXUDhmzycyxq9Y3Iq-UQ.jpeg" /><figcaption>Image designed by the author</figcaption></figure><p>If you don’t yet know Marshall Rosenberg’s<a href="https://www.cnvc.org/bookstore/books/NVC-A-Language-of-Life-3rd-Edition"> “Nonviolent Communication</a> — A Language of Life”, — go check it out! It’s a great way to increase empathy and give conversation partners the ability to contribute their perspectives in a way that doesn’t degrade, threaten or otherwise scare them away — and hence improve the quality of work/life for both.</p><p>It’s essentially formulating a statement that includes an <strong>observation</strong>, how it made you <strong>feel</strong>, what you <strong>need</strong>, and a concrete <strong>action</strong> request towards meeting this need.</p><h3><strong>5. Make the other person feel safe and check your intent</strong></h3><figure><img alt="An abstract, colourful illustration of a handshake" src="https://cdn-images-1.medium.com/max/1024/1*V7IZMXSGq67oC5SbZufZcQ.jpeg" /><figcaption>Image by paul_craft — stock.adobe.com</figcaption></figure><p>Think back to any of the fables you were told as a kid. Remember the villain that pretended to want the best for the hero but secretly wanted to boil them in their cauldron? Did you shout, “don’t trust them!”? Whilst those stories wildly overstate the situation, most people have developed a sense of when their counterpart <strong>doesn’t come from a place of good intent</strong>.</p><p>We will likely fail if we’re having a conversation from a place of bad intent. So it’s critical to gain clarity about our intent. Don’t start the conversation until you’ve found a way to frame your motive that values all conversation partners.</p><p><strong>Motives might be:</strong> exploring a situation, finding the truth, finding a win-win situation, creating long-term results or strengthening the relationship. I like to spend quite a bit of time getting my motivation right and framing it in a way that feels authentic.</p><p>Sharing our good intentions upfront is like <strong>laying down one’s arms</strong>: “Hey, I’m here because I want the best for us / our relationship.”</p><p>What if the conversation started safely, but you notice the other person is becoming more <strong>silent</strong> or retreats to <strong>verbal violence</strong>? This might show through:</p><ul><li>Sarcasm</li><li>Sugarcoating</li><li>Phrases like “some people” instead of “I” when sharing opinions</li><li>Changing the topic</li><li>Withdrawing from the conversations</li><li>Using absolutes (the worst, the best, the only)</li><li>Name-calling</li><li>Taking over a conversation through constant/loud speaking</li><li>Asking directive questions</li><li>Belittling others or their ideas</li><li>Threatening</li></ul><p>Focus on rebuilding the safety immediately. Address safety concerns openly, and clarify what you <em>don’t</em> mean. Don’t continue the conversation until you’ve rebuilt safety.</p><h3><strong>6. If we don’t say it, our body will tell it</strong></h3><figure><img alt="An abstract, colourful illustration of a head — you can see the universe is behing the face" src="https://cdn-images-1.medium.com/max/1024/1*kN5OUDp2MU8O233Yqda7pw.jpeg" /><figcaption>Image by paul_craft — stock.adobe.com</figcaption></figure><p>I find opening up about my feelings, perspectives and stories quite intimidating at times. I understand that sometimes, not sharing holds me back from achieving what I want. I didn’t realise for a long time that while not speaking up verbally, my body does a fair share of unconscious communication. It’s one thing holding back words. But completely altering our body language and facial expressions — that’s a skill that not even spies master, as seen in <a href="https://www.youtube.com/watch?v=4jwUXV4QaTw">this video</a> about non-verbal communication. Joe Navarro, a former FBI agent, explains how to read body language:</p><blockquote><em>“We may think we’re very sophisticated, but in fact, we are never in a state where we are not transmitting information.”</em> — Joe Navarro</blockquote><h3><strong>7. Prepare for a conversation from different perspectives</strong></h3><figure><img alt="An abstract, colourful illustration of a head with a door, stairs and windows" src="https://cdn-images-1.medium.com/max/1024/1*-SRHy3ghOqJzjAO7vmYC8g.jpeg" /><figcaption>Image by paul_craft — stock.adobe.com</figcaption></figure><p>What should this conversation bring about? It’s helpful to prepare this question from different perspectives:</p><ul><li>What do I want for myself?</li><li>What do I want for the other person?</li><li>What do I want for our relationship?</li><li>What do I want for our organisation?</li></ul><h4>The Negotiation Canvas</h4><p>I was introduced to a valuable tool in a recent training on “Strategic Business Thinking” — the<a href="https://negotiationbydesign.com/tools"> Negotiation Canvas</a>. It is a helpful guide to preparing the different perspectives in a negotiation and a valuable primer for a crucial conversation.</p><figure><img alt="An illustration of the two tools mentioned in this paragraph: the Negotiation Canvas and the Empathy Map" src="https://cdn-images-1.medium.com/max/1024/1*DvkC9IF19H2SKLMvqvpHsw.jpeg" /><figcaption>Images – left: the <a href="https://negotiationbydesign.com/tools">Negotiation Canvas</a> — right: designed by the author</figcaption></figure><h4><strong>Empathy Map</strong></h4><p><a href="https://www.uxbooth.com/articles/empathy-mapping-a-guide-to-getting-inside-a-users-head/">Empathy maps</a> are a tool from the design world to empathise with the users of a product/service. It’s a living document meant to shift the attention away from technology toward humans, with their emotions, goals and challenges. They help teams to build better services. So why not use it to empathise with colleagues at work? It allows us to put ourselves in their shoes and design a conversation from a <em>“we”</em> perspective rather than an <em>“I” </em>perspective.</p><h3><strong>8. Appropriate depends</strong></h3><figure><img alt="An abstract, colourful illustration of a head that’s melting into another head. A planet is next to it." src="https://cdn-images-1.medium.com/max/1024/1*G5F6EVFyCaWxI223HJ9HcQ.jpeg" /><figcaption>Image by Martyshova — stock.adobe.com</figcaption></figure><p>This is a lesson I quickly learned when I first became a manager of an international team. The company I work at, <a href="https://tanzu.vmware.com/labs">VMware Tanzu Labs</a>, is a global organisation. We have branches in London, Berlin, Paris and Amsterdam in Europe. The people in my team are from Germany, the US, the UK, France, Italy and the Netherlands. I’m Austrian. Every person has a slightly different way of communicating, and we’re just spread across Europe and the US!</p><p><strong>For example, </strong>it differs greatly how literal and direct people like to say things. With my quite explicit Austrian nature, I’m having a hard time recognising when my colleagues from the UK subtly try to tell me I’m doing something stupid. And the other way around: what I deem a considerate way to deliver feedback might be quite upsetting to others.</p><p>I’ve recognised this gap and am working on adopting a global communication style toolkit I can localise as needed. For everyone working with or leading an international team, I can recommend Erin Meyer’s <a href="https://erinmeyer.com/books/the-culture-map/">The Culture Map</a>. This book helped me understand how I can adapt the way I communicate and subsequently have better conversations.</p><h3><strong>9. How to be more memorable</strong></h3><figure><img alt="An abstract, colourful illustration of a rainbow, clouds, the sun and a tree with smiling faces" src="https://cdn-images-1.medium.com/max/1024/1*-RGrJ2_WvskS5IxiJpeB3A.jpeg" /><figcaption>Image by paul_craft — stock.adobe.com</figcaption></figure><p>What about the conversations that <em>aren’t</em> per se crucial, that happen after work or during lunch? The ones we might frame as small talk? They feel less deep but are valuable to strengthen our relationships because they help others see us as humans, with our uniqueness and flaws. I reflected a lot on how much of my personality I want to show at work without being inappropriate.</p><p>A short read that I love is<a href="https://www.theschooloflife.com/article/how-to-be-a-good-guest/"> “How to Be a Good Guest”</a> by The School of Life. Essentially: don’t be a mirror to the other person. Mimetic people aren’t memorable; they aren’t interesting. A more characterful person offers a fresh perspective, respectfully disagrees, and speaks a bit about themselves. It’s a mix of being candid — like a four-year-old child — but with the empathy of a socially aware adult.</p><p>A good, genuine conversation at work is about intentional, interpersonal risk-taking. I prefer occasionally overstepping over being an unmemorable blurb.</p><figure><img alt="A visual divider that says “Thank You” in a fancy western typeface" src="https://cdn-images-1.medium.com/max/1024/1*WAYJtMTxV3Tya7LPv1KSdg.jpeg" /><figcaption>Image by paul_craft — stock.adobe.com</figcaption></figure><h3><strong>Credits</strong></h3><p>Nothing is written out of a vacuum. I was inspired by the perspectives of</p><ul><li>Most fundamentally, this two-day training on <a href="https://cruciallearning.com/crucial-conversations-for-dialogue/">Crucial Conversations</a> by Crucial Learning. Sections 1–3 and 5–7 are my takeaways from the training</li><li>Recent workshops with <a href="https://www.theschooloflife.com/work/">The School of Life</a> on diplomacy, adaptability, failure and confidence</li><li>A leadership class on Strategic Business Thinking (now called <a href="https://www.secondwavedive.com/courses/strategic-design-leadership">Strategic Design Leadership</a>) by SecondWaveDive</li><li>The book <a href="https://www.cnvc.org/bookstore/books/NVC-A-Language-of-Life-3rd-Edition">Nonviolent Communication</a> by Marshall Rosenberg</li><li>The book <a href="https://erinmeyer.com/books/the-culture-map/">The Culture Map</a> by Erin Meyer</li><li>This video on <a href="https://www.youtube.com/watch?v=4jwUXV4QaTw">non-verbal communication</a> by former FBI agent Joe Navarro</li></ul><p>What ideas and concepts have helped you better communicate with others? I’m curious about your feedback! Find me on<a href="https://www.linkedin.com/in/antonia-horvath/"> LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ba089526d46" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-humans/nine-ideas-to-inspire-more-meaningful-conversations-at-work-4ba089526d46">Nine ideas to inspire more meaningful conversations at work</a> was originally published in <a href="https://betterhumans.pub/">Better Humans</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we designed our London office to be a collaboration hub that supports our hybrid way of working]]></title>
            <link>https://antonia-horvath.medium.com/how-we-designed-our-london-office-to-be-a-collaboration-hub-that-supports-our-hybrid-way-of-working-34710fa4cf41?source=rss-5dc5553f6d0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/34710fa4cf41</guid>
            <category><![CDATA[office-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[hybrid-working]]></category>
            <dc:creator><![CDATA[Antonia Horvath]]></dc:creator>
            <pubDate>Thu, 07 Jul 2022 10:12:16 GMT</pubDate>
            <atom:updated>2022-07-07T10:36:10.596Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Picture of an industrial-style office with a man sitting at a high table with stools, working on his laptop. In the foreground, you can see a movable whiteboard and a monstera plant." src="https://cdn-images-1.medium.com/max/1024/1*kkvF4N8ISf2Sp1SaLya13Q.jpeg" /><figcaption>Our new office: a hybrid collaboration hub. Image taken by the author</figcaption></figure><h4>The Future of Work</h4><h4>Useful tools and lessons learned from designing the office of the future for our team and customers in an evidence-based way</h4><p>In 2021, <a href="https://tanzu.vmware.com/labs">VMware Tanzu Labs</a> reflected on what the future of work looks like for us and what role we want our offices to play. Normally, we design and build software. Designing office spaces has been quite an exciting stretch. We learned that the basic process of designing software applies really well to office design: understand people’s needs, co-create together and then iterate.</p><h4><strong>Do we even need an office?</strong></h4><p><strong>Yes.</strong> The nature of our work is highly collaborative. We solve complex business challenges through software. The essence of our services offering is teaching clients how to build amazing modern apps. We identified that while most of our work can be done well remotely, we’re most successful when the first team bonding phase and other key project rituals happen in person.</p><blockquote>We redesigned our largest offices in Europe, London and Paris to serve as collaboration hubs for our team and our clients.</blockquote><h4>Can we keep on using our offices from before the pandemic?</h4><p><strong>No. </strong>Historically, VMware Tanzu Labs, formerly Pivotal Labs, had a primarily in-person culture with most team members and several client teams working at the office at any given time. In 2020, we went fully remote. In 2021, we re-opened the London and Paris office as collaboration hubs at a smaller capacity. It would be a waste of money to keep on investing in offices that are too large for what we actually need.</p><blockquote>We used surveys, interviews, workshops as well as historic engagement data to identify how much space we needed and how to best design our new collaboration hubs.</blockquote><h4>Our budget</h4><p>We had a budget available, but it didn’t allow for extraordinarily large investments (<em>bye-bye </em><a href="https://www.youtube.com/watch?v=2GrXTLe9ztA&amp;ab_channel=PortalUnityNetwork"><em>real-time digital portal</em></a> 😭). Our mission was to build upon what is already there, and to make iterative, impactful changes. And create evidence-based business cases for additional investments.</p><h4><strong>Program structure: a dedicated office working group</strong></h4><p>VMware invested in designing our future of work globally. The office redesign was part of our European future of work program. We created office working groups for London and Paris. Members weren’t working full time on the initiative, everyone gave as much time as they could. Almost every Labs team member got involved in one way or another, it was a great team effort. We paired up to address the different challenges and met for a weekly standup.</p><h3><strong>What we achieved: a hybrid collaboration hub</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hEBEyKLu8i0P1L9lnkF-Dg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zwt0IFuZJ8LhN6Tyf5yiSg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*piLtyGPodSRPGumgudZGTw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g38cfp1id7C9Z9MxJmpHKw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H0zLm77prz2vsByhhZhlOA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VqKpgESR99D6M9G-TEPYiQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_peVrP4EtbXtBXD0fOUu9g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wUz6hMobHA6ab65nDojoCw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nKLQJTc2PKBDW6eAWYgDaQ.jpeg" /><figcaption>Our new office: a hybrid collaboration hub. Images taken by the author</figcaption></figure><h4><strong>Key spaces</strong></h4><ul><li>Four team spaces with a mix of in-person and remote pairing workstations</li><li>Two open-plan spaces to conduct ideation sessions and workshops</li><li>Several snugs to have semi-private conversations, a library corner</li><li>A kitchen for lunch breaks and a living-room type coffee corner</li><li>Two focus-rooms for deep work without distraction</li><li>A comfy room for 1:1s, several more formal conference rooms</li><li>Two large conference rooms optimised for video conferences</li></ul><h3>How did we get there?</h3><p>It took us about 2 months from first research to providing a plan to our facilities team, who then ordered and arranged the furniture and IT equipment. The London office opened in October 2021. Since then, we’re iterating on making it better every time we come in.</p><h3>1. Interviews with our team</h3><p>🔗 View the team interview guide <a href="https://docs.google.com/document/d/1MhiB94NoAWXbrKxTkCR0NEzkzklTuCq7bQ2NFG29ZNg/edit?usp=sharing">here</a></p><p>We conducted in-depth interviews with 8 people to understand how frequently the team expects to be using the space, how much space is needed and what the space needs to look like. We interviewed engineers, product managers, designers, delivery leads, people managers and salespeople because we anticipated their space needs to be quite different.</p><figure><img alt="A screenshot of a Miro board with lots of sticky notes in affinity groups" src="https://cdn-images-1.medium.com/max/1024/1*05PkyBKtRflmNqYRbGiWTg.png" /><figcaption>Synthesis of the team interviews</figcaption></figure><h3>2. Team workshop — hybrid working needs</h3><p>🔗 View the team workshop Miro template <a href="https://miro.com/app/board/uXjVOo2RQuI=/?share_link_id=249599384084">here</a></p><p>In addition to in-depth interviews with team members, we conducted a team workshop to collect a more conclusive picture of team members’ needs. We asked about people’s hopes and fears for returning to the office, how often they were looking to come in and for what rituals.</p><figure><img alt="A screenshot of an empty  Miro board workshop template" src="https://cdn-images-1.medium.com/max/1024/1*pO3PZYPue0axei4SZVJYnA.png" /><figcaption>Team workshop to understand hybrid working needs</figcaption></figure><h3>3. Model past and future engagement data</h3><p>To determine how many team collaboration spaces we need across Europe, we looked at historic client engagement data as well as all predicted client engagements for 2021/22. We analysed engagement type (build new apps, modernise existing apps, improve a team’s way of working...) engagement length, team size, team and client location as well as a client &amp; team happiness score, to ensure we make an informed decision for our future working model.</p><h3>4. Interviews with our clients</h3><p>🔗 View the client interview guide <a href="https://docs.google.com/document/d/1GQYCDg6cXAXfo7wqDwov60jOWMLy2w9nSztXhRSwLpw/edit?usp=sharing">here</a></p><p>We performed in-depth interviews with 4 clients from France, the UK and an area we call Emerging Markets, where we’re about to expand our services: Middle East, Africa and Southern Europe.</p><h4>💡 Key insights from our clients</h4><ul><li><strong>Looking for recommendations:</strong> just like for best practices in software development, our clients are looking to us for advice and best practices on what working model makes sense for successful software teams</li><li><strong>Hybrid approach: </strong>clients believe the vast majority of software development can be done remotely. They are open to spending time at significant engagement events with us in our collaboration space</li><li><strong>Varying regulations:</strong> it’s mostly the human resources department that is in charge of creating the working model, not the people we tend to interact with during our engagements. Different countries have different COVID regulations that companies comply with. The UK and hence our UK clients tend to be more liberal, the rest of Europe is more strict with in-person working (vaccines, masks…)</li><li><strong>In-person — risk of attrition:</strong> most of the people we spoke with were well aware that they need to compete for highly skilled tech talent and are mindful not to dictate rules that contradict the local market situation</li></ul><h3>5. Design the actual office space</h3><p>At Labs, we have a powerful workshop practice for facilitating the co-creation of ideas. We call it a <a href="https://tanzu.vmware.com/developer/practices/design-studio/">design studio</a>. We announced the design studio on Slack so that everyone who was interested could sign up. We also added an asynchronous board for inspiration.</p><figure><img alt="A screenshot of a Miro board with several frames, containing: photos of the office space, a plan of the office, inspiration for the look and feel and a feedback section." src="https://cdn-images-1.medium.com/max/1024/1*QgBmsFu5kxXYO1rOeqQaWQ.png" /><figcaption>“Design Studio” workshop to design the office space</figcaption></figure><p>We came together as a balanced team to design the space. Using a digital whiteboard, we provided a plan of the building. My design skills proved to be useful for this: I simplified the initial complicated floor plan to contain just walls, windows and doors. In the workshop, people added furniture like desks, chairs, whiteboards, plants etc.</p><p>There were a couple of furniture pieces already in the space, predominantly desks and chairs for pairing. We tried to leverage what we already had, to optimise costs.</p><h4><strong>Prompt:</strong></h4><blockquote><em>“How might we design the London office space in a way that meets our &amp; our clients’ needs in a new, hybrid way of working? For the types of work that you do: what spaces do you need &amp; what recommendations can you give for those spaces? Think of equipment, furniture, inspiration, …”</em></blockquote><p>The team hadn’t seen the new office space. We conducted a video tour and took pictures from all angles to help people understand what we were working with. The London office is a leased space, so we knew we would not be able to carry out architectural changes.</p><h3><strong>6. Synthesising our ideas into a plan</strong></h3><figure><img alt="A detailed office plan that shows how the new furniture should be arranged." src="https://cdn-images-1.medium.com/max/1024/0*5uCS4cM9Ofgns3-U" /><figcaption>Synthesis of our design ideas into an actual plan</figcaption></figure><h4><strong>Fast feedback loops: improve for neurodiverse people</strong></h4><p>Before providing the recommendations, we walked a number of people through the plan to ask for feedback. Talking to a team member with ADHD, one of their key pieces of feedback was: <em>“Where will I be able to find a room for deep work? Occasionally, I would like to have a space just for me.”</em>. Based on this feedback, we added two “focus rooms”, (J and K) with a single desk and a large monitor.</p><h4><strong>Translating the plan into more tangible recommendations</strong></h4><p>We created a deck of recommendations, introducing the new plan incl. a prioritisation. We also created mood boards about the look &amp; feel: “what Labs feels like”. Each area was defined through the actual plan, a short description of the intended use and images for inspiration.</p><figure><img alt="A collage of several pictures to transport the mood of working at VMware Tanzu Labs. People workshopping, drawing out ideas, writing code in pair programming style, having a 1:1 conversation and playing pingpong.ping-pong" src="https://cdn-images-1.medium.com/max/1024/1*lWx1wlN_sBXC9QCanKlK7Q.jpeg" /><figcaption>“What Labs feels like”, image sources: the VMware Tanzu Labs <a href="https://tanzu.vmware.com/labs">website</a>, the dedicated London office <a href="https://tanzu.vmware.com/locations/london">website</a>, the VMware brand asset pool and the author</figcaption></figure><h4>Example: Kitchen — reflective of London Old Street culture</h4><p>This room should feel like a café. Light, plants, wood, busyness… It will be used to: have breakfast, prepare lunch, socialise, celebrate successes, have a coffee, chat with clients &amp; potential hires and do a jigsaw during the break. It’s a place where you can bump into colleagues you haven’t seen in a while.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hF0oAPPd4oJ4ERxcnXNSUQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fzgAHvpU3H8ZhagW9owq8w.jpeg" /><figcaption>Moodboard for the kitchen area, images from unsplash</figcaption></figure><h4>Example: Open plan, customisable team space</h4><p>“All things movable, we can make the space ours”: Optimised for in-person work, customizable to team’s needs. They can create their own setup. Four pairing stations, accommodating up to 8 people, plus space to workshop.</p><ul><li>Movable whiteboard-walls</li><li>1 movable big screen, camera and microphone per team</li><li>2 lounge chairs and a coffee table to move round</li><li>Standing desk with stools incl. large whiteboard for ad-hoc collaboration</li></ul><figure><img alt="A collage of several pictures to transport the mood of the customisable collaboration space: standing desks, movable whiteboards and furniture." src="https://cdn-images-1.medium.com/max/1024/1*DVecJijKT3pvt1tE4cf9tw.jpeg" /><figcaption>Moodboard for the customisable team space, images from unsplash</figcaption></figure><h3>Tech setup</h3><h4>Pairing stations</h4><p>Our office <a href="https://tanzu.vmware.com/developer/learningpaths/application-development/pair-programming/">pairing stations</a> are made of a Steelcase electric <a href="https://www.steelcase.com/products/height-adjustable-desks/">sit/stand desk</a> and two ergonomic Hermann Miller <a href="https://www.hermanmiller.com/en_gb/products/seating/office-chairs/aeron-chairs/">chairs</a>. They are equipped with two Dell UltraSharp 27 USB-C <a href="https://www.dell.com/en-uk/shop/dell-ultrasharp-27-usb-c-hub-monitor-u2722de/apd/210-ayuj/monitors-monitor-accessories">monitors</a> with Logitech BRIO — 4K Ultra HD <a href="https://www.logitech.com/en-gb/products/webcams/brio-4k-hdr-webcam.960-001106.html">webcams</a>, that can be easily connected to our MacBooks. Apple <a href="https://www.apple.com/shop/product/MK293LL/A/magic-keyboard-with-touch-id-for-mac-models-with-apple-silicon-us-english?fnode=0d7ccde96bff78885fc3f94d68dba869d6b499940257e79dba6d2af0775d47026da419952b20138c363c5790772d74d208221d8eefca513159cbd7cc8ace84e4e1c76c77f5fb3b634dc2cb954a9ee7598077ffb84f78fcc688b6ec3820a8912fbe121c1cf0c64491bdb85527671a1437">keyboards</a> and <a href="https://www.apple.com/shop/product/MMMQ3AM/A/magic-mouse-black-multi-touch-surface?fnode=0d7ccde96bff78885fc3f94d68dba869d6b499940257e79dba6d2af0775d47026da419952b20138c363c5790772d74d208221d8eefca513159cbd7cc8ace84e4e1c76c77f5fb3b634dc2cb954a9ee7598077ffb84f78fcc688b6ec3820a8912fbe121c1cf0c64491bdb85527671a1437">mice</a>/<a href="https://www.apple.com/shop/product/MMMP3AM/A/magic-trackpad-black-multi-touch-surface?fnode=0d7ccde96bff78885fc3f94d68dba869d6b499940257e79dba6d2af0775d47026da419952b20138c363c5790772d74d208221d8eefca513159cbd7cc8ace84e4e1c76c77f5fb3b634dc2cb954a9ee7598077ffb84f78fcc688b6ec3820a8912fbe121c1cf0c64491bdb85527671a1437">trackpads</a><strong> </strong>as well as noise-cancelling Jabra <a href="https://www.jabra.co.uk/business/office-headsets">headsets</a> are individual to each person, an adaptation we made since the pandemic. They’re stored in personal lockers.</p><h4>Conference rooms</h4><p>Our hybrid optimised meeting rooms are equipped with a large Samsung <a href="https://www.samsung.com/uk/business/display-solutions/samsung-logitech-video-conferencing-solution/">TV/monitor</a> with Dell Optiplex and Extron/Lightware management devices controlling the functions of the room as well as a Logitech Rally <a href="https://www.logitech.com/en-gb/video-collaboration/partners/crestron.html">camera</a> with Crestron touch controls.</p><h4>Team spaces</h4><p>Our two rolling displays for hybrid teams are NEC flat monitors with Mac minis in the base, with external conference <a href="https://www.clearone.com/chat-150-chatattach-150">microphone/speakers</a> and a Logitech webcam attached… a very simple but effective way to keep hybrid teams in touch and give remote access to the office vibe.</p><h3><strong>Naming our meeting rooms after inspiring thought leaders</strong></h3><p>We did a call for theme ideas and suggestions from the team and decided to name our meeting rooms after inspiring people. We wanted the work of the people to represent <a href="https://news.vmware.com/company/vmwares-culture-built-epic2-values">our values</a>: execution, passion, integrity, customers and community. Choosing names people haven’t heard of also helps to inspire curiosity, and encourage people to learn a little more about the diverse innovators who have helped shape our society.</p><p>We aimed for geographical representation across EMEA, as well as gender and racial representation. We chose: <a href="https://www.bbc.co.uk/sport/football/55338104">Marcus Rashford</a>, <a href="https://en.wikipedia.org/wiki/Inge_Lehmann">Inge Lehmann</a>, <a href="https://en.wikipedia.org/wiki/Rosalind_Franklin">Rosalind Franklin</a>, <a href="https://en.wikipedia.org/wiki/Alexander_von_Humboldt">Alexander von Humboldt</a>, <a href="https://en.wikipedia.org/wiki/Marie_Curie">Marie Curie</a>, <a href="https://en.wikipedia.org/wiki/Jeanne_Villepreux-Power">Jeanne Villepreux-Power</a>, <a href="https://en.wikipedia.org/wiki/Avicenna">Ibn Sina (Avicenna)</a>, and <a href="https://en.wikipedia.org/wiki/Himla_Soodyall">Himla Soodyall</a>.</p><figure><img alt="Images of (left to right): Ibn Sina (Avicenna), Inge Lehmann, Jeanne Villepreux-Power, Alexander von Humboldt, Marie Curie, Rosalind Franklin." src="https://cdn-images-1.medium.com/max/1024/1*TjRV-5Rvl-FXMvUYWBr2QA.jpeg" /><figcaption>Images from Wikipedia, left to right: <a href="https://en.wikipedia.org/wiki/Avicenna#/media/File:1950_%22Avicenna%22_stamp_of_Iran.jpg">Ibn Sina (Avicenna)</a>, <a href="https://en.wikipedia.org/wiki/Inge_Lehmann#/media/File:Inge_Lehman.jpg">Inge Lehmann</a>, <a href="https://en.wikipedia.org/wiki/Jeanne_Villepreux-Power#/media/File:Jeanne_Villepreux-Power.jpg">Jeanne Villepreux-Power,</a> <a href="https://en.wikipedia.org/wiki/Alexander_von_Humboldt#/media/File:Stieler,_Joseph_Karl_-_Alexander_von_Humboldt_-_1843.jpg">Alexander von Humboldt</a>, <a href="https://en.wikipedia.org/wiki/Marie_Curie#/media/File:Marie_Curie_c._1920s.jpg">Marie Curie</a>, <a href="https://en.wikipedia.org/wiki/Rosalind_Franklin#/media/File:Rosalind_Franklin_(1920-1958).jpg">Rosalind Franklin</a>.</figcaption></figure><h4>Working with the facilities team</h4><p>Our office facilities team was brilliant! They were super collaborative throughout the whole process. They did the heavy lifting of finding excellent vendors, arranging and overseeing the delivery and assembly of the furniture. <strong>Prioritisation is key, compromises necessary: </strong>As software people, we embrace prioritisation. We were well aware that we won’t be able to make everything happen. So we sat down and prioritised our vision for the future.</p><h3><strong>7. Iterate together</strong></h3><p>Ordering furniture in an enterprise context takes time. The last bits only just arrived in early 2022. Since we opened up the office again in September 2021, we ran experiments and iterated on how we use the office.</p><figure><img alt="A violet neon sign, saying “we are open”." src="https://cdn-images-1.medium.com/max/1024/1*L03MQDSuvr0tf-GwCyq_OA.jpeg" /><figcaption>Image from unsplash</figcaption></figure><h3>Experiments we ran</h3><h4><strong>🐝 Office Thursday</strong></h4><p>To re-ignite human connection and interactions with colleagues, customers and friends, we voted for one day a week where we all try to be in the office. It isn’t mandatory, we equally support colleagues who want to stay fully remote. But we recognized that for the people that <em>do</em> want to come in, we’d get a more vibrant office buzz when we all come in on the same day.</p><h4><strong>🥗 Bi-weekly lunches</strong></h4><p>To support community building and create an additional incentive to travel to the office. Conveniently located next to our ping-pong tables, our lunches turn out to be a great way to socialise with colleagues across VMware. Additionally, we have a decent stock of snacks, fruit and drinks.</p><h4><strong>💙 In-Person collaboration time</strong></h4><p>On Thursdays, we go light on remote meetings and prioritise on in-person collaboration. We have in-person 1:1s, and you see crowds around whiteboards, solving tough challenges together.</p><h4>👀 Remote advocate</h4><p>Whenever we had hybrid events, we defined one person who was responsible for a great experience for remote participants. This might be through setting up an additional camera &amp; microphone to see a speaker close-up, paying attention to virtually raised hands or comments from remote participants or simply sharing photos from the in-person atmosphere during the day.</p><h4><strong>🧐 Back to the office retro</strong></h4><p>After four weeks of coming in more regularly, we conducted a team retrospective to understand what people value and to find improvement opportunities. Additionally, we created an asynchronous retro board for people to share ideas for further improvements.</p><h4><strong>🚊Flexible commute time, half-day in</strong></h4><p>On Thursdays, we enable a more flexible working model for people who want to come to the office to better enable parents to do school drop-offs and enable off-peak travelling. Some colleagues come in around lunchtime, working from home for the first half of the day.</p><h4>🚲 Cycle to work, bicycle storage and showers</h4><p>This isn’t a new offering, but since the pandemic, more people cycle to work and greatly appreciate the facilities we offer. What’s more, VMware grants a considerable annual health and wellbeing allowance — that I, for example, invested in a new bicycle last year.</p><h4>💻 <strong>Remote optimised pairing stations</strong></h4><p>We normally work in pairs, all our desks in the office are optimised for pairing. To enable a similar experience for remote &amp; in-office pairing, we invested in a decent setup with excellent audio &amp; a high-quality webcam.</p><h4>🖥 A portal between the office and remote team members</h4><p>For everyone who wasn’t making it into the office, we created a zoom room to drop in and hang out. We used our large moveable screen &amp; camera to give remote people direct access to everyone who is in the office.</p><h4>⌨️ Extra keyboards, mouse and charger for the office</h4><p>One of the cumbersome things about hybrid work is to carry your equipment back and forth. We arranged for a second set of equipment just for the office to make coming to the office a less heavy experience.</p><h4>⚡️ New business workshops and strategy on-site</h4><p>While the vast majority of our client engagements continue to be delivered fully remotely, we came together for strategic workshops and new business conversations. We had a leadership onsite to develop our strategy for 2022, including an in-person Labs-pitch training.</p><h3>What we learned</h3><figure><img alt="Photo of a whiteboard containing a team retrospective. It has three sections: green for positive things, yellow for things that could be improved and red for things that need to be addressed soon." src="https://cdn-images-1.medium.com/max/1000/1*3yYy1gQ5I8q-7xK3QRaqKQ.jpeg" /><figcaption>Team retrospective on the office re-opening, image taken by the author</figcaption></figure><h4><strong>🏠 🏢 Hybrid model</strong></h4><p>We won’t be coming back to the office full-time. The vast majority of our team and clients prefer coming to the office for one day a week for team bonding as well as for key team rituals. We’ll continue to do most of the work remotely.</p><h4>🤝 The office as a collaboration hub</h4><p>We are using the office for the human aspect of our work: team rituals like kickoffs, workshops, ad-hoc whiteboarding and problem-solving and ideation sessions, one-on-ones and career conversations etc.</p><h4><strong>✅ Flexibility is key</strong></h4><p>Our team likes the flexibility that working from home has brought them. Commuting 1–2h per day across greater London in crowded trains isn’t something everyone is comfortable with coming back to. People appreciate being able to decide what’s best for themselves and their teams.</p><h4><em>📈 Empathy levels spiked for folks who met in person</em></h4><p>I think many of us felt a “Labs vibe” that we haven’t felt for a long time, including whiteboard-marker spots on our hands. It felt amazing having lunch together, the occasional coffee/tea, playing ping pong and celebrating wins and other occasions together.</p><h4>🏓 Building relationships and taking a break is work, too</h4><p>At Labs, we have a very sustainable work culture. We start and end on time, we take an hour lunch break and several smaller breaks throughout the day. When coming back to the office, taking regular breaks felt a bit weird. After a couple of times, we got back into the habit of our late afternoon ping-pong matches and occasional coffee chats.</p><h4><em>🤖 We’re not robots</em></h4><p>After over a year of not meeting anyone in person in a work context, we had to re-learn how to socialise at work, how to facilitate engaging workshops in person and how to manage our energy to suffice for a full in-person day.</p><h4>⚠️ Proximity bias is real</h4><p>As a leadership team, we intentionally invest in remote relationships to ensure we equally bond with everyone in the team, not just the people that we see in person.</p><h4>🐶 People would like to bring their furry friends</h4><p>Working remotely gives a great deal of freedom. Many team members have gotten dogs since the pandemic started. One thing that we, unfortunately, haven’t managed to improve yet is enabling team members to bring their dogs into the office.</p><h4>🛋 Furniture ordering &amp; delivery takes time</h4><p>When we first re-opened the office after the pandemic, the office didn’t yet look like our vision. Our team is used to shipping software on a daily basis, I think people were a little disappointed about the slow progress.</p><h3><strong>Shoutout</strong></h3><p>Almost every Labs team member contributed to the Future of Work program in one way or another. Thank you in particular to the people more closely involved with the London and Paris office design: Nick, Andrea, Jon, Gagan, James, Anna, Paul, Emina, Vitor, Dale, Michael, Liam, Annamaria, Thomas, Agnes, Marco, Nana, Amanda, Tom, Rose and Natalie</p><figure><img alt="A visual divider saying “Thank you!”" src="https://cdn-images-1.medium.com/max/1024/1*r173i6VN7JE3xlmT2LiFXA.png" /></figure><p><em>How are you going about in-person working versus remote? What has worked well for your team — and what didn’t? I’m passionate to create a space where teams can do their best work and want to learn from you. Find me on </em><a href="https://www.linkedin.com/in/antonia-horvath/"><em>LinkedIn</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34710fa4cf41" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Six Unexpected Leadership Lessons I Found in Improv Theatre]]></title>
            <link>https://medium.com/better-humans/six-unexpected-leadership-lessons-i-found-in-improv-theatre-336fbc35fab8?source=rss-5dc5553f6d0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/336fbc35fab8</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[improv-theatre]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Antonia Horvath]]></dc:creator>
            <pubDate>Tue, 17 May 2022 20:31:08 GMT</pubDate>
            <atom:updated>2022-05-17T20:31:08.047Z</atom:updated>
            <content:encoded><![CDATA[<h4>About leading with yes, the beauty of mistakes and the art of making the other person look good</h4><figure><img alt="An abstract image. Red lines on beige background, looks a little like a poppy flower." src="https://cdn-images-1.medium.com/max/1024/1*F1HEax7upwPKNJjoYFbAvQ.jpeg" /><figcaption>Image by Login — stock.adobe.com</figcaption></figure><p>‘This is wild. I’m not sure if I hate it or love it’. That was my state of mind after the very first time trying improv theatre. It was a Monday evening after work with 12 strangers in a theatre in central London.</p><p>After two years of socialising too little during the pandemic, I thought Improv would be great to connect with my fun, creative and resourceful social self around others.</p><p>Over time, the strangers from my group turned into trusted partners. Monday evening improv quickly became the highlight of my week. It made me feel alive. I loved playing with my first impulse. Being bold, ridiculous, illogical.</p><p>Improv is highly collaborative. It has a couple of key concepts that make it work. I didn’t expect it, but those concepts taught me a great deal about leadership and collaboration at work, too. I guess you find advice where you least expect it, right?</p><h3><strong>Six unexpected leadership lessons</strong></h3><h3>1. Listen as if your life depended on it</h3><figure><img alt="All in yellow: an oldscool telephone handset on a yellow background." src="https://cdn-images-1.medium.com/max/1024/1*-M1H7ERwy__Ti83-428msw.jpeg" /><figcaption>Image by wacomka — stock.adobe.com</figcaption></figure><p>You think you’re a good listener? I thought I was. I’ve conducted a lot of user research and have recently invested in enhancing my active listening skills as a manager.</p><p>I dare you to think back to your last heated work discussion. Did you truly listen to every word others said until the very end of the sentence? Or did you secretly plan your response? Yeah… I’m totally guilty here.</p><p>The first exercise we did in the improv class was <strong>‘life story’</strong>: in pairs, telling each other our life stories, and then presenting the other person’s story back to the group. Each person got 1 minute, and then we swapped. Coming back into the larger group, we had to introduce the other person’s story as detailed as we possibly could.</p><p>A more physical listening exercise that I loved was <strong>‘mirroring’</strong>: Silently, one person plays a scene. Doing something, somewhere. Like mixing a cocktail at a bar. Another person has to mirror what they’re doing. When mastered, the audience cannot tell who’s mirroring and who’s leading.</p><p>Listening is the basis of improv. People give each other offers, opportunities to jump on the game and spin it further together.</p><p>Active listening and creating an environment where people feel safe to share will offer the perspectives necessary for your organisation to compete in today’s business world. Foster psychological safety at work. Learn how to observe. Find and deliver constructive feedback as well as praise. Have regular 1:1s and retrospectives.</p><h3>2. Lead with yes</h3><figure><img alt="All in pink: two batteries, with plus and minus signs floating in the air with a pink background." src="https://cdn-images-1.medium.com/max/1024/1*Z7_UoCDH46QBRWcBN9XZLw.jpeg" /><figcaption>Image by MaximB — stock.adobe.com</figcaption></figure><p>Another improv rule that helps the story unfold. You agree with and embrace the underlying reality presented by the person you’re playing with. And you’re adding to it by providing more context to the situation.</p><p>The following exercises helped me better understand what leading with yes feels like and how dissatisfying it is to be blocked:</p><p><strong>‘Blocking’</strong>: You enthusiastically present your pair with a suggestion. Say, “Let’s go climb that tree”. The other person blocks your suggestion and suggests something unrelated instead. For example by saying: “No. How about we go to the beach instead?”</p><p>We instantly lost any positive momentum.</p><p>In contrast: <strong>‘accept and build’</strong>. You’re again suggesting something. The other person now enthusiastically answers “Hell yes!” And adds more detail to your suggestion to make it even better.</p><p><em>That’s when the magic unfolds.</em></p><p>Not many people are in the position to take all the decisions at work. You need the capability to accept and build. It’s an electrifying power learning how to ‘lead with yes’ and help shape a suggestion into something feasible.</p><p>Even for day-to-day collaboration: don’t block. Think back to a time when you’ve suggested something unconventional and a team member — or worse — your manager shut you down. Feels horrible, doesn’t it? Don’t be that person. Instead, carefully find a way to help the other person channel their drive onto something more closely aligned with what your team needs.</p><p>To clarify: I’m not suggesting ditching your boundaries! Don’t let other people take advantage of you, don’t take any shit. Set clear rules and call out when someone oversteps. But within this playing field: don’t block. Lead with yes.</p><h3>3. Establish context and add perspective</h3><figure><img alt="All in blue: 3d abstract shapes: balls, lines and circles floating around in front of a blue background." src="https://cdn-images-1.medium.com/max/1024/1*wVT8uozucBstJEzU488adQ.jpeg" /><figcaption>Image by VAlex — stock.adobe.com</figcaption></figure><p>When you’re improvising, you’ll want to establish context while playing. Who are you? What’s everyone’s name? What relationship do you have with each other? Where are you and what are you doing? <strong>Every improviser is responsible for putting together the scene by adding context.</strong></p><p>This part I love because it maps to how you approach any good decision-making meeting at work: You tailor the context and level of detail to the audience. You facilitate collective decision making by painting a conclusive picture of evidence.</p><p>Be the person that adds something their colleagues haven’t thought of, <strong>an original perspective</strong>, a fresh insight that helps the team to move forward.</p><h3>4. Embrace making mistakes</h3><figure><img alt="All in turquoise colour: furniture (sofa, chairs) floating around in front of a turquoise background." src="https://cdn-images-1.medium.com/max/1024/1*d_o2nXrrPhBBQBuwgZTQUg.jpeg" /><figcaption>Image by Jokiewalker — stock.adobe.com</figcaption></figure><p>You’ll make a lot of mistakes and that’s beautiful because it doesn’t matter in improv. You’re not being evaluated. Your fellow improvisers will jump on your train regardless. Better yet: <strong>an unplanned, whole-hearted fuckup can be the most hilarious thing in a whole show.</strong></p><p>One warm-up exercise I loved was walking through the room and telling every fellow improviser: <strong>“I’m going to make many mistakes today and I’m going to cherish them.”</strong></p><p>Many other improv games are based on standing in a circle and creating patterns, like passing on claps to other people. More and more rules get introduced so that inevitably, you’ll drop the ball at some point. You then celebrate the moment and yell: “Yay, I failed!” and run one round around the group.</p><p>Actively seeking out the discomfort of failing constantly was one of the biggest stretches for me. I don’t like to fail. I don’t like to look ridiculous. I prepare and I deliver. Consistently.<strong> The many many mini failures during improv class helped me be more generous with myself.</strong></p><p>With constant failure, came my confidence to recover. This helped me try more unconventional things at work — that might not be received well. I’m gradually losing my fear of retaliation. The most beautiful effect is that, by allowing myself to suggest more unconventional ideas, amongst many things that won’t work out, there is a chance for a big idea.</p><h3>5. Make the other person look good</h3><figure><img alt="All in purple: a round stage with light floating on it" src="https://cdn-images-1.medium.com/max/1024/1*TjF2stQmZVMa0Q68HoVzxQ.jpeg" /><figcaption>Image by wacomka — stock.adobe.com</figcaption></figure><p>Once you get to know your fellow improvisers a little, you’ll get to know their passions and strengths. <strong>Play to <em>their</em> strengths!</strong> Give them little gifts. Drop hints you know they’ll love.</p><p>For example, we had one fellow improviser who did an amazing job in leveraging her whole body in scenes. Like: getting hurt while dancing ballet or playing a reluctant toddler, refusing to get up. We learned how to set the scene for her strength.</p><p><strong>If you focus on making the most of peoples’ strengths, it will help you and the rest of the performance.</strong></p><p>This couldn’t be more true for work. You want to be the person lifting others up, getting to know them, learning about their goals, and subsequently providing them with opportunities. Call out other people’s great work. Be their cheer. More than anything, people will remember how you made them feel uplifted.</p><p>Be generous with constructive criticism in a way that brings your team forward. But beware! Don’t complain, don’t gossip, and don’t talk badly about others.</p><h3>6. Own your body and voice</h3><figure><img alt="Abstract image, all in red: glas balloons &amp; laser light" src="https://cdn-images-1.medium.com/max/1024/1*22x-adYRbRTuh9pz94Pkww.jpeg" /><figcaption>Image by wacomka — stock.adobe.com</figcaption></figure><p>Improv is great for getting to know who you can be. You’ll get to explore different characters, tones of voices, energies and scenes. I cherished the safe space to experiment with the power of my body and voice.</p><p>An activity that stood out to me here was: <strong>pretending to be different characters</strong>, for example, the bravest person you know. Or the most caring person you know.</p><p>Another great exercise: <strong>‘leading’ a character with different body parts: </strong>nose first felt like a curious kid to me. Hips first felt like a lazy teenager, having to do household chores. Chest first felt like I’d just been promoted. And feet first felt like I’m a duchess in the 18th century, wandering the most beautiful English garden in the last sunlight of a warm summer day.</p><p>At work, you’ll want to be able to <strong>engage people when you say or do something. Your body is your greatest resource to do this</strong>: Powerful and open body language. Deliberate adjustment of your tone of voice. Occasionally doing something unexpected like being silent for a little too long are powerful techniques to captivate a room.</p><h4><strong>And now? Try improv!</strong></h4><p>I fell in love with improv theatre. It helped me connect with my fun, creative and resourceful social self around others. Anyone can join a beginner’s course. You don’t have to be funny or a good actor. If you’re London based, check out<a href="https://www.hooplaimpro.com/beginner-improv-comedy-course.html"> Hoopla’s beginners’ course</a>. Want to try out some exercises in advance? Hoopla generously open-sourced their<a href="https://www.hooplaimpro.com/improv-exercises-games-formats.html"> beginners’ improv exercises</a>.</p><p><em>What surprising insights have your hobbies brought you that inspires your work? Find me on </em><a href="https://www.linkedin.com/in/antonia-horvath/"><em>LinkedIn</em></a><em>.</em></p><figure><img alt="An image saying “Thank you”" src="https://cdn-images-1.medium.com/max/1024/0*S9NI6inlINVgCLim" /></figure><p><em>A big thanks to </em><a href="http://www.lisalynn.co.uk/"><em>Lisa Lynn</em></a><em>, you’ve been the most fabulous improv teacher. Thanks to Charlotte, Maria, Anna, Patrick and Fade for becoming trusted improv partners, it’s a pleasure to perform with you! And thank you </em><a href="https://www.linkedin.com/in/walgedeon/"><em>Wal Gedeon</em></a><em> for your feedback on this article </em>💙</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=336fbc35fab8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-humans/six-unexpected-leadership-lessons-i-found-in-improv-theatre-336fbc35fab8">Six Unexpected Leadership Lessons I Found in Improv Theatre</a> was originally published in <a href="https://betterhumans.pub/">Better Humans</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Newspaper Article Workshop: inspire your team to find their ‘why’]]></title>
            <link>https://uxdesign.cc/newspaper-article-workshop-inspire-your-team-to-find-their-why-ea7a4186f8c1?source=rss-5dc5553f6d0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea7a4186f8c1</guid>
            <category><![CDATA[workshop]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Antonia Horvath]]></dc:creator>
            <pubDate>Fri, 22 Apr 2022 11:10:52 GMT</pubDate>
            <atom:updated>2022-04-22T11:10:52.463Z</atom:updated>
            <content:encoded><![CDATA[<h4>Imagine a famous newspaper was to write an article about the impact of your team’s work in 5 years&#39; time. What would it say?</h4><figure><img alt="An image of an old-style newspaper with orange paper. It shows an article containing a headline, the main text and a quote. The headline says “Newspaper Article Team Workshop”. The text says “You’ve launched your product. What’s the big headline? It’s time to become a journalist — just for now: It’s been 5 years since the Technology Company first launched This Incredible App. Ever since, nothing is the same. People suddenly get their jobs done — and well! Who’d thought that!”" src="https://cdn-images-1.medium.com/max/1024/1*Ml5bkNPvNxskd32XgFhqwQ.jpeg" /></figure><p>When was the last time your team stepped back and reflected on why you’re doing what you’re doing? This workshop is a great way to bring your team up to that 10.000 feet view. Every team member gets to be a journalist and write their own version of this big story.</p><figure><img alt="This image contains a quote in handrwiting, saying: “Riiight, this is why we’re doing this.”" src="https://cdn-images-1.medium.com/max/1024/1*-BOTZMKG8HFj-salGMMD_g.jpeg" /></figure><h3>Outcome</h3><h4>Find your ‘why’ …</h4><p>This workshop helps envision the best possible future for your team/project/product. It uncovers different possibilities and helps to find your teams’ why.</p><h4>… in a fun way</h4><p>Run this workshop when you want to probe smiling faces and laughter. It’s one of the workshops where people come to you afterwards and say: “that was fun!”. Some participants get really creative and put a fun spin on their article. Each person has a different perspective on why the product matters.</p><blockquote>“Huge thanks for driving this workshop. It’s a creative way to align our vision. We need to run this workshop with all our product teams!” — Luisa, Head of Product</blockquote><figure><img alt="A collage of 4 images, all related to a newspaper. Image one: a man sits on a bench and reads a newspaper. Image two: a sticker on a pillar saying “good news is coming”. Image three: a printing press, printing a newspaper. Image four: oldstyle, metal letters, used in printers before digital printing was invented." src="https://cdn-images-1.medium.com/max/1024/1*NgfZFjJzaeOiPka5MgS40g.jpeg" /></figure><h3>Who can run it?</h3><p>The only qualification so to say is that your team needs to work towards something. A digital product, an event, a new branch opening, anything. I like to run this workshop with software teams, to get them excited about the impact the product will have.</p><h3>When best to run it?</h3><p>You can run this workshop on different occasions. Before a new idea even gets funding, at a project kickoff as well as a few months into a project. The articles might differ in accuracy but the effect is the same.</p><h3>How to run the workshop</h3><p>The concept is simple. Everyone writes a newsletter article about the project/product —pretending it’s 5 years from now. Headline, main article and perhaps a quote, some people like to add an image — no limits to creativity here.</p><h3>Agenda</h3><p>⇢ 5 min: explain how it works<br>⇢ 10 min: silent writing<br>⇢ 15 min: everyone reads their story</p><h3>Prep-work</h3><p>Skip the prep work using <a href="https://miro.com/miroverse/newspaper-article/">this Miro Template</a>.</p><figure><img alt="An image showing a preview of the Miro template: a headline says “It’s in the news…”. Followed by six old-style pink newspapers that workshop participants will be able to edit. It also contains a Miro logo, with an arrow pointing towards it, saying “Miro template available”" src="https://cdn-images-1.medium.com/max/1024/1*jrAx3hqyJPMuKmzxHJPmHQ.jpeg" /></figure><p>This workshop is equally impactful when held in person. You’ll want to have desks around, as you’ll be writing. You will also need a large whiteboard with magnets to pin the articles afterwards. Provide everyone with 2–3 large pieces of paper (A3 if you can, else A4), a very thick marker for the headline and a regular one for the article.</p><h3>During the workshop</h3><p>Every person writes their name on top. Then onto the actual article. It can be easier to write the article first, and the headline last. Adding quotes, images or emojis aren’t a must but you can mention them for inspiration.</p><h3>Pro-tips</h3><p><strong>Don’t let participants be held back by language.</strong> I like to encourage people that it’s not about correct grammar, or an elaborate writing style. This helps, in particular when folks are doing this workshop in their second language.</p><p><strong>Don’t force people to share their stories.</strong> Perhaps they’re having a bad day and didn’t find the words they were looking for. Ask for volunteers instead.</p><p><strong>Adjust your agenda to the number of participants.</strong> Got 4 people in the room? You won’t need 15 mins to share out. Got a full house with say, 12 participants? You’ll want to plan 2–3 mins time to share per participant.</p><p><strong>Tweak the year.</strong> I initially ran this workshop with an article to be published 1 year in the future. One participant thought I said 10 years and their article was even more inspiring. I’ve since changed the standard to 5 years.</p><figure><img alt="A tag, saying in handwriting: “It’s July 2023 (crossed trough), July 2030. An open marker plus the lid lie to the right”" src="https://cdn-images-1.medium.com/max/1024/1*YVfjQ8j7R6USCyjQrGQTWQ.jpeg" /></figure><h3>Contributors</h3><p>This workshop isn’t new. It has been around for some time. I think it should be in every facilitator’s repertoire. I haven’t yet seen it put together on a visually appealing Miro board, so I designed the template. If you’re interested in this workshop method, read about how others run it. My favourite versions are from <a href="https://gamestorming.com/cover-story/">gamestorming</a> and <a href="https://pipdecks.com/pages/newspaper-headline">pipdecks</a>.</p><figure><img alt="A visual divider that says “Thank you!”" src="https://cdn-images-1.medium.com/max/1024/1*q5QhZWHO5PRlcrlTHy3Vcw.png" /></figure><p><em>How do you go about focussing your team on greater, long-term impact? Any other workshops you can recommend? Find me on </em><a href="https://www.linkedin.com/in/antonia-horvath/"><em>LinkedIn</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea7a4186f8c1" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/newspaper-article-workshop-inspire-your-team-to-find-their-why-ea7a4186f8c1">Newspaper Article Workshop: inspire your team to find their ‘why’</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 power of recognition: increase employee happiness through this appreciation workshop]]></title>
            <link>https://uxdesign.cc/the-power-of-recognition-increase-employee-happiness-through-this-appreciation-workshop-8f440013dca9?source=rss-5dc5553f6d0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f440013dca9</guid>
            <category><![CDATA[remote-work]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[workshop]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Antonia Horvath]]></dc:creator>
            <pubDate>Wed, 02 Feb 2022 11:29:48 GMT</pubDate>
            <atom:updated>2022-02-04T21:19:00.825Z</atom:updated>
            <content:encoded><![CDATA[<h4>Remote team building activity</h4><h4>A collaborative way to share praise between team members</h4><figure><img alt="A digital whiteboard with a template of this workshop: sticky notes are arranged as little hearts in different colours: yellow, green, blue, pink and orange." src="https://cdn-images-1.medium.com/max/1024/1*5aQu0ZJwhL27M0R-hbujBQ.jpeg" /></figure><p>When was the last time you stopped the daily grind and recognised the great work of your colleagues? Well, then it’s about time. Psychological safety is a key pillar for successful teams. Recognizing each other is a great way to build trust. This workshop creates the space for team members to give and receive praise for specific situations &amp; actions.</p><h3>Outcome — amplify positive behaviours</h3><p>After this 1h workshop, your face muscles will hurt from all the smiling. Folks will walk away with a confidence booster. They will also know what things they should do more of. It’s a great amplifier of any behaviours that are helpful to the team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dyetKR5w4Iz4C6-9TovHtA.jpeg" /></figure><h3>Who can run this workshop?</h3><p>Everyone that works in a team can run this workshop. You don’t need to work in a specific industry or job. I recently ran it with our <a href="https://tanzu.vmware.com/labs">VMware Tanzu Labs</a> leadership team with 10 participants. And with our whole team across Europe with 30 participants. You might want to tweak the length or the way you run it based on the number of participants. 30 participants: not likely to praise everyone more than once. 5 participants: likely to get through all sticky notes.</p><h3>How to run the workshop</h3><p>The concept is simple: people write nice things about each other on sticky notes.</p><h4>Agenda</h4><p>⇢ 5 min: explain how it works<br>⇢10 min: silent writing<br>⇢45 min: walking through the sticky notes</p><h4><strong>Prep-work</strong></h4><p>Skip the prep work using <a href="https://miro.com/miroverse/i-love-your-work-7tn7rtkxltycsql1/">this Miro Template</a>. Here is how to prepare manually: set up a digital whiteboard that is accessible for each participant. Design little hearts with sticky notes &amp; add headlines for the behaviours you’d like to praise — or perhaps your organization’s values. For example “model good behaviour” or “serve our customers”. This workshop is equally impactful when held in person. Prepare a large whiteboard with headlines. Provide plenty of sticky notes and sharpies.</p><figure><img alt="An illustration that shows a set of three hearts made of sticky notes, each titled differently: “Model good behaviour”, “Serve our customers” and “Serve our team”." src="https://cdn-images-1.medium.com/max/1024/1*yUOUZDL029U1L-4bVuiyWA.jpeg" /></figure><h4>During the workshop</h4><p>Every person writes their name and then the recipient’s name on a sticky note, followed by what they’d like to appreciate. Write as many notes for as many people as you want – in any category you like. After 10 minutes of silent writing, start to share out the sticky notes. Let the authors add their personal stories. Set a 1 — 2 min timer per sticky note.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e8aVrvlYcdtQqMR1iDNhTg.jpeg" /></figure><h4><strong>Pro-tip</strong></h4><p>If you fear you might not get through all stickies: prepare a list of participants and mark who was appreciated to ensure that everyone is mentioned. This also ensures that high-performers aren’t getting <em>all</em> the attention.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nYGjb2SAafLTFcEDZc-0QQ.jpeg" /></figure><h3>Considerations</h3><p>This workshop can be very powerful in a good way. We run it quarterly with our team. However, it can feel fake if the general psychological safety in your team isn’t great. It’s also not a magical solution that will solve your team’s challenges. Continue to do the hard work to make your place a good place to work at. If you’re just starting to think about your team’s health, I’d encourage you to learn about the value of <a href="https://tanzu.vmware.com/developer/practices/3-column-retro/">weekly retrospectives</a> and how to run them.</p><figure><img alt="A divider image saying “Thank You!”" src="https://cdn-images-1.medium.com/max/1024/1*LZe3g9RdCsa9p_0Ve1Mt6A.png" /></figure><p>How do you go about sharing appreciation within your team? I’d love the next version of this workshop to incorporate your feedback. Find me on <a href="https://www.linkedin.com/in/antonia-horvath/">LinkedIn</a>.</p><p><em>A big thanks to Aly Blenkin, Ellie Ereira and Erin Cobb, who ran this format for the first time with our team. And to Andrea Nagel, who inspired me to share this template through her recent webinar </em><a href="https://www.brighttalk.com/webcast/14883/520196"><em>Learn to build and retain development teams</em></a><em>. And Dale Owen, who continuously innovates how we help our teams feel more psychologically safe.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f440013dca9" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-power-of-recognition-increase-employee-happiness-through-this-appreciation-workshop-8f440013dca9">The power of recognition: increase employee happiness through this appreciation workshop</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[Run a hack-day to solve your next  product challenge]]></title>
            <link>https://medium.com/design-bootcamp/run-a-hack-day-to-solve-your-next-product-challenge-56fa9026a8d0?source=rss-5dc5553f6d0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/56fa9026a8d0</guid>
            <category><![CDATA[facilitation]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Antonia Horvath]]></dc:creator>
            <pubDate>Wed, 14 Apr 2021 04:01:26 GMT</pubDate>
            <atom:updated>2021-05-04T20:20:50.792Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A colourful illustration of a woman who kneels on the floor and assembles a huge app with a screwdriver" src="https://cdn-images-1.medium.com/max/1024/1*kCDuVzC0OBIVyodTt1IJpA.jpeg" /><figcaption>All illustrations are made by <a href="https://www.antonia-horvath.com/play">the author</a></figcaption></figure><h4>H O W - T O</h4><h3>Run a hack-day to solve your next product challenge</h3><h4>… and spice up the software delivery phase</h4><h4>What’s a hackathon, usually?</h4><p>People with different backgrounds and expertise come together to solve a problem through software. In a limited timeframe and through intense collaboration. Hackathons are run out of different motivations: To solve a challenge for society. To practice a particular technology. To attract talent or to solve business challenges with fresh minds. A phenomenal concept.</p><h4>Experiment: a product-focused hack-day</h4><p>Having worked with different teams on a variety of digital products, I like to carefully craft highlights that lift the teams spirit and bring fresh perspectives in the delivery phase. I was looking for an opportunity to experiment with a hackathon because I love the playful, yet intense collaboration. Last year, I ran the first product-focused hack-day experiment with my team.</p><h4>Who can run it?</h4><p>Everyone in a software development team, who wants to try a different, collaborative approach to problem-solving. Designers, product managers, and engineers alike can run a product-focused hack-day. Even when you are not normally a leader, this is a great opportunity to lead your team and practice facilitation techniques.</p><figure><img alt="A colourful illustration of a woman who leans on a giant hourglass. She is bored by the usual product development rhythm." src="https://cdn-images-1.medium.com/max/1024/1*vQXBpfeBz74t9SJEwoHw-g.jpeg" /><figcaption>Highlights like a hack-day can spice up the delivery phase</figcaption></figure><h4>Like a design sprint paired with a technical spike</h4><p>Think of a product-focused hack-day as a mix of a <a href="https://www.thesprintbook.com/how">design sprint</a> and a <a href="http://www.extremeprogramming.org/rules/spike.html">technical spike</a>, run in one day. I picked a product challenge, pitched the idea to my team and they got excited about it. Two days later, everyone stepped aside from their usual work and focused on solving a challenge together. It felt like a day in the workshop, crafting the bizarre and eventually, something useful.</p><h4>Outcomes</h4><p>It’s up to you to design the outcome of a hack-day. It could be prototypes in real code that you can test with users to validate your product hypotheses. This was the desired outcome when I ran the last two hack-days with my teams. Or maybe you‘d like to explore a problem from a technical perspective in a timeboxed manner? If you can, focus on a key challenge for your users.</p><p>No matter the focus, a hack-day will help your team shift their perspective away from business as usual and come up with unconventional ideas. It’s most likely also going to be great fun. It will nurture collaboration as a balanced team. And you’ll have something cool to show in your next product demo.</p><figure><img alt="A colourful illustration of a woman who sits on a gigantic present. She is excited to unwrap it." src="https://cdn-images-1.medium.com/max/1024/1*jZ8fTZAb2GM2EREgXkC6WQ.jpeg" /><figcaption>Example 1: making digitally unwrapping a present fun</figcaption></figure><h4>Real-world example 1: digitally unwrap a present</h4><p>The most exciting hack-day I ran with my team so far was when we wanted to investigate different ways to digitally unwrap a present. The goal was to find out whether users would get as excited as in the real world. Everyone in the team came up with cool unwrapping interactions and later in the day we paired up to test whether we can actually get them working. And we did. We tested them with users the week after. One of the unwrapping interactions went live only weeks after the hack-day.</p><figure><img alt="A colourful illustration of a woman who leans on a pie chart. She is in the middle of interpreting data, pointing towards another chart." src="https://cdn-images-1.medium.com/max/1024/1*px51L9u-wPdeX5fUgZ887A.jpeg" /><figcaption>Example 2: making analysing data easier</figcaption></figure><h4>Real-world example 2: make patterns in data visible</h4><p>Another time, another hack-day. We wanted to explore different ways for our users to easily find patterns in a large amount of data. For our prototype, we wanted to use real data, which is difficult to mock in a design tool. We came up with three different models that we went ahead and built in the afternoon. These prototypes laid the foundation for the next product iteration. They helped us to understand what works and what doesn’t work so well, from a technical perspective.</p><h3>Ready? Go run your own hack-day</h3><h4>Look for opportunities</h4><p>Every team member can propose a product-focused hack-day. Whether you are a designer, a product manager, or even an engineer.</p><p>Think about picking a tricky product challenge, or kicking off the next major product outcome. Perhaps you have a problem where you don’t yet know the solution. Or your team is divided and cannot yet commit to one solution. The hack-day is a great addition to your regular ideation techniques, particularly when the problem is complex.</p><p>Many teams and companies regularly donate their time to give back to local communities. You can use a hack-day event to hack on something to support your own local community and raise team morale.</p><h4>Validate the problem up-front</h4><p>Start by defining the challenge and doing some up-front user research to validate that the challenge is relevant for your users. Interview your sponsors to ensure that the challenge has sufficient business value to fetch y’all’s brains for a day to solve it.</p><figure><img alt="A colourful illustration of a woman who is excited about the hack-day. She is surrounded by sticky notes that were created during the hack day." src="https://cdn-images-1.medium.com/max/1024/1*G1w2zuMVj5labspe7WhWaQ.jpeg" /><figcaption>Get buy-in from your team</figcaption></figure><h4>The foundations</h4><p>Find a time where your team can step a whole day aside for a hackathon. Get buy-in from your fellow team members and the product owner. Consider inviting subject matter experts, if helpful for the challenge. Organize facilities, if in person. Get the day booked into everyone’s diary.</p><p>Ensure whiteboards, sticky notes, paper, sharpies, a timer, and other fun supplies are available. Make sure everyone has access to an infrastructure that lets them set up branches for their code. Even if messy and hacky, so that you can use the prototypes to test with users afterward. In a remote setup, plan a space for collaboration like a digital whiteboard and set the video conferences plus breakout rooms. A Slack or Teams group doesn’t hurt, either.</p><blockquote>Provide snacks, if you can. Even in a remote setting, having a pizza 🍕 delivered is a nice gesture that does not cost the world.</blockquote><h4>Give you team research prep-work</h4><p>In the invite, set expectations. Share the problem space and give participants research-prep-work, if appropriate. I like to ask everyone to research at least one cool example of how others solve a similar challenge.</p><h4>Set the agenda, define facilitators</h4><p>Plan the agenda by defining key activities, without restricting your team too much. Think about if you want to split your team into pairs or sub-groups. Appoint a facilitator for the day [This can be you 🎉].</p><blockquote>“The facilitator’s job is to support everyone to do their best thinking.” — Sam Kaner, Author of Facilitator’s Guide to Participatory Decision-Making</blockquote><h3>During the day: make some magic</h3><figure><img alt="A colourful illustration of a woman who writes code on her laptop during a hack-day. She is surrounded by notes on paper." src="https://cdn-images-1.medium.com/max/1024/1*5SJKxYiu26iwFthl4Q-trQ.jpeg" /><figcaption>Do some magic during the hack-day ✨</figcaption></figure><h4>Outsmart business as usual</h4><p>Remember, it’s a hack day, so it’s good to do things differently. As a facilitator, encourage people to work with people they wouldn’t normally, solve problems using different tools and techniques they want to practice, and generally be free of normal workday constraints.</p><blockquote>“We cannot solve our problems with the same thinking we used when we created them.” — Albert Einstein</blockquote><h4>Start the day together, ideating</h4><p>Get everyone in one room, share the agenda and the problem space. Set the scenario and define the desired outcomes. Share user evidence to set your team up for success.</p><p>If you are looking for some steer in where the teams are going, start the day by running a <a href="https://tanzu.vmware.com/developer/practices/design-studio/">design studio</a> with everyone. Vote on the ideas that seem the most promising and then split into teams around the top-voted ideas. This way, you collectively decide what to focus on during the day and avoid folks going down irrelevant paths or pursuing similar ideas.</p><h4>Split into teams and check in with them</h4><p>Leave the groups to self-organize. In a remote setting, agree where and how you can reach each other. For example: in the last hack-day that I ran, folks have split in breakout-rooms and created dedicated slack channels. As a facilitator, check-in with people to see whether you can help unblock them.</p><h4>Come together for a shareout</h4><p>Set a specific time when everyone agrees to come together to share out what they have developed. Ask each team to walk through their work, encourage questions. Document the ideas: take photos, screenshots, and notes that explain the essence. Record, if you can.</p><p>At conventional hackathons, the top ideas are rewarded. I like to set expectations with my team that there will not be a reward, but there will be free snacks &amp; pizza. If you can think of something small that makes sense in your context, go for it!</p><figure><img alt="A colourful illustration of a retrospective board with stickies for positive, negative and neutral feedback." src="https://cdn-images-1.medium.com/max/1024/1*v2Y8PD3iMvOjeyA6aKOouA.jpeg" /><figcaption>Always ask for feedback</figcaption></figure><h4>Close off the day with a short retro</h4><p>Ask your team to reflect on the day and close off with a quick retro: what went well, what didn’t go so well? What will you do differently next time? Make sure you end on a high note.</p><h4>Next steps: validate and share</h4><p>As a user’s advocate, I’d like to highlight that this step is key. Validate/invalidate ideas from the hack-day with users before you proceed to implement them. The week after a hack-day is ideal to run a round of qualitative user research.</p><h3>Feedback from participants</h3><figure><img alt="Sticky notes that contain feedback about the hack-day. They say: “A difrent kind of day than normal”, “Omg, how fast can we create something cool?”, “Anything allowed, hacky and fast. We have working prototypes in code now!”, “Great for team bonding!”, and “Learned a lot about the domain.”." src="https://cdn-images-1.medium.com/max/1024/1*ySX9IcxGS7fP39xQHIbllg.jpeg" /><figcaption>What people have said about the hack-day</figcaption></figure><p>Folks were genuinely excited about the speed as well as the creativity of the outcomes. People felt proud of what they have created as a team. They were keen to participate in the user research afterwards to see users’ reaction to their ideas. Some constructive feedback, to consider for your hack-day:</p><ul><li>🔎 Provide enough lead-time to enable people to do research in advance</li><li>🗓 Make sure peole do not get pulled out. No other appointments that day</li><li>🍕 Snacks seem to really matter for people :) Provide them</li><li>🥇 People who participated in hackathons before might expect a prize</li></ul><figure><img alt="An image that says in handwriting: “Yay, free stuff!”" src="https://cdn-images-1.medium.com/max/1024/1*ShIu8FVGfl0Gpyym-J0dpA.png" /></figure><h3>The Hack-Day Pack</h3><figure><img alt="An illustration of the Miro-template that comes with this article." src="https://cdn-images-1.medium.com/max/1024/1*de96hWj8tuAdPXfheEMx7A.jpeg" /></figure><p>Save time and use this free <a href="https://miro.com/miroverse/product-focused-hack-day/">Miro template</a> with a sample agenda and frames for homework, design studio, and feedback</p><p>How do you go about keeping the team spirit high and your ideas fresh when building software? I’m curious about your feedback! Find me on <a href="https://www.linkedin.com/in/antonia-horvath/">LinkedIn</a>.</p><p><em>A big thanks to Tim Jarratt and Dale Owen for sharing your thoughts and feedback. They form the basis of this article </em>🧡</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56fa9026a8d0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/run-a-hack-day-to-solve-your-next-product-challenge-56fa9026a8d0">Run a hack-day to solve your next  product challenge</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting started: user research for rapid digital innovation]]></title>
            <link>https://medium.com/swlh/getting-started-user-research-for-rapid-digital-innovation-5579556423ea?source=rss-5dc5553f6d0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/5579556423ea</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[lean-ux]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Antonia Horvath]]></dc:creator>
            <pubDate>Tue, 23 Feb 2021 11:07:52 GMT</pubDate>
            <atom:updated>2021-02-23T11:07:52.219Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A woman sitting in front of her laptop, preparing user research, smiling." src="https://cdn-images-1.medium.com/max/1024/1*WVaq4OIGUwt2HacZL5nJEQ.jpeg" /><figcaption>Photo by ‘DimaBerlin’, purchased on <a href="https://www.shutterstock.com/home">Shutterstock</a></figcaption></figure><h4>G U I D E</h4><h4>How to find the balance between knowledge and time investment</h4><h4>Tips from the field</h4><p>How much do we need to know about the people we design for to make a confident decision about what to build? I help organizations find their sweet spot of certainty through user research when innovating at high speed.</p><p>In 2020, the teams I worked with have conducted qualitative research with over 140 people. Many of the sessions I have facilitated myself. Including 1:1 interviews, diary studies, contextual inquiries and usability tests. All teams have launched MVPs within a matter of weeks, improving them ever since through a tailored, lean way of user research.</p><p>The following recommendations are the essence of what I have learned. They aim to help you find an actionable balance between knowledge and time investment.</p><blockquote>This way of approaching user research will enable you to gain the speed you need to in order to compete in the unforgivingly fast software industry.</blockquote><p>Why does speed matter? One of the biggest risks for any software is the risk of delay. A major shift in the industry? A sudden change in management? If your product has not yet launched and proven to be valuable, even after months of development, it is at risk to be abandoned. It happens all the time. Also, whilst you take it slow, others won&#39;t. Don’t be the organization missing out on opportunities because you’re too hesitant to act before you know it all.</p><h3>Is it an actual problem worth solving?</h3><p>Many people, when they think of user research, they think of testing ideas. But the most essential form of user research happens before teams decide what to build in the first place. It‘s that powerful moment when you investigate the problem space to find opportunities worth acting upon.</p><p>Ideally, this is how innovation starts. In reality, it almost never does. In one way or the other, someone (usually higher up the food chain) will have an idea about how to fulfil their business targets.</p><p>What follows then is the one, often overlooked step, where designers are most needed. Particularly when you seek to <em>truly</em> innovate. You need to validate whether business hypotheses are rooted in an actual need from real people. This step needs gut. At some point, it will involve telling powerful people their idea isn’t worth pursuing and offering a better alternative.</p><figure><img alt="A comic of a product sponsor, giving his very detailed, subjective idea. A designer is advocating for user needs instead of fulfilling individual ideas" src="https://cdn-images-1.medium.com/max/1024/1*LXPokdFoaVvU8ylqSivJyg.jpeg" /><figcaption>Illustrations: Pablo Stanley’s amazing <a href="https://openpeeps.com/">open peeps</a>, text added by the author in <a href="https://www.figma.com/">Figma</a></figcaption></figure><p>My best advice: before you start writing one line of code, go talk to people who you believe are your target audience. Observe what they struggle with. Ask open-ended questions. Listen with the intention to change your mind rather than confirming what you already believe to know. This step will help you form a proposition hypothesis that is based on first real-world evidence. It will have a significantly higher chance of success.</p><h3>Start simple, do it yourself</h3><p>Don’t rely on external partners or other parts of the organisation to do user research for you. Upskill your product teams. This will save you a lot of time and money and will give you the flexibility you need. Get started by learning how to set research goals &amp; map assumptions. Learn how to <a href="https://www.uxmethodsbook.com/">pick the right method</a> and how to conduct and <a href="https://uxdesign.cc/synthesis-how-to-make-sense-of-your-design-research-d67ad79b684b">synthesise</a> the research, bias-free.</p><p>Are you just getting started with user research? In that case, I recommend reading Erika Hall‘s 📓 <a href="https://abookapart.com/products/just-enough-research"><em>Just enough research</em></a><em>.</em></p><p>Qualitative 1:1 interviews with self-sourced participants are a great way to get started. Read how to find potential candidates aside from friends &amp; family to get unbiased insights <a href="https://medium.com/mixed-methods/diy-recruiting-how-to-find-participants-for-your-research-6f9a05dd1a33">here</a>. 1:1 interviews will provide your team with the <em>why’s </em>behind people’s behaviours. Running them on a regular basis will reduce the stress to get everything right the first time. It will give your team the freedom to experiment a little.</p><p>Whilst working remotely can limit the methods, there are plenty of great ways to run user research remotely. Plus: talking to users in their known environment (aka home, these days) might help them to behave more naturally and open up more.</p><figure><img alt="A video call where people conduct user research remotely" src="https://cdn-images-1.medium.com/max/1024/1*ML6tbaxDBrZ1pha-_g1t0A.jpeg" /><figcaption>Image of woman by ‘fizkes’, purchased on <a href="https://www.shutterstock.com/home">Shutterstock</a>. Image of video call made by the author in <a href="https://www.figma.com/">Figma</a></figcaption></figure><h3>Make user research a habit</h3><p>User research is like brushing your teeth: there is no point in doing it for an hour before leaving the house. 3 mins are sufficient, as long as you do it regularly. If you don’t do it, phew… fixing teeth hurts and it will cost you a small fortune.</p><p>I encourage teams to ditch massive up-front research and run research <em>at least </em>every second week instead. If this shocks you, let’s talk about the scope. A frequent cadence means a smaller scope than the research an ‘old world’ UX designer might have run every couple of months.</p><figure><img alt="A calendar entry of a weekly slot for user research" src="https://cdn-images-1.medium.com/max/1024/1*1iPJTQojmem56KTVoQ4zoA.png" /><figcaption>Image created by the author in <a href="https://www.figma.com/">Figma</a></figcaption></figure><p>Test whatever you have. A paper sketch, a rough wireframe, a prototype, the product of a competitor. If you don’t yet have something tangible to show, observe how people get the job done now. Ask open ended questions.</p><p>Also, stay curious. Exploratory research isn’t just for the start of a product. It’s not like you ask openly at the beginning, and in later iterations you only validate ideas. I like to ask a couple of exploratory questions at the start of every 1:1 interview. Regardless of the stage of product development.</p><h3>Replace big studies with real-world experiments</h3><p>I see organizations do excessive user research mainly when it is a separate discipline, away from the product teams. Often with a dangerous lack of speed, business thinking &amp; connection to the real world impact of their work. Sometimes research departments have fought hard for their existence and tend to over-do the job in order to prove their value. I am an advocate for balanced software teams. Having a user researcher embedded within each team will prevent them from going off on a tangent.</p><p>Some people worry that user research with 5 people per week will not provide teams with enough certainty. You <em>could</em> set up a big, quantitative study with thousands of participants. This is likely to take you a couple of weeks, if not months.</p><p>The reality is: businesses simply cannot afford to spend months on studies in order to decide whether they should start to build a product. They need to validate their ideas as fast as they possibly can.</p><p>Now, what do you do instead to get data on a larger scale? In software, big, time-intensive studies are replaced with ‘beta versions’ or ‘minimum viable products’. They are experiments that take as little effort as possible to run. They aim to test whether an idea will actually work in the real world. These real-world experiments can take many shapes and forms (<a href="https://medium.com/lean-startup-circle/how-to-conduct-lean-experiments-aecc6aae17c5">a video, a landing page…</a>). They deliver more relevant evidence than a study, faster.</p><figure><img alt="A landing page where people can sign up for a product that does not yet exist, to validate the demand" src="https://cdn-images-1.medium.com/max/1024/1*rSmCi-Gy_TlDT6Tno7qxfA.jpeg" /><figcaption>Image created by the author in <a href="https://www.figma.com/">Figma</a></figcaption></figure><h3>Make research a team responsibility</h3><p>Do you know anyone who gets excited by reports? I don’t. Designers: don’t go away, interview users and then present your team &amp; stakeholders with the synthesized results. You’re the masters of designing experiences. I’m sure you can find a better way for your team to learn about user needs and build empathy. Inviting the team to do user research with you is a great way to start.</p><p>At <a href="https://tanzu.vmware.com/labs">VMware Tanzu Labs</a>, alongside the designer, we also have product managers and engineers run user research sessions. They are also great notetakers and take part in the synthesis. It’s an invaluable skill to truly listen to people and get them to open up. It’s a powerful provider of „why“. When synthesizing, more diverse brains will help prevent bias. And you can skip updating your team because everyone has been part of the process.</p><figure><img alt="A team, clustering sticky notes during research synthesis" src="https://cdn-images-1.medium.com/max/1024/1*KxjTYGY9XcfGwGvu9V1g5w.jpeg" /><figcaption>Image by ‘You X Ventures’, from <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p>It’s also a very powerful way to engage stakeholders. Get sponsors to experience what people actually worry about. Let them hear first hand what they don’t care about. Let them see how people sigh, smile or struggle when using your product. Invite them to a <em>little dip into reality</em>.</p><h3>Keep documentation lean</h3><p>Have you ever heard of <a href="https://medium.com/@fluidui/21-examples-of-waste-in-lean-product-development-90f488ffd778">minimizing <em>waste</em></a> in the context of lean software development? It means that teams ruthlessly prioritise work that will benefit a user over all else. For the sake of efficiency.</p><p>There is also a lot of waste in classic UX and UI work. Documenting user research excessively is a good example. Think of it: instead of building that dreadful slide deck or cumbersomely transferring insights to a wiki, the designer could work on something that actually delivers value to users. A way to reduce documentation efforts that has worked well for me in the past: I like to use <a href="https://miro.com/index/">Miro</a> for the team to take notes and synthesise.</p><blockquote>The great thing about tools like Miro is: at the time you finished synthesis, your documentation is done, too.</blockquote><figure><img alt="A screenshot of the app Miro, showing a user research and synthesis board where you can see the progress from many raw-note stickies to clustered stickies that form insights" src="https://cdn-images-1.medium.com/max/1024/1*LwFOnSYcpm4TLRb_b4BDRQ.jpeg" /><figcaption>Image created by the author in <a href="https://www.figma.com/">Figma</a></figcaption></figure><p>There is one exception to my self-inflicted rule of not leaving Miro. My dear friend and designer <a href="https://www.linkedin.com/in/walgedeon">Wal Gedeon</a> introduced me to the concept of the <em>Slack-snapshot: </em>a list of 3–5 top-insights. I post them in a common Slack channel, the very evening after synthesis. I like to use it with bigger teams or when working on a high profile project with a high interest across the organization. Creating the <em>Slack-snapshot</em> should only take you 5 minutes.</p><figure><img alt="A screenshot of a Slack-snapshot of key insights for bigger teams" src="https://cdn-images-1.medium.com/max/1024/1*3rpM4TbBxK6Z1AWXjKTrVA.jpeg" /><figcaption>Image created by the author in <a href="https://www.figma.com/">Figma</a></figcaption></figure><p>Thinking of long-time insight documentation: I like to have design artefacts like <em>personas</em> or <em>jobs to be done</em> also live in Miro. That way, I can easily update them with evidence. People’s behaviours and interaction with software changes over time. That’s why I’m hesitant to create huge user insight databases. I would not want to risk building a product on the basis of 1-year-old insights.</p><h3>Create a culture of genuine curiosity</h3><p>I believe that user research can only flourish in an environment where failures and successes alike are humbly analysed and taken for what they are: an opportunity to grow. For software and people alike.</p><p>UX standards and the designers’ expertise are a great place to start but can never replace getting actual feedback from people. Today’s challenges in software are way too complex and unpredictable to be solved purely based on best practices or past experience.</p><blockquote>Users don’t care about what deciders and experts think or want. If you do not provide them with the most helpful way of getting a job done, they’re likely to get the job done differently, without your software.</blockquote><p>This article started with how user research will help you innovate at high speed. It ends with how user research will improve your work culture and ultimately make you a better person.</p><p>Practising evidence-based design will help your team to adopt a growth mindset. It starts with the product. But it will eventually create a culture that values interpersonal feedback, too. People will become more supportive of their individual growth.</p><p>Start listening to people with humble curiosity and the genuine intention to have your mind changed by what they say. It will make you have better conversations, professionally and personally. Ask open questions, get behind people’s motivations. I guarantee you it will show new perspectives you didn’t know could move you.</p><h3>TLDR; Summary</h3><ul><li>User research isn’t just testing ideas. Start with <strong>investigating the problem space</strong> to find opportunities worth acting upon</li><li>Don’t outsource user research. <strong>Upskill your team</strong> instead. Learn how to plan, conduct and synthesize research together</li><li>There are<strong> plenty of research methods you can try</strong>, most of them are working well when remote working</li><li><strong>Conduct user research weekly</strong> or biweekly with 5 participants. To keep up with that cadence, reduce your scope</li><li>Replace big, time-intensive studies with <strong>real-world experiments</strong>. They deliver more relevant evidence than a study, faster</li><li><strong>Involve the whole team</strong> in user research. It will help to build empathy for users and it helps reduce bias in the results</li><li>Minimize waste through <strong>lean research documentation</strong>. Use a collaborative whiteboard to take notes &amp; synthesize to replace slides</li><li>Create a culture of <strong>feedback and learning</strong>. Embrace failures as well as successes as an opportunity to grow</li></ul><p>How do you balance getting the user evidence you need with maintaining a high speed when building software? I’m curious to start a conversation with the genuine intention to have my mind changed 🙏 Find me on <a href="https://www.linkedin.com/in/antonia-horvath/">LinkedIn</a>.</p><p><em>A big thanks to Wal Gedeon, Anna Shausmanova, Jana Lasser and Erin Cobb for sharing your thoughts and feedback. They form the basis of this article </em>💚</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5579556423ea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/getting-started-user-research-for-rapid-digital-innovation-5579556423ea">Getting started: user research for rapid digital innovation</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How designers and engineers can collaborate closer and build better digital products]]></title>
            <link>https://uxdesign.cc/how-designers-and-engineers-can-collaborate-closer-and-build-better-digital-products-508e5f27134b?source=rss-5dc5553f6d0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/508e5f27134b</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Antonia Horvath]]></dc:creator>
            <pubDate>Tue, 10 Nov 2020 10:18:17 GMT</pubDate>
            <atom:updated>2021-05-04T20:27:49.011Z</atom:updated>
            <content:encoded><![CDATA[<h4>GUIDE</h4><h4>Unleash designers’ &amp; engineers’ superpower to solve the world’s most complex problems together.</h4><figure><img alt="An illustration of an engineer and a designer. They are sitting in front of a computer, working together, smiling." src="https://cdn-images-1.medium.com/max/1024/1*uBWMw1Mp3yh0WHi9Fb4GAQ.jpeg" /></figure><p>Helping teams to validate business ideas quickly and build lean, user-centred products is what I am passionate about. A significant part of the job is encouraging individuals to work closer together. Oftentimes, engineers and designers, left-brainers and right-brainers have to work the hardest to find a fruitful way to collaborate.</p><p>Out of many conversations with engineers and designers as well as learnings from team retrospectives over the last years, I’ve synthesised actionable tips and smart rituals that will fuel every designer/engineer collaboration.</p><h4>Why invest in this relationship?</h4><p>Businesses are increasingly achieving their goals through software. They need to learn how to build great software, fast, and develop the agility rapidly react to user feedback. A proven approach to achieving this mission is establishing balanced product teams. Engineers, designers, and product managers work together in an agile manner.</p><figure><img alt="A drawing of a brain. The left side &amp; the right side are highlighted to show how engineers &amp; designers think differently" src="https://cdn-images-1.medium.com/max/1024/1*udFYAKwd0anWrcaDwE0ciA.jpeg" /></figure><p><strong>As a designer,</strong> investing in your relationship with engineers helps you to understand code better, and to suggest potential solutions that will better inspire the engineers you work with. Everyone needs to be technical these days, and as a designer, it feels good to solve problems in a smarter way.</p><p><strong>As an engineer,</strong> investing in your relationship with your team’s designer(s) helps you to understand how users interact with the code you write and to empathise with their needs. No one likes to rewrite a feature because it was poorly understood when it was first created; working closely with design allows us to reduce unnecessary work and spend more time making cool stuff.</p><blockquote>Designers and engineers are a strong alliance, equipped to solve the world’s most complex problems together. Let’s unleash their power by fuelling their collaboration.</blockquote><figure><img alt="An illustration of an iPad that shows a simplified calendar view with four entries of rituals for engineers &amp; designers" src="https://cdn-images-1.medium.com/max/1024/1*LiqE1oXcFWoxfgAH2oDfEw.jpeg" /></figure><h3>1. Rethink your rituals &amp; habits</h3><figure><img alt="An infographic that shows the difference between no collabration and close collaboration between engineers &amp; designers" src="https://cdn-images-1.medium.com/max/1024/1*8m5swYFCdYEGKSLtDnDt8g.jpeg" /></figure><p>I’ve collected a couple of rituals &amp; habits that have helped engineers/designers in the past. Some of them are well-known from agile software development, others are rather new. They’re all about moving from a world of ‘handoff’ with little collaboration to a world of ‘handshake’ with close collaboration.</p><figure><img alt="Several logos of design &amp; engineering tools come out of an open laptop." src="https://cdn-images-1.medium.com/max/1024/1*2HA3j86A_rRcg3myICtBxw.jpeg" /></figure><h4>Tool and technology intro</h4><p>This session is a kickoff at the beginning of a product lifecycle. It’s an intro to the tools and technologies you will be using. It’s also a great opportunity to teach others the parts that are necessary for their work. This includes enabling engineers to work with Figma or whatever tool designers use to translate designs into specs. Show them how to export assets etc. Designers get access to the pre-live environment so that they can see the status quo of the product at any time.</p><p>For example, a native app differs from a website. Each platform has its unique interaction patterns, the programming language differs even more. Whilst engineers tend to be specialised in one platform, digital designers are generally not. You may well have to rely on each other’s expertise around the platform your product will be built for. It’s worth sharing knowledge and best practices from day one.</p><figure><img alt="Two people have a casual video conference together. In the foreground you can see two coffee mugs." src="https://cdn-images-1.medium.com/max/1024/1*H9Rb3yGzwJX50TbSZyFv7A.jpeg" /></figure><h4>Casually hang out together</h4><p>Human connection matters. A lot. Especially when working remotely, I would advise to actively plan for human connection. Building relationships with the humans you work with requires a little work upfront. So turn your video on and open up about yourself a little.</p><p>It might be a scheduled coffee break once or twice a week, or an evening hangout. I’ve also seen team breakfasts. This is work time too, so try to schedule it at a time that works for everyone. Be mindful of people that don’t work full-time. When working remotely, playing an online game like <a href="https://skribbl.io/">skribbl</a> can help to get everyone laughing together.</p><figure><img alt="A person looking out of a window, waving a sign that says “Hi!” on it." src="https://cdn-images-1.medium.com/max/1024/1*gL22w0oC9qLK03-4mJKCyg.jpeg" /></figure><h4>Reach out, at any time</h4><p><a href="https://www.pivotaltracker.com/blog/daily-standup-is-planning-meeting">Daily standups</a> are like a sport’s team huddle before a play and a great way to highlight blockers and ask for help. The team gets together and everyone briefly shares their progress and challenges for the day so that you can step up and help each other out.</p><p>However, standups are not the only time you should act upon blockers. A mature relationship between engineers and designers means that you can spontaneously reach out and get time together within a matter of minutes or hours. Not via email, not via a Jira request. Don’t hide. Afraid you’re interrupting the other person/pair? Don’t worry.</p><blockquote>“Approach the engineer/designer with a friendly wave and a “let me know if you’ve got 5 mins”. Or a slack message, asking to jump on quick a zoom call. That way, you’re not disrupting their work. Still unsure when to best approach? Grab people on the go: for example when they are are just sitting down after lunch. If you want more structure, think about naming an “interrupt pair/person”.”<br>— Gagandeep Kaur, a software engineer at VMware Pivotal Labs</blockquote><figure><img alt="An illustration of an engineer and a designer. They are sitting in front of a computer, working together, smiling." src="https://cdn-images-1.medium.com/max/1024/1*k-ft2h4p6s6FzLRbyPeAtQ.jpeg" /></figure><h4>Dev/design pairing</h4><p>This is my favorite ritual. Engineers and designers improve the design of a product, coding together, live. That way, you can accept user stories even when they are not yet visually perfect, as long as the functionality works. Small design improvements make it to the designer’s backlog for the next pairing session.</p><p>Dev/design pairing is usually driven by the designer. They closely observe what has been built and makes notes on improvements. It can take from 1–2h per week up to several hours when you are about to release your next iteration. Whatever you cannot fix during this time, will make it into a bug or story and will be prioritized later.</p><p>Dev/design pairing can be scary for engineers. You will sit in front of the same screen (or a screen share) with the designer and will try to adapt their suggestions, live. Don’t worry, the designer isn’t testing how fast you can code. They will also embrace the fact that part of your job is not knowing and researching on the internet. And if you can’t find out after some research, that’s ok too.</p><p>Designers sometimes fear these sessions because they lack the proper terminology. Don’t worry. You can use any words, the engineer will ask until they understand. Plus: over time you’ll get used to how engineers relate to things and your ability to talk in code will improve.</p><p>A little kindness can go a long way when establishing these sessions. Over time, you will get used to each other and the sessions will become more fun. And your product will benefit a great deal.</p><blockquote>“It’s amazing how the tweaks from our dev/design pairing sessions have improved the look and feel of our product. It’s so much more fun to use now. The pairing is like a timeboxed, additional code-review, where you can optimise things that are not tied to stories, but will benefit the user. Since we are doing dev/design pairing, I have become a more active advocate for the user and their experience.”<br>— Maximilian Zuleger, software engineer @ <a href="https://www.audi.com/en/career/professionals/audi-software-development-center.html">Audi Software Development Center</a></blockquote><figure><img alt="Three paper sketches of a design for an app. Two sharpies lie next to them. Random parts of the sketches are highlighted." src="https://cdn-images-1.medium.com/max/1024/1*wve08UspK8uH8JAIUeJQyA.jpeg" /></figure><h4>Ideate together</h4><p>Amazing ideas emerge when you include engineers in ideation sessions. It’s great a way to live shared product ownership. It will empower each team member to take an active part in where the product is heading. It’s the designer’s role to facilitate these sessions and make sure every idea is heard. They form the basis of the designer’s future work.</p><p>At VMware Pivotal Labs, we call our ideation sessions design studios. The whole team gets together to solve a clearly defined problem. The goal is to find as many solutions as possible in a short amount of time (say, 2 hours). Collectively prioritize which parts you will proceed and create actual design hypotheses for. We run 2–3 rounds of sketching and do a shareout after each round. That way, others can get inspired by ideas and think them further.<br>💡<em> </em>Read <a href="https://medium.com/product-labs/how-to-run-a-quick-design-studio-workshop-remotely-934ed48e4e31">how to run a design studio remotely</a><em>.</em></p><figure><img alt="A simplified app design has red and green sticky notes all over it. They stand for negative and positive feedback." src="https://cdn-images-1.medium.com/max/1024/1*PtkqWcOch7sMDHH_O_fEwg.jpeg" /></figure><h4>Design critiques</h4><p>Feedback from the product team is a great addition to feedback from real users. Fellow designers can provide their user centred view. Engineers can provide a more technical perspective on feasibility.</p><p>There are many ways to do a design critique. I like to do something like this: In a weekly rhythm, the designer brings what they are working on (high level user flows, visual designs, research hypothesis etc.) to a 1h session with the whole team. Print out artefacts or share them on a digital whiteboard.</p><p>I like to start by introducing the challenge in advance. I also specify what kind of feedback I’m looking for (e.g. “Is there a leaner / smarter / more user-friendly way to do this?”). Then, give everyone time to silently review and write their feedback on sticky notes. That way, you ensure everyone, not only the loud people are heard. Too many sticky notes? Ask everyone to dot vote for their top 3.</p><p>After the individual review, give everyone the same amount of time to share their feedback with the group. As a designer, listen closely and do not defend your work. Close the session by thanking everyone for their contribution, as it is an integral part for the next design iteration.</p><figure><img alt="A simplified illustration of a tool for retrospectives. It contains columns for “happy”, “meh..” and “sad” and action items." src="https://cdn-images-1.medium.com/max/1024/1*0G-jSYSP8MWvZcYWIctMqQ.jpeg" /></figure><h4>Designer/engineer retrospectives</h4><p>Retrospectives are another well-known tool from agile software development. The whole team comes together after each iteration and reflects on how they can improve as a team. You can either make the engineer/designer workflow part of the team retro. Or you can introduce an additional, smaller retro, dedicated to this relationship.</p><p>Need <a href="https://www.funretrospectives.com/">inspiration for your retrospective</a>? Our team at VMware Pivotal Labs has built <a href="https://pivotal.github.io/postfacto//">postfacto</a>, a remote retro tool to self-host. It’s free to use for everyone. Whatever format you choose, it’s all about the action items. The more concrete actions you have, the better. Item per item, ask people to volunteer to be responsible. If no-one is happy to volunteer re-think or delete the action.</p><figure><img alt="Actual craftsmen tools (a measuring tape, pincers and a brush) are used to “build” a website. A mix of digital and analogue." src="https://cdn-images-1.medium.com/max/1024/1*DlO8lfHa9g-e7C2P1iTNxw.jpeg" /></figure><h3>2. Rethink your tools &amp; workflow</h3><p>Designers, have you heard of <a href="https://medium.com/swlh/what-is-dx-developer-experience-401a0e44a9d9">Developer Experience</a>? It means that you consider engineers as your users, too. If you think about it, it makes total sense. They’re the very first people that work with your design before a user even sees them. I’d recommend treating the developer experience like the user experience of your product. Try to improve the engineers’ experience working with your designs.</p><h4>Considerations</h4><p>Engineers need to be able to extract specs, behaviours, and assets from the design file. It’s worth considering a design tool that enables them to do this independently and conveniently. In addition to the regular design needs, consider the following:</p><h4>Working in the open, in real-time</h4><p>Can everyone from the team see the design progressing in real-time? Can they give feedback in a convenient way? Are the design files optimised to load fast for ‘lightweight contributors’ like engineers? A web view that takes ages to load will become utterly annoying if you need to work with it on a daily basis. Working in the open is equally significant for engineers. Everyone in the product team should have access to the pre-live environment to see new user stories come to life. They will want to give feedback here, too.</p><h4><strong>Translating design into specs</strong></h4><p>How easy is it for engineers to take specs and behaviours from designs and turn them into actual code? I recommend having design and specs live in one tool so that both always reflect the latest version.</p><p>“But how do I know which version of the design I should work on if they’re not officially handed over to me?” you might ask as an engineer. That’s a legit question, considering the designer might create multiple versions to try out what works best. What has worked well for teams in the past is to create a dedicated page in the design document that only contains designs that will not be touched (for now!). A ✅ ready for backlog page with all necessary viewports, states and notes on the behaviour. From this page, I like to create links to dedicated screens that I can attach to user stories. That way, updates are reflected in real-time.</p><h4>Assets, accessible for everyone</h4><p>“Could you please export X for me?”. A question no-one should ever have to ask a designer again. Great design tools make assets accessible for anyone to export. To enable everyone in the team to do this, I like to run a quick “how to export assets” tutorial as part of the tool and technology intro mentioned above.</p><h4>Global styles and names</h4><p>Defining global rules for your designs saves time. A design system defines how elements look and behave. So that you don‘t have to invent them from scratch for every new product under the same brand. Design systems are usually manifested in guidelines as well as a library with two versions. One for designers (e.g. a Figma or Sketch file). And one for engineers (e.g. a component library)</p><p>No matter if you have a component library at hand or not. Designers and engineers should get together and agree on naming conventions for the basics like type styles, colours etc. This will save engineers a lot of time later on.</p><figure><img alt="The logos of the three most common digital design tools “Figma”, “Sketch” and “Adobe XD” in a row." src="https://cdn-images-1.medium.com/max/1024/1*RbzCDGfrp0ud84B8eSacGw.jpeg" /><figcaption>Figma, Sketch &amp; Adobe XD, the top tools for digital design</figcaption></figure><h4>Ok, but which tool does all that?</h4><p>There are several great tools out there for digital design. As design tools evolve on a constant basis, don’t get too friendly with one.</p><p>Currently, the design tool closest to my heart is Figma. They have invested a lot in <a href="https://www.figma.com/best-practices/tips-for-a-better-developer-workflow/">making the designer/engineer collaboration smooth</a>. They’re promoting a mindset of moving the relationship “from handoff to handshake” (Thomas Lowry, Designer Advocate at Figma).</p><p>Sketch previously relied on third party apps like Abstract or Zeplin to provide design specs to engineers. They have introduced a new <a href="https://www.sketch.com/blog/2020/01/29/introducing-cloud-inspector-free-developer-handoff-in-the-browser/">developer handover function</a> in their 2020 cloud version though. Adobe XD also enables <a href="https://youtu.be/ygXaiKxCqQA">extracting design specs as css snipet</a>s.</p><figure><img alt="An illustration that contains icons for design, engineering and product management, symbolising a balanced software team." src="https://cdn-images-1.medium.com/max/1024/1*I39sowX-7C8GyKzrtNWFKA.jpeg" /></figure><h3>3. Rethink your ways of working</h3><p>Teams that have the freedom to take product decisions independently and share product ownership equally have the best chances to build useful digital products. Only when designers, engineers and product managers work together on eye-level are they able to bring the various perspectives and experiences necessary to drive innovation.</p><h4>Collaborate closely and share knowledge</h4><p>Cross-discipline collaboration and knowledge sharing are key. I recommend you either sit in the same space or are connected via slack/zoom and talk on a daily basis. Involve the whole team (yes — engineers too!) in key product steps like user research or ideation sessions. Everyone must be able to empathize with users and contribute to where the product is heading.</p><blockquote>For some engineers, taking part in user research might feel a bit weird at first, because it is widely considered a ‘design activity’. I always encourage fellow engineers to take part in user research though. It’s very powerful to see that what you’re building can actually affect people’s lives.</blockquote><p>Marco Garofalo, senior software engineer at VMware Pivotal Labs</p><h4>Share product ownership</h4><p>As a team, you are accountable for how well customers get the job done through the product you’re building. It’s not about how beautiful the design is, how many lines of codes you have written, features shipped or bugs fixed.</p><figure><img alt="Two people are doing an exaggeratedly large jigsaw on a massive  iPad. Symbolising “building” a digital product." src="https://cdn-images-1.medium.com/max/1024/1*urtsvpGHhfLUajdZ1zrbcA.jpeg" /></figure><p>These things only matter if they have a measurable positive impact on the product. Make sure you set goals that everyone understands and works towards. Measure the progress diligently and have it visible for everyone in the team at any time. You are all equally accountable for reaching them.</p><h4>Cherish both perspectives</h4><p>The value that it brings to it’s users is what makes or brakes a product and the designer is the person responsible for finding and framing this value. Designers often misinterpret the technical complexity of their ideas though. And that’s ok. Inviting engineers to the table from the start will help you come up with better ideas that are also feasible in a reasonable amount of time.</p><p>Build great software by equally valuing both perspectives. The designers’ impact to make it useful and the engineers’ impact to find a feasible way of building it.</p><h3>Build, measure, learn 🖤</h3><p>I believe the lean startup feedback cycle is not only helpful for building products but also for building teams. I’d encourage you to check your workflow and rituals regularly and thoroughly. I’ve adapted rituals and switched design tools so many times in my career, constantly on the lookout for which tool or format will enable the team to do their job even smoother in the future.</p><p><em>What has helped you to improve the engineer/designer relationship? I appreciate your constructive feedback and am happy to have a conversation about this topic. Find me on </em><a href="https://www.linkedin.com/in/antonia-horvath/"><em>LinkedIn</em></a><em>. A big thanks to Gagandeep Kaur, Marco Garofalo, Maximilian Zuleger, Tim Jarratt and Froso Ellina for sharing your thoughts and feedback. They form the basis of this article </em>💚</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*87gDfM49pt3wayUg" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=508e5f27134b" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-designers-and-engineers-can-collaborate-closer-and-build-better-digital-products-508e5f27134b">How designers and engineers can collaborate closer and build better digital products</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[Workshop & guide: define the tone of voice of your product]]></title>
            <link>https://uxdesign.cc/workshop-guide-define-the-tone-of-voice-of-your-product-e1a34f27af2c?source=rss-5dc5553f6d0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1a34f27af2c</guid>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Antonia Horvath]]></dc:creator>
            <pubDate>Tue, 15 Sep 2020 12:57:24 GMT</pubDate>
            <atom:updated>2020-11-18T21:29:32.701Z</atom:updated>
            <content:encoded><![CDATA[<h4>WORKSHOP</h4><h4><strong>A collaborative way to improve how your product communicates with its users</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z39ZNQwQeVUzoZZY5ip5GA.jpeg" /></figure><h3>Awaken your inner UX writer</h3><p>Product teams come in all shapes and forms, but they often don’t have a dedicated writer. Writing the text for products often happens on the fly and the result does not always support users best. This workshop is for designers, product managers, and anyone who wants to improve the way their product communicates with its users. You can run it anytime, it does assume that you already talked to your users though. You need to have a solid understanding of their goals, problems, and their context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x3pCaVvQqMT8VlOF4e54tw.jpeg" /></figure><h4>Why run it</h4><p>Outcome: You will have a product that people understand and ultimately want to use. Your product will sound human and will enable your users to get to their goal smoothly. You will know when this is the case because you will test it with real people and refine it.</p><p>The workshop emerged of exercises I successfully ran with different teams and clients over the past years. To innovate fast and keep the product cycle lean, teams at VMware Pivotal Labs are small. They only consist of 1 product designer, 1 product manager, and 1–2 engineers. This means that as a designer, I get to wear many hats. I facilitate teams to run user research, find users’ pain points, create solution hypotheses, and test them with users. We don’t have a dedicated user researcher, content strategist let alone a UX writer. Being responsible for the success of the product means we have to embody these roles though.</p><h4>Improve your users’ experience and save your team’s time</h4><p>This workshop has saved teams hours when writing because they knew how the product should sound in advance. More importantly: it has significantly improved the experience for users. I like to think of the workshop as a toolbox rather than a strict guide: take what works for you. Ready? Let’s unleash the inner UX writers of your team!</p><h4>Already have a tone of voice guide?</h4><p>That’s great! This workshop is still valuable to align your team and set them into the right state of mind for copywriting. You’ll receive feedback on how the guide works for your users. Share it at the beginning of the workshop when you share user evidence. ( 💬 <em>My favourite tone of voice guides are by </em><a href="https://monzo.com/tone-of-voice/"><em>Monzo</em></a><em>, </em><a href="https://www.gov.uk/guidance/content-design"><em>gov.uk</em></a><em>, and </em><a href="https://material.io/design/communication/writing.html#principles"><em>google material</em></a><em>).</em></p><h4>Have a writer on your team?</h4><p>If you are lucky enough to have a dedicated writer, that’s even better. No workshop can replace what a professional brings to your team. You can still run the workshop. Just as design, writing should not be done hidden away from the team anyway.</p><h3>Ready? Start preparing!</h3><p>Block about 2 hours of your team’s time. It’s key to run this workshop with the whole product team. Creating a product’s way of communication needs diverse views and healthy disagreements along the way. Plus: your team will be aligned on it. As the facilitator, it’s on you to use your team’s time wisely though, and prepare everything for a smooth workshop. (⏱<em> Need to refresh your remote facilitation skills? Check out </em><a href="https://www.mural.co/ebook"><em>this guide</em></a><em>)</em>.</p><h4>Set your team up for collaboration</h4><ul><li><strong>In-person:</strong> A large room with a screen to connect with your laptop, sticky notes, sharpies, and two large whiteboards. Bring your phone to <a href="https://medium.com/@tomomiq/how-to-get-the-workshop-photos-you-need-76ad338e68c3">take photos</a> and a timer to keep the time.</li><li><strong>Remote:</strong> A video conferencing tool<em> </em>and a digital whiteboard (<em>my personal favourites: </em><a href="https://miro.com/workshops/"><em>miro</em></a><em> and </em><a href="https://www.figma.com/collaboration/"><em>Figma</em></a><em>)</em>. Tidy your screen, you’ll be sharing it and ask everyone to switch on their camera, human touch matters.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ksFTZ9V0I7goacMxBbn8dg.jpeg" /></figure><h3>Free Template</h3><p>Save time and use this handy template: all exercises including homework. It’s free to download for everyone:</p><ul><li><a href="https://www.antonia-horvath.com/wp-content/uploads/2020/09/Tone-of-Voice-Workshop_V1-0.pdf">PDF workshop template</a></li><li><a href="https://miro.com/miroverse/category/newly-added/tone-of-voice-workshop?social=copy-link">Miro workshop template</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Plq9Bjyu8UqnI28mYsuohg.png" /></figure><h3>Step 1: Understand your users</h3><h4>Homework: Ask your team to listen to real users</h4><p><em>Plan 30 minutes for this activity in advance</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q7c3ExJZjXvmQqboPvokiQ.jpeg" /></figure><p>Ask your team to do a little upfront research: where do real people already talk about a similar topic? What words do they use? Good places to look for user conversations are online forums, social media sites, product reviews, or the comments section in the app store. Remember: this is not about other companies talking, but real user conversations. Everyone should bring at least 5 words or sentences to the workshop.</p><h4>Share user evidence</h4><p><em>Plan 30 minutes for this activity</em></p><p>Set your team in the right mindset: your users’. It is important that you have already talked to real users before you run this workshop. It should not rely on assumptions but user evidence — as should your product!</p><blockquote><em>At VMware Pivotal Labs, we run a 4–6-week discovery and framing phase 🗺 at the beginning of every product development. We make sure we get to know our users and we are solving the right problem for them. Sounds interesting? The free </em><a href="https://tanzu.vmware.com/design"><em>Design Guide</em></a><em> at the bottom of the page explains it all.</em></blockquote><p>Prepare what you’ve learned about your users and bring this info to the workshop. Think about using personas, user journeys, problem statements, etc. Choose what will spark your team’s empathy the most. You should be able to answer:</p><ul><li>Who are your users?</li><li>What problem are you solving for them?</li><li>What is their context?</li><li>What is their journey?</li><li>How do they talk about this topic?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cf2kvroIMYHaNV2OEALDWA.png" /></figure><h3><strong>Step 2: Define the personality</strong> of your product</h3><p><em>Plan 60 minutes for this activity</em></p><p>This is the ‘define’ part of the workshop. Make sure to schedule a short break for your team, they will need a clear head. Run the following exercises:</p><p>⇢ Exercise: Personality traits<br>⇢ Exercise: How is the product NOT?<br>⇢ Exercise: Write a dialogue &amp; play it<br>⇢ Exercise: Experiment with the tone</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rpm4yLkJD_fAwwupfte_KA.jpeg" /></figure><h4>Exercise: Personality traits</h4><p>Write down key personality traits your product had if it was a real person. They should match your users’ expectations and align with the existing tone of voice guidelines. Help your team by giving example <a href="https://www.nngroup.com/articles/tone-voice-words/">personality traits</a>.</p><p><strong>5 min:</strong> silent writing<br><strong>10 min:</strong> shareout with the team, ask clarifying questions, or disagree<br><strong>5 min:</strong> cluster similar ones, dot-vote on the most important ones</p><h4>Exercise: How is the product NOT?</h4><p>Write down adjectives the product will NOT embody. This will help you eliminate doubt when writing. They can turn out to be the opposite of the adjectives you set as personality traits, but they don’t have to.</p><p><strong>5 min:</strong> silent writing<br><strong>10 min:</strong> shareout with the team, ask clarifying questions, or disagree<br><strong>5 min:</strong> cluster similar ones, dot-vote on the most important ones</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_LX2yUWCHWuP_bhObmaNaw.jpeg" /></figure><h4>Exercise: Write a dialogue &amp; play it</h4><p>If your product was a real person: how would it help your users through the task? Split into groups of 2. Pick a crucial part of your product and write it as a dialogue between your user and a fellow human, tasked to solve the user’s problem. Pro tip: pretend your user does not understand any technical term. Let them ask for every word they don’t understand.<em> </em>This will help your team humanize tech language and jargon.</p><p>Get together and play the dialogues from each group. This will help you to see whether the conversation flows naturally and to have a bit of fun.</p><p><strong>10 min: </strong>write the dialogues in groups of 2<br><strong>20 min:</strong> play the dialogues from each group in front of the team<br><strong>5 min: </strong>capture the parts of the dialogues that felt the most human and why</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Snq9Wq93-Gw0GDVOq1-PiA.jpeg" /></figure><h4>Exercise: Experiment with the tone</h4><p>Individually, pick key parts of your product and write these in different styles. What are parts where you deliver a positive message, or a negative message? 🖋💡 <em>Make sure your team knows these </em><a href="https://uxplanet.org/16-rules-of-effective-ux-writing-2a20cf85fdbf"><em>16 rules of effective UX writing</em></a><em> before they run this exercise</em>. Dot-vote on the parts that you agree to be most valuable to test with real users. If you are unsure which route to go: test both.</p><p><strong>10 min: </strong>write the experiment, individually<br><strong>15 min: </strong>play back all copy experiments<br><strong>5 min: </strong>dot-vote on the parts you think your users will resonate with</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YDtFNbH6kkQWM2SX3g9_uw.png" /></figure><h3>Step 3: Ask for feedback</h3><p>After defining what you think your product should sound like it’s time to ask real users. This step is crucial before you proceed with writing/rewriting your product’s whole text. Otherwise, you might stick with an approach that does not speak to your users after all.</p><p>This step does not necessarily have to happen in the workshop itself. If you have the opportunity to schedule one or two user interviews directly after the workshop I would encourage you to do so. It’s a unique experience for your team to observe users react to the product.</p><p>How do you go about evaluating the tone of voice? I find Beant Kaur Dhillon’s <a href="https://uxdesign.cc/methods-to-evaluate-the-text-copy-or-content-of-your-product-a2d5d62d18de">methods to evaluate the text or content of your UI</a> very helpful. My favourite activity to get feedback on the tone of voice is:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pd_gvrp_sTPv-Q1BYtsArw.jpeg" /></figure><h4><strong>The highlight method</strong></h4><p>When you run 1:1 interviews, hand participants a printed version of your screens at the end of the session. Ask them to underline in light green what makes them feel confident about the product. Then ask them to underline in red what makes them feel less confident or confused. For remote interviews, miro &amp; co. offer great digital ways to highlight. Make sure you ask why participants feel this way. Combining these parts from each participant will help you understand where to improve — and why.</p><p>As your product emerges iteratively, your copy should, too. I recommend making the text of your product part of your regular research cycles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8PsfB5oOHHiWOaIslEkDYg.jpeg" /></figure><h4><strong>Task-based usability test for comprehension</strong></h4><p>If you need to understand whether the way you describe things enable your user to reach a certain goal, run a task-based usability test. As Sarah Richards put’s it in her <a href="https://youtu.be/UO0BIEkhsug">talk on content strategy</a>:</p><blockquote>Users shouldn’t read anything. They should understand.</blockquote><p>This method is the ultimate way to test if they understood. It is not only run to test the copy but also the visual interface. In a nutshell: you give the participant a task and observe how they go about it. Encourage participants to talk out loud. Ask them ‘why’-questions along the way, if they don’t naturally share what they think.</p><p>The great thing is: after running this workshop with your team, you’ve not only had valuable discussions and agreed on the tone of voice. The documentation is done at the same time. Capture the boards as PDFs or take photos of the exercises. They make excellent lean documentation of your tone of voice that already contains examples. (No-one wants to read 100 pages anyway.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IBryyq_eTHvlpL5Nr_1dlw.png" /></figure><p><em>What has helped your team to find the tone of voice of your product? What would you do differently? This workshop template is version 1.0 and I’d love the next version to incorporate your feedback. Find me on </em><a href="https://www.linkedin.com/in/antonia-horvath/"><em>LinkedIn</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*mGE3iGyx_w5PQGXj" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1a34f27af2c" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/workshop-guide-define-the-tone-of-voice-of-your-product-e1a34f27af2c">Workshop &amp; guide: define the tone of voice of your product</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>
    </channel>
</rss>