Wednesday, November 5, 2008

Educause Notes - Part V

I finally located my notes on the "Heroes, Silos and Small Boxes" session I attended at Educause last week. It was led by a project manager from Harvard Faculty of Arts and Science IT who discussed some of the processes they have in place over there. I particularly found it interesting that they have a very structured change management process in place. They have a committee that vets all change requests; everyone who proposes making systems or other types of changes has to be prepared to discuss their plans (which must also include backout plans) and to answer questions in front of the committee. On top of this, they also do a post-implementation review of all changes that take place. In addition, the presenter mentioned a very interesting statistic (one which caused our CIO to kind of nod in agreement when I mentioned it to him) - 80% of all unplanned downtime is self-inflicted.

Another thing that Harvard FAS has in place is strong project management. When a project is proposed, whether it is taken on or not depends on its priority, achievability and value to the business. In addition - and this ought to be a no-brainer for anyone who has ever worked on any type of project - the project intake is absolutely pivotal. Get it right, and you stand a decent chance of succeeding. Get it wrong, and you've added obstacles that can prove to be a project's death-knell.

Another take-away from this session is that organizations ought to reward people for being team players. This serves as a disincentive for hero-like behavior and helps minimize resentment - both on the part of the "hero" who can end up feeling overwhelmed as well as on the part of others who may resent the accolades that the "hero" receives. Also, I got the sense that encouraging hero-like behavior serves as a potential incentive for counter-productive behavior (counter-productive if you are a believer in proper teamwork).

With regards to project management, change management, and pretty much everything else, Harvard FAS IT utilises ITIL generously. Their motto for ITIL is "Just Do It". Also, management buy-in and support is crucial for ITIL initiatives to succeed.

What I ultimately took away from this session vis-a-vis our department is the following:

  1. We absolutely need to implement a formal change management process as soon as possible. Right now, we don't have a process and there really is very little, if any, peer review of proposed changes. It usually takes someone who is not directly involved with a project to spot problems that the project manager or team members may not notice.
  2. We should involve folks from outside our department where appropriate in terms of serving on governance committees. I realize that it may not be appropriate to involve non-IT folks in all situations, but there are definitely ones (e.g., change management, selection of new technologies) where such involvement is warranted. This provides transparency as to what the IT department is doing and what direction we're headed in. We currently have a technology steering committee that is fairly young; I'll reserve judgment until enough time has passed to allow the committee to get its legs under it.
  3. Common terminology - aka, ITIL terminology - is crucial. In order to get everyone on the same page, we need to begin using a common language in terms of processes and procedures. To achieve this end, we need to ensure that everyone in the department is properly trained/educated on this common language. Now, this doesn't necessarily mean that everyone should be sent out to training on this stuff. It could mean having those who are already familiar with frameworks like ITIL or CoBIT train others who are not familiar with these things.

Finally, the gentleman recommended a few books:
  1. "Leading Change" by John Kotter
  2. "Our Iceberg is Melting" by John Kotter
  3. "The Five Dysfunctions of a Team" by Patrick Lencioni
I picked up the third book on Friday just before I returned home and finished reading it a couple of days ago. It was very interesting and one I believe everyone on our team should read, as Lencioni goes through what he considers to be the five dysfunctions that prevent teams from working as effectively as they can. I particularly liked how he tied each dysfunction in to the others - e.g., lack of trust leads to a fear of conflict and so on. His style in getting his points across makes this an easy and compelling read (at least it did for me).

1 comment:

John Stucki said...

Wow Razi, your blog is great. Very insightful and inspiring.