I received an email from Strategic CIO Journal entitled – Top CIOs Become Business Process Czars.
The key focus of the article was raising the bar on CIOs to become more broadly engaged in the overall business and the processes to deliver value.
https://thestrategicciojournal.com/2018/07/23/top-cios-become-business-process-czars-2/
Now, I’m not going to critique the article. Because it was the title alone that inspired this response. It made me think about senior technology leaders – CTOs, CIOs, and any senior technology leader in a larger organization.
It made me think of their Prime Directive. Is it:
Technology Leadership?
Business Process Leadership?
Or is it, Culture Builder?
The article seemed to allude to role moving from a focus on #1 to #2. And that is a relevant and important shift given today’s Digital Transformation strategy focus.
But that being said, in some ways, I think the article set the bar too low or in the wrong direction.
I might be the first one to complain about bad managers. Heck, throughout my career, I’ve had more than my share of incompetent, self-centered, and poor-intentioned leaders. So, it would be easy for me to jump on the bandwagon in the agile community that lambastes managers on a daily basis.
No, you say. This doesn’t happen. We in the agile world embrace and respect all roles and all people.
Well here’s an example from the Larman & Bodde – Large-Scale Scrum (LeSS) book. The reference is from Anton Zotin, an agile coach, and it was published on LinkedIn. And no, I’m not picking on Anton or the LeSS guys. I’m just using this as an example. There are countless others.
One of the larger challenges facing many agile teams is having the requisite skills to deliver the goods. And it’s an insidious problem because it’s hidden by the very nature of cross-functional teams.
When I coach agile teams, I usually emphasize a couple of things:
I often exaggerate the responsibility by saying – the team needs to “suck it up” and work together to deliver on their shared goals. Everyone chipping in and helping each other out. There are no lone wolfs in an agile team and folks often need to do work that may be beyond their skill comfort zone.
But that has a prerequisite supposition…
Dan Mezick wrote about the Agile Industrial Complex in this article. It’s inspired me to respond with this one.
Personal Aside
I really like Dan’s work. It’s truly inspirational to me. There are folks who are leading some different thinking in the agile community, swimming upstream if you will, and Dan is certainly one of them.
Dan is expert in Open Space. He’s also introduced the notion of Open Space Agility as a means of introducing agile to organizations. One of the hallmarks of OSA is the aspect of invitation. In OSA, folks are not told to be agile, they are invited to be part of crafting the organization transformation to agility.
In other words, they’re a part of it. It’s inclusive.
Now moving on from my bromance with Dan…
There is the notion of – The ONE Metric that Matters. I want to translate that metric into the agile transformation space.
You could also replace agile transformation with:
Lean Change Initiative
Agile Adoption
Digital Transformation
DevOps Strategy
Organizational Agility
I know, you’re heavy with anticipation. What IS the ONE Metric?
It’s engagement vs. disengagement. That is, how are your leaders affecting the engagement of your teams as they shift the organization towards more of an agile approach?
Another way of looking at it is this,
If the leaders are engaging and pulling their team members into the process of the transformation. Asking them instead of telling them, then they are engaging;
However, if the leaders are more telling them what to do, deciding which specific agile frameworks and tools will be used, and then telling them from “on high”, then they are disengaging.
Of course, it’s not quite as simply as this, but you certainly get the idea.
Not that long ago, I wrote a blog post that was inspired by Kim Scott, the author of Radical Candor. She had written a very brief note around a leader’s responsibility to receive feedback, as well or better than, they are at giving feedback.
And many leaders, to put it mildly, suck at receiving feedback.
And you want to know another surprise? Most of them are unaware of this blind spot. They think they’re great listeners. But they’re not.
They are simply not self-aware!
Frankly, I’m tired of all of the scaling frameworks. They’re mostly driven by three needs:
Creating revenue for the firms creating them;
From a company or organizational perspective, they’re indicative of lazy, buy agile in-a-box, thinking;
And they feed the “certification happy” nature of our community.
And yes, I too am guilty of falling into the above traps.
I think the introduction of Scrum@Scale has ticked me over the edge and inspired me to write this post. That and reading this article by Neil Perkin, which takes a more reflective view to leveraging useful bits from the various scaling frameworks.
A ScrumMaster asked me the other day how they should handle the situation where half their team doesn’t seem to care about the work. They don’t seem to be motivated. They seem to be slacking…a lot. And where two individuals seem to be doing all the work. And they seem to be burning out.
A senior leader in an organization that I’m coaching asked me the following when he found out I would be meeting with his boss. He asked me to tell him that they have too much work to do. That they are being stretched over capacity and that it’s causing delivery, quality and morale problems. In fact, the house of cards is about to fall.
I was training a class at a client the other day and three individuals, not at the same time, asked me to escalate their impediments. One impediment was that their leaders were excessively interrupting the sprints. Creating chaos. Another was that the priorities changed constantly. And the final, small problem, was that the leadership team expected the team to exceed their capacity by 350%. They wanted me to address these (fix it) with their organizational leaders. And, believe it or not, they were all serious.