#3/10 Crucial Survival Skills for the 21st Century CIO - Collaboration

This is the third article in the series of 10 Crucial Survival Skills for the 21st Century CIO. If you haven't read the earlier postings, start your journey here.

"No man is an island unto himself, every man is a part of the whole." 
- John Donne

When I started my new role as CIO at a large college, I spent time meeting with other executives in order to introduce myself and find out from their perspective how the IT department had provided services.

I was somewhat shocked when the theme of many of the answers came back something like this - "IT folks are nice people, but I'm not really sure what they do".

Many saw us as a large budget, and a huge team (over 100), and while they liked us as people, they weren't sure we needed the large budget, or the large team. (This is not comforting coming from the CFO)

A secondary theme of the answers was "IT couldn't help us do what we need, so we are doing it ourselves."  Two of the departments in the school had formed their own shadow IT departments.

This was a marked contrast to the excellent innovation, creativity and world class implementation of hardware, software and systems I saw when I interviewed my new team.

Where was the disconnect?

I thought long and hard about it...The answer?... "IT does not play well with others".

Today's post is about - collaboration.

Aside from Finance, IT is one of the only departments that is horizontal - working with every department and function within the organization.  We offer great value in our exposure to all of the parts and processes, and our knowledge of how things fit together.  This can create a potential problem where the CIO works in isolation from the other departments, since we feel confident we know what is needed.  This is a sure fire way to alienate your users.  How many stories do we hear about "IT forcing solutions on us"?  Learning to engage and involve your user community is a crucial survival skill.

Collaboration in practice looks like this:

  • You actively seek out and engage your stakeholders.  You know their pain points, their projects, their goals and their dreams as well as they do.
  • At first you ask to attend their planning meetings as an observer... to learn (not to pontificate). You are now invited to the planning sessions as a contributor.
  • You have discarded waterfall methodology to develop new applications. You've implemented a highly interactive, iterative methodology.  Non IT people are now part of your project teams.
  • You've brought in, (or trained) strong project management professionals to ensure that all projects are managed well, and all stakeholders are kept informed.  Note: I'm not talking about someone calling themselves a project manager. I'm talking about a certified professional. If you haven't got the talent internally, bring in an expert. (My personal endorsement for resources in the Toronto area is the SPM Group)
  • You've taken down the "If you build it, they will come" poster from your wall, and replaced it with "Find a need, and fill it".  You will have much better results.
  • You throw out your Strategic IT Plan, and replace it with a section in the organizational strategic plan.  IT requirements are now woven into all into all strategic initiatives.  They are not an afterthought at the end of the project.
  • The other executives in your organization can articulate how IT has helped their department be successful.
  • You resist the urge to sit in your office and command the ship.  You are constantly out engaging with your stakeholders. You, your directors and managers are well known by other key stakeholders in the organization.
And I bet you thought I was going to talk about collaborative tools such as Apple's Facetime, Microsoft Lync, and video conferencing?  These are just tools to achieve the collaboration skill you need as a 21st Century technology leader.

IT's influence is everywhere.  As the IT leader, you and your team should be known everywhere as well.  Otherwise, it may be easy for departments (or individuals) in your organization to end run you to find solutions. See my earlier post on this topic here.

I'll be presenting one competency per posting over the next while, and compile them into one big, long post when complete.

Here is the list of all 10 competencies with links.

Next posting: Corporate Contributor

How would you describe collaboration in action?


Post a Comment