Viewing entries in
Agile Leadership

Leaders, should your Agile Coaches be doing your job?

2 Comments

Leaders, should your Agile Coaches be doing your job?

I was coaching another agile coach the other day and they presented the following story to me looking for my coaching wisdom & guidance…

I know, I know, but I shared as much wisdom as I could ;-)

The sponsor/stakeholder/client (a senior executive in the technology organization) asked them to coach one of their direct reports. That person is a senior manager in the organization, well respected, and long-tenured.

The senior leader gave the coach a list of challenges they had with the individual that they wanted them (the coach) to work on fixing in (the senior manager).

When the coach attempted to “coach” that individual, they met resistance. In fact, the person didn’t see the need for coaching. They recounted that in their last performance review their manager (senior leader) had given them a stellar review, wonderful feedback, and a nice promotion and salary increase. So, they really didn’t feel the need for much in the way of coaching and personal improvement.

The coach went back to the stakeholder and respectfully and delicately communicated the resistance and tried to bow out of coaching the manager. They told the senior leader that, if they felt that individual needed some help, that they would have to communicate that to them themselves, thus opening the door for the leader performing the coaching.

The senior leader didn’t accept that position. In fact, they pushed back hard. They said that (1) the manager had a performance problem and (2) that they were delegating to the coach to “fix it”. As part of their ongoing responsibility as a “coach”. To be honest, they resented having to repeat themselves…

And this is where I came in. The coach was looking for me to do something (ask powerful questions, provide advice, suggest options, mentor them, anything…) to help them to decide what to do next.

2 Comments

My Cognitive Relationship with Cynefin

Comment

My Cognitive Relationship with Cynefin

I’ve been struggling with Cynefin for many years. First, let me share some (perhaps partially) knowns—

  • I know Dave Snowden is smarter than me;

  • I know that his Cynefin model is the result of many years of thoughtful research and experience;

  • I know there is a strong connection between Cynefin and agile approaches and an agile mindset;

  • I know I like Dave’s stance when it comes to SAFe and other agile disruptors;

  • I’m slowly working my way through the recently published Cynefin book.

But… 

All of that being said, I didn’t “get it” until recently. It all started and came together for me with this video by Sharon Robson.

It’s short, ~5-minutes. And in the 5-minutes Sharon does a wonderful job of explaining how agile leaders can use Cynefin as a sensing, thinking, and reacting model/tool for their tactical and strategic interactions with their teams and their businesses.  

It helped me to “get it”. Not just understand the model, but understand how it can be applied in our agile leadership journey. It’s caused me to become much more patient in my leadership, sensing first, and then deciding on what path to take given the situation, context, and nature of things.  It’s also amplified how interesting and valuable being able to help my teams navigate complexity and chaos can be.  

I thought I’d share it with you. Now, back to reading (and digesting) the book…

Stay agile my friends,

Bob.

Comment

A Leader’s Prime Directive

Comment

A Leader’s Prime Directive

A leader’s primary job or Prime Directive is not to—

  • Find people to fill out the org chart; or re-org;

  • Get things done, predisposed to action;

  • Drive revenue, ROI;

  • Solve problems;

  • Connect to customers or create value;

  • Envision the future; develop strategy;

  • Grow their responsibility & impact.

Instead, it’s to be a catalyst in creating, building, and growing an organization that can do all of these things…and more!

Agile leaders out there, is that YOUR Prime Directive?

#itsnotaboutyou

#build, #grow, #create

Stay agile my friends,

Bob.

Comment

More?

Comment

More?

I was in a coaching conversation the other morning with another agile coach. They brought up a scenario at work where one of their key stakeholders (executives) had said something like—

I’m fully on board and bought into what you’re focusing on in the agile transformation…

And I stopped them.

As I thought about it, the thought that kept coming up was this—

  • Being supportive of;

  • Fully backing;

  • Having their buy-in;

  • Being on board with.

