Coaching

Agile Coaches - Becoming a Trusted Advisor

Agile Coaches - Becoming a Trusted Advisor

As I think about the Agile Coaching Growth Wheel Advising (consulting, consultative) stance, I don’t think it’s initially something you automatically do as an agile coach. Instead, I think it’s something you are either invited to do or become over time.

That aspect makes it quite different than some of the other stances. For example, Coaching, Facilitation, or Guiding Learning includes the invitation and empowerment with the role.

I also think the Advising stance aligns with the Leader stance; in that, you must be more intentional in becoming an Advisor—

  • It’s something you step into and earn over time.

  • It has more risk associated with it than the other stances, thus requiring more courage and resilience.

  • And finally, it places more pressure on your Self-mastery and Leader stances.

This may be why many coaches struggle so much with the stance. Not only from a skills perspective, but many seem afraid of it—so they find excuses to avoid operating as an advisor. And they’re not necessarily wrong. 

To help empower more coaches to become comfortable with advising, I thought I’d share some ideas around elements supporting their evolution.

Measuring your Impact & Value as a Leadership-level Agile Coach

Measuring your Impact & Value as a Leadership-level Agile Coach

I recently shared a piece entitled Measuring Leadership Coaches and Their Impact. The perspective in the article was primarily mine. What did I look for in leadership coaches (agile coaches) when they coached me in agile contexts?  

There were a few questions in the LinkedIn responses where folks sought specific metrics. I’m guessing outcome-based, results-based, specific measures I used to evaluate my coaches. The reality was I didn’t have those. Truthfully, I didn’t care about them. I cared about how the coach connected to me as a human and leader rather than some arbitrary metric that I applied to the coach. And to me, any metric was a “system metric” in that it applied to the coach + me and how we impacted the system…together.

I feel like this answer will disappoint those looking to create a leadership coaching metrics dashboard, but so be it.

All that being said, I was inspired to share these indicators of a leadership coach’s performance. They augment what I was trying to say in the first article, and I hope you find them more helpful in guiding you toward measuring your systemic value.

Measuring Leadership Coaches and their Impact

Measuring Leadership Coaches and their Impact

Today, there’s a tremendous amount of discussion on measuring the impact of agile coaches and their coaching effectively. 

The coaches referred to in this discussion would include—

  • Leadership coaches

  • Organizational coaches

  • Change Management coaches

  • And, most importantly for this discussion, Enterprise-level Agile coaches

These are people who often coach up to leadership and across the organization. It’s a different sort of coaching that requires different skills, competencies, and experience than other forms of coaching (Scrum Masters, Team-level, RTE, etc.) in agile contexts.

While often the organization and coaches try to tie success downward at the team level towards execution performance and delivery impact, I believe these are red herring measures for these sorts of coaches.

So, the critical question becomes, how should we measure the effectiveness of this sort of coach?

I’m glad you asked!

Coachability

Coachability

In 2018 I wrote a post entitled—The First Rule of Agile Coaching – Be Coachable!

It’s one of the most popular and re-posted of my blog posts. And its core theme is the notion of a coach—

  • Consistently walking their talk

  • Having and growing their self-awareness

  • Having a continuous growth mindset

  • And ultimately, being coachable

But one of the things I struggle with is that, beyond the “be coachable” diatribes, I don’t have tangible tools to offer. Yes, I firmly know what it looks like to me, but it’s hard to share that (or explain or expect) that of others.

And then I stumbled upon a wonderful book…

The Book

I saw this post by Pete Berridge sharing his thoughts on Kevin Wilde’s book entitled—Coach-ability – The Leadership Superpower.

Finally – Shining a Light on Badass Agile Coaches

Finally – Shining a Light on Badass Agile Coaches

I’ve been a Scrum Alliance Certified Enterprise Coach (CEC) since 2012. It’s one of two coaching certification levels, the other is Certified Team Coach (CTC), which are sponsored by the Scrum Alliance as part of their guide-level certifications. The other guide level is the Certified Scrum Trainer (CST). 

Over the years, I’ve been frustrated with the Scrum Alliance because they’ve done a mediocre-to-poor job of shining a light on the CEC & CTC coaching communities. As of this writing, there are 140 CEC’s and 237 CTC’s in the world, compared to 277 CST’s.

