Tag: agile leadership

Is Agile Shaping Your Culture by Accident or by Design

In the first article of this series, we shared the specific challenges we witnessed when launching an Agile Leadership Program at a leading financial services company. In the second article, we shared our thinking around the principles that informed our approach. Now in this third and last article of the series, we share the top lessons we learned alongside the participants and sponsors of this journey.
 

What we would keep doing

    1. Preserve the spirit of wholehearted co-creation. As a consulting firm, we have our proven methods and tools. However, we chose to be highly vigilant and not drink our own Kool-Aid. Show me practitioners who have only a handful of red lines and are willing to adjust everything else on their book, and I will show you professionals who truly put clients first.
    2. When working with top leadership, there is a weight attached to their positions – conscious or unconscious. We genuinely strive to connect from human to human, scrapping all titles. Now we insist more often that leadership journeys begin with coach and coachee sharing a virtual coffee, free from agenda, simply for the sake of connecting.
    3. We will continue to act on feedback as if our lives depended on it. This is no minor task. The distinction between integrating feedback and accepting to do everything your client asks for is not commonly understood. It takes serious preparation.
    4. We will always honor the past AND look forward with curiosity.

Is Agile Shaping Your Culture by Accident or by DesignAllow me to emphasize this fourth lesson for a moment. Agile is often presented as the remedy that will heal all corporate ailments. This is overly simplistic, and some may even consider it an insult to their intelligence. However, the natural tendency of this person is to sway to the other end of the pendulum and negate any benefit of the new way of working. This, too, is foolish.
Many leaders feel trapped in a false dilemma because they think they are facing an either-or choice when we present the gap ‘From-To’. Either we are pro-command and control OR anti-command and control. When we introduced polarity thinking, this subliminal tension dissipated. We honor where we are coming from AND (not OR) acknowledge that moving forward, we need to do some things differently. In Dr. Marshall Goldsmith’s words, “What got you here won’t get you there.” It was no longer a problem with a single solution (agile or bust) but rather a polarity to manage. For leaders, that meant they needed to maximize the time spent on the benefits of agile and the benefits of what preceded it, instead of viewing agile as a new, unquestionable dogma.
 

If we could take a Mulligan…

If you’re not familiar with golf, the term Mulligan means a ‘do-over’. It’s a second try given to a player, without penalty, after a first stroke that did not go well. So, if we were granted a Mulligan, there are some things we wouldn’t have done or that we would have done less.
 

What we would do differently

  1. We are executive coaches, so we didn’t think it was necessary to connect with the agile coaches in the organization. We figured that our work was different. In hindsight, this was a missed opportunity to join forces. In future assignments, we would make it a point to connect the ‘do-agile’ and ‘be-agile’ parties.
  2. We took the sponsor’s brief for granted. Our prototyping, co-creating approach saved the day in the end, as it allowed us to pivot from the original learning journey design. Nevertheless, in the future, we would push for an if-then scenario planning. If the brief is accurate, we will deploy plan A; if it isn’t, we will go with plan B.
  3. We used an in-house feedback tool. We knew it was not ideal and we wouldn’t compromise on it again. A robust feedback tool provides participants excellent traction for change. It is paramount to select it with care.
  4. The preliminary design allowed several weeks between group workshops, and only two individual coaching sessions per participant seemed sufficient. Experience tells us that it is far more effective to shorten the time between team sessions to keep the cohorts focused and on-task. It would also be wise to dedicate a higher number of individual coaching sessions than we had initially planned.

 
These are the lessons we learned behind the scenes of one of the boldest adoptions of agile in a non-tech industry. Are there any lessons that you would like to share around leadership development in an agile context? Have you had similar experiences or were they entirely different? Let us know in the comments! We would love to have a mutual learning conversation with you.