Viewing entries in
Agile Leadership

I was wrong

Comment

I was wrong

As I reflect on my 40+ career, with over half of it in leadership roles, I think about things that I did that made me different and potentially more effective than most leaders. 

One thing that stood out is related to my reflective nature.

If you’ve ever worked with or for me, you’ll know that it’s quite common for me to have a strong initial reaction or opinion to something. Imagine that.

Then, upon ongoing reflection…

I’ll come in the next day and say—

You know, I thought about your idea more

And you know what, I was wrong. I want to support your approach (idea, strategy).

The notion that I’m not stuck on my ideas I think opens up the creative process for folks. It creates safety and the knowledge that (over time) I can be open-minded 😉

I experienced that this level of vulnerability, my willingness to admit I was wrong, opened up my culture.

The key message here is for leaders. When was the last time you said to your teams, your peers, your boss, or yourself—

I was wrong, you have my full support, let’s do it your way?

Stay agile, my friends,

Bob.

BTW: It’s not always easy to say it, so I need to practice in the mirror each morning.

Comment

Disagree and Commit

Comment

Disagree and Commit

There is something to be said about the notion of Disagreeing and then Committing that resonates with me as a valid approach for today’s organizational cultures making decisions. I’ve heard the expression for many years, so I became curious about its origins and did a little research that I’d like to share with you.

Here’s a wonderful video by Meirav Owen to start things off –

https://ecorner.stanford.edu/clips/learning-to-disagree-and-commit/

I believe Andy Grove was the first to reference it in his role at Intel –

https://hackernoon.com/disagree-and-commit-the-importance-of-disagreement-in-decision-making-b31d1b5f1bdc

Jeff Bezos famously leveraged the idea at Amazon –

https://www.inc.com/jeff-haden/jeff-bezos-uses-disagree-commit-rule-to-overcome-an-uncomfortable-truth-about-teamwork.html

SuperPower of the Disagree & Commit Culture –

https://medium.com/blablacar/the-superpower-of-the-disagree-and-commit-culture-c7085956bde0

Another take by Aaron Lynn –

https://aaronlynn.com/business/people-teams/disagree-and-commit/

Gustavo Razzetti helps deepen D&C by creating a 5-step playbook of sorts –

https://gustavorazzetti.substack.com/p/disagree-and-commit-a-5-step-playbook

Kim Scott and the Get Sh*t Done Wheel seem to be a similar approach –

https://www.linkedin.com/pulse/how-use-get-sht-done-wheel-reinforce-collaborative-respectful-scott/

Wrapping Up

I hope you found the articles around Disagree & Commit to be a useful exploration. I also hope it heightens your cultural decision-making evolution.

I often refer to decisions as having a “stickiness” factor, and D&C helps focus on increasing their stickiness.

One final reference is to the Core Protocols, which Jim and Michele McCarthy introduced in their book Software for Your Head and Richard Kasperowski in his work at https://thecoreprotocols.org/

The McCarthy’s work doesn’t receive nearly the attention it deserves. I recommend you take a deeper dive into the Core Protocols – https://mccarthyshow.com/the-core-html-version/

Whether you agree or disagree with me, I hope you can commit to weaving this model into your decision-making culture.

Stay agile my friends,

Bob.

 

Comment

Leadership’s 4% Blind Spot

Comment

Leadership’s 4% Blind Spot

I saw post on LinkedIn from Corporate Rebels that highlighted the information gap between top executives and frontline employees.  

I’ve heard this many times before. However, it resonated strongly with me this time, and I wanted to share it more broadly.

The big message here is that senior leaders, leaders, and managers often think they understand the situation (problems, challenges, situational awareness, etc.) but don’t. The higher you go in the organization chart, the less you truly understand.

The big problem, though, is that they think they understand. I.e., there is a self-awareness gap, which creates a huge blind spot.

How do we begin to mitigate this gap? I’d suggest more leaders—

  • Develop and activate their humility,

  • Sharpen their questioning & listening skills,

  • Trust what their teams say, ask for help, and take action based on team feedback.

And did I mention staying humble?

This is one blind spot that can be easily reduced…

Stay agile my friends,

Bob.

Comment

Our Value Isn’t Arithmetical

Comment

Our Value Isn’t Arithmetical

I saw a post the other day on LinkedIn where someone made the case on how to show value as Agile coaches, consultants, trainers, and leaders. 

The article was very math-focused, basically boiling everything down to the following—

Value = (The benefits a client/customer/leader receives – Total cost of ownership)

Then, they provided some value ROI calculations for various roles. All in all, it was a nice, tight argument. The numbers were precise, and the conclusions were telling.

The numbers don’t lie

