<?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 Andy Tabberer on Medium]]></title>
        <description><![CDATA[Stories by Andy Tabberer on Medium]]></description>
        <link>https://medium.com/@consultantmicro?source=rss-605eb46ecf0b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*cBLMacxoUm4iqEDZksDmIA.jpeg</url>
            <title>Stories by Andy Tabberer on Medium</title>
            <link>https://medium.com/@consultantmicro?source=rss-605eb46ecf0b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:56:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@consultantmicro/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[Citizenship: What it means to be a good team member]]></title>
            <link>https://consultantmicro.medium.com/citizenship-what-it-means-to-be-a-good-team-member-6bf97b576645?source=rss-605eb46ecf0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/6bf97b576645</guid>
            <category><![CDATA[ways-of-working]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[self-organized-teams]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Andy Tabberer]]></dc:creator>
            <pubDate>Sun, 04 Feb 2024 15:32:36 GMT</pubDate>
            <atom:updated>2024-02-05T13:12:45.826Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4cxOgryEkM3vjcXpPSuTXg.png" /><figcaption>Good team members are key</figcaption></figure><h3>What is citizenship?</h3><p>This is the bond between a team member and the team. We make a commitment to the team to honour our obligations — our agreed ways of working and our working agreements — in exchange for agreed rights and liberties.</p><p>We give and take in equal measure.</p><p>— — —</p><p><em>So, what makes a good team member?</em></p><h3>Practices empathy</h3><p><em>Empathy is the capacity to understand or feel what another person is experiencing from within their frame of reference; the capacity to place oneself in another’s position.</em></p><p>As an individual, ask yourself the following questions to help practice empathy:</p><ul><li>What is going on for the other person?</li><li>What emotions might they be feeling? Are there signs of emotion?</li><li>How might this look from their point of view?</li><li>How might they be experiencing the situation?</li><li>What challenges are they facing?</li></ul><p>As a team, we work together to avoid ruinous empathy. This is when we opt for being nice, so we spare people’s feelings. Instead, we avoid telling people what needs to be said, we tell white lies. We offer verbal pats on the back and virtual love hearts and thumbs up instead of constructive feedback. We should be more specific and sincere with praise and kinder and clearer with criticism. And we remember empathy is a two-way street.</p><h3>Shows commitment</h3><p><em>To be committed means binding yourself, intellectually or emotionally, to a course of action. To make a pledge or a promise. Being committed to the team covers ways of working, goals, and team standards.</em></p><p>As an individual, you use unambiguous language when you are asked to make a commitment to the team. In our remote-first world, this also means you have your camera on. You give concrete ‘yes’ or ‘no’ answers when you’re asked if you agree with what we are being asked to do. Otherwise, we are giving ourselves a ‘get of jail free’ card when it comes to accountability for delivering our commitments.</p><p>As a team, we can encourage commitment by allowing everyone the opportunity to offer their view on what is being asked and encouraging individuals to offer dissenting views. We feel empowered to disagree with a decision while it is being made, but once it has been made, we all commit to the decision regardless of our earlier opinion — otherwise known as ‘disagree and commit.’</p><h3>Taking part</h3><p><em>Participation is the act of taking part in an event or activity. It is being involved in decisions that affect you. Through participation, we can identify opportunities and strategies for action and build solidarity to make change. It is people’s individual actions and choices that reflect the kind of team they want to work in.</em></p><p>As an individual, you can take part in several ways. An effective way for new teams/team members to get to know each other is by creating a ‘manual of me’ and presenting it to the team. You ask ‘how’ and ‘what’ questions and you actively listen to what others have to say. You think aloud, encourage others to speak up, and volunteer to run events, all to help increase engagement.</p><p>As a team, we create a working agreement on what participation looks like in our group. We share what we need people to think about before a meeting or discussion, giving others time to think beforehand — this is particularly helpful for our neurodivergent colleagues. We take the time to read the ‘manual of me’ for everyone on the team and adjust how the team works so we meet everyone’s needs. We ensure active participation is embedded in our onboarding as this helps create a team culture of wanting to take part in the running of the team.</p><h3>Being dependable</h3><p><em>You are reliable and trustworthy.</em></p><p>As an individual, you make sure you get things done on time and to the standard that is expected. You proactively communicate with each other about things like delays. You take responsibility for your work.</p><p>As a team, we hold each other accountable for promises and commitments we make as individuals. We avoid ruinous empathy and if someone does not deliver, we ask what stopped them and how can we avoid this in the future. We make dependability something that is celebrated.</p><h3>Having important conversations when it’s needed</h3><p><em>An important conversation is a planned discussion about an uncomfortable topic or an experience that may be considered negative. The goal of this is to share different perspectives, build mutual understanding, and develop respect (not to persuade or win).</em></p><p>As an individual, we do not wait to have difficult conversations. The lingering worry or tension can spiral, far outweighing the uncomfortable feeling we get when we think about what needs to be said. You can practice these conversations with your colleagues or prep beforehand, so you are more comfortable with the situation. When you have these important conversations, you actively listen to all sides of the discussion.</p><p>As a team, we create a culture where there is space to have important conversations. We do not accept second-hand feedback. We avoid ruinous empathy and focus on understanding different perspectives. We attack problems, not people. We challenge negative narratives about the past so we can move on. We accept that sometimes the goal is not to agree — it is to gain a deeper understanding. We accept conflict — or difference of opinion — can be a good thing.</p><h3>Setting high standards</h3><p><em>We continually raise the bar and drive our teams to deliver high-quality products, services, and processes.</em></p><p>As an individual, think about what standards you set yourself. Do you invite accountability? Remember that no matter who you are, you can always improve as a person and as part of a team.</p><p>As a team, we understand that if we lower our standards, our products and services will suffer. Our standards should be documented and shared, so everyone knows what to expect. This, along with making progress visible, keeps the team accountable for making sure they are meeting their standards (and commitments).</p><h3>Remain curious</h3><p><em>Curiosity is a quality related to inquisitive thinking such as exploration, investigation, and learning. It is a strong desire to know or learn something.</em></p><p>As an individual, you can show curiosity by taking an interest in all your teammates — reading their ‘manual of me’ is a great way to get started. Take an interest in your stakeholders and their world and what matters to them. Find out about what the teams next to yours do and what matters to them. Being curious will help you build better relationships and improve your empathy skills.</p><p>As a team, we ask our fellow team members about their work. We normalise asking questions at meetings like Show and Tells and when our colleagues present their work to the team. This is always preferable to default to ruinous empathy when we give thumbs up and love hearts instead of feedback and questions.</p><h3>Avoiding professional protectionism</h3><p><em>This is when we feel overprotective about their role at the expense of collaboration and sharing with others… this often occurs with the introduction of new roles or new ways of working and can be perceived as a challenge or threat to pre-existing professional identities.</em></p><p>As an individual, you avoid professional protectionism by focusing on what you can do to be helpful or useful — you role model this whenever you can. You are curious when another person wants to pick up something that you usually do. You are open to collaboration and consider how sharing responsibilities may help the team.</p><p>As a team, we predict when professional protectionism may occur, such as when we change our ways of working, or a new team member joins the team. We remember handing responsibility to “another person can feel like a loss of status, authority, responsibility or experience”. We define and revisit team roles and responsibilities and spot grey areas that may need further exploration.</p><h3>What happens if we all do this?</h3><p>If we get the balance right between the team and the individual, then we have unity, we are working together. This then improves team maturity and leads to more autonomy, giving us the freedom to work how we want to work.</p><p>Isn’t that what we all want in the end?</p><h3>Further reading resources and tools that can help</h3><ul><li><a href="https://miro.com/miroverse/dysfunction-mapping/">Dysfunction mapping</a></li><li><a href="https://www.linkedin.com/pulse/what-language-commitment-why-probably-most-tool-product-alon-gildoni/">The language of commitment</a></li><li><a href="https://www.radicalcandor.com/stop-ruinous-empathy/">Stop Ruinous Empathy</a></li><li><a href="https://www.radicalcandor.com/a-hip-approach-to-feedback/">HIP</a> feedback method (avoid ruinous empathy)</li><li><a href="https://www.liberatingstructures.com/1-1-2-4-all/">Liberating Structure 1–2–4-all</a></li><li><a href="https://rework.withgoogle.com/print/guides/5721312655835136/">Re:work Google 5 dynamics of a high performing team toolkit</a></li><li><a href="https://estherderby.com/wp-content/uploads/2014/10/CongruentFeedback.pdf">Congruent Feedback (Esther Derby)</a></li><li><a href="https://emilywebber.co.uk/why-cant-we-all-just-get-along/">Why can we all get along (Emily Webber)</a></li><li><a href="https://www.liberatingstructures.com/6-making-space-with-triz/">Liberating Structure Triz</a></li><li><a href="https://miro.com/templates/reverse-brainstorming/">Reverse Brainstorm</a></li><li><a href="https://resources.scrumalliance.org/Article/facilitate-powerful-working-agreements">Facilitate powerful working agreements</a></li><li><a href="https://www.coop.co.uk/experience-library/ways-of-working/">Coop Experience Library — ways of working</a></li><li><a href="https://miro.com/guides/team-charter/">Miro Guide to Team Charters and templates</a></li><li><a href="https://www.wcupa.edu/coral/tuckmanStagesGroupDelvelopment.aspx#:~:text=These%20stages%20are%20commonly%20known,more%20collaborative%20or%20shared%20leadership.">Tuckman’s stages of group development assessment tool</a></li><li><a href="https://www.executiveagenda.com/resources/blog/five-dysfunctions-team">5 dysfunctions of a team explained and approaches to take</a></li><li><a href="https://hbr.org/2018/09/the-business-case-for-curiosity">The business case for curiosity</a></li><li><a href="https://www.forbes.com/sites/forbescoachescouncil/2021/08/25/stay-curious-the-importance-of-continually-asking-questions/">Stay curious: the importance of continually asking questions</a></li><li><a href="https://www.forbes.com/sites/triciaemerson/2018/06/24/what-youre-willing-to-tolerate-sets-the-tone-for-your-company-culture/#1716205737c7">What you are willing to tolerate sets the goal for your company</a></li><li><a href="https://thesystemsthinker.com/introducing-the-systems-archetypes-drifting-goals/">Drifting goals aka boiling frogs</a></li><li><a href="https://www.nngroup.com/articles/empathy-mapping/">Empathy mapping explained</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6bf97b576645" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile gardening adventures]]></title>
            <link>https://consultantmicro.medium.com/agile-gardening-adventure-8b780ea90ba3?source=rss-605eb46ecf0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b780ea90ba3</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[allotment]]></category>
            <dc:creator><![CDATA[Andy Tabberer]]></dc:creator>
            <pubDate>Wed, 25 Oct 2023 06:57:38 GMT</pubDate>
            <atom:updated>2023-10-25T08:13:07.078Z</atom:updated>
            <content:encoded><![CDATA[<p>Inspired by <a href="http://twitter.com/liannemellor">@liannemellor</a> and her <a href="https://medium.com/@liannemellor/why-allotment-gardening-is-a-lot-like-being-an-agile-coach-a87eb673d055">agile gardening post</a>, here’s my take on agile ways of working through the medium of an allotment diary.</p><figure><img alt="Our allotment with a freshly dug bed" src="https://cdn-images-1.medium.com/max/1024/1*Xq6A-4CUT9td2rX6_ZBv_Q.jpeg" /></figure><h3>Gardening is rich with workplace metaphors.</h3><p>A propagator = an environment for safe-to-fail experiments. Those that work go into the greenhouse (we scale). Those that don’t we learn something about our environment which we take into future experiments</p><h3>Delivery in action at the allotment</h3><p>Goal — we’ll be eating organic potatoes this summer. The first iteration was to clear a grass-infested area. The second was to dig up and replant gooseberry bushes that were in situ. For this iteration, I dug over and weeded a small patch, with paving slabs added to block grass/weed overspill — the value (again) is future capability. Next iteration, the value will be we can now grow veg (potatoes planted). Then we start on another small patch. And repeat.</p><h3>The latest allotment sprint</h3><p>Research spike to test the size and suitability of the pathing slabs we’d put aside for our final wall — success! We refactored our ‘dug’ bed by removing a further ton of bindweed. Finally, we extended the bed another metre to enhance its future capability. Moved closer to our goal of eating organic spuds this summer.</p><h3>The agile allotment</h3><p>We’ve changed direction (pivoted 😜) due to a new opportunity (a cheap greenhouse became available). This better meets our emerging needs as we have lots of toms, chilies, etc growing around the house and we can grow more varied, specialist produce. Today’s sprint goal: we have cleared and leveled the ground ready for greenhouse assembly (future capability &amp; learning/skills development).</p><h3>Timeboxing</h3><p>Lots of timeboxed graft and activity this weekend, embracing change, but staying focused on what is most valuable, we have turned an overgrown, unloved, and unproductive area of the allotment into a potato patch, a tool storage area, and a greenhouse full of toms and chilies.</p><p>What you learn at work you can apply at home and vice versa!</p><h3>Work mirrors allotment life part 20</h3><p>Day off. Preparing two beds at the allotment for crop rotation. I am doing something similar at work with new teams forming. Preparing fertile ground to grow. Right people in the right place. Sharing what we learn from our most recent experience.</p><h3>More agile allotmenteering today</h3><p>We are paving our allotment (with recycled slabs) so it is safer to walk around and kill off bindweed.</p><p>Used story slicing to consider our options. We opted for paving the path by the greenhouse as it has high use and high bindweed levels.</p><h3>Organoponicos</h3><p>What lessons can we learn from Organoponicos when it comes to our teams? This is the epic tale of Cuba’s pursuit of self-reliance and sustainability when its trade was cut off — when the USSR collapsed, so did Cuba’s food and fuel supplies. The ‘grow your own [food] rather than import it’ approach could be applied in the workplace. Cultivate the space between teams, the knowledge in-between disciplines, like the Cubans did with public green space. Encourage cross-functional teams to form supported by experts, like the urban farmer co-operatives supported by universities. Give people the skills to grow/nurture the people they need, trained by experts in each discipline, and coached to understand the relationships between each role. These people would ‘naturally’ work across teams, cultivate cross-functional teams, be the fertilizer for sustained growth, and be self-reliant ps I’ve had too much coffee (again).</p><p>Happy gardening!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b780ea90ba3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The human side of delivery in a remote world]]></title>
            <link>https://consultantmicro.medium.com/the-human-side-of-delivery-in-a-remote-world-f7050391494f?source=rss-605eb46ecf0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7050391494f</guid>
            <category><![CDATA[delivery-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[delivery-software]]></category>
            <dc:creator><![CDATA[Andy Tabberer]]></dc:creator>
            <pubDate>Mon, 03 Jan 2022 17:42:47 GMT</pubDate>
            <atom:updated>2022-06-15T07:53:45.054Z</atom:updated>
            <content:encoded><![CDATA[<p>There are three parts to what I call the Human side of Delivery — those things we can do to make things more human in a digital and often remote world. Note what is covered here is not an exhaustive list; it is, I hope, the start of a wider conversation about how soft skills (which should be called hard skills) are the most important thing we can master right now in delivery.</p><p><em>TL:DR: save yourself minutes of reading time by listening to this 30-minute </em><a href="https://open.spotify.com/episode/047jfzURNcNkWuZY7XHVXp?si=GQYG2uIyToaK03cVekWoTg&amp;utm_source=copy-link"><em>podcast </em></a><em>I recorded for the Delivery Manager Daily with </em><a href="https://www.linkedin.com/in/mariodecristofano/"><em>Mario DeCristofano</em></a><em> which covers most of the themes below.</em></p><h3>Getting to know you</h3><p><em>‘We connect with each other so we thrive together’</em></p><p>This is what we used to do around the water cooler (what even is one of these?), when we sat next to each other in buildings, over a spot of lunch, or while waiting for meetings in the old pre-Covid days. Weirdly, getting to know each other and how we work is even more important now we are physically separated most days. Often, we have to accelerate this process, do it en masse, so we have our relation-building blocks in place quickly for teams forming online. We have to do it mainly via video calls with people we may never meet in person. And we have to think of ways to do this through the medium of remote workshops and activities rather than naturally, and over time.</p><p>Here are some examples of things I’ve done over the last two years so the people I work with can share something of themselves so we can begin to get to know each other:</p><p><strong>Manual of me — </strong>the classic way for everyone on the team to describe themselves and how they work.</p><p><strong>Commonalities </strong>— a get-to-know-you exercise to seek common attributes between team members — think who has brown eyes, speaks more than one language, has emigrated to another country. Think ‘we are not so different you and I’ stuff.</p><p><strong>The Thumb game — </strong>an alternative and very simple get-to-know-you exercise. Get all participants to cover their cameras with their thumbs. Then the participants answer a series of yes or no questions by removing their thumbs for yes and holding fast for no. Can be as serious or fun as you like.</p><p><strong>Life highlights games</strong> — we pick and reveal which 30 seconds of our lives we’d relive if we could. A lovely way to get a feel for each other’s passions, loves, and personalities.</p><p><strong>What One Question … </strong>— split team members into pairs (with someone they don’t work with often) and pose one question: what one question should we ask interview candidates to discover a person’s suitability to join our team. You’ll find out what your emerging values are.</p><p><strong>What are we drinking today?</strong> — ask team members to bring their favourite hot drink to a meeting and we talk about our drinks and their stories.</p><p><strong>What’s your favourite food?</strong> — the most hotly debated session I have EVER run. A fun way to get to know the cultures and tastes of your teams mates especially those based in other or from other countries.</p><p>As delivery folk, our job here is good old facilitation, which is a cornerstone of the human side of delivery IMHO. We coax, charm, encourage, enable, appeal, persuade, and include, so others have a platform to connect.</p><h3>Creating the safe environment</h3><p><em>‘We have fun, we are inclusive, we value one another and our contributions, and we enjoy being with each other’</em></p><p>As we get to know each other, we need a safe environment in place so can grow, learn, and succeed together. Here’s how I do this:</p><p><strong>Trust everyone on day one — </strong>you acquire trust by giving trust (Tom DeMarco). It’s a leap of faith, the first step to creating a safe environment. Trust me :)</p><p><strong>Do fun and be happy </strong>— start meetings with a positive round of chat to get everyone in the right place. Think about what will make you happy about the meeting you are currently in. Tell bad Dad jokes, finish meetings with a riddle, pick a song to end meetings with. And despite what people say, you can do ‘fun’ and put on a ‘happy face’ with practice. Keep trying and you’ll get better, I promise.</p><p><strong>Mind your language </strong>— remember the power of words like ‘we’, ‘us’, and ‘ours’. Repeat these over and over so everyone feels part of the team. Keep your questions open. Avoid asking ‘why’ as it makes folk defensive. Try using questions starting with ‘what’, ‘how’, ‘has’, ‘is there’ and coaching-type questions like ‘tell me about’ and ‘help me understand’. Remember slang and euphemisms may not be understood by everyone (especially with distributed teams abroad). In short, think before you speak and make your words count.</p><p><strong>Thoughtful onboarding </strong>— show you care by welcoming new people to the team in advance with an email explaining key roles, what day one, week one, and month one look like. Share any videos, articles, and so on (we recorded key presentations for new starters so we could share these, the one benefit of Teams). Pair new folk with a buddy — try the last person who joined the team this as they know the questions and the worries well.</p><p><strong>Celebrate each other </strong>— whether it’s having fun or a flash of brilliance, use Slack/Teams to thank someone for doing something good. Use Town Halls or wider meetings to celebrate the good work your good people do — we have a regular slot every two weeks where people get a shout out for a positive act or great piece of work</p><p><strong>Embrace vulnerability</strong> — talk openly and freely about mental wellbeing and regularly remind people that no person owes the company their mental wellbeing. Show when you are finding things difficult or a struggle and normalise asking for help for everyone’s sake.</p><p><strong>Show empathy, be kind </strong>— encourage team members to see the world through someone else’s eyes by asking these questions* regularly:</p><p>- What is going on for the other person/people?<br>- What emotions might they be feeling?<br>- How might this look from their point of view?<br>- How might they be experiencing this situation?<br>- What challenges may they have/might be facing?</p><p>*from the estimable <a href="http://www.estherderby.com/">Esther Derby</a></p><p><strong>Remember what people share with you </strong>— if someone shares something about them or their work, treasure this information. Whenever I do an exercise to get to know people or if someone opens up in a meeting about work or life, I ALWAYS follow this up. A Slack message, a call, whatever works. People really appreciate this and you remembering the little things they have shared — kids or pet being ill, learning a new skill, moving house, an evening out…</p><p><strong>Always assume positive intent </strong>— start from this position and work and life’s outcomes are infinitely better*. It alters how you think, promotes empathy, and enables kindness. It’s hard, and I’m still learning, but it makes such a difference.</p><p>*my wife has taught me this. She’s the best :)</p><p><strong>Risk and failure go hand in hand </strong>— encourage people to take risks — the pathway to innovation and improvement — and demonstrably acknowledge this will mean people fail, which is 100% ok.</p><p>Your primary role here, delivery folk, is role modeling the above and recognising and acknowledging this in others. Think of yourself as a good virus, make yourself and what you do contagious by doing it every time you come into contact with your team(s).</p><h3>How to keep it going</h3><p><em>‘Turning what we do into a mindset and applying this beyond our team’</em></p><p>Keeping this going — connecting, and keeping things positive and safe — is tricky. It’s how we earn our money IMHO. So, what does it take?</p><p><strong>It’s a mindset </strong>— instill the following into everyone, make it part of every interaction:</p><p>- we turn up with only good intentions<br>- hope is something you do, not ‘have’, so do hope every day<br>- ours is a participative workplace where we do things together (and not do things to others)<br>- practice kindness and empathy (using the questions above)</p><p><strong>Nurture connections and connect people and teams</strong> — remember what people share with you, it is important! Keep your connections alive and connect people with others outside your team based on what you learn about them. This creates corridors between teams so information and learning move freely.</p><p><strong>Share team data and spread team health mantra</strong> — share your Team Health with leaders and teams who interact with your team(s). Publishing this (anonymised) data acts as a nudge so we continue to strive to improve health and reinforce its importance.</p><p><strong>Revisit what it means to be human </strong>— use your retros to consider how to improve your events, environment, team health, and interactions so they remain human at heart.</p><p><strong>Cultivate the space between your team and other teams/depts/your suppliers</strong> — the psychological safety of the whole (org) is never the sum of its parts (teams), but it’s the safety (and quality) of the interactions between teams. By bringing the wider team(s) together we show we trust each other and we make our interactions a safe place, too.</p><p><strong>Spreading the concept of Citizenship </strong>— this is the bond between a team member and the team. We make a commitment to the team to honour our ways of working in return for agreed rights and liberties. We give and take in equal measure.</p><p><strong>Cut yourself some slack — </strong>you need time to do this stuff, it needs to be a dedicated part of your job. Set aside a percentage of your time/capacity to focus on the human side, too. Otherwise, it will have to be a hobby, something you do in your spare time, and you don’t really want that (and it’s poor role-modeling behaviour, too).</p><p>That’s my take on the Human side of delivery. Through it, we start to connect as individuals, as a team, as teams. We participate, take part. We learn to give and take. We see little separates us really, we have a lot in common. We start to think of each other and how we can meet each other’s needs. We create and maintain a safe space to do this. And we have the shared mindset to keep it going by focusing on the ‘doing’ every single day.</p><p>What do you think, dear reader?</p><p>AndyT x</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7050391494f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Helping our colleagues to be good Stakeholders]]></title>
            <link>https://consultantmicro.medium.com/helping-our-colleagues-to-be-good-stakeholders-ad7095d0d163?source=rss-605eb46ecf0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad7095d0d163</guid>
            <category><![CDATA[delivery-software]]></category>
            <category><![CDATA[stakeholder]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[delivery]]></category>
            <dc:creator><![CDATA[Andy Tabberer]]></dc:creator>
            <pubDate>Fri, 12 Feb 2021 17:03:48 GMT</pubDate>
            <atom:updated>2023-11-02T17:50:19.835Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*HYMOc4LgOfy1pv_HplRJcA.jpeg" /><figcaption>Be a Good Samaritan to your Stakeholders.</figcaption></figure><p>Following on from my <a href="https://consultantmicro.medium.com/how-to-be-a-good-stakeholder-c075d439cb85">‘How to be a good stakeholder’</a> post, here are a few ideas and suggestions designed to help you help your colleagues to be good Stakeholders and so you can work in harmony together.</p><p><strong>Write a Wiki</strong></p><p>Wikis are a great way to share important information with Stakeholders so they have everything they need to know about your product at their fingertips (keypad?) — knowledge and insight gained, design thinking, decisions made, the way you work, service and journey maps, technical diagrams, team bios, and the story of your product or service. For extra bonus points, add a glossary for capturing any technical and business jargon you use so you speak a common language.</p><p><strong>Create Nudges</strong></p><p>Think of nudges as little prompts to help Stakeholders to do the right thing. We can nudge with language, like the power of ‘We’, not ‘They’. They can be reminders, such as ‘you’re not the user’. Those tiny pushes to attend workshops and demos or facilitatory questions (see below) we use to enable counterpoints. Think of what your Stakeholders need to help themselves and start experimenting AKA release the Trojan Mice (see below).</p><p><strong>Have roles &amp; responsibilities</strong></p><p>Work with your Stakeholders to identify the rich tapestry of skills and knowledge at your disposal. <a href="https://product.club/pages/workshop-tactics">Workshop Tactics</a> has several activities to help you here. Taking the <a href="https://product.club/pages/stakeholder-map">Stakeholder Mapping</a> as read, I’d start with a Skills Market session so you can understand every stakeholders’ skills and abilities. Our findings feed into a session on Stakeholder roles and responsibilities. This will help everyone see the value each stakeholder brings to our extended team. Make sure this work is displayed somewhere prominent — did I say wiki (see above)? Alternatively, the outcome of this work could form part of a Charter of Commitment (see below).</p><p>If you want to jazz things up, create Stakeholder personas — using the <a href="https://product.club/pages/prototype-persona">prototype persona</a> template — and have these in view when you’re working so you can ask ‘What would this stakeholder say?’ when considering complex issues. I guess this would help all of us empathise better with Stakeholders.</p><p><strong>Sign up to a Charter</strong></p><p>Write a Charter of Commitment for you and your Stakeholders. This should set out our expectations for all parties involved — perhaps building off your roles and responsibilities workshop? It might be an idea to reference psychological safety, too. <a href="https://consultantmicro.medium.com/a-charter-of-commitment-ce7374bfaa73">Here’s one I wrote </a>a while ago now, but it should give you a flavour of what’s needed.</p><p>NB: maybe rewrite the <a href="https://retrospectivewiki.org/index.php?title=The_Prime_Directive">Retrospective Prime Directive</a> in future tense and have everyone sign up for this as a simple alternative.</p><p><strong>Set Confidence levels</strong></p><p>Another way to set expectations with stakeholders is to ask ‘What do we have to do for you to feel confident about our work and its progress?’. It’s direct, yes, but the answers you get mean you’re confident you’re delivering what is required and they’ll be confident you’re working on the right things in the right order. I have two approaches here:</p><p>1) write down the confidence levels as outcomes e.g. I can answer questions about our progress at senior leadership meetings. These outcomes guide the team in its work and are on your mind when you talk with your Stakeholders.</p><p>2) create a very simple Stakeholder happiness survey with a max of 3 statements around a) whether a Stakeholder would promote our work, b). whether we’re delivering value and c) the likelihood of product success. Make sure this is completed regularly - perhaps as the last agenda item in any Stakeholder catch-up meeting? <a href="https://consultantmicro.medium.com/gross-customer-happiness-bba8e5f5b557">Here’s an old example</a> from my Agency days, but you get the drift.</p><p><strong>Experiment often</strong></p><p>I love the concepts of <a href="https://whatsthepont.blog/2020/02/09/trojan-mice-in-900-seconds/#:~:text=So%2C%20Whats%20the%20PONT%3F,sense%20of%20the%20problem%2Fsituation.">Trojan Mice</a> and <a href="https://medium.com/mindsea-development-inc/why-your-rat-riskiest-assumption-test-is-the-real-mvp-177d66cde3e1">RATs (Riskiest Assumptions to Test)</a>. At their heart, they are both about learning and gathering data (for measurement/validation) through experiments.</p><p>Use Trojan Mice to introduce the mindset of running multiple small safe-to-fail experiments over testing — and investing in — one good idea to your Stakeholders. RATs allow you to show Stakeholders how to learn about and validate your product before committing to a product or feature that may not be worthwhile.</p><p><strong>Attack the problem, not the person</strong></p><p>We win if we cooperate and use our skills and knowledge to tackle a shared problem — FACT. Run a workshop about defining mutual outcomes together with Stakeholders and use an independent facilitator (see below) — this can be a Product or Delivery Manager from another team. The key to success here is all parties being honest about what they need and then adopting flexibility and creativity when needs are opposed. I’ve found the <a href="https://product.club/pages/five-whys">5 Whys technique</a> can also help Stakeholders and the team here by focusing on the root cause.</p><p>NB ‘Attack the problem, not the person’ could be part of your charter, confidence levels doc/measures, or an extended team value.</p><p><strong>Corkscrew thinking</strong></p><p>Sometimes it pays to turn things on their head. Invite stakeholders to help you shape the perfect working relationship (or working <a href="https://medium.com/@awilkinson/the-power-of-anti-goals-c38f5f46d23c">day as the example used in this article</a>) by first imagining the worst it could be before working on ways to avoid it together. Also see <a href="https://product.club/pages/reverse-brainstorm">Reverse Brainstorming</a> for a similar approach for tactics to keep your product on track.</p><p><strong>Elicit knowledge and input</strong></p><p>The Skills Market exercise should give you a head start here, supplemented by Stakeholder interviews. I’d suggest building on these by asking Stakeholders to draw the system you work within, what the goal(s) of the system are, where the boundaries are, and what rules and policies you need to know and understand. This will give you valuable insight into the system and your Stakeholder’s worldview and the leverage points for change/influence.</p><p>Finally, when you do encounter resistance to your work or approach from a Stakeholder ask yourself this question — what do they know that we don’t know? Then work through the layers of resistance or buy-in (below) lifted from the wonderful <a href="https://www.amazon.com/Behavior-Driven-Development-Cucumber-Specification-Example/dp/0321772636">Behaviour-Driven Development with Cucumber</a>. A veritable goldmine of insight and opportunity awaits you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dbI2GY4HjPAgIMy7" /><figcaption>Dr J K Youngman’s layers of resistance</figcaption></figure><p><strong>Develop and maintain empathy</strong></p><p>Run an <a href="https://product.club/pages/empathy-map">empathy mapping</a> workshop with different stakeholders as the audience and see what assumptions you’ve made. Validated them. Run a <a href="https://product.club/pages/hopes-and-fears">hopes and fears</a> session with your stakeholders to find out their secret goals and what keeps them awake at night. Good, old-fashioned <a href="https://18f.gsa.gov/2016/06/20/build-empathy-with-stakeholder-interviews-part-1-preparation/">Stakeholder interviews</a> can also help build empathy. See if you can shadow a Stakeholder or invite them to try a variation of the <a href="https://whatsthepont.blog/2012/03/10/ricoh-gemba-mat-the-best-of-ohno-circles-gemba-walks-and-employee-engagement/">Gemba Mat </a>and watch the team working in situ (or spend a day attending your ceremonies and meetings). Finally, invite them to lunch with you (when it’s safe). A team that eats together succeeds together :)</p><p><strong>Consider Consequences</strong></p><p><a href="https://www.tech-transformed.com/product-development/">Consequence Scanning</a> provides an opportunity for the team and Stakeholders to focus on the positive aspects of a product while mitigating or addressing potential harm or disaster before it happens. You can gain an alternative perspective by running a <a href="https://product.club/pages/premortem">premortem session</a> with Stakeholders. This will help everyone consider what could go wrong so we can work as a group to stop it from happening. Together, these will give you the steps you need to take to mitigate risk, avoid the asteroids, and deliver business benefits.</p><p><strong>Limit communication in progress</strong></p><p>Be strategic about how and what you communicate with Stakeholders. Share only what’s important, at set intervals, providing space for deep thinking time. This will reduce the cognitive overload for them — and for you — by making things predictable. We developed <a href="https://write.as/footasylum-tech/how-basecamps-shape-up-approach-helped-our-relationship-with-stakeholders">a whole approach</a> around this on my previous team.</p><p><strong>Work in the open</strong></p><p>Host all ceremonies and workshops on public Slack channels (where possible). Open invites all round. Use your public channels to share your progress, notes, and actions. Open your kanban boards to one and all. If you have a wiki, use this to share what you’re doing with the wider world. Publish your lead, wait, and cycle times so that Stakeholders can see the flow of work, the time it takes to put features in customer’s hands, and any waste. If you’ve set confidence levels and measures, share these too.</p><p>NB: think about creating an <a href="https://www.industryweek.com/operations/continuous-improvement/article/21987518/obeya-the-brain-of-the-lean-enterprise">Obeya Room</a> or Virtual Office wall in Miro. We did it at my last place and it worked well.</p><p><strong>Facilitate</strong></p><p>Facilitation enables great Stakeholder collaboration so brush up on your facilitation skills <a href="https://www.amazon.co.uk/Facilitators-Participatory-Decision-Making-Jossey-Bass-Management/dp/0787982660">— this book is awesome</a> and here’s a <a href="https://www.england.nhs.uk/improvement-hub/wp-content/uploads/sites/44/2017/11/2010_handy_guide_to_facilitation_final__low-res_-1.pdf">handy free guide</a>. A simple start would be getting an independent person to host your key Stakeholder workshops or meetings where you have a stake in the outcome. Just doing this will make a massive difference. Assign roles to people at meetings, such as note-taking and recording actions, so key folks can focus on the meeting outcomes. Seek ‘balancing’ views — ‘Are there other ways of looking at this issue? Encourage others — ‘We’ve heard from Finance, what do our friends in Retail think?’. Help people take turns speaking — ‘raise your hand if you want to talk. Andy, you’re first. Dennis, you’re second. Mel, you’re third. Paraphrase to validate views — ‘…it sounds like you’re saying..’. Just read the book/guide already, it will supercharge your team’s collaboration skills.</p><p><strong>Decision-making</strong></p><p>For the important decisions, present clear options linked to long-term consequences including trade-offs that can be made — could these be linked to Consequence Scanning outcomes? Think of it as a menu. You want Stakeholders to be ‘present in the moment’ when they make important decisions. For more complex decisions, consider using a technique called ‘<a href="https://www.behavioraleconomics.com/resources/mini-encyclopedia-of-be/elimination-by-aspects/">elimination by aspects’</a> with Stakeholders. This is where you approach decision-making in the same way you’d buy a car or choose a holiday. What’s the most important attribute? Price. Set criteria — £5000-£7000. Any cars outside the price range are eliminated. Next important, mileage. Set criteria — 35–45 miles to the gallon. Eliminate those outside the range. And repeat. Eventually, you’ll have just one option left, the best.</p><p>NB Record and share your decisions, and the context, somewhere public — did I say wiki?</p><p><strong>Making bets</strong></p><p>Use the <a href="https://www.tonym-v.com/blog/2019/10/2/improve-your-estimations-with-the-equivalent-bet-test">equivalent bet test</a> game to help Stakeholders understand the perils of over and under-confidence with estimation. Essentially, we ask ‘If your own money was at stake, which bet would you take: my estimate that has a 90% chance of being right, or take a spin on a wheel in which there’s a 90% chance of winning”. The aim of the game is to help Stakeholders understand the limits of estimation and the role of probability in delivering products. No more big bets, and it’s fun, too.</p><p><strong>Prioritising requirements</strong></p><p>For capturing what our priorities should be with Stakeholders try a <a href="https://methods.18f.gov/discover/kj-method/">KJ Method workshop</a>. If it’s more about prioritising known requirements with Stakeholders — maybe in a stalemate scenario — try this game. Each Stakeholder is shown two requirements, picked at random, and must choose which one is most important. This is repeated until you have a ranked list in order of votes/importance.</p><p><strong>Agile mindset</strong></p><p>Remember that being ‘agile’ is ‘the capability to respond to challenges quickly’ and not enforcing ‘agile’ thinking and doing on Stakeholders, often against their will. If we focus on the former, we can deliver value to our customers together at a gallop.</p><p><strong>Have a brew together</strong></p><p>The last and sometimes most effective technique is getting together with a Stakeholder for a brew and chat, always with cake, the currency of delivery. If it can’t be in person, then Zoom will do. And take the time to get to know your Stakeholder and the cake they like. They are human, too.</p><blockquote>What do you do to help Stakeholders do a good job? What have I missed? I’d love to hear your suggestions.</blockquote><p>Now go experiment!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad7095d0d163" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to be a good Stakeholder]]></title>
            <link>https://consultantmicro.medium.com/how-to-be-a-good-stakeholder-c075d439cb85?source=rss-605eb46ecf0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c075d439cb85</guid>
            <category><![CDATA[delivery]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[stakeholder]]></category>
            <dc:creator><![CDATA[Andy Tabberer]]></dc:creator>
            <pubDate>Thu, 11 Feb 2021 17:20:04 GMT</pubDate>
            <atom:updated>2023-11-02T17:43:50.696Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k2aqioIhLqNyqTAF6kGJOA.jpeg" /><figcaption>Taking a stakeholder through the customer journey</figcaption></figure><p>There’s a real dearth of articles out there on how to be a good stakeholder — it’s all variations of managing or taming the difficult ones. It made me wonder if many stakeholders know what the role involves and what good looks like. Do they receive training or guidance? Do they even get a choice about whether they want to be one? This led to a bout of empathy for our stakeholder sisters and brothers, sparking an extravagance of further thinking, leading to these very words.</p><p>What follows is my take on the stakeholder mindset we (delivery and product folk) ought to promote, teach and coach. My hope is it helps someone, anyone, approach this vital and difficult role afresh.</p><p><em>Let’s start with a ‘stakeholder’ definition so we’re all on the same page.</em></p><h3>What is a stakeholder?</h3><blockquote><em>a person with an interest or concern in something, especially a business</em></blockquote><p>Let’s add a little context. My focus is on those internal stakeholders who affect or who are affected by a goal or a product or service. They usually represent a business function or team and play a role in ensuring a product or service delivers value to a customer(s). These stakeholders can wear multiple ‘hats’ concurrently, as well as wearing different ones in sequence, depending on the situation. Finally, these stakeholders are human beings, too, lest we forget.</p><h3>What might we expect to see from a good Stakeholder?</h3><p>Think of this as the ‘about you’ part of a job description, the bit that captures the essence of the role and the mindset you possess.</p><p><strong>Trust</strong></p><p>We build trust together, it’s a daily commitment. You start by taking a leap of faith and trusting the work of our teams on day one.</p><p><strong>Reliability</strong></p><p>The business relies on your ability to work together with other stakeholders and product teams toward the business’s goals.</p><p><strong>Advocacy<br></strong> <br>Be an advocate for our product or service, spreading the good word every chance you get. If you serve on any leadership teams, be our voice there, too.</p><p><strong>Approachable</strong></p><p>Make yourself available, invite awkward questions and ask people to challenge your thinking.</p><p><strong>Vested Interest</strong></p><p>Remember you have a stake in our work and a vested interest in the outcome, so do what you can to help.</p><p><strong>Language</strong></p><p>Help us learn the language of your function, team or department. This will help us immerse ourselves in your world and its problems. It will make us understood. It also breeds confidence.</p><p><strong>Confidence levels</strong></p><p>Be clear about what’s needed from us so we’re confident we’re delivering what is required and you’re confident we’re working on the right things in the right order.</p><p><strong>Decision-making</strong></p><p>Make your decisions based on the options we take time to prepare and present so we make better choices for the customer and the business. Always ask to see supporting data or evidence (see below).</p><p><strong>Risk and Planning</strong></p><p>Remind us of our past results on similar products and services, so we don’t make naive predictions and we accept the cumulative risk of something going awry is high. Provide oversight where needed.</p><p><strong>Data-driven</strong></p><p>Let the data decide — where we have it — and remind others we are not the user(s). Acknowledge it’s ok to make assumptions as long as we seek the data to validate these. Accept user research that might challenge your perceptions and understanding.</p><p><strong>Curiosity</strong></p><p>Ask how things are going out of interest. Be an active participant in demos and reviews, too. Show you want to know how things work.</p><p><strong>Delivering value</strong></p><p>We’ll help you identify, define and realise the business benefits you crave. In return, you’ll help us by providing expertise, feedback and support so we deliver value to the customer in the quickest time possible.</p><p><strong>Problems, not solutions</strong></p><p>Together, we act as proactive problem solvers; but first, we must fall in love with the problem. You provide as much context and detail around your problem and the benefit you seek as possible. This way, we are more likely to find the right solution later on.</p><p><strong>Mutual outcomes</strong></p><p>Embrace cooperative conflict, so the problem becomes the opponent we must join together to defeat. We can then create mutual outcomes that consider all our needs and goals, so we both win.</p><p><strong>Readiness to experiment</strong></p><p>Resist the temptation for big bang releases as these are loaded with risk. Instead, let’s hedge; making small, frequent outcome-based bets which help us deliver value to customers quickly. And we learn about customer needs as we go.</p><p><strong>Empathy</strong></p><p>You understand and share the feelings and needs of the customer, other stakeholders, and the team. We promise to remember empathy is a two-way street.</p><p><strong>Work in the open</strong></p><p>Everything we do is public and participatory — Slack, emails, docs, wikis, meetings. You make sure important information gets to the right people at the right time because this is key to building great products and services for customers. No sneaky back channels, no sir-ee.</p><p><strong>Goal-focused</strong></p><p>Our work is always focused on achieving our business goals and you ensure we are aligned together in this pursuit.</p><p><strong>Expertise</strong></p><p>We need to tap into your knowledge and your specialist skills so we make the best product or service possible. You help us understand the local landscape and its boundaries. You explain any policy or rules we need to know. Think of yourself as our guide on this journey.</p><p><strong>Support and guidance</strong></p><p>We share people, resources and data. You hold other stakeholders to account and help resolve conflict and align interests and priorities if needed. Together, we remove blockers, manage dependencies and mitigate risks.</p><p><strong>Communication</strong></p><p>We honour and protect information and we work together to make sure we communicate effectively. If you need more or less communication, just say, and remember we need to hear from you, too.</p><p><strong>Prioritisation</strong></p><p>Requirements are prioritised based on maximising value to (internal and external) customers while minimising the cost to the business. The outcome we seek is an evolving roadmap which we use to manage and align all stakeholders with clearly defined features that move us closer to our product goal or vision.</p><p><strong>Listening</strong></p><p>Be whole-minded when listening to ideas, research, different ways of working, and hear what others have to say. This also builds trust, empathy and a more productive workplace.</p><p><strong>Optimisation</strong></p><p>We optimise the whole, not just individual functions or teams. This means we focus, laser-like, on what is best for the performance of the system as a whole.</p><p><strong>Psychological safety</strong></p><p>You are happy to see safe-to-fail experiments because you know we’ll learn something new. You encourage diversity of thinking, seek feedback and critique of your ideas, help to legitimize differences between teams and people and find the common ground for robust decision-making.</p><p><strong>Money talk</strong></p><p>You help us work within the budget and navigate any financial constraints. You’re the expert here, thank God.</p><blockquote>This is the Stakeholder mindset IMHO. It’s tough gig, for sure!</blockquote><p>Finally, this is not meant to be an exhaustive list — and I’d love to hear your suggestions, dear reader. You’d never expect a stakeholder to exhibit all of these things daily, just at one time or another. These behaviours aren’t mutually exclusive; one act might cover many behaviours — think holistic, not atomistic.</p><p><a href="https://consultantmicro.medium.com/helping-our-colleagues-to-be-good-stakeholders-ad7095d0d163">Part two</a> of this blog post will follow shortly. Here, I’ll highlight a few ways we can help and enable stakeholders to be good and do the right things. It would be rude not to, wouldn’t it?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c075d439cb85" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dial M for McKinley]]></title>
            <link>https://consultantmicro.medium.com/dial-m-for-mckinley-fbf02fa66509?source=rss-605eb46ecf0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/fbf02fa66509</guid>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[agency]]></category>
            <category><![CDATA[microfiction]]></category>
            <category><![CDATA[fiction]]></category>
            <category><![CDATA[agencylife]]></category>
            <dc:creator><![CDATA[Andy Tabberer]]></dc:creator>
            <pubDate>Mon, 29 Jul 2019 12:32:42 GMT</pubDate>
            <atom:updated>2023-01-07T10:05:15.441Z</atom:updated>
            <content:encoded><![CDATA[<p>Dipping my toe into microfiction. This story was inspired by a character I encountered many years ago. It is pure fantasy, the revenge you dream of but you know will never happen, obvs. Enjoy (hopefully).</p><h3><strong><em>If you have a difficult client that just won’t pay, dial M for Mckinley…</em></strong></h3><p>“I’ll never ppaayyyy!” shrieked Joe. It was the sort of shriek that could cut through polite conversation, reinforced steel and the hopes and dreams of men. He flipped the phone to his good side. “You’ll do it for free or I’ll take my money elsewhere” he shrilled. Victory was his.</p><p>“Ok, Joe. You win again” said the dismembered voice on the other end of the phone.</p><p>“You win again…” trilled the cocksure Joe, the Bee Gees being his go-to band.</p><p>The voice cut in. “Tell McKinley I said hi”.</p><p>And with that, the line went dead.</p><p>The tone bleeped coldly for a short while before Joe replaced the receiver. He stood up and started to dance, slowly but surely. His hips began to gyrate, quite naturally, as he’d done this dance before. He brought the routine to a close with a little light groin thrusting. He always did. He high-fived nobody in particular and retook his seat. He reached for his journal, where he recorded such victories. Quietness descended. A nagging doubt surfaced. Was the room beginning to shrink, he thought? Fear slowly squeezed his heart. He became aware of his own breathing. He held his breath. The breathing continued.</p><p>“McKinley?” whispered Joe.</p><p>“Yes” came the soft reply. McKinley stepped out of the shadows. His calmness filled the room. This was no happy hippy calm. This was the special kind of calm that very violent men have. That calm that says ‘I will fuck you up’.</p><p>Joe gulped.</p><p>McKinley smiled.</p><p>“What do you want?” squeaked Joe, losing his bluster by the millisecond.</p><p>“Your balls in the drawer,” said McKinley in a voice that could stop traffic, hearts, time, and bullshit.</p><p>“Eek!”</p><p>“Dues, Joe, have not been paid. That just won’t do”</p><p>“I’ll do anything. McKinley. Anything”</p><p>“Balls! In! The! Drawer!” barked Mckinley. Each word cracked like gunfire — to Joe at least.</p><p>“I’ll pay. I’ll pay. Take my money, it’s in the safe. Take all of it!”</p><p>“Too late for that. Now, Joe, if you could strip from the waist down, while I remove these soft-close slides off this here filing cabinet.”</p><p>McKinley knelt down. “Forgive the sins of my hands, Lord” he whispered. Joe passed out. He slid down his chair.</p><p>“Probably for the best,” said McKinley before launching a glorious, bloodcurdling practice slam.</p><p>BANG, went the drawer.</p><p>BANG. BANG. BANG.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbf02fa66509" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weekly Notes #5]]></title>
            <link>https://consultantmicro.medium.com/weekly-notes-5-9ab9c9ae710b?source=rss-605eb46ecf0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ab9c9ae710b</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[delivery]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[digital]]></category>
            <dc:creator><![CDATA[Andy Tabberer]]></dc:creator>
            <pubDate>Fri, 21 Jun 2019 16:45:45 GMT</pubDate>
            <atom:updated>2024-04-12T07:02:02.047Z</atom:updated>
            <content:encoded><![CDATA[<p>Well, we made it, dear reader, to Friday, Fri-yay, or as the French call it, Le Weekend. Expect some flow, profundity (not mine), meet-ups magic and my hopes for future work. Stay strong, dear reader, it only takes a minute, girl (or boy), to read this blog.</p><h3>Let it flow, people</h3><p>I finally understand how to <strong>draw flowcharts</strong> thanks to my pal <a href="https://twitter.com/PixelBeardWill"><strong>@</strong>PixelBeardWill<strong> </strong></a>. These are so invaluable for writing acceptance criteria and for building in quality into our delivery of requirements. We’re adopting these are part of our <strong>minimum standard</strong> for all our work as part of our Delivery Essentials* work.</p><p><em>Do you write flowcharts as part of your user stories? How’s that going for you?</em></p><p>*Coming to a shop near you soon.</p><h3>Draw the system</h3><p>We’re about to <strong>map out our system </strong>together at PixelBeard so we understand at a high level how work flows through our system (see image below). We’ll then work together to identify any barriers so we can improve our cooperation and increase the flow. I am <strong>very excited</strong> about what happens here — I am, really. I have a feeling that we’re going to learn a lot about what we each do within the system and each other. Some <strong>surprises in store</strong> for sure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*McB6zHy4uVcOTpXSAo7ghA.jpeg" /><figcaption>Let it flow, let it flow, let it flow.</figcaption></figure><p><em>Have you drawn your organisation as a system? What effect did that have on your understanding of workflow and barriers?</em></p><h3>What I am reading?</h3><p><a href="https://www.amazon.co.uk/Four-Days-Dr-Deming-Reengineering/dp/0201633663">Four Days With Dr. Deming — A Strategy for Modern Methods of Management</a> AKA the <strong>System of Profound Knowledge</strong>. Essentially, everything you think about work is wrong and this easy to follow <strong>masterpiece </strong>is your guide to achieving true cooperation, process improvement, and long-term productivity. Here are a few <strong>epiphany-inducing</strong> statements that Deming has gently cuffed me with along the way:</p><p><em>Sure we want best efforts, but best efforts must be guided by theory and knowledge.</em></p><p><em>Quality is made in the boardroom and must be built into production.</em></p><p><em>Cease relying on inspection.</em></p><p><em>If the system is stable any real improvement must come from action in the system, which is the responsibility of management.</em></p><p><em>We need a new theory of cooperation, with the focal point of our joint work set through voluntary standards. With cooperation, we all win.</em> NB he did not use the C word…Collaboration. *Rubs chin* interesting…</p><p><em>Leadership is…</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SWByXe3KgR6tok5B8YjMbw.jpeg" /><figcaption>Dr Deming nails it. FACT.</figcaption></figure><p><em>Do you have profound knowledge of your system? How do you use this for good?</em></p><h3>What do I want to be working on?</h3><p>This is something new I’m trying. Kudos to <a href="https://twitter.com/neil_vass"><strong>@</strong>neil_vass<strong> </strong></a>for the suggestion :)</p><p>Using the theory of variation so I can make control charts so I can see how our subsystems are performing. I am fascinated to see if I can take data from a system, analyse and plot this and see if any special causes are indicated or whether everything is within common causes of variation. Time — that precious Agency commodity — seems like a good place to start.</p><p><em>What would you like to be working on? And why?</em></p><h3>Deliver Sessions — North West repping 123…</h3><p>It was lovely to meet up with the NW Deliver Sessions folks on Tuesday. Heavy discussions around topics for future events with ‘Feedback’ seeming to suggest itself as something we all need to do better. I may even step up for that one. You can find out more about these events here -&gt; <a href="https://www.meetup.com/Deliver-Sessions/">https://www.meetup.com/Deliver-Sessions/</a></p><p><em>Do you go to a meet-up? If so, why?</em></p><p>I’m off to see Tears for Fears in a forest. We’ve planned our getaway so we avoid traffic. Ultimate delivery geeks or just plain wrong? You decide :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ab9c9ae710b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weekly Notes #4]]></title>
            <link>https://consultantmicro.medium.com/weekly-notes-4-386dd546fb09?source=rss-605eb46ecf0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/386dd546fb09</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[delivery]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[dpm]]></category>
            <dc:creator><![CDATA[Andy Tabberer]]></dc:creator>
            <pubDate>Fri, 14 Jun 2019 16:51:34 GMT</pubDate>
            <atom:updated>2020-12-02T12:59:00.956Z</atom:updated>
            <content:encoded><![CDATA[<p>Despite the limiting factor of time, I’ve managed to fire off an adequate set of notes. <strong>Less exuberance, more substance?</strong></p><p><em>Read on, dear reader, read on, for you make me whole…</em></p><h3>Boiled Frog Syndrome -</h3><p>Last week it was the Cobra Effect, this week’s animal in the spotlight is the humble frog aka <a href="https://en.wikipedia.org/wiki/Boiling_frog"><strong>Boiled Frog Syndrome</strong></a>. The story goes, if you toss a frog into boiling water it would hop out sharpish like. If you, however, place the frog in tepid water and boil it slowly the frog won’t notice until it is too late. Think of it as a metaphor to describe circumstances where we unwittingly accept a dangerous situation because we don’t notice or sense the gradual change over time. This made me think of <strong>toxic cultures</strong> and how they are formed in the workplace. You cannot remember when toxic behaviour was normalised because it happened over a long period of time. Well, at least I have a name for it now :)</p><p><em>Have you been that frog in the saucepan? Did you hop out?</em></p><p>Ps. what is it with Frogs and business fables? If we’re not boiling them, we’re eating them first!</p><h3>It’s good to talk -</h3><p>This week reaffirmed my view that if you need to have a difficult conversation then it’s <strong>good, nay, better to talk</strong>. More and more people seem to favour written communication at work — whether IMs or email — which just seems to lend itself to confusion and entrenchment when things get difficult. So I say unto you, if you think that your message might be taken out of context or it risks knocking a relationship out of kilter, <strong>take a deep breathe and make that call. </strong>Even better, meet people face-to-face if you can.</p><p><em>When was the last time you had a difficult conversation? How did you feel afterwards?</em></p><p>Ps. there seems to be a direct correlation between money, delays and difficult conversations in my world…how about yours?</p><h3>What I’ve been reading -</h3><p>I’ve just finished <a href="https://en.wikipedia.org/wiki/Donella_Meadows">Donella H. Meadows </a>— Thinking in Systems: A Primer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0FFyhVJQNubBIaUoEyoBvQ.jpeg" /><figcaption><em>Here’s Donella (above) with her towering intellect flickering behind her ready smile. Another great photo I think. Nice use of the blurred effect as you asked.</em></figcaption></figure><p>This book has and continues to have a<strong> profound effect</strong> on me. I recognise system archetypes I’ve orbited or been part of, in the present and the past. It’s not always pleasant reading but <strong>it is enlightening</strong>. Her words on the ‘drift to low performance’ archetype have helped with handle personal bad news and cope with the more general eroding of the goal of morality we are experiencing both here and across the Pond. I guess there’s a bit of the ‘Escalation’ archetype involved here with the current political situation, too, leading to smear campaigns and in-the-gutter political point-scoring.</p><p><em>But, I digress…</em></p><p>The <strong>most important lesson </strong>of this week has been the realisation that missing information flows is probably the most common cause of system malfunction in the Digital Agency world. How often do we water-down, obfuscate or suppress important information because how it will be received is more important than the information itself? This allows people to <strong>swerve the consequences</strong> of their actions and decisions and keeps up the pretence that everything is ok. We all know where that leads…</p><p><em>What important but overlooked or ignored information would you provide or restore to folk? How would you make that compelling?</em></p><h3>Note taking -</h3><p>I’m trying out a new way of <strong>managing my work note</strong>s courtesy of @thekieran. He’s the poetry-writing, UFC-fighting, system-thinking Scots DPM explaining the method in his own words:</p><p><em>“When you start a new notebook, reserve the first 3 pages for a contents page. Then number each page after that, just a little number in the bottom corner will do. The only extra work after that is titling and dating your notes and adding them to the contents page once a day.”</em></p><p><em>Do you using a notebook method you’d be willing to share? Did you manage to keep it up for long?</em></p><p>Right, time to do one. I am going out for Tacos and beer this very evening, where my friend and I shall be masters of all we survey :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=386dd546fb09" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weekly Notes #3]]></title>
            <link>https://consultantmicro.medium.com/weekly-notes-3-e706e05cd938?source=rss-605eb46ecf0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/e706e05cd938</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[digital-project-manager]]></category>
            <dc:creator><![CDATA[Andy Tabberer]]></dc:creator>
            <pubDate>Fri, 07 Jun 2019 17:53:35 GMT</pubDate>
            <atom:updated>2019-06-07T17:53:35.076Z</atom:updated>
            <content:encoded><![CDATA[<p>Fire in the hole, dear reader, we have made it to week three. A hat trick no less. Expect flights of fancy, exuberance and a mixed format.</p><h3>Distributed wobbles aka mental health support -</h3><p><strong>Mental health</strong> and building resilience are widely discussed now and rightly so. This phrase came up today when I was talking to an Agency owner — and he’s one of the good ones. Essentially, many of us can manage our mental health because we have <strong>someone to talk with </strong>who also experiences peaks and troughs, highs and lows. And as we don’t wobble at the same time we can help each other hence the phrase ‘Distributed Wobbles’.</p><p><em>Are you part of a ‘Distributed Wobbles’ support network? How does that work for you?</em></p><h3>Hot pink based tension diffusion -</h3><p>Whenever inline comments or feedback start getting spicy in a document or email I always switch my font colour to <strong>Hot Pink</strong>. You’d be amazed at how good a bit of Hot Pink is at diffusing tense situations. Try it, it won’t let you down.</p><p>In fact, whenever things get hairy, always <strong>go kinder and softer </strong>so eventually, it makes it too hard to keep up a cold front or snarky tone.</p><p><em>What your go-to feedback font? What does that say about you?</em></p><h3>PWAs are the future -</h3><p>I’ve been learning a lot about <strong>PWAs (thanks Ben Brookes)</strong>, which stands for Progressive Web Apps — and not Programmers With Attitidue (disappointingly). Think website that’s been turned into an application, a limited version of which is available offline. PWAs promote accessibility and better security, too. What’s not to love? This<a href="https://developers.google.com/web/showcase/2017/lancome"> Lancome </a>case study is worth a butchers if yer not convinced like. Here are <strong>the key stats</strong>:</p><ul><li>17% increase in conversions</li><li>53% increase in mobile sessions on iOS</li><li>8% increase in conversion rates on recovered carts via Push Notifications</li></ul><p><em>Do you build PWAs? How’s that working for you?</em></p><h3>Delivery Essentials -</h3><p>I’m working out the <strong>minimum documentation</strong> we need on any project. I know some folk get upset about documentation, but it is needed. So, I’m writing something called Delivery Essentials, which sounds like a shampoo but will be <strong>a nifty guide </strong>to what is needed to meet everyone’s needs on a project, from team members through to stakeholders. Might even share it, like, open source it.</p><p><em>What are your Delivery Essentials? Would you be willing to share them?</em></p><h3>What I’ve been reading -</h3><p>More systems thinking shizzle with the powerhouse that is<a href="http://donellameadows.org/"> Donella H. Meadows</a>. What intrigued me most this week were the characteristics of a <strong>highly functioning system</strong> — namely, resilience, self-organisation and hierarchy. The ‘H’ word gets a hard time these days in some circles and this probably explains the resistance to self-organisation (and the removal of hierarchies) in some orgs. Donella explains that the <strong>hierarchy’s purpose</strong> — in a system — is to help the originating subsystems — or teams — do their jobs better. Many hierarchies forget this and their supporting function highlighted in the image below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jCUJHGhADCB6MmcFY1RJcw.jpeg" /><figcaption><em>More wisdom from Dana H. Easy to see why most people have a downer on hierarchies when they don’t do what they are meant to do within a system/subsystem relationship :( ps Don’t you think my photography is really coming along?</em></figcaption></figure><h3>Dead Cobras aka the Dead Cobra effect -</h3><p>Probably <strong>my highlight of the week</strong> was reading this <a href="https://whatsthepont.com/2019/05/19/campbells-law-and-why-outcome-measurement-is-a-dead-cobra/">blog </a>— Campbell’s Law and why Outcome Measurement is a <strong>Dead Cobra</strong>. I loved it primarily for introducing me to the Cobra Effect, where an attempted solution to a problem makes the problem worse. On that note, I’m thinking of creating a new time tracking product called Dead Cobra.</p><p><em>What do you use to track time? Do you ever see perverse outcomes? Why might that be?</em></p><h3>Internet friends -</h3><p>Finally, I wanted to <strong>raise a glass</strong> to ‘Internet Friends’, those people on Slack and Twitter who indulge my random thoughts, flights of fancy, loose systems talk and bizarre music recommendations. I’m looking at you <strong>@thekieran</strong> and <strong>@ThatIanMay</strong>. You have kept me sane.</p><p>I hope someone somewhere finds this useful. Ps, I’m off to #CampDigital on Wednesday. Say hello if you’re there but approach downwind and no eye contact, please.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e706e05cd938" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weekly Notes #2]]></title>
            <link>https://consultantmicro.medium.com/weekly-notes-2-cd76b0d918df?source=rss-605eb46ecf0b------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd76b0d918df</guid>
            <category><![CDATA[digital-agency]]></category>
            <category><![CDATA[weekly-notes]]></category>
            <category><![CDATA[digital-project-manager]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Andy Tabberer]]></dc:creator>
            <pubDate>Fri, 31 May 2019 16:14:45 GMT</pubDate>
            <atom:updated>2019-05-31T16:14:45.174Z</atom:updated>
            <content:encoded><![CDATA[<p>Well, I’ve managed to dispatch another set of weekly notes. Wow, this could become a thing. Ps there’s a few <strong>unnecessary flourishes</strong> but I am feeling exuberant today, so indulge me, dear reader :)</p><h3><strong>What I’ve been reading -</strong></h3><p>This week has been <strong>dominated</strong> by <a href="https://www.amazon.co.uk/Thinking-Systems-Primer-Donella-Meadows/dp/1603580557/ref=sr_1_1?crid=1QSJH6TQEMOW5&amp;keywords=donella+meadows+thinking+in+systems&amp;qid=1559313747&amp;s=gateway&amp;sprefix=donalla+%2Caps%2C847&amp;sr=8-1">Thinking in Systems: A Primer by Donella H. Meadows. </a>I love the simplicity of the explanations and the thoughtfulness of the author. The bathtub thinking it promotes to understand systems has really helped me get my head around what is a difficult subject. I love stuff like this, <strong>stuff that challenges me to think</strong>, that I don’t always get the first time, that compels me to keep reading until that lightbulb moment when it finally clicks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*31QbhQs3T0b37jO-LT9w7Q.jpeg" /><figcaption>A deliberately blurred image to convey my eyes attuning to seeing the world as a systems thinker.. or a having my eyes tested for a pair of systems thinking glasses but they’re not quite in focus yet. Either way, you get the picture…or not.</figcaption></figure><p>I’ll leave you with a bit of Dana wisdom <em>— that’s what those in the know call Donella :). </em>Think about this, which made my tiny mind pop like a Poundshop party popper.</p><blockquote>‘If A causes B, is it possible B also causes A?’</blockquote><p>I’m still rummaging around <strong>The Hidden Life of Trees: What They Feel, How They Communicate by Peter Wohlleben. </strong>My evergrowing love of Trees continues unabated. So many connections with humans and how we thrive and survive. One thing that caught my eye was the concept of the <strong>Pioneer Tree</strong>. These are the trees that strike out on their own, they live outside the forest and like starting new communities. They love the forest and that, its comforts and social interactions, its shade, but they definitely prefer to live on the outside and pioneer in the open space. It’s more dangerous and less stable, but they grow a lot quicker.</p><p><em>What type of tree are you? A pioneer or a forest dweller? I’m deffo a pioneer, but that’s not to say I don’t love and respect those that like to live in the forest.</em></p><h3>What a noob aka You’d think I’d know better -</h3><p>I made a <strong>BOO BOO</strong> this week, ripping the plaster off a healing wound. In my haste, I sent an email about costs which didn’t read well and, as a result, booked myself in for a short working holiday at the Hotel De Client Confusion. Now a further meeting is needed to untangle the ball of confusion I have made. So, next time you (or I) need to send something important, get someone else cast their eye over it. <strong>IT SAVES TIME.</strong></p><h3>There’s nowt as kind as folk -</h3><p>A rant of mine on that there Twitter about <strong>Steve Jobs wannabes </strong>sparked a conversation with a Twitter friend who I’ve yet to met in real life. They — I won’t name them — always look to offer balance when I rant about Agencies and paint the digital sector in a kinder light — which it needs for sure. They are a reminder that <strong>kindness is better than acerbity</strong>. Something I need to do better.</p><p>I hope to meet with them at the <a href="https://www.wearesigma.com/campdigital/2019/"><strong>#CampDigital event</strong></a><em>.</em></p><p><em>Are you going to Camp Digital, dear reader? Say hello, but expect no eye contact and massive awkwardness.</em></p><h3>A definition of done -</h3><p>Will we ever be done with the definition of done? I think not, but this is one of the best I’ve heard for a while via Mike Burrows over yonder on Twitter -&gt; <strong>A good working definition of “Done”: Someone’s need was met </strong>-&gt; <a href="https://twitter.com/asplake/status/693120263446269952">https://twitter.com/asplake/status/693120263446269952</a></p><p><em>Can you think of a better one, my solitary friend?</em></p><p>I hope someone somewhere finds this useful. I’m off for a rest, and then a wedding reception tomorrow evening — yes, on the same night as the Champions League final. I shall keep my phone sheathed throughout the proceedings, but will others?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd76b0d918df" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>