Oct 13, 2011 9:46 AM
Should you abolish your Change Advisory Board?
-
Like (0)
Earlier today, I delivered a BrightTalk webcast on Five Key Considerations For Cloud Service Management. The crux of the presentation is that cloud computing demands service management excellence despite the outcry from many that service management is an impediment to cloud computing services. I won't go into all the points here. Watch the webcast for the details.
In this webcast, I made a bold statement that I hope will generate some heated debate. That statement was, "Abolish the CAB!"
Change management is one of the most fundamental processes in IT Service Management. Without good change management, services are unreliable and the IT organization suffers a lousy reputation with the business stakeholders. Does this sound familiar?
Change management has been around for years, indeed since the beginning of IT, but that doesn't mean it's effective. As with all good things, some people take it too far. We see a polarization of positions, with sloppy change on one extreme and rigid, draconian change enforcement on the other. Like the political landscape, both extremes are wrong. We need to find a balance, what I like to call the Goldilocks Point where it's not to little and not too much, but just right.
A major criticism of IT's inability to serve the demands of cloud computing is the extreme of being too rigid. It takes too long to implement the changes needed to be adaptive. Such criticism is warranted because change management is indeed too slow. Does this sound familiar? In an interesting and disturbing paradox, we see far too many organizations that are on BOTH extremes simultaneously!
The main culprit of inflexible change - in my opinion - is the Change Advisory Board (CAB). The CAB is an anachronism. It has become a speed bump in the journey to cloud flexibility. Those on the CAB are often power-hungry narcissists who merely want to impose their control over the process instead of serving the needs of the business. Regardless of the makeup of the CAB, they are also clueless about the realities involved. The world has gotten far too complex for this panel to make any trustworthy judgement calls. Even the best and brightest technologists are losing grasp of this complexity. The CAB rarely includes such people, thus even further diminishing the CAB's insight to reality.
The CAB has become more a liability than an asset, adding little or no value and slowing progress. What do you think? In less than an hour since finishing the webcast, I've already had people both applaude and criticize my position. Let the firestorm begin! ![]()
Thank you!
-- Glenn --
You are throwing out the baby with the bathwater. To paraphrase: "let's abolish consulting stakeholders before making change". The CAB is essential.
As with all these things it is how well it is done that varies. But don't shoot the message ebcause the messenger screws up: the CAB is a good idea.
Anyone who properly understands chnage knows that the CAB is only required for some changes. Many changes should be Standard or Minor and not need CAB review. I'm also a fan of virtual CAB, where approval is given by email or by an online tool, and the CAB only physically convenes for major or controversial changes. Likewise I'm also a fan of dynamic CAB, where the membership is determined according to the change in question, so that staff aren't forced week after week to sit through innumerable changes that don't interest them. No wonder they turn nasty.
A CAB is only as good as the people implementing it, but that's true for everything.
Thanks Rob!
I agree in theory that the CAB is a good idea, however it conjures up one of many immortal quotes by the great philosophers Albert Einstein and Yogi Berra: "In theory, theory and practice are the same. In practice, they're not!" (both claim credit to the quote although I suspect Einstein said it first) In practice, the CAB has become a symbol of overbearing bureaucracy.
The role of the CAB should be twofold:
I do maintain my position that CAB members are becoming increasingly clueless about the nature of the changes they're approving, though. It's kinda scary that we can't count on the CAB to understand what they're approving. We have to figure out what to do here ... and yes, we have some answers.
Decisions (many of them, not just CAB decisions) will become more dependent on analytics to tell us the truth about what to do. Our technology has become too unweildy for the human mind to comprehend, so we need even more technology to assist us. Have we stepped into a viscious cycle of technology dependence? I think we have. Is that bad? It depends on your view of technology. I for one, think it's kinda cool! Can we stop this progression? Not a chance! Our only option is to strap in and enjoy the ride! Is this the beginning of Skynet? No. Get real! But is it one step closer to the singularity that Ray Kurzweil talks about? Indeed it is.
-- Glenn --
Glenn, Holy cow! The members of the CAB you describe should not only be dismissed from the CAB, but they should be put on written warning. An organization that allows its CAB members to get away with that behavior gets exactly what they deserve.
You speak of a mid-point between two extremes, but then you try to make the case for one of those extremes. Yes, the CAB needs to adapt to contemporary needs. Wouldn't that be more of a mid-point position?
Thanks Dan!
Yes, I do articulate a strong position to get the dialogue flowing. Although I guess I do imply that we should do away with the CAB completely, I do not believe that is the right answer. As I replied to Rob, there is a role for a CAB, but it cannot be the same old CAB that we have come to know and hate. Unfortunately, I've seen many CAB structures that are indeed set up as a "gestapo" of sorts and this is just plain dangerous. I doubt anyone starts off with that model in mind, but they develop a rigidity to them and the people seem to get caught up in their own power. This is of course a generalization, but a very real problem. There are flexible CABs that are not staffed by egomaniacs, but they are rarer than they should be.
If anyone is pursuing the use of cloud computing in any form, a CAB in the execution path will decimate those cloud initiatives. Indeed, there can be no human involved in the execution, period. This is one of Staten's Laws of Cloud Computing, "If a human is involved in execution, it's not cloud!" Mike Gualtieri and I wrote about the need to eliminate people from the execution in our Augment DevOps With NoOps report.
We are in a new age of agility and complexity, both of which are forces that require a far more refined approach to change management than is typical. We still need a means to approve (some) changes. It just can't be the classic CAB. The CAB as we know it is indeed an anachronism and has to disappear.
-- Glenn --
Glenn
As Rob abd others may be saying, the idea of a CAB is not at fault here its the inflexible manner in which its applied as a concept. In previous lives I served in organizations that lacked the equivalent of a CAB and had one in some form. A CAB provides parental control over change. In the organization where it was missing I ended up getting divorced in part as a result of being camped onsite fixing indisciplined application changes. Thats my excuse anyway! In the contrary organization little could change without offering a first born. So folks went around and under the process.
What folks forget is that the accounatbility for what happens as a result of a change rests with the sponsor - not the change 'manager'. The CAB concept provides everyone involved with the opportunity to document the risk, effort and hopefully benefits and allocate resources appropriately. It enables change and offers visibility into changes as well as the chance to coordinate matters better. It needs to have a rigid backbone but flex organically based upon the need. It should operate in a federated, virtual mode, using technology to manage a queue of changes and support a 'voting system' allowing stakeholders to promote or demote changes.
We are blessed with so much technology, skype, ipads, smartphons, cloud, it begs the question why the change system does not move to the cloud and why the orgnanization required to support the system doesn't likewise be 'virtualized'? I think those who teach and consult around frameworks such as ITIL, where this term was popularized, lack the experience and confidence to 'adopt and adapt' the better parts of the guidance they find into existing or required practices.
No, I think I agree with others, the concept of a CAB is important and should not be discarded because certain styles of 'implementation' don't work. Step away from the 'implement', understand each change is an opportunity to improve, and make sure you organize organically and virtually with flex that supports remote and discrete stakeholder and resource involvement...
Forrester Research, Inc. is an independent research company that provides pragmatic and forward-thinking advice to global leaders in business and technology.
Forrester supports leaders in 19 roles across three distinct groups: IT, Marketing & Strategy, and Technology Industry.
Aligned to your professional role, Forrester's analysts are experts in the specific technologies, issues, and trends currently impacting your business.
Fresh thinking and collaborative problem-solving through an unmatched combination of peer networking, forward-looking analysis, and professional guidance.
Our expert analysts apply custom research-based solutions and data-rich insight to your critical challenges and opportunities.