We’ve all heard this argument or position when folks are speaking about organizational leaders and how they determine value. It’s often arithmetic, algorithmic, and quantifiable. The phrase, the numbers don’t lie or the data doesn’t lie, is usually attached to their perspective.

Comment

2023 Agile Skills Survey – Another Reaction

Comment

2023 Agile Skills Survey – Another Reaction

The Scrum Alliance and the Business Agility Institute partnered on a client survey focused on—Skills in the New World of Work released in October 2023. You can get a copy of the report here

As a follow-up to the last article I shared on this topic, I thought I’d share something that Jesse Fewell wrote reacting to it.

His reaction was posted on the Scrum Alliance blog, so seemingly in full support of the report.

In it, Jesse highlights three fundamental pivots that agilists should be considering based on the report’s findings. I’ll share my thoughts on each pivot next.

Pivot #1 – Broadcast your bottom-line impact.

This recommendation aligns with the number one human skill recommendation from the report—Communication skills.

Comment

2023 Agile Skills Survey – My Reactions

1 Comment

2023 Agile Skills Survey – My Reactions

The Scrum Alliance and the Business Agility Institute partnered on a client survey focused toward—Skills in the New World of Work that was released in October 2023. You can get a copy of the report here

The key question on the cover – Which agile skills are most in demand in today’s workforce?

But on page #20, the key question is reframed to – Which skills are most in demand in today’s workforce?

While the questions are close, I’m imagining the “agile” drove most of the respondent thinking.

I would encourage everyone to read it, as it contains some interesting findings and insights. That being said, there are some things in the survey (assumptions, commentary, shared data, and conclusions) that I want to challenge a bit. While the overall tone of this article will be constructive feedback, I don’t want to diminish the effort behind the report.

In a recent Moose Herd the discussion surrounded the release of the report and the impact and relevancy of the findings. How it was something interesting, thought-provoking, insightful, and new. I honestly didn’t read it entirely that way. Instead, I felt it also a bit contrived, self-serving, and old news. Now let’s serially walk through the report for my more detailed reactions…

1 Comment

Explorations Around Agile Teams

1 Comment

Explorations Around Agile Teams

I’ve been doing agile coaching for over two decades. If there were a Top 5 question I get when doing organizational and leadership coaching, it’s—

  • How do I set up my teams? Vertical, horizontal, hybrid.

  • What exactly is an x-functional team?

  • What about distributed team dynamics?

  • Are the roles full-time? Or can I share everyone?

  • How do I handle shared, service-oriented, or platform teams?

For a long time, I wished for a solid reference that I could send to folks when they have these sorts of “teaming” related questions.

Well, the good news is now I do, but it’s not one book. It’s a triplet of books.

1 Comment

Respect!

Comment

Respect!

I saw this post on LinkedIn the other day from Brian Orlando. I read it and a few comments, which motivated me to write this post. 

Here’s Brian’s initial post—

I've been thinking...

In the latest 
Arguing Agile Podcast podcast where Hemant (Om) Patel and I discuss Peter Drucker's three different types of teams, right near the end we started to talk about aligning #management with/to the appropriate team model.

Anyone who has been involved in an 
#agile transformation knows organizational design changes are likely required for success (in response to product challenges, changing markets, etc).

I'm wondering why the obstinate resistance to responsive 
#organizationaldesign and #organizationaldevelopment?

Comment

Staying in Your Lane

Comment

Staying in Your Lane

I was coaching someone new the other day. I knew they had a broad and deep non-software background and were pivoting into a Scrum Master role. It was their first job as a Scrum Master, and the hiring company was taking a leap of faith in hiring them. But I knew they had deep skills that would translate into the Scrum Master role and that they would do well. 

That is…if…they would stay in their lane.

They had ~20 years of experience and had held organizational leadership roles in their previous companies. Given that, I knew it would be a challenge for them to, how to say it, be a Scrum Master. Especially when they encountered organizational, leadership, and broadly impacting impediments.

They also seemed to have a very proactive, fix-it mindset. I thought this would be hard to throttle in the context of Scrum Mastery in an early-stage and chaotic agile transformation, mainly if they were focused on doing things “right.”

Comment

Value Stream or Organizational Structure?

Comment

Value Stream or Organizational Structure?

The chicken or the egg

It’s a bit of a chicken and egg problem. Which comes first when transitioning to agile ways of working? Do you re-organize or restructure your organization first – setting teams and roles up for more agile execution? Or do you align your product, application, and workflows into value streams to feed to your teams? What a conundrum.

Ten years ago, I saw most organizations leaning into organizational changes and not putting much thought into the value streams their teams would be working on.

Now it’s flipped a bit, and there’s a strong focus on value streams, probably influenced by SAFe, amongst many factors. And then, the executing organization is composed as an afterthought.

Comment