Isn’t good enough for leaders when you’re a coach in an organizational transformation. Sure, those words are nice and appreciated, but I was thinking they are just table stakes. That the coach needed MORE from the stakeholders.

Comment

Standish and other Oracles

1 Comment

Standish and other Oracles

I’ve been seeing these surveys and statistics reference around The Chaos Report for nearly two decades. Often, as in this article here, they are used as citations supporting agile ways of working. And since I’m an aglist, you’d think I would be in full support of them. But I have three core problems with the reports themselves and the incessant quoting of them to support some position.

Trust?

First, I’m not sure I trust the data. Where does it originally come from AND are the collections accurate?

For example, I used to fill in project timesheets at the end of each week. I filled them in with the best recollection I had and with my perception of time spent. I realized over time that I was probably only reporting at 50% accuracy. And that was as an individual contributor. Aggregate that data over 100 developers over 1-+ projects every week. Would you trust what that data was telling you?

So, rolled-up statistics collected from a wide variety of companies doesn’t always make me that trustful and confident in the data.

1 Comment

Culture Design Canvas

Comment

Culture Design Canvas

Based on a bit of a lark, I attended Gustavo Razzetti’s Culture Design Masterclass on March 19th. I’ve been wanting to get around to talking about it for quite some time, so here are some reactions…

https://www.fearlessculture.design/

First of all, the attendees were outstanding. It was a very diverse and eclectic mix of folks that were fare wider than my typical “agile coaching” colleague universe. I enjoyed and learned much from the diverse perspectives.

Second, I want to highly recommend the Culture Design Canvas as a very general-purpose tool for exploring, exposing, understanding, and potentially changing your culture. As an agile coach, I saw many applications of it in my Enterprise-level agile coaching activity.

Comment

Achieving Critical Safety

Comment

Achieving Critical Safety

As a leader, you want to hear the truth from everyone.  

I can hear what many of you are saying. No, I don’t. I want to hear thoughts that align with mine. My plans, my strategies, my ideas, and my approaches. And I’m here to tell you…

NO! You Don’t! You want the Truth!

Getting critical feedback is a skill and habit exemplified by the best of leaders. They are adept at creating an organizational ecosystem where feedback, all types of feedback are welcome and encouraged. Even critical feedback. No. Most importantly, critical feedback.

The point being, we want to be told when the Emperor (the leader, we/us, Me) Has No Clothes.

But the challenge is creating that ecosystem. One where it’s safe to speak truth to power. And not just stipulated safety, but tried, true, real, and absolute safety. Where the most critical of feedback is welcome, embraced, and even celebrated. With no immediate or later ramifications to the giver. 

Kim Scott, the author of Radical Candor, wrote a post recently entitled 11 Ways to Get Feedback from Others. I’ve long been a proponent of Radical Candor and this complemented the ideas in it so nicely.

Here are four of her TIPS that resonated the most with me around the topic of safety. I’ll add a bit of my own color commentary to each, but please read her article first.

TIP 4: Reward Criticism to get More of It

I think this starts with thanking folks for the critical feedback. Honestly and genuinely thanking them.

Another aspect is rewarding it in your coaching conversations. Noticing it and sharing how much you value the courage it takes for individuals to “speak truth to power” when that power is you.

I’ve often given people that feedback in your reviews. Of how much I value their opinions and thoughts even when they contradict my own. Emphasizing that I’m not looking for “Yes, persons”, that tell me what they think I want to hear.

Another great way to reward feedback is to actually…do something with it. Consider it, tell people what conclusions you’ve come to around it, and take action based on it. You don’t have to take immediate action on all feedback, but you don’t want to be a receiver who never takes action.

TIP 5: Ask for Public Criticism

I love this idea. That is, ask for out in the open criticism. In hallways, meetings, conferences, wherever.

But the important thing here is not the ask. While that takes quite a bit of courage, it’s not that hard. No, what’s challenging is how you respond to public criticism.

  • Do you embrace it or deflect it?

  • Do you thoughtfully consider it or argue against it?

  • Do you thank the person for it or attack them personally?

