CIO’s – Are you hearing your team say No?

iStock_000004060935XSmallIn a previous article titled “Leading by saying No“, I implore CIO’s to lead their organization by saying ‘no’ whenever necessary.

As I said in that article:

Saying “no” is a powerful thing. No can mean rejection, disappointment, being wrong, being right and a whole host of things. The one thing it doesn’t mean is ‘yes’….well…unless you or the person saying ‘no’ is a psychopath.

Even though ‘no’ can be a horrible thing to hear, it’s a word that must be used in order to lead. It’s a necessary word for The New CIO. You’ve got to say no to those ‘cool’ projects. You’ve got to say no to new staff. Sometimes you’ve even got to say no to budgets.

Pretty good stuff if I may say so 🙂

So you say you’ve mastered saying “no”?   Good for you…but…have you mastered the art of hearing the word “no”?

Hearing “No”

While you may be able to say “no” to the organization, are you able to hear the same word from the organization and/or your team?  Are you listening to them?

While you’ve got to be able to say “no”, you also need to allow your team and your organization to say “no” to you as well.

An Example of not hearing “no”

I know a CIO who has a reputation for getting things done.   He also had a reputation for driving his teams very hard.  He was well known as someone who could easily say “no” to his team and organization.   He’s able to point to some major wins while in the role of CIO and was seen as a rising star in the IT world.

While this CIO was able to get a lot of good stuff accomplished he was also very disliked throughout the organization. There were many reasons for this dislike, but the main reasons revolved around his inflexibility and inability in hearing “no”.   There were many projects  undertaken that shouldn’t have been started or should have been postponed but this CIO wouldn’t hear his team.  He didn’t listen. He couldn’t hear “no” and, in fact, he would get extremely angry if someone said “no” to him.

What did this do to the IT group? Not hearing “no” created an environment of disengagement.  The folks working in IT felt as though their experience, opinions and ideas weren’t valued by the CIO.  They didn’t believe the CIO listened to them. T

This CIO did get some good stuff done….but he might have accomplished much more if he had listened to his team and heard them “no”.  Many of the mistakes  that were made during his tenure were made because he didn’t listen to the warnings of his more experiences team members.

These mistakes eventually cost that CIO his job.  All because he couldn’t hear “no”.

What’s the Moral of this story?

Listen to your team.  Hear what they’re saying.  If they say “no” to you, engage them in conversation to understand why.  The worst thing you can do is say “no” to your team without hearing them in return.

Reblog this post [with Zemanta]

If you'd like to receive updates when new posts are published, signup for my mailing list. I won't sell or share your email.