The Scrum Alliance has always leaned more heavily into supporting the CST’s. My guess is because of the part they play in granting certifications and driving revenue. But that being said, and I’m probably a wee bit biased, I’ve always felt that the coaches are equally as or even more critical to achieving the overarching goals of the Alliance than the CST’s.

I can hear you ask—but Bob, if you’re so frustrated, why have you continued with your CEC certification?

My Journey into Change Artistry

My Journey into Change Artistry

I came upon this LinkedIn post by Angela Belle Agresto— 

One of the biggest potential pitfalls to implementing successful Agile methodology? Resistance to change.

This can stem from various factors, including fear of the unknown, lack of understanding of Agile methodologies, or attachment to traditional ways of working.

Resistance to change can slow down the transformation process and hinder the adoption of Agile principles across the organization.

Want to overcome this obstacle?
💼 Involve all stakeholders from the beginning;
💬 Communicate the benefits of Agile methodologies; and 
🙌 Provide adequate training and support to help employees adapt to a new way of working.

For more like this, be sure and check out the latest from the blog: Agile Transformation Best Practices – Expert Tips for a Successful Implementation

I used to view the world of change much as Angela does. That is, I need to go through a “process” with you to change you from point A to point B in your operational thinking and ways of working.

Putting the ME Back into Agile Coaching

Putting the ME Back into Agile Coaching

 I want to share two quick stories…

First story…

I was mentoring the Agile Disciples USA group a while back, and I presented an idea, theme, and set of slides around the notion of agile coaches needing to be more assertive when it came to—

  • Communicating their value,

  • Showing their value,

  • Demonstrating their value,

  • Claiming their value,

  • Declaring their value, and

  • Owning their value.

in their organizational contexts.

You might have thought I suggested harming a puppy with the reactions in the Zoom room. Reactions like—

  • But we’re servant leaders; it’s not about us;

  • We can only measure our impact thru those we coach;

  • It’s up to our coaching clients to sing our praises, not us;

  • I don’t want people to think I’ve got a big ego or am full of myself;

  • Value determination comes from our clients.

You get the picture. And I certainly understood where they were coming from and honored their humility and selflessness, but I wondered if they were missing something important.

The Gambler in Agile Coaching

The Gambler in Agile Coaching

For some unknown reason, I was thinking of the Kenny Rogers song, The Gambler, the other day as I pondered some of today’s challenges in agile coaching. Here’s a famous excerpt from the song—

You've got to know when to hold 'em
Know when to fold 'em
Know when to walk away
And know when to run
You never count your money
When you're sittin' at the table
There'll be time enough for countin'
When the dealin's done

And I began to think how applicable these lines were to working as an agile coach. Yeah, I know, but I had some free time on my hands…

Here’s what I came up with.

Agile Coach as Consultant?

Agile Coach as Consultant?

The wise Nigel Thurlow posted the following on LinkedIn

A consultant should never implement solutions or attempt to fix anything. In most cases they’ll simply create thrash and often make things worse.

They should instead light the way and teach others to “learn to see”. Once others are able to see the consultant can guide them on contextually relevant tools, techniques, methods, and approaches.

Hint: you should be an expert generalist and possess deep knowledge beyond frameworks. People solve problems, not frameworks.

Teach others how to fish. Help them see and solve their own challenges. Trying to fix companies will only result in frustration for both sides.

Caveat: leaders (the ones with big job titles) must be engaged and participatory otherwise the best that can be hoped for is a short-term placebo effect.

Why do Agile Coaches have an Aversion to Consulting?

Why do Agile Coaches have an Aversion to Consulting?

It seems to be an ongoing topic within the agile coaching community.  

Can an Agile Coach provide advice or consult with a client? The predominant answer seems to be no. Or something like—if you’re providing advice, then you’re NOT coaching. So, do you want to be a Coach? Or do you want to be a Consultant or Advisor? But you certainly can’t be both!

I’ve always wondered where this position comes from. If I’m advertising myself as an Agile Coach serving my clients…

  • Is it simply wrong to mix the two? Am I doing my client a disservice if I give them advice?

  • Or is it a skills challenge where many coaches find themselves under-skilled or uncomfortable delivering consulting advice?

  • Or, is it easier or less risky to professionally coach versus providing consulting advice?

  • Or is it something else altogether?

My initial reaction is that it might confuse Professional Coaching and Agile Coaching.  Thinking that they are the same. As I explored in my Extraordinarily Badass Agile Coaching book, they are not.