<?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 Hugo Ferreira on Medium]]></title>
        <description><![CDATA[Stories by Hugo Ferreira on Medium]]></description>
        <link>https://medium.com/@hugocf?source=rss-1d7d57245202------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*I6djEttn115fQHroX4Ehaw@2x.jpeg</url>
            <title>Stories by Hugo Ferreira on Medium</title>
            <link>https://medium.com/@hugocf?source=rss-1d7d57245202------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:49:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hugocf/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[Diversity and Inclusion: Reflections on Empathy, Hiring, and Transformation]]></title>
            <link>https://hugocf.medium.com/diversity-and-inclusion-reflections-on-empathy-hiring-and-transformation-1685ff8c1196?source=rss-1d7d57245202------2</link>
            <guid isPermaLink="false">https://medium.com/p/1685ff8c1196</guid>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[relationships]]></category>
            <dc:creator><![CDATA[Hugo Ferreira]]></dc:creator>
            <pubDate>Mon, 06 Nov 2023 00:00:47 GMT</pubDate>
            <atom:updated>2023-11-07T12:14:05.723Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="a mural depicting people gathered in a dimly lit room, showcasing unity and diversity" src="https://cdn-images-1.medium.com/max/1024/0*S8sKCNrGEB2qKcgi.jpg" /><figcaption><a href="https://unsplash.com/photos/3-men-and-2-women-smiling-1gh6oD6aDhs">Photo</a> by <a href="https://unsplash.com/@milesypea">Miles Peacock</a> on <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p>A few days ago, I had the privilege of participating in a group discussion about diversity and inclusion in the workplace. This insightful conversation was quite enriching and eye opening. It left me with a few things to ponder.</p><p>Here are 3 thoughts that emerged from my reflection on the conversation:</p><ul><li>Empathy is essential, as we may not grasp each others’ experiences</li><li>Recruitment needs companies to reveal themselves to overcome reluctance to change jobs</li><li>Meaningful change requires decision-makers with diverse perspectives, by becoming one</li></ul><h3>About empathy: “You don’t know what you don’t know”</h3><p>Empathy is fundamental to understand the experiences of others and overcome misunderstandings.</p><p>Let me illustrate this with a simple yet revealing story.</p><p>I have spent many years doing pair programming, where two people work together on the code implementation.</p><p>During a session with a female colleague, we encountered one of those tiresome captchas. The task was to “pick the dresses” from a list of images. My colleague selected two images, and as she was about to submit, I called out a bit too late “wait, you missed one!”</p><p>Sure enough, the captcha failed and we had to respond to a new question…</p><p>She rolled here eyes 🙄 and sighed with disappointment “oh, this was made by men, for sure. That one was not a dress, it was a blouse.” 🫤</p><p>Me calling out the “mistake” was in good faith, with intention to help a joint task. But it could be easy to perceive me as arrogant, trying to correct a minority who knows much more than me about the subject.</p><p>But we cannot know what we don’t know. We cannot see what we’re blind to. This scenario highlights the potential for misunderstandings and unintentional insensitivity. Had we not been working together for a long time and built a trusting relationship, I’m sure that would have been the case.</p><p>Only sharing our different mutual realities, with <a href="https://hugo.ferreira.cc/receiving-feedback">patience and understanding</a>, can we recognise our limitations.</p><h3>About recruitment: “Better the devil you know than the devil you don’t”</h3><p>Recruiting candidates from underrepresented groups can be an uphill battle.</p><p>It’s very common for companies to offer “referral bonus” for bringing colleagues into the recruitment pipeline.</p><p>In my experience, it takes me 10 times more effort to convince a female former colleague to apply for a new job opportunity than a male one. And with much less success in getting them to do so.</p><p>This highlights the reluctance to change that many individuals, particularly minorities, often feel.</p><p>Especially for employees from underrepresented groups, the switch to a new company can be daunting. In their current company, they’ve already established themselves at great cost. They feel comfortable navigating the existing challenges, and understand where the “dragons” lie.</p><p>The idea of having to start over that struggle and the possibility of having even more pronounced challenges, can be intimidating. This fear makes the idea of staying in a familiar, albeit imperfect, environment more appealing than venturing into the unknown.</p><p>To overcome that, companies must reveal what it’s like to work there, for real. This involves getting representative people to share what it is like for them to work in the company. To share both the positives and the areas that need improvement. To be straightforward about the reality of the work environment they foster.</p><p>This way, companies can make a stronger case for why it’s worth taking a leap into the unknown. By making it less “unknown”. By making the “devil you <em>don’t</em> know” seem less intimidating.</p><h3>About transformation: “A seat at the table”</h3><p>Real change in diversity and inclusion requires more than well-intentioned advice. It needs decision-making power.</p><p>For many years I have worked as a consultant. Among other things, we would do digital transformation for clients in software development. One of my former colleagues, now serving as a director of engineering in a product company, shared a valuable insight…</p><p>When he was in a consultant’s role, he could only offer guidance and suggestions and lacked the authority to enforce changes. Transformation was slow and full of mishaps, especially when leadership got misaligned.</p><p>In contrast, as a director of engineering, he could influence the teams’ incentives and structures in a direct manner. It led to quicker and more effective transformations than when we was not as empowered.</p><p>This same principle applies to diversity and inclusion efforts. We need people with diverse mindsets and perspectives sitting at the decision-making table. Otherwise, attempting to drive change from the sidelines will be much more frustrating and less effective.</p><p><em>Originally published at </em><a href="https://hugo.ferreira.cc/dei-reflections/"><em>https://hugo.ferreira.cc</em></a><em> on November 6, 2023.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1685ff8c1196" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navigating people: The antisocial guide to survive social gatherings]]></title>
            <link>https://hugocf.medium.com/navigating-people-the-antisocial-guide-to-survive-social-gatherings-1e6155d29c9d?source=rss-1d7d57245202------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e6155d29c9d</guid>
            <category><![CDATA[humor]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[introvert]]></category>
            <category><![CDATA[events]]></category>
            <category><![CDATA[guidelines]]></category>
            <dc:creator><![CDATA[Hugo Ferreira]]></dc:creator>
            <pubDate>Mon, 17 Jul 2023 05:27:42 GMT</pubDate>
            <atom:updated>2023-07-19T14:17:56.034Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>Guide to being invisible in a crowded party. The subtle art of staying present and mingling with people, at the same time absent without engaging, all without raising suspicion.</em></p><figure><img alt="pop art painting of a crowded office party with many people" src="https://cdn-images-1.medium.com/max/1024/1*c--3p6IT3eeuCPOvQq5zlQ.png" /><figcaption><a href="https://openai.com/dall-e"><em>DALL·E</em></a><em> </em>— <em>“pop art painting of a crowded office party with many people”</em></figcaption></figure><p>Parties and social gatherings with many people can be interesting… or a complete nightmare. Either for work or for family, there are times where we’re not up to it and yet, because we couldn’t get away, we must do attend.</p><p>Doesn’t matter what the reasons you have to lack enthusiasm on a particular social gathering. You can be a shy person. Or an introvert¹ that is needing alone time to recharge your batteries. Or even an extrovert² that isn’t keen on being with a particular group of people.</p><p><em>¹ See book </em><a href="https://www.goodreads.com/book/show/8520610-quiet"><em>Quiet: The Power of Introverts in a World That Can’t Stop Talking by Susan Cain | Goodreads</em></a></p><p><em>² See book </em><a href="https://www.goodreads.com/book/show/35712351-the-science-of-introverts-and-extroverts-and-everyone-in-between"><em>The Science of Introverts (And Extroverts and Everyone In-Between) by Peter Hollins | Goodreads</em></a></p><p>These tips can help you survive such situations…</p><p>First things to remember are the following guiding principles:</p><ul><li>Look busy</li><li>Avoid eye contact</li><li>Move around</li><li>Everyone cares about themselves</li></ul><p><strong><em>Look busy</em></strong></p><p>Most encounters in social gatherings happen when someone sees you idle. People don’t like to interrupt. So don’t be idle. Read a pamphlet, scribble notes somewhere, pretend to send a text. Your phone is an excellent tool to look busy and avoid people approaching you.</p><p><strong><em>Avoid eye contact</em></strong></p><p>At all costs! For real. This is the main invitation signal for people to approach you, even if not immediately. Allowing eye contact, nodding, and other common social rituals, are an open invitation. Close those doors.</p><p><strong><em>Move around</em></strong></p><p>A moving target is hard to hit, so always be moving. Be slow, pause for a bit but don’t stay for long in the same place. If you stay put, you’re creating opportunities for other to approach and engage. It’s harder to talk to someone who is going somewhere. People don’t like to interrupt and you can always say you’ll be right back.</p><p><strong><em>Everyone cares about themselves</em></strong></p><p>Since everyone’s focused on their own experience, no one cares what you are doing. People remember the interactions they’ve had, not the ones they didn’t. Who they talked to, not who they didn’t. This opens ample opportunities to survive a party by “walking between the raindrops”.</p><p>These guiding principles apply is many ways and to many situations. Here are some examples…</p><p><em>— In a walking around cocktail-style event —</em></p><p>If you see someone approaching, don’t try to identify who it is. Curiosity killed the cat and you’ll end up creating eye contact by accident. Turn away in a slow page, as if you didn’t notice and go look for something else to do, like choosing what to eat from some tray.</p><p>Never join an area of the table with lots of people on it. You might end up eating the less popular food but you need to prioritise avoiding people. That’s what’s more important!</p><p>Going to pick up some food but someone anticipates you and gets there first? Pretend something distracted you (a painting on the wall, a flower on a vase, your shoelaces) and buy time. Approach it again only after the person has left. Nothing opens the door to conversation like deciding who gets the last croquette.</p><p>Always have food with you. If someone is entering the danger zone looking to chat, start eating, look away and walk out. People tend to not interrupt if your eyes are on your plate and no one expects an answer from someone chewing.</p><p>Another option is having a drink with you. Doesn’t work so well (taking a sip is too fast compared to chewing a bite) but can be better than nothing.</p><p>Are you seeing movements for social games like “musical chairs” or, god forbid, a “conga line”? Great timing to step outside for a smoke, go look for the bathroom or answer some “urgent” messages on your phone.</p><p>If someone catches you on the way out and insists you join the “fun”, answer with “yes, I’ll be there right after”. Saying “no” will only make it worse. You become a challenge and will engage their evangelisation impulse. They’ll try to convince you with “it’s so much fun”, “you must join”, “it’s not the same without you”, etc.. Answering “yes, later” fulfils their desire to gather people around and buys you time. Time after which you’ll have no intention of following through, of course.</p><p>Don’t stay outside too long though. If you abuse it, people will worry where you are and be more motivated to approach you asking if everything is ok.</p><p><em>— In a sitting down conference-style event —</em></p><p>Joining a restaurant where you’ll have a group meal together? Make sure to be in the middle of the pack. This way there’s already enough people seated when you join the table to let you read the room. Yet, there will still be enough seats available to let you choose the most pleasant or quiet people to sit next to. Don’t be the first ones to sit since you’ll have no control who sits next to you and it’s awkward to move away once you’re seated. Also, don’t be the last ones to sit since all the good places will be gone and you’re now stuck with the group’s leftovers.</p><p>Is it a place where everyone’s lined up in chairs, like in a cinema, for a talk or to watch some family holiday pictures? While everyone is setting up things, go grab a beer or sneak into the toilet. Let others occupy the seats first. When you’re back, skip the chairs and stand at the very back against the wall. You’ll be safe from happenstance conversation about what you’re watching.</p><p>Does someone take a wall spot too close to you? Be discrete but be quick (as if you’ve just realised something) and go pick something else to eat or drink. Then stay around that area and don’t return to where you were on the wall. Remember, it’s more important <em>where</em> (how isolated) the place you’ve pick something from is, than what you picked up.</p><p>Sitting down is risky because it affects your mobility but if you want to sit, avoid clusters of empty chairs. An empty cluster might be appealing because there is no one there. But since there are so many free seats, it’s very risky. Someone outside of your control can sit right beside you and start a conversation.</p><p>Choose a chair at the end of a line and pull it way from the others if they are movable. Never sit in chairs in the middle of a row: too many chances to get people on either side of them.</p><p>If you can stomach the noise of children, and there are some around, pick a chair next to them. That keep most of the other people at bay, especially guys. If you sense someone approaching, look at what the children are doing as if you’re interested. Give a faint smile and focus on whatever they’re doing or chatting about. This will send a message of “being occupied” and people won’t want to bother you.</p><p><em>— At the end of the event —</em></p><p>Never be the first one to leave the party. You’d have to say goodbye to everyone and explain each time why you’re leaving “so early”. Plus, you’ll have to deal with all the “ooh, already?” and “why don’t you stay longer?” departure rituals.</p><p>Pay attention to the first people to leave, and take a “ride” with them. Let them take the blunt of the departure ceremonies. Wait for those to finish and the ones staying get tired and give up trying to convince them. Then you can nudge the hosts with a shrugging “I need to leave as well 🤷” and walkout together with the first people. Timing for this is critical but the resistance will now be minimal. You can finally take yourself out of there, into freedom.</p><p>Being invisible in a crowded party is a <em>subtle art</em>. Present and mingling with people, while absent without engaging, and without raising suspicion.</p><p>Hope these guiding principles and tips can help you survive such places without harm.</p><p>Take care.</p><p><em>And realise this is a work of fiction, doesn’t necessarily have any parallels with reality… kinda</em> 😏</p><figure><img alt="animated gif with a character looking surprised, the other responding with “I’m kidding” and making a serious face right after" src="https://cdn-images-1.medium.com/max/400/1*V6NwHENy54GjpZbCK13fVw.gif" /><figcaption><a href="https://giphy.com/gifs/fx-on-hulu-im-kidding-POlRuKwo6HEnZsp3DQ">via GIPHY</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e6155d29c9d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Speaking or communicating? Easily recall how to give good feedback]]></title>
            <link>https://hugocf.medium.com/speaking-or-communicating-easily-recall-how-to-give-good-feedback-5c3576424533?source=rss-1d7d57245202------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c3576424533</guid>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[observing]]></category>
            <category><![CDATA[guidelines]]></category>
            <category><![CDATA[asking]]></category>
            <category><![CDATA[behaviour]]></category>
            <dc:creator><![CDATA[Hugo Ferreira]]></dc:creator>
            <pubDate>Tue, 13 Jun 2023 04:16:07 GMT</pubDate>
            <atom:updated>2024-05-19T02:34:03.456Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>Talking or speaking? Easily recall how to give good feedback</h3><p><em>There are many guidelines on how to structure feedback but human nature is quite common. A simple mnemonic will help your recall your favourite framework when it matters the most — talk about what you “observe”, its “impact” and then “ask”.</em></p><p>Negative feedback is never easy to impart on others. Emotions and ego tend to trigger defensive behaviour. This, in turn, creates friction and noise in the communication.</p><p>There are several structured ways to help us shape our message for others in a way that helps people receive it well. Unfortunately, some of them are useless and even disrespectful (e.g. the <a href="https://www.forbes.com/sites/forbeshumanresourcescouncil/2022/04/25/why-the-sandwich-approach-to-criticism-is-terrible-advice/">“shit” sandwich</a>, and <a href="http://blog.idonethis.com/sandwich-feedback-performance-management/">others</a>).</p><p>The following frameworks are ones that I’ve found more useful and helpful.</p><p><a href="https://en.wikipedia.org/wiki/Nonviolent_Communication"><strong>NVC — Nonviolent Communication</strong></a> <em>by Marshall Rosenberg (</em><a href="https://www.cnvc.org/"><em>CNVC</em></a><em>)</em></p><p>An approach to communication based on principles of nonviolence. Was developed by clinical psychologist Marshall Rosenberg beginning in the 1960s and 1970s.</p><p>This is a very popular approach, with lots of books, articles and training going around for it.</p><ul><li><strong>Observation</strong> — Facts we are seeing, hearing, or touching, as distinct from our evaluation of them</li><li><strong>Feelings</strong> — Emotions or sensations, free of thought and story</li><li><strong>Needs</strong> — Universal human needs, as distinct from particular strategies for meeting those needs</li><li><strong>Requests</strong> — Distinguished from demands in that one is open to hearing a response of “no” without this triggering an attempt to force the matter</li></ul><p><a href="https://www.ccl.org/articles/leading-effectively-articles/closing-the-gap-between-intent-vs-impact-sbii/"><strong>SBI+I — Situation-Behavior-Impact + Intent</strong></a> <em>by Center for Creative Leadership (</em><a href="https://www.ccl.org/"><em>CCL</em></a><em>)</em></p><p>A more niche approach written in 2022, from a nonprofit organisation focused on leadership. Their goal is improving the understanding, practice, and development of leadership.</p><ul><li><strong>Situation</strong> — Clarify and describe what happened, when and where</li><li><strong>Behavior</strong> — Describe the observable behaviour, without assuming what the person was thinking</li><li><strong>Impact</strong> — Explain what you thought or felt in reaction to the behavior</li><li><strong>Intent</strong> — Inquire about their original intentions, to clarify the gap between intent vs. impact</li></ul><p><a href="https://www.radicalcandor.com/core-feedback/"><strong>CORE — Context, Observation, Result, nExt stEps</strong></a> <em>by Kim Scott (</em><a href="https://www.radicalcandor.com/the-book/"><em>Radical Candor</em></a><em> book)</em></p><p>From the author of a best seller in the business category, published in 2017. This method makes sure you’re not criticising someone’s personality when delivering negative feedback (or even praise).</p><ul><li><strong>Context</strong> — Cite the specific situation</li><li><strong>Observation</strong> — Describe what was said or done</li><li><strong>Result</strong> — What is the most meaningful consequence to you and to them?</li><li><strong>nExt stEps</strong> — What are the expected next steps?</li></ul><p><strong>A simple mnemonic to remember</strong></p><p>As you can see, there’s plenty to study and choose from. I recommend you look through the methods in more detail and see what you can relate with more. Practice it whenever you have a chance…</p><p>In reality though, situations that bother you and demand these tools happen in real time. Quite often, the timing to say something is in the moment and it’s hard to remember all the above rules.</p><p>Unless you’ve practiced enough for these concepts to become <a href="https://en.wikipedia.org/wiki/Four_stages_of_competence">unconscious competence</a> (i.e. have an intuitive level of familiarity with these tools), it can be hard to remember how to say things on the spot.</p><p>While still in the <a href="https://en.wikipedia.org/wiki/Four_stages_of_competence">conscious competence</a> phase, this <strong>simple mnemonic</strong> has helped me recall how to structure my feedback:</p><ul><li>👁️ … talk about what you <strong>Observe</strong></li><li>🔨 … talk about what was the <strong>Impact</strong></li><li>❓ … then <strong>Ask</strong> a question as follow up</li></ul><p>This is because there’s a natural overlap between the methods. They emphasise different parts of the conversation. The authors chose different terms for similar underlying principles. But human nature is constant.</p><figure><img alt="comparison table between the different feedback frameworks (NVC, SBI+I, CORE) to highlight how each one maps to the “Observe”, “Impact” and “Ask” principles" src="https://cdn-images-1.medium.com/max/1024/1*n2CgWFXnodZKdAqcG1GVOA.png" /></figure><figure><img alt="an eye, a hammer and question mark, side-by-side next to each other in graffiti style" src="https://cdn-images-1.medium.com/max/1024/1*tKU9JS8Mm006zQ5RZJWQPA.jpeg" /><figcaption><a href="https://www.bing.com/images/create"><em>Image Creator from Microsoft Bing</em></a><em> — “an eye, a hammer and question mark, side-by-side in random painting art styles”</em></figcaption></figure><p>One more thing…</p><p>Beyond the scope of “negative feedback”, we are sometimes asked to provide general feedback about other people. Could be about a new hire during their probation period. Could be preparing for a “<a href="https://medium.com/@joshproduct/speedback-de-stigmatise-feedback-with-speed-dating-principles-4708d493fb63">speedback</a>” session with team members. Could be many other scenarios.</p><p>What should we say? What can we talk about?</p><p>An easy way to identify topics to talk about is to brainstorm using the <strong>“start, stop, continue”</strong> pattern:</p><ul><li><strong>Start</strong> — Think whether there are things the person should do, which they are not currently doing</li><li><strong>Stop</strong> — Think if you can see anything that the person should not do anymore</li><li><strong>Continue</strong> — Think about if some of the person’s current behaviours they should maintain</li></ul><p>All this is, is a guide to <em>think</em> about different “things to say”:</p><ul><li>You don’t need to be exhaustive in covering the 3 aspects</li><li>You can have several things to say for the same aspect</li><li>You don’t have to follow this specific order</li><li>You can mix and match different aspects, as it feels more natural to you</li></ul><p>Happy feedback 🙂</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c3576424533" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“The Business” considered harmful]]></title>
            <link>https://hugocf.medium.com/the-business-considered-harmful-6d8b425929a7?source=rss-1d7d57245202------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d8b425929a7</guid>
            <category><![CDATA[people]]></category>
            <category><![CDATA[jargon]]></category>
            <category><![CDATA[corporations]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Hugo Ferreira]]></dc:creator>
            <pubDate>Mon, 05 Jun 2023 02:10:58 GMT</pubDate>
            <atom:updated>2023-07-23T17:32:33.305Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>Draw back the curtain to reveal the real people behind it</h4><figure><img alt="DALL·E AI generated photo of several silhouette shadows behind a curtain" src="https://cdn-images-1.medium.com/max/1024/1*RqHwZWnP7nJ9qPs4fBei0Q.png" /><figcaption><a href="https://openai.com/dall-e"><em>DALL·E</em></a><em> — “photo realistic several silhouette shadows behind a curtain”</em></figcaption></figure><p>Few <a href="https://en.wikipedia.org/wiki/Corporate_jargon">corporate speak</a> expressions annoy me in as much as these 2 words: 😬</p><blockquote>“The business”</blockquote><p>This <em>is</em> a pet peeve of mine, for sure. But beyond that, it’s important we stop covering decision makers behind “The Business” curtain.</p><p>There is no such entity called “The Business” in companies.</p><p>“The Business” isn’t a job function or role or group of people.</p><p>“The Business” is everyone in the company.</p><p>So what is happening in reality, behind “The Business” curtain?</p><p>It‘s quite frequent that “The Business” is shorthand for “I’m only doing what someone asked me”.</p><p>Quite often it means the request came through a chain of so many people, no one knows anymore who asked it and what for.</p><p>Behind this expression there’s <strong>always people</strong>: <em>someone</em> who wants something <em>for a reason</em>. They need a problem solved, an opportunity to explore, an experiment to try.</p><blockquote><em>People are the link to context.</em></blockquote><p>To be effective in our jobs, we must know who are the people at the source of a decision or request. It’s the only way to sidestep all the “<a href="https://en.wikipedia.org/w/index.php?title=Broken_telephone">broken telephone</a>” effect that exists in any chain of requests.</p><p>Being able to ask clarifying questions to the source is essential to get an accurate context. And as we know, <a href="https://hugocf.medium.com/context-is-everything-even-when-you-dont-see-it-8d56715c7c32">context is everything</a> for the decisions that affect us and requests we’re asked to fulfil.</p><p>Next time someone says “The Business” asked, decided, demanded, etc. follow these 3 simple steps:</p><ol><li>Ask “<strong>Who</strong> was it that did that?”</li><li>If you didn’t get a real person, repeat the question applied to that answer</li><li>Continue as often as needed until you get to <em>names</em> of real people</li></ol><p>Well, it’s actually only 1 step 🙂 — Keep asking who’s the person until generic groups or terms becomes actual people names.</p><p>It never ceases to surprise me how hard it is sometimes to get to the names of the people who are making some decisions. It gets worse the larger the company is.</p><p>Be prepared for the possibility of some interactions to become something like this:</p><blockquote>X: “The Business” decided to use Foo for everything<br>Me: Who made that decision?<br>X: It was at the board level<br>Me: Who in the board was deciding it?<br>X: Oh, that was done in the steering committee<br>Me: And who’s part of the steering committee?<br>X: VPs, C-level and our main stakeholders<br>Me: Who are those stakeholders?<br>X: Jane from Bar and John from Baz<br>Me: And who from the VPs and C-level belongs in the committed?<br>X: VP of Tech and VP of Product, and now the CFO and CEO as well<br>Me: Ok, thanks [*sigh* I guess I can get those last titles from the org chart now]</blockquote><p>Now we know who to ask for clarification on the rationale behind the Foo decision. I’d bet that decision more nuanced than the “use Foo for <em>everything</em>” you got at the start.</p><p><strong>Why go through all this trouble?</strong></p><p>Because <a href="https://hugocf.medium.com/context-is-everything-even-when-you-dont-see-it-8d56715c7c32">context is everything</a>…<br>Because people are the link to context…</p><p>So, remember to always ask:</p><blockquote><strong>Who</strong> is “The Business”?</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d8b425929a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mental model for Booleans vs Enumerates]]></title>
            <link>https://hugocf.medium.com/mental-model-for-booleans-vs-enumerates-df70d917fb41?source=rss-1d7d57245202------2</link>
            <guid isPermaLink="false">https://medium.com/p/df70d917fb41</guid>
            <category><![CDATA[data-type]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[criterion]]></category>
            <category><![CDATA[comparison]]></category>
            <dc:creator><![CDATA[Hugo Ferreira]]></dc:creator>
            <pubDate>Mon, 15 May 2023 11:08:02 GMT</pubDate>
            <atom:updated>2023-07-23T17:39:27.710Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>Choosing between Booleans and Enumerates when the options are binary</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Ws3e4gCSi6x0YdBr-V4w5w.jpeg" /></figure><p>In programming, <a href="https://en.wikipedia.org/wiki/Boolean_data_type">Booleans</a> and <a href="https://en.wikipedia.org/wiki/Enumerated_type">Enumerates</a> are common data types to represent the concept of “choice”.</p><p>When there are several things to choose from, the Enumerate is the only one to support it, so that’s clear.</p><p>But what about when you have two things to choose from? There might be some confusion between both data types since either of them supports handling binary choices.</p><p>The confusion arrises in particular when you want to add the choice of a new behaviour, on top of an existing one. For example:</p><blockquote>We’re torn between adding a boolean called supportsBarMode or having a more descriptive model with an enum that lists all the supported options [FooMode, BarMode].</blockquote><blockquote>The enum solution feels a bit <a href="https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it">YAGNI</a> at the moment, but we&#39;re open to suggestions. What do you think?</blockquote><p>Don’t tie yourself to whether you’ll need more options in the future or not. Instead, look at how you can <em>communicate intent</em> the best way possible.</p><p>The mental model for encoding these binary choices is to identify which of these scenarios we are in:</p><ul><li><strong>Switch something on/off</strong> — e.g. enabling or disabling an extra option</li><li><strong>Select mode of operation</strong> — e.g. choosing between ways of doing things</li></ul><h4><strong>Boolean = </strong>Switch something on/off</h4><figure><img alt="red switch with a 1 on top, a 0 on the bottom, and turned to the 1 position" src="https://cdn-images-1.medium.com/max/300/1*3krH8wr5LqAipijlT5NNhQ.jpeg" /><figcaption>On-Off Switch</figcaption></figure><p>A Boolean fits the 1st scenario. A light switch is either on (have light) or off (don’t have light). When it’s off, there’s no “default alternative behaviour” associated with it: the thing we want to turn on just isn’t there.</p><h4><strong>Enumerate</strong> <strong>= </strong>Select mode of operation</h4><figure><img alt="a coaxial selector with the input on the bottom, an A and B position of top, and the central nob set to the A position" src="https://cdn-images-1.medium.com/max/300/1*OtDrWO6ngc-RNGj3ST4gBg.jpeg" /><figcaption>A/B Selector</figcaption></figure><p>An Enumerate fits the 2nd scenario. A coaxial selector is either on position A or on position B . It lets you choose between two options. There is a clear meaning associated with each position.</p><p>In the example above, the Enumerate data type would be the right choice.</p><blockquote>… an enum that lists all the supported options [<em>FooMode, BarMode</em>]</blockquote><p>Even if we never add other options to that Enumerate, it is not a case of <a href="https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it">YAGNI</a>. The Enumerate could have only 2 options forever that it would still communicate the correct intent.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df70d917fb41" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pairing Reviews: Bridging the gap between pair programming and code reviews]]></title>
            <link>https://hugocf.medium.com/pairing-reviews-bridging-the-gap-between-pair-programming-and-code-reviews-781a1c6ba4bc?source=rss-1d7d57245202------2</link>
            <guid isPermaLink="false">https://medium.com/p/781a1c6ba4bc</guid>
            <category><![CDATA[pair-programming]]></category>
            <category><![CDATA[code-review]]></category>
            <dc:creator><![CDATA[Hugo Ferreira]]></dc:creator>
            <pubDate>Mon, 08 May 2023 22:59:29 GMT</pubDate>
            <atom:updated>2023-07-23T17:45:15.036Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>Paring technical sessions for kick-offs and reviews can be a good alternative for programmers frustrated with async code reviews and unhappy with continuous pair programming.</h4><figure><img alt="a pair of glasses sitting on a table facing two blurred screens filled with code" src="https://cdn-images-1.medium.com/max/1024/1*QM4AIEtMb0Z9Wj2TqLV1Tw.jpeg" /><figcaption><a href="https://unsplash.com/photos/w7ZyuGYNpRQ"><em>Photo</em></a><em> by </em><a href="https://unsplash.com/@ikukevk"><em>Kevin Ku</em></a><em> on </em><a href="https://unsplash.com/"><em>Unsplash</em></a></figcaption></figure><h3>Hugo Ferreira on Twitter: &quot;When the time for code review comes it&#39;s a) obvious who should review it, b) easier to review because people have the context already, c) quicker to review because it becomes more focused on details and easier things to correct / Twitter&quot;</h3><p>When the time for code review comes it&#39;s a) obvious who should review it, b) easier to review because people have the context already, c) quicker to review because it becomes more focused on details and easier things to correct</p><p>Over the years I’ve worked in many software delivery teams under a multitude of working formats:</p><ul><li>Sometimes working collocated, others as a remote satellite worker, to completely distributed¹</li><li>With people having very different skill sets and levels of experience²</li><li>Dealing with many different geographical and cultural backgrounds³</li></ul><p><em>¹ See post section </em><a href="https://www.martinfowler.com/articles/remote-or-co-located.html#TheManyShadesOfRemoteness"><em>The Many Shades of Remoteness</em></a><em> by </em><a href="https://www.martinfowler.com/aboutMe.html"><em>Martin Fowler</em></a><em>.</em><br><em>² See </em><a href="https://staffeng.com/guides/overview-overview/"><em>Guides for reaching Staff-plus engineering roles</em></a><em> by </em><a href="https://lethain.com/about/"><em>Will Larson</em></a><em>.</em><br><em>³ See book </em><a href="https://www.goodreads.com/book/show/22085568-the-culture-map"><em>The Culture Map</em></a><em> by </em><a href="https://erinmeyer.com/about/"><em>Erin Meyer</em></a><em>.</em></p><p>Under very different types of pressures,</p><ul><li>Greenfield projects with strict deadlines</li><li>Rescuing huge legacy codebases</li><li>Long running product development</li></ul><p>All these experiences forced me to reassess some of my long held assumptions about ways of working.</p><p>In particular, the dichotomy between <strong>pair programming</strong> and <strong>async code reviews</strong>⁴ started to feel too strict and “religious” at times. There are many situations where people don’t want the burden of lengthy code reviews for which they lack context. Many other cases where continuous pair programming is not even possible (e.g. large timezone differences or appalling internet connections).</p><p><em>⁴ See the </em><a href="https://docs.github.com/en/get-started/quickstart/github-flow"><em>GitHub flow</em></a><em> pull request (PR) model, popularised by GitHub.</em></p><h3>Pair programming is not for everyone</h3><figure><img alt="two men with their backs turned to the camera coding together in a laptop with two other large screens displaying code" src="https://cdn-images-1.medium.com/max/1024/1*oYAEIgJNXXTudl2uH7rWcA.jpeg" /><figcaption><a href="https://unsplash.com/photos/fSWOVc3e06w">Photo</a> by <a href="https://unsplash.com/@alvarordesign">Alvaro Reyes</a> on <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p>This story started during a project with a tight 3 month deadline. We had to be very strict with our scope and be fast on how we ensured quality in the delivery.</p><p>All members had years of exposure to pair programming, so they chose to work like that, as a way to deliver faster. By bouncing ideas and reviewing code on-the-fly, we could evolve the code base as a team in an organic way.</p><p>One colleague was struggling though. They couldn’t adjust to the format under this particular context and delivery pressures.</p><p>Either due to personality traits⁵ or personal preferences⁶, whatever it was at the core, the team felt the need to embrace it and make some adjustments on the way we worked.</p><p><em>⁵ For example, some people have a way of “thinking with their fingers” where they need to do exploratory code refactoring. Others prefer to do a more strict TDD style, write test cases first and let production code evolve in a fluid way. There are those who need conceptual thinking and brainstorming before writing any code.</em></p><p><em>⁶ For example, listening to music or chasing “the zone” are things that you cannot do in pairing.</em></p><p>There are many ways around personal differences to make pair programming work. In fact, this is a common practice in pairing since no two people are alike. But sometimes those differences are irreconcilable and this was such a case.</p><p>We all agreed that several people looking at the same piece of code was essential to ensure code quality. So, our initial change was to use the most common alternative in the industry: <strong>async code reviews</strong>.</p><h3>The problems we faced with async code reviews</h3><p>Code reviews are easy, right?</p><ol><li>The team kicks off a story</li><li>A developer works on it on their own until development is “done”</li><li>Some team members review it</li></ol><p>and then… well, then what? Then that’s where our problems started.</p><p>Setting aside how hard it was for a reviewer to get up to speed with the code to review, due to the lack of detailed context…</p><p>Setting aside that, since it required quite a significant mental effort to do the above, finding the time to review was also a problem…</p><p>Once a code review was in though, the type of issues we caught would fall under 3 categories:</p><ol><li><strong>Finishes and polish</strong><br>• Stuff that’s simple and easy to change: better names, move something around, extract a method, inline a variable, etc.<br>• It was easy for the author and reviewer(s) to discuss and align these changes. It improves the code base a little and the cost is very low.<br>• ✅ Small benefit<br>• ⛔️ Small cost</li><li><strong>Marginal better structure</strong><br>• The change to the codebase is not wrong or unworkable. We could improve something and bring marginal benefits but it is not trivial to change at this stage.<br>• These changes ended up not happening. They were hard to justify at this stage with the <em>perception</em> was that the benefits were small. It was also hard to overcome the arguments of “but it’s already working”.<br>• ✅ Small benefit<br>• ⛔️ ⛔️ Medium cost</li><li><strong>Wrong implementation approach</strong><br>• This is where something was “lost in translation” completely. This might not be that frequent but we’ve seen it happen enough times to hate the experience.<br>• Catching severe misconceptions in the implementation approach at such a later stage has a very high cost. This means lots of rework, lost time, and waste. Regardless, we must do it.<br>• ✅ ✅ ✅ Large benefit<br>• ⛔️ ⛔️ ⛔️ Large cost</li></ol><p>The first category of issues (#1) is a no brainer and hardly a contentious point. This is an obvious benefit of code reviews to improve code quality.</p><p>The last category (#3) is very painful and quite a blow to the team. To throw away and rework all the investment at such a late stage is painful. It’s a necessary evil that everyone can agree and, again, a clear benefit of code reviews.</p><p>The biggest problem and what concerns us the most were the middle category (#2) of issues. These missed opportunities lie <em>only</em> on the fact that the team caught these issues <em>too late</em>.</p><p>There reason these changes are so important relate with the <a href="https://en.wikipedia.org/wiki/Broken_windows_theory">broken windows theory</a>. There’s the <em>perception</em> that these benefits are marginal, but they compound over time. They end up becoming a tangled web inaccurate abstractions, faulty approaches and bad code. These are not straight forward to solve, especially in a time constrained project.</p><p><strong>Catching issues too late</strong> is a good summary of the key problems we faced with code reviews.</p><p>Pair programming gives realtime feedback, since discussions happen <em>as people write the code</em>. Being used to that, all the waste illustrated above was more that the teams could handle.</p><h3>Our guiding principles</h3><p>When we have conflict between people due to <em>practices we deem fundamental</em>, where do we draw the line?</p><p>All this adds tension and complexity to our ways of working. Working through these differences and find effective strategies, requires <strong>compassion</strong> between team members.</p><p>More than specific <em>practices</em>, our focus should be in the <em>immutable principles</em> behind those practices. They set the stage and give context for the team’s choices.</p><p>These are the key foundational principles that were guiding our directions:</p><ol><li><strong>Team-based ownership of the entire delivery</strong><br>• At the technical level, this means more than one person understanding and caring for each piece of code written.<br>• Not only the technical aspects (codebase, pipelines, observability) but also including roadmap, backlog, priorities, etc.<br>• Several people together think better than a single one. Over time, this reflects in an increased quality of the code base.</li><li><strong>Include all the members of the team as equals</strong><br>• It is usually said that whenever someone leaves or joins a team, it becomes a new team altogether.<br>• Being a cohesive team implies welcoming the participation and voices of all its members.<br>• Seek for “consent” and “acceptance” from the group, rather than aiming for the elusive “consensus” or “agreement” from everyone.</li></ol><h3>A positive mix between both approaches</h3><blockquote><em>I think both techniques are clearly a net </em>good<em>, although they each have their particular pros and cons.</em></blockquote><blockquote><em>I don’t think it’s a matter of picking one over the other so much as </em><strong><em>ensuring you have more than one pair of eyes looking at the code you’ve written</em></strong></blockquote><blockquote><em>— </em><a href="https://blog.codinghorror.com/about-me/"><em>Jeff Atwood</em></a><em> in </em><a href="https://blog.codinghorror.com/pair-programming-vs-code-reviews/"><em>Pair Programming vs. Code Reviews</em></a></blockquote><p>How could we leverage the benefits of pair programming and avoid the flaws of async code reviews? Something that incorporates some of the learnings and key strengths of both approaches:</p><ul><li>Develop code with collaboration built-in from the start</li><li>Avoid building a wasteful inventory of code changes pending review</li><li>Make the review experience engaging and straightforward, with reduced cognitive load (as possible)</li></ul><p>So we started doing what you can call a <strong>“sandwich”</strong> of both approaches:</p><ul><li><strong>Start</strong> with a pair programming session for <strong>technical kick-off</strong> and code design/exploration</li><li><strong>Continue</strong> with individual <strong>async development</strong> and implementation</li><li><strong>End</strong> with a pair programming session for <strong>code review</strong> and discussion</li></ul><p>In more detail, the story development workflow became:</p><ol><li><strong>Story kick-off with all the team’s disciplines⁷ involved (UX + PO + QA + DEVs)<br></strong>• Here we shape the user story acceptance criteria and scenarios.</li><li><strong>Once it’s over, the DEVs (a pair or trio) would stay on for a technical kick-off<br></strong>• Here they discuss the actual technical design and implementation approaches<br>• This implies going over the code base and exploring alternatives<br>• Discuss modelling options (e.g. extend a class vs extract an interface), explore potential new patterns or structural refactoring, etc.</li><li><strong>The solo DEV would move on and do the development as discussed with their colleagues in #2</strong></li><li><strong>Once it’s development finishes, it’s time for the code review<br></strong>• It’s now trivial to identify <em>who</em> should join the code review: those that were in the technical discussion in step #2<br>• They join the DEV implementing to walkthrough the code changes and discuss them<br>• Depending if the changes are quite simple, if it remains aligned with the initial direction, then this could an async step</li></ol><p><em>⁷ Some people call this “3 amigos” but this is more like “all the amigos”. Every discipline in the team joins to discuss it together.</em></p><p>Notice that step #3 implies a good level of maturity from the solo DEV implementing the story. They need to reassemble with the people from the pairing kick-off in step #2 whenever the direction diverges:</p><ul><li>They face a roadblock or start entering a rabbit hole</li><li>They realise the initial ideas are no longer valid with new discoveries</li><li>The direction becomes impractical or turns out more complex than expected</li></ul><p>The main takeaway is that the team must discuss technical approaches together, and the earlier this happens, the better. This approach promotes those discussions to happen much earlier than in async code review.</p><p><strong>So, does this mean more meetings?</strong></p><p>No, definitely not. These are work sessions. You start, work together, and finish when the group understands they’re in a good place of understanding. It takes 30 min or several half days, depending on the complexity of the work at hand.</p><p><strong>Then it’s only for complex stories?</strong></p><p>Not at all. Do it for <em>every</em> user story, no matter how simple it seems at first.</p><p>While complex stories need to involve the entire DEV team, simpler stories should only need one other developer. And if the story turns out to be very simple, them it’ll take only a few minutes and you’re done.</p><p>The most important factor is to build the habit muscle of doing it always. This will help you catch and avoid several blind spots and assumptions. Sometimes behind that seems simple hides a crucial decision when you start trading ideas with others.</p><p><strong>Does splitting up and coming together increase Work in Progress (WIP)?<br></strong><em>(by </em><a href="https://beny23.github.io/about/"><em>Gerald Benischke</em></a><em>)</em></p><p>It’s the same as if you’d be in an “async code review” model where each dev picks up a story individually.</p><p>If you switched an entire team doing pair programming into this model, then yes, WIP would increase since you’d now have single devs coding stories instead of pairs.</p><p>In our case though, we applied it only to the single dev mentioned in the story above. The two other pairs continued to do pair programming, so there was no significant change in WIP.</p><h3>Benefits of the “pairing code reviews” approach</h3><p>To start with, the focus of the reviews became all about the “1. Finishes and polish”. Easy refactoring, practical renames, etc. which code reviews well suited for stayed.</p><p>The problems with “2. Marginal better structure” and “3. Wrong implementation approach” disappeared from the reviews. They’d either be all discussed at the start or along the way, close to when they became relevant.</p><p>Pairing at the time of code review also helped with the fluidity of the review. Since all had context, it was much easier to discuss and change the code as we went along. Much better than dealing with a lengthy back and forth of asynchronous interruptions.</p><p>It lifted the weight of constant pairing, for those who had difficulty with it or which the timezones did not permit. Because it happened only at clear distinct milestones in the development lifecycle,</p><p>Also, it removed the feeling a being “evaluated”. It added a more collaborative mindset of working together, of building something together.</p><p><strong>There are no silver bullets for most things in life. Everything is a tradeoff. With this, you have one more useful approach to consider when your context needs it.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=781a1c6ba4bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Context is everything, even when you don’t see it]]></title>
            <link>https://hugocf.medium.com/context-is-everything-even-when-you-dont-see-it-8d56715c7c32?source=rss-1d7d57245202------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d56715c7c32</guid>
            <category><![CDATA[bias]]></category>
            <category><![CDATA[characteristics]]></category>
            <category><![CDATA[comparison]]></category>
            <category><![CDATA[decisions]]></category>
            <category><![CDATA[context]]></category>
            <dc:creator><![CDATA[Hugo Ferreira]]></dc:creator>
            <pubDate>Mon, 24 Apr 2023 21:53:24 GMT</pubDate>
            <atom:updated>2023-05-17T13:42:31.710Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>Why nothing has advantages or disadvantages, only characteristics</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ssl_7XvnnNhurNoZu32jqw.jpeg" /><figcaption><a href="https://unsplash.com/photos/aGxMCcAh2Pw">Photo</a> by <a href="https://unsplash.com/@mohammadtkh">Mohammad Takhsh</a> on <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p>We have all heard the common sense¹ saying that “context is everything” at some point of our life. It’s a reminder to consider the circumstances before making judgments or decisions.</p><p>Especially in consultancy, “context is everything” is a famous adage. What is true in one company, almost never applies directly to another. We always need to do major adjustments to the new context and the different realities.</p><p>But what if I told you that we can take this idea even further? What if I told you that <em>nothing</em> has advantages or disadvantages, only characteristics?</p><p>At first, this might seem like a strange notion. After all, we are so used to consider pros and cons when comparing different products or services.</p><p>Take, for example, someone in the market for a home safe. Most suppliers will brag about how resistant to tampering theirs locks are. An advantage, right? After all, that’s what all homeowners will be looking for: protection.</p><p>But what if we are talking about a burglar? Now, that <em>same</em> characteristic is a big disadvantages when looking for a home to target.</p><p>Still with a burglar in our minds, what if they are looking for a safe to take home and <em>practice</em> breaking into? It’s the same person but now that <em>same</em> characteristic is again an advantage.</p><p>We can see many more examples like this in the software development industry. It’s common to find technical analysis of frameworks, libraries, or programming languages. They are usually filled with positive and negative evaluations, advantages and disadvantages.</p><p>But what context are the authors using to assess them? Most of the times this is absent, which can lead to controversy and people talking past each other.</p><p>What the above examples illustrate is the <strong>implicit context</strong> we all have that is very often not said out loud. Not clarifying this full context is the most common pitfall of comparisons.</p><p>It’s the implicit context that “the purpose of safes is to protect”. It’s the implicit context that “frameworks should be stable”, or “performant”, or “easy to use”. Same goes for programming languages, where implicit contexts are many and sometimes contradictory. If we dig a little deeper, we will find that all these comparisons are only meaningful under some context.</p><p>Everyone has their own <em>implicit</em> context in their minds. In society, within cultures, we share common <em>implicit</em> contexts. This all bleeds in when we talk to each other.</p><p>So, what’s the solution? We need to make the <em>implicit</em> context <em>explicit</em>. Even if it seems redundant! Even when “everyone knows this”.</p><p>Always question yourself and be aware of the context you bring to every conversation. This include your goals, your constraints, past experiences and values. These are the “tinted glasses” you see the world through, and everyone else has their own.</p><p>Be curious about how other people’s <em>implicit</em> context differs from yours. You can gain a better understanding of their perspective and work better together.</p><p>If you analyse something by yourself, the danger of misunderstandings isn’t there. Implicit and explicit context tend to mix since it’s all internal. But looking for that <em>implicit</em> context might surprise you and shed new light into the “why” of your choices.</p><p>When analysing with someone we know very well, relying on a shared <em>implicit</em> context is possible. Misunderstandings are less likely but can still happen. Be very attentive and default to clarifying and making it <em>explicit</em> at the first sign of trouble.</p><p>Not relying on <em>implicit</em> context becomes crucial when working in larger collaborative groups. It’s impossible to rely on <em>implicit</em> context because everyone has a different one. This is especially important when working in multicultural environments, which bring even wider <em>implicit</em> context differences.</p><p>So, when preparing for a group discussion by yourself, start by gathering the different characteristics of the topic. Aim to do it in an impartial way, devoid of context. Then, with the group, define together which context to assess those characteristics under.</p><p>If you’re in the middle of a group brainstorming going sideways, go back to ensure that the context aligns. Clarify what is the agreed-upon context and, if there’s none, define it. Give everyone a shared frame of reference to assess the different solutions.</p><p>Next time you think about pros and cons of something, take a moment to consider the <em>implicit</em> context.</p><p>Remember that <strong>nothing has advantages or disadvantages, only characteristics.</strong> We can assess them under different contexts, and yours will likely differ from someone else’s.</p><p>Make all context <em>explicit</em> and be curious about other people’s perspectives. This way you can make work more effective and make better decisions together.</p><p><strong>Update 2023–05–17:<br></strong><em>(via </em><a href="https://mmitii.mattballantine.com/2023/05/17/pick-up-a-penguin/"><em>Andy Kemp</em></a><em>)</em></p><p>Interesting research supporting this notion of implicit context in the Scientific America article <a href="https://www.scientificamerican.com/article/people-differ-widely-in-their-understanding-of-even-a-simple-concept-such-as-the-word-penguin1/">People Differ Widely in Their Understanding of Even a Simple Concept Such as the Word ‘Penguin’</a>:</p><blockquote>“The probability two people selected at random will share the same concept about penguins is around 12 percent,” Kidd says.</blockquote><p>The reason is people’s different life experiences:</p><blockquote>For example, “people disagree about things like whether penguins are heavy, presumably because they haven’t lifted a penguin.” Here, Kidd hints at where a lot of these differences likely come from: they boil down to a person’s life experiences “If you’ve spent time watching penguins walk, you’re maybe more likely to think they’re heavy from their waddle,” Kidd says. “If you’ve spent time learning about anatomy, you’ve maybe learned birds have light skeletons and so think penguins are light.”</blockquote><p>And the differences can be quite numerous:</p><blockquote>…the team’s results suggest that at least 10 to 30 quantifiably different concept variants exist for even common nouns such as penguin.</blockquote><p>¹ <em>I know, sometimes “common sense” is not that common</em> 😏</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d56715c7c32" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Slack Overload? Regain control with Inbox Zero principles]]></title>
            <link>https://hugocf.medium.com/slack-overload-regain-control-with-inbox-zero-principles-7187fb283664?source=rss-1d7d57245202------2</link>
            <guid isPermaLink="false">https://medium.com/p/7187fb283664</guid>
            <category><![CDATA[clutter]]></category>
            <category><![CDATA[overwhelm]]></category>
            <category><![CDATA[inbox-zero]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Hugo Ferreira]]></dc:creator>
            <pubDate>Mon, 17 Apr 2023 14:18:24 GMT</pubDate>
            <atom:updated>2024-05-09T21:48:23.482Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>Get control of your Slack inbox with Inbox Zero principles and enjoy a clutter-free workspace.</h4><p><em>Note: This post is now quite outdated. See the </em><a href="https://hugo.ferreira.cc/slack-inbox/"><em>updated article</em></a><em> on my site:</em></p><p><a href="https://hugo.ferreira.cc/slack-inbox/">Slack Overload? Regain control with Inbox Zero principles</a></p><blockquote><strong><em>Update 2024–05–08:</em></strong><em> Finish updating the </em><a href="https://hugo.ferreira.cc/slack-inbox/#setup"><em>full setup</em></a><em> description according to the new sections format. Also, add a cover image.</em></blockquote><blockquote><strong><em>Update 2024–04–19:</em></strong><em> Add illustrative images to the </em><a href="https://hugo.ferreira.cc/slack-inbox/#context"><em>Context</em></a><em> section, including info on </em><a href="https://hugo.ferreira.cc/slack-inbox/#rivers-not-buckets"><em>Rivers, not buckets</em></a><em>.</em></blockquote><blockquote><strong><em>Update 2024–02–13:</em></strong><em> Introduce headings for easier navigation and highlight </em><a href="https://hugo.ferreira.cc/slack-inbox/#problem"><em>the core problem</em></a><em> with messaging apps.</em></blockquote><blockquote><strong><em>Update 2023–10–17:</em></strong><em> Replace simplistic “Channels/Someday” channel organisation with a </em><a href="https://en.wikipedia.org/wiki/MoSCoW_method"><em>MoSCoW</em></a><em>-inspired </em><a href="https://hugo.ferreira.cc/slack-inbox/#sections"><em>sections structure</em></a><em> optimised for fast processing.</em></blockquote><p><a href="https://hugo.ferreira.cc/slack-inbox/">Slack Overload? Regain control with Inbox Zero principles</a></p><p>“Inbox zero” is a pivotal concept to deal with the constant influx of information we have nowadays. <a href="https://en.wikipedia.org/wiki/Merlin_Mann#Writing">Merlin Mann coined it</a> in 2006, during a <a href="http://www.43folders.com/2006/04/05/wrapup">series of posts on 43Folders</a>.</p><blockquote><em>That “zero?” It’s not how many mes­sages are in your inbox–it’s how much of your own </em>brain<em> is in that inbox. Especially when you don’t want it to be. That’s it.</em></blockquote><blockquote><em>— </em><a href="https://web.archive.org/web/20110712000524/http://inboxzero.com:80/"><em>Internet Archive’s Wayback (2011–07–12)</em></a></blockquote><p>It was not about “perfection” but rather a way for us to take back control of our time and avoid being reactive. To do that, you triage messages to focus on what matters:</p><ol><li>Take fixed times in the day to go through your inboxes — close or ignore them outside of those times</li><li>Make decisions, not actions — triage fast and act later, so you’re not derailed into a long essays</li></ol><p>Once you’re done for the time slot, you can get out of that “new unread” mind space. Go back to doing your actions, according to which criteria you think should do first.</p><p>At the time, this concept appeared to deal with the problems of overwhelmed email inboxes. Its core principles expand beyond email though. They are essential to get out of a reactivity loop and quite generic that they apply to other areas or our life:</p><blockquote><em>Accept that almost everything in your life is an inbox</em></blockquote><blockquote><em>— </em><a href="https://www.wired.co.uk/profile/natasha-bernal"><em>Natasha Bernal</em></a><em> on </em><a href="https://www.wired.co.uk/article/inbox-zero-mentality"><em>Everything you thought you knew about inbox zero is wrong | WIRED UK</em></a></blockquote><p>Nowadays work happens on instant message applications, not email.</p><p>These types of applications are quite bad in letting us apply these concepts. Their structure is around immediacy and synchronous messages &amp; responses. <strong>Slack</strong>, in particular, is one of the worst offenders in this matter.</p><p>This is how I setup my <strong>Slack</strong> channels list to make it behave more like an inbox. The goal is to apply the “inbox zero” concepts outlined above and mitigate the pressures to “respond immediately”.</p><figure><img alt="Slack context menu displaying the “Show and sort” details of a sidebar section" src="https://cdn-images-1.medium.com/max/572/1*hWPgH360T1acW9gVfYkagA.png" /></figure><p>🚧 <strong>Setup</strong></p><p>The sidebar consists of the following sections, in this order:</p><ol><li><strong>Starred</strong> default section<br>• Sorted <a href="https://slack.com/help/articles/212596808-Adjust-your-sidebar-preferences#sort-your-conversations">Alphabetically</a> and showing <a href="https://slack.com/help/articles/212596808-Adjust-your-sidebar-preferences#choose-which-conversations-to-show">All</a> channels<br>• <em>Expanded</em> all the time<br>• Contains channels that I want to remain “pinned” on the top of the sidebar for a short time, regardless of read or not<br>• Used for ongoing group message or temporary channel with an active conversation for a few days or so<br>• @Slackbot and my own user @me direct messages are always starred here</li><li><strong>Direct messages</strong> default section<br>• Sorted <a href="https://slack.com/help/articles/212596808-Adjust-your-sidebar-preferences#sort-your-conversations">By most recent</a> and showing channels with <a href="https://slack.com/help/articles/212596808-Adjust-your-sidebar-preferences#choose-which-conversations-to-show">Unread messages only</a><br>• <em>Expanded</em> all the time</li><li><strong>Channels</strong> default section<br>• Sorted <a href="https://slack.com/help/articles/212596808-Adjust-your-sidebar-preferences#sort-your-conversations">By most recent</a> and showing channels with <a href="https://slack.com/help/articles/212596808-Adjust-your-sidebar-preferences#choose-which-conversations-to-show">Unread messages only</a><br>• <em>Expanded</em> all the time<br>• This section contains <em>only</em> the channels that are <strong><em>essential</em></strong><em> to my day-to-day work</em></li><li><strong>Someday</strong> <a href="https://slack.com/help/articles/360043207674-Organize-your-sidebar-with-custom-sections#create-custom-sections"><em>custom</em></a> section<br>• Sorted <a href="https://slack.com/help/articles/212596808-Adjust-your-sidebar-preferences#sort-your-conversations">By most recent</a> and showing channels with <a href="https://slack.com/help/articles/212596808-Adjust-your-sidebar-preferences#choose-which-conversations-to-show">Unread messages only</a><br>• <em>Collapsed</em> most of the time<br>• All the remaining channels that are less critical end up in this “catch-all” section (e.g. leisure, info, etc.)</li><li><strong>Apps</strong> default section<br>• Sorted <a href="https://slack.com/help/articles/212596808-Adjust-your-sidebar-preferences#sort-your-conversations">Alphabetically</a> and showing <a href="https://slack.com/help/articles/212596808-Adjust-your-sidebar-preferences#choose-which-conversations-to-show">All</a> channels<br>• <em>Collapsed</em> most of the time<br>• Easy access to apps I use on occasion but not so often that I remember their name</li></ol><p>📨 <strong>Processing</strong></p><p>With this, my daily process becomes, at specific times during the day:</p><ol><li>Check for <strong>Threads</strong> updates</li><li>Deal with <strong>Direct messages</strong></li><li>Process the updated <strong>Channels</strong></li></ol><p>When I have some more relaxed time, usually at the end of the day:</p><ol><li>Cherry-pick from the <strong>Someday</strong> channels some that spark my curiosity</li><li>Shift-Esc to “mark all as read” and have an clean slate for next day</li></ol><p>ℹ️ <strong>Tips</strong></p><p>With this, channels and conversations disappeared from the sidebar once we read them. There are few options to navigate around and finding previous channels or conversations:</p><ul><li>Shortcut CMD-K to find and jump to a specific channel</li><li>History 🕒 view to go back to recent chats and last visited channels</li><li>Threads view, to see updates on conversations I choose to <a href="https://slack.com/help/articles/115000769927-Use-threads-to-organize-discussions-#manage-thread-notifications">Get notified about new replies</a></li></ul><p>Also, to keep usage of the sidebar <strong>Unread messages</strong> aligned with this concept, set it to:</p><ul><li>Display only the <strong>Channels</strong> section</li><li>Sorted from newest to oldest</li></ul><blockquote><strong>Does it mean that with this you have Slack under control, almost empty, and you’re very responsive?</strong></blockquote><p>Of course not 🙂</p><p>Days still go haywire and messages backlog accumulates. and quite often it all becomes chaotic. That’s a consequent of the environments we work in.</p><p>With this setup, I’m able to take care of the most urgent and important messages in those chaotic days. Also, it’s easier to recover from a crazy week without the fear of missing out (FOMO) some interesting message.</p><blockquote><strong>What about using sections to organise and classify channels? For example, by type, scope, urgency, etc.</strong></blockquote><p>Before, I was using different sections to categorise and classify channels. This way I was able to scratch my itch for having everything organised and their “right” places.</p><p>I stopped doing it because it was getting hard for me to maintain them and was getting lost on too many places to check. There was no easy way to triage what was recent vs old and important vs secondary.</p><p>It was a hard to kill all those sections curated with care, after lots of time invested. This was quite scary 😬) but the benefits from the gained simplicity have made up for it.</p><blockquote><strong>What about the mobile app “Newest to oldest” view?</strong></blockquote><p>This inbox approach started in the Slack mobile app. I switched my channels list to sort by <a href="https://slack.com/help/articles/212596808-Adjust-your-sidebar-preferences#sort-your-conversations">“Recent activity” (recently renamed to “Newest to oldest”)</a>. This lists updated channels under “Today”, “Yesterday”, and “Last 7 days” groupings.</p><p>This change was such huge improvement. I found myself switching from desktop to my smartphone to check Slack messages. I could focus only on the “Today” view and keep up-to-date with what was changing (even if there was some past backlog).</p><p>The only drawback was that there was no easy way to distinguish between <em>important</em> vs <em>unimportant</em> channels. Triage of what could wait for later in the “Today” section was only visual.</p><p>Shortly after, a colleague shared a similar “timeline” setup of their desktop sidebar. Inspired by it, I decided to take the plunge and experiment with this “Slack as an inbox” setup in both desktop and mobile.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7187fb283664" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hearing or listening? Unlock the value of receiving feedback]]></title>
            <link>https://hugocf.medium.com/hearing-or-listening-unlock-the-value-of-receiving-feedback-705b9a09c4a0?source=rss-1d7d57245202------2</link>
            <guid isPermaLink="false">https://medium.com/p/705b9a09c4a0</guid>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[compassion]]></category>
            <category><![CDATA[ego]]></category>
            <category><![CDATA[guidelines]]></category>
            <dc:creator><![CDATA[Hugo Ferreira]]></dc:creator>
            <pubDate>Mon, 10 Apr 2023 08:11:46 GMT</pubDate>
            <atom:updated>2023-05-22T10:57:46.898Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>Most information on feedback focuses on how to give negative feedback. But what about receiving negative feedback? How better would it be if both ends shared the burden of having productive conversations? Let’s put our egos to the side and be emphatic with those who give us criticism, so the burden isn’t on the speaker alone.</em></p><p>Whenever the topic of feedback comes up, the emphasis is usually on how to <em>give feedback</em> in an effective way.</p><p>The concerns are also usually about <em>negative feedback</em>. It’s quite easy to give praise or positive feedback to people, since they receive it very well in general.</p><p>The internet is full of advice and frameworks to help us shape our message in a way that people receive it well. For example:</p><ul><li><a href="https://en.wikipedia.org/wiki/Nonviolent_Communication">NVC (Nonviolent Communication)</a></li><li><a href="https://www.ccl.org/articles/leading-effectively-articles/sbi-feedback-model-a-quick-win-to-improve-talent-conversations-development/">SBI (Situation-Behavior-Impact)</a></li><li><a href="https://en.wikipedia.org/wiki/Praise_sandwich">The feedback sandwich</a></li><li>and many others, I’m sure…</li></ul><p>It makes sense that it is so. It’s a natural psychological reaction to become defensive when people criticise us.</p><p>But what about the other side of the coin, <strong>the way we <em>receive</em> feedback</strong>?</p><p>Aren’t we loosing valuable information if the success of <em>negative feedback</em> is only on the speaker?</p><p>Won’t some difficult conversations not happen if the burden is only on the person <em>shaping the message</em>?</p><p>I, for one, have refrained on occasion from giving <em>negative feedback</em> to people because of that. Sometimes the emotional bandwidth to tone down my initial impulse wasn’t there. Sometimes I didn’t have energy to do the mental gymnastics needed to restructure it into a thoughtful message.</p><p><strong>Poorly shaped <em>negative feedback</em></strong> can take many common forms:</p><ul><li>It can be sloppy, too blunt, or even aggressive</li><li>Can come from a colleague, a boss, or a client</li><li>Someone might think they are better than those around them</li><li>In some environments, competition and antagonism can be the norm</li></ul><p>And yet, there seems to be lack of awareness and interest on how to deal with it.</p><figure><img alt="Google Trends chart from 2010 to 2023, showing high interest for “giving feedback” and around one third of it for “receiving feedback” and residual for more specifically “receiving negative feedback”" src="https://cdn-images-1.medium.com/max/1024/1*C8HUF3kjEFMllj2JuoU5rg.png" /><figcaption><a href="https://trends.google.com/trends/explore?date=2010-01-01%202023-03-31&amp;q=%22giving%20feedback%22,%22receiving%20negative%20feedback%22,%22receiving%20feedback%22&amp;hl=en-US">Source</a> <em>(blue = “giving feedback”, yellow = “receiving feedback”, red = “receiving negative feedback”)</em></figcaption></figure><p>Consider this real example of feedback to a technical proposal, many years ago. At the time, several people pilled on the proposal, with lots of comments received like these:</p><blockquote><em>This change makes absolutely no sense to me.</em></blockquote><blockquote>…</blockquote><blockquote><em>I’d vote against this immediately! Why not just use [some simplistic alternative] instead?</em></blockquote><blockquote>…</blockquote><blockquote><em>Sure, let’s all do [insert gross exaggeration / ridiculous simplification] from now on.</em></blockquote><p>What do you think each person was <strong><em>actually</em> saying</strong>?</p><blockquote><em>“You’re incompetent. This idea is stupid.”</em></blockquote><p>or,</p><blockquote><em>“I’m missing the context where this makes sense.”</em></blockquote><p>We can interpret both these thoughts from the comments above. The first one is more likely to be the one we latch on (because of our ego, our sense of self-preservation, etc.). Yet, <strong>we get to choose which interpretation</strong> to focus on and respond to.</p><p>At its core, <strong>feedback is only information</strong>. It’s very easy for emotion and flawed terms to <strong>camouflage</strong> that information, tough.</p><p>We can approach the feedback we’re given like detectives or scientists solving an interesting puzzle. Investigate beyond what’s most obvious and uncover the information behind it.</p><p><strong>Show </strong><a href="https://www.wired.co.uk/article/tania-singer-compassion-burnout"><strong>compassion</strong></a><strong> when we’re on the receiving end</strong> of feedback given in a “bad” way:</p><ol><li>🙉 Ignore “intention”, remove “tone”, <strong>strip the message down</strong> to its essence to <strong>put it into perspective</strong></li><li>🤔 Take the feedback in and relax by thinking <strong>what would it take for you</strong> to be the one saying that</li><li>🎯 Thank the person for <strong>the essence of their point and consider</strong>, in a factual unemotional manner, what to do with it</li></ol><p>One of the core principles of Stoicism can guide us here: the <a href="https://www.njlifehacks.com/what-is-stoicism-overview-definition-10-stoic-principles/#tab-con-3">acceptance of things we cannot control</a>. And we cannot control other people’s words, only ours!</p><p>In the words of the ancient Greek philosopher <a href="https://dailystoic.com/Epictetus">Epictetus</a>:</p><blockquote><em>Remember that it is not he who gives abuse or blows, who affronts, but the view we take of these things as insulting. When, therefore, anyone provokes you, be assured that it is your own opinion which provokes you. Try, therefore, in the first place, not to be bewildered by appearances. For if you once gain time and respite, you will more easily command yourself.</em></blockquote><blockquote><em>— in </em><a href="https://www.gutenberg.org/files/45109/45109-h/45109-h.htm#:~:text=XX"><em>The Enchiridion, Section XX</em></a></blockquote><p>So remember:</p><ul><li>How you <strong><em>perceive</em></strong> other people’s words has more impact on you than the way people <strong><em>said them</em></strong> or their <strong><em>real intention</em></strong>.</li><li>You are <strong><em>in full control</em></strong> of how you interpret what others said and you <strong><em>cannot control</em></strong> how other people say it.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=705b9a09c4a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Chaos to Strategy: Embracing Firefighting at Work]]></title>
            <link>https://hugocf.medium.com/from-chaos-to-strategy-embracing-firefighting-at-work-1ec65a6be852?source=rss-1d7d57245202------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ec65a6be852</guid>
            <category><![CDATA[emergency]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[training]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Hugo Ferreira]]></dc:creator>
            <pubDate>Mon, 03 Apr 2023 07:01:45 GMT</pubDate>
            <atom:updated>2023-07-23T17:54:41.515Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>From Chaos to Strategy: Embracing firefighting at work</h3><h4><em>Did you know firefighters are strategic? So why do we use the term firefighting when we mean “reactive and impulsive”?</em></h4><p><em>We use the analogy of firefighting when people handle unexpected problems at work. Instead of reacting in a chaotic manner like civilians, adopt the strategic approach of trained firefighters. This involves having a plan, clarifying roles, training people and practicing together. Doing so, we can create a better culture of preparedness in our companies.</em></p><figure><img alt="A firefighter using a hose to extinguish a fire" src="https://cdn-images-1.medium.com/max/1024/0*G1eQ0iUGYgEV_9nl" /><figcaption><a href="https://unsplash.com/photos/e5s4jQxEExo">Photo</a> by <a href="https://unsplash.com/@hush52">Hush Naidoo Jade Photography</a> on <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p>We’ve all heard people say they’re in “firefighting mode” or “putting out fires” at work. They mean they’re dealing with unexpected problems and everything feels chaotic. But have you ever thought about <em>why</em> we use the analogy of firefighting for this kind of scenario?</p><p>Picture a real life fire. People feel confused, scared, and don’t know what to do. They’re stressed and drop everything, scrambling around to deal with the emergency. They disperse their focus and their actions are erratic. Chaos is all around.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FZD8ZjehSsLDZQRKJjJ%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExODY4OGIxZTZlNmE1NDgxMTg1NDk0YTY1ZTJiZDZhNGI3ODUyOTMxOSZjdD1n%2FZD8ZjehSsLDZQRKJjJ%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FZD8ZjehSsLDZQRKJjJ%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/df1e7c63bb23a106a21710b5cc9d62c9/href">https://medium.com/media/df1e7c63bb23a106a21710b5cc9d62c9/href</a></iframe><p>As you can imagine, I don‘t think this is how we should react. What might surprise you is that I don’t think the analogy is wrong. I’d argue though, that we should embrace it even further.</p><h3>Even firefighting needs a strategy</h3><p><strong>Trained firefighters</strong> make up another crucial group of people in firefighting. Their <em>actions</em> and <em>attitudes</em> are completely different from those described above:</p><ul><li>They have a well thought out <strong>strategy</strong> for tackling fires, which they adjust to the reality on the ground</li><li>They have pre-established <strong>roles</strong> and <strong>communication</strong> lines, so everyone knows what to do</li><li>They follow <strong>safety rules</strong> of engagement based on their learnings from past emergencies</li><li>They <strong>train</strong> together, in controlled environments simulating reality, to improve their coordination</li></ul><p>With this, they are ready to handle emergencies with calm and expertise. When fires do occur, they feel “familiar”. Even considering the natural levels of stress and adrenaline involved in these situations.</p><figure><img alt="A group of firefighters coordinating together to pass along buckets of water to the top of a ladder" src="https://cdn-images-1.medium.com/max/260/1*2QLhBLvTN3VS9WVx5qSl3A.gif" /><figcaption><a href="https://www.youtube.com/shorts/UQLUP6PwGRk"><em>Source</em></a></figcaption></figure><p>Consider the case of forest fires and how trained firefighters behave when they’re on the scene:</p><ul><li>Headquarters coordinates efforts based on constant reports from the field</li><li>Coordination teams choose where to best deploy their people and physical resources</li><li>They take changing context into account (e.g. weather and wind forecasts) to decide which fire fronts to attack first</li><li>At times, they even decide which areas to let burn to create a natural barrier for other advancing fires</li></ul><p>So, why can’t we operate in a similar way in our companies? Why are we in constant in firefighting mode, reacting to emergencies as they arise?</p><p>We can choose to look at “firefighting” in a strategic way. We can seek to act like “trained firefighters”, rather than in a chaotic way like “civilians”:</p><ul><li><strong>Have a plan</strong> in place for handling unexpected problems</li><li>Make sure people <strong>understand their role</strong> in responding to unexpected challenges</li><li><strong>Train</strong> people on <strong>how to respond</strong> to crises in a calm and efficient manner</li><li><strong>Practice</strong> how to <strong>work together</strong> to find solutions in emergencies</li></ul><p>This way we can create a better culture of preparedness in our companies. Like trained firefighters, we can be ready to handle whatever challenges come our way.</p><p>So, the next time you find yourself in firefighting mode at work, remember that you have a choice. Don’t react in a chaotic manner, like a civilian in a fire. <strong>Be strategic like a trained firefighter.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ec65a6be852" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>