<?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 Alon Gazit on Medium]]></title>
        <description><![CDATA[Stories by Alon Gazit on Medium]]></description>
        <link>https://medium.com/@gazitalo?source=rss-764221b576e9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*PVOs86NiRxX51j4K.</url>
            <title>Stories by Alon Gazit on Medium</title>
            <link>https://medium.com/@gazitalo?source=rss-764221b576e9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 17:44:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gazitalo/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[Agilists, beware of the Missing Coach Syndrome]]></title>
            <link>https://medium.com/@gazitalo/agilists-beware-of-the-missing-coach-syndrome-ed75b4915219?source=rss-764221b576e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed75b4915219</guid>
            <category><![CDATA[coach]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Alon Gazit]]></dc:creator>
            <pubDate>Thu, 19 Nov 2020 14:22:25 GMT</pubDate>
            <atom:updated>2020-11-19T14:22:25.001Z</atom:updated>
            <content:encoded><![CDATA[<p>You just completed an intervention; it was a long winding process but the positive results are obvious and spirits are high. During the following retrospective you facilitate, or whatever other processes you employ to collect feedback and get better, everybody is celebrating the great decisions that made such a difference. As the meeting is about to conclude, and even though you are fully present, you realize there is one thing that is missing from their celebrations and acknowledgments and that is… you. Voila — you and your team are exhibiting the Missing Coach Syndrome.</p><p>Before you think “I don’t need acknowledgments, I know my worth”, remember this- it is not about your ego. You are selling a service and if your value is not evident, no one will bother buying it. It does not happen every time, but chances are that if you are coaching teams, you already experienced some version of this more than once. The funny thing is, the better you are as a coach, the higher the likelihood of this happening to you. Unfortunately, this is also true for the worst coaches, but that is a different story…</p><p>By definition, our job as coaches is to support our teams’ growth by helping them find their path to develop into better versions of themselves. ‘Them’ and ‘their’ being the keywords! Even if, based on our knowledge and experience, we think that we know what is the right thing to do, which is often the case, we are not supposed to tell our cochees what it is. If we tell them what to do, we betray the coaching mandate they gave us, not to mention we risk being wrong. We are not walking in their shoes so we cannot know in advance what is going to work for a specific team, working on a specific product, at a specific time and context.</p><p>What is the coaching mandate? From highlighting patterns to encouraging introspection and retrospection to asking powerful questions, coaches are there to help search for answers to problems that are relevant to a unique set of parameters. This is exactly the point! We cannot know what the answer is until the current team came up with it and until they proved it to be right by solving real issues. But then again, this is where the problem lies. We do all our “magic”, asking a question here, nodding there, observing from some distance, listening attentively to the conversation and atmosphere in the room, encouraging experimentation and gradual measurable improvement, pushing our teams gently to hold certain discussions and make the decisions that will lead their growth. And still, it is easy for the team to think “We made that decision and it turned out great, we must be awesome” (which is true!), but aren’t they forgetting all the hard work, experience and attentiveness that went into nudging them in the right direction?</p><p>I would like to offer the following analogy; coaching is like exercising. If you exercise regularly you “only” feel good and then it is easy to forget why you spent the time and energy that got you there. It is only when you think you can keep feeling good without training, that you realize it does not work that way. And if we take this analogy one step further, maybe what is needed to make the coach reappear, is some sort of “training record” that will keep track of everything that happened: small process changes, experiments and interesting interventions that were performed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ux1MFvkDsiRkxAjw-OQRpw.jpeg" /></figure><p>Lately, I started writing Agile journeys for the teams I support. Just a few words every month, drawn from my notes, to make the gradual maturation process visible. I do this first and foremost for myself, but also for me to share with my teams, stakeholders and sponsors. I hope this will make me less likely to suffer from the Missing Coach Syndrome. Wish me luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed75b4915219" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>