Over a million developers have joined DZone.

Are You a Thief-Coach? Agile Coaching by Invitation and Not-Safe-To-Fail Situations

DZone's Guide to

Are You a Thief-Coach? Agile Coaching by Invitation and Not-Safe-To-Fail Situations

While Agile Coaches should help to facilitate the Agile process within their teams, sometimes they can over coach and take away a team's ability to self-organize.

· Agile Zone ·
Free Resource

The Agile Zone is brought to you in partnership with Techtown Training. Learn how DevOps and SAFe® can be used either separately or in unison as a way to make your organization more efficient, more effective, and more successful in our SAFe® vs DevOps eBook.

Don’t do this to your teams.

Remember when you were a kid and were in the middle of doing something amazing that you were excited about, and an adult came along to tell you what you should do next?

Remember how deflating and frustrating that was? Remember how you felt demotivated to move forward as your amazing project was inadvertently stolen from you and you felt a lack of ownership and pride?

Coaches, this is what happens to teams and people when you offer help that they haven’t asked for: you are stealing from them. You are a thief-coach.

You’re assuming that your insights are somehow new to your audience, instead of respecting that they may (and probably have) already considered what you have thought of, and have tried some variation (or are about to try). If you offer a solution that they were already about to try, you are taking away their self-organization – because now that idea is no longer theirs. It just became yours.

Even offering coaching observations to someone who hasn’t asked for them can be damaging. Doing so can come across as condescending or ignorant of the full picture of what is happening in a team. It can cost you credibility, and being credible is one of the most important traits you need to possess to be an effective coach. If your observations fail to resonate with your audience – or are just plain wrong – it can alienate you from the team, making future coaching interactions less impactful.

This all begs the oft-recurring question: “If I’m not invited, how do I coach?”

I prefer to deal with this issue from a delivery perspective, and reframe the question into a different format:

How does a coach balance ensuring successful delivery against giving teams the space to safely fail?

The answer should not be “coaches aren’t responsible for delivery” – in my experience, coaches can certainly be responsible for delivery without compromising their commitment to the team’s health and safety; in fact, it is essential that coaches do feel that responsibility if they want to coach in the most effective way.

When coaches do not consider themselves responsible for delivery, it becomes harder to identify those experiments that really are “safe to fail” versus those that are not. Teams may go on failing for too long, with too many things, before leadership and the team realize that essential course correction is necessary to save the project and restore trust with the customer.

To determine whether a team is trying something that is safe to fail at, a coach who cares about delivery should ask the following two questions:

  • If this experiment fails, is the impact on delivery acceptable?
  • Do we feel comfortable sharing this experiment with our customer?
  • If the answer to either of these questions is “no” then this is not a safe-to-fail experiment. Even more, you may have a serious problem – one that, as a trusted coach with credibility, with context and strong relationships within the team, and with skin in the game for delivery, you can more quickly and effectively recognize and then help the team to correct.

    In summary: if you are a coach who is deeply invested in the successful delivery of your team, the issue of coaching by invitation becomes less critical. You would already have established your value to the team over time by being present, engaged, listening, and asking good questions. That way, you can more readily recognize a serious problem (and avoid making mountains out of molehills).

    When the time comes for addressing a serious problem, you are not lamenting your lack of invitation (or worse, trying to coach without one) – you will already be so valuable to the team that your opinion on how to improve a not-safe-to-fail situation will be thoroughly informed, credible, and appreciated.

    Adopting a DevOps practice starts with understanding where you are in the implementation journey. Download the DevOps Transformation Roadmap, brought to you in partnership with Techtown Training

    agile coaching ,agile teams ,agile

    Published at DZone with permission of

    Opinions expressed by DZone contributors are their own.

    {{ parent.title || parent.header.title}}

    {{ parent.tldr }}

    {{ parent.urlSource.name }}