Remember to stay sharp in how you receive your feedback, knowing that if you don’t receive it well, it will certainly stop. 

TIP 6: Criticize Yourself in Public

One great way to support Tip #5, is to criticize yourself in public. No, not overtly or artificially, but in a self-deprecating way. I’ve found that one of my Super Powers is my self-deprecating humor. I found this definition of self-deprecation on Wikipedia

Self-deprecation is the act of reprimanding oneself by belittling, undervaluing, or disparaging oneself, or being excessively modest. It can be used in humor and tension release.

Don’t be afraid to criticize yourself in public and look for frequent opportunities to do so. How you show up to others can work wonders in creating the space for the critical feedback you need to be a better leader.

TIP 8: Relish Being Wrong and TIP 11: Get Theatrical

I enjoy being wrong. I didn’t start out that way though.

Early in my leadership career, I was under the false assumption that I needed to always be right. In my thoughts, decision-making, approaches, literally everything. And when I wasn’t, I kicked myself. But over time I’ve learned that it’s normal to make mistakes and to be wrong. In fact, I’ve learned to relish those times, to celebrate them as the learning experience they are, and to sometimes go over the top in my storytelling of those events.

And there’s a point to be made here. There’s criticizing when the going is easy. For example—low risk, low impact, everything is going fine, no pressure or stress. Then there is criticizing when the going is tough. When the shit is literally hitting the fan. I want to appreciate the criticism and relish being wrong under both conditions, the latter being the most powerful.

Wrapping Up

I often use Steve Jobs as a leadership example. Sure, he had many failures and weaknesses as a leader. But there were things he was really good at.

Here are two videos that I would recommend you view as a way of closing this post. The first is an example of how Jobs handled VERY public and HARD criticism - https://www.youtube.com/watch?v=oeqPrUmVz-o

I really think it’s an exemplar for this sort of thing and worth a look.

The second is short and sweet. It shows Jobs’ position on being wrong - https://www.youtube.com/watch?v=kBlc4UX9vZI

I think it’s something we all need to grapple with around criticism. Around our ego, our intentions, our perceptions, our goals, and our intentions.

Stay agile, be safe, and be critical my friends,

Bob.

Comment

Revisiting Pareto and You

Comment

Revisiting Pareto and You

I haven’t thought of the Pareto Principle in quite a long time.

It was a central theme to my 2004 Software Endgames book because of the implications of Pareto and software defects (trending, clustering, resolution, complexity, etc.) It was a rich and interesting way to view defects at the time. Still is.

Then I wrote a blog piece entitled Pareto and You – Separating the Wheat from the Chaff in 2013, where I explored the implications of Pareto beyond software testing and defects. At the time, I saw the principle as something that could potentially have broad implications beyond software and into life itself. That is, could we view it as something as reliable, consistent, and law-like as the law of gravity?

I had been thinking the answer to this was yes. That is, as long as we view it as a lens for guidance rather than a law that strongly drives our behavior, measurement, and reactions. Consider it a Pareto Compass that would guide you towards True North in your understanding of complexity.

We were chatting about agile coaching the other morning in the Moose Herd and the principal came up again. I mentioned it as a lens that an agile coach could leverage in their assessment of and navigation thru Agile & Digital Transformations. Afterward, I put on my brainstorming hat to envision scenarios in my agile coaching journey where I might be able to look at the world through a Pareto lens—

Comment

What If…

Comment

What If…

We always talk a good game about the concept of Servant Leadership in agile contexts. But I have a hypothetical thought experiment for you. What if…

  • There was a relatively small or mature start-up company;

  • Where the founders were developers or individual contributors;

  • They hired a leadership team to “run” the company, but maintained primary ownership;

  • The founders are still actively on the board and guiding overall strategy;

  • But they simply enjoyed the product innovation and creation process associated with being a team member.

Now, as time goes on, these folks simply blend into the woodwork of the “teams”.

Comment