The micromanagement macrocosm

As he entered the room, he was looking quite frustrated to say the least, and he is someone who does not feel frustrated so easily. That raised the curiosity of many in the room who have known him as the “jolly old fellow” always ready to help anyone with a smile. As someone who had been there done that with rarely a fluster it was unusual and appeared unnatural. We naturally gravitated towards him wanting to understand the load of the mountain he was carrying that bowed him down.

He was an acknowledged leader and had been a CIO for close to two decades; his business acumen, industry and domain experience was unparalleled. As a turnaround CIO he had changed IT perceptions and created delivery frameworks in many companies. Through thick and thin he portrayed himself as the savior for challenged business and IT; the image stuck and led to his enviable growth. If he ever had moments of uncertainty or felt overpowered by a situation, no one had the privilege of seeing that.

So the emotion that he displayed was alien to the group; they tentatively edged up to him to seek the reason for his annoyance. What could have flustered the first amongst equals ? He looked around at the anticipation and decided to share his situation. It appeared to be an innocuous position which everyone felt should be easily resolvable. As the discussion progressed the perception slowly faded away to leave the group in an exasperated state of mind. It was as if there was no way out.

The CIO was doing well working with the business and the Board; the company had endorsed his plan and strategy including required investments. Everyone was happy with progress, direction and outcomes. He had no reason to worry or think about anything adverse happening or changing his reality. The company underwent a management change and he now had a new boss whose belief system was a contrast to the earlier culture. She challenged everything and wanted to be involved in every meeting with peers and be the gatekeeper to every communication.

She restricted access to the CEO and the Board with a view that their time is valuable and everything that goes upwards or sideways needs her endorsement. The CIO used to a free hand started feeling stifled and struggled to work within the new rules. Every presentation, communication, and meeting request needed approval; the new manager appeared to require control of everything. Other CXOs reporting into her also shared similar experiences. Individually and collectively a solution failed them.

Seeking advice from other peers and earlier managers did not reveal any new solutions. The CEO was either unaware of the discomfort of the team or did not believe that the situation warranted a change. So everyone who was being touched by her cringed and wondered how to overcome the overbearing and autocratic behavior of their new colleague. Her credentials were reasonable, the bravado and projected success larger than life. Her conviction and mannerism did not easily allow for a challenge.

Having run out of options, our CIO friend was thus wallowing in choppy seas with no straws to clutch and wondering if he should look for new opportunities. A few members of the group shared similar experiences in their respective careers where they finally found a way out on their way out. People join companies, people leave their bosses stood proven many times over. Then someone raised an interesting question. “Why not align to the new style and start working to new expectations rather than fighting them ?”

It was as if that option was never considered and fight of wills was the only option.  Agreed that it is a departure from the conventional and it puts a constraint on the ability of the CIO to continue to innovate, in the absence of any other avenue, this may be a model that allows progress. It had everyone wondering and as they thought deeper, the solution appeared practical though not in the best interest of the flexibility and freedom that typically CIOs enjoy. I am not sure I would choose that path, but then …

What would you do ?

Insecurity is good

“Insecurity is Good”, so said a KOL CIO (Key Opinion Leader, a term I pick from my current industry - pharmaceuticals) in a conference which had over 100 CIOs gathered for a couple of days. It had the audience arise from their post-partum slumber, suddenly awake and scratched their collective heads in an attempt to decipher the deeper meaning (if any) of the phrase. Seeing the disbelief and curiosity on almost everyone’s face, he clarified his stance. The moderator and co-panelists raised more than an eyebrow !

The panel discussion among the CIOs was an attempt to unravel the seed of the perennial discussion on the endangered CIO. All the panelists had close to three decades of experience each with more than half their tenure as the head honcho. They were beacons of success and looked up to by every aspiring and junior CIO. News and views on the waning influence, diminishing power, struggle to hold on to budgets, and finally with every new technology an adverse opinion required a platform to unravel the reality and learn from the learned.

The CIO clarified his position: CIOs should not get into comfort zones and shun risks that may require a different level of thinking. They should be risk takers, and as they take on the unconventional, it is natural to feel insecurity; the opposite being complacency, insecurity is a preferred state of mind. Insecurity ensures that complacency does not set in and that the CIO will think out of the box and explore all options before taking a decision. The calculated risk and the accompanying insecurity are essential to keep the bar of performance high.

Are CIOs really an insecure lot ? Are CXOs really insecure about their future ? Do they really live in a world of uncertainty with no visibility of how their role will change for the good or worse ? Do utterings from a motley lot of opinionates indeed make their daunting predictions require rebuttal ? (see Chief Insecure Officer). The group largely disagreed and opined that once for all this debate should be put to rest; not just by argument, but by actions which shall strongly signify reality as it is, giving a burial to this postulation.

A potential solution was proposed by one: CIOs are reluctant communicators; they send occasional status reports, outage notices, a project go-live or delay, and a few times an update on the industry or a new trend. A lot of the good work done by the IT organization remains unnoticed or unappreciated only to be negated when something fails. There is almost no match to the communication sent by other CXOs or their functions on specific/generic issues internally or externally. This commentary is rarely matched by IT.

Another viewed the situation as a self-inflicted disease; why are CIOs so gullible that they are willing to be swayed so easily ? Why do they have to retaliate to every small instigation ? They should ignore the doubters and work towards creating a position for themselves driven by results rather than by debate. I kind of agree with the view except that I cannot let go of a good fight without getting into the ring. Should the CIO take the non-violent biblical path towards his/her success and acknowledgement ?

I do not believe that any hypothesis is universally applicable to the entire fraternity. There are some who have adapted and evolved to becoming KOLs, while some remain in their positions of perceived insecurity. Evolution is selective and that is nature’s way of weeding out the weak. Everyone without exception has to build relationships on the foundation of credibility and trust which is derived from success. Most shortcuts lead to perdition, the escalator to success is rarely sustainable. Take the ladder or stairs up.

So coming back to “Is insecurity good” ? I believe that insecurity is not the opposite of complacency, it is an inexplicable feeling of being incomplete that keeps you from achieving more. It does not and should not have anything to do with external stimulus or instigation; the CIO gets to this position based on some core competencies and deliverables. S/he has adapted to the changes thus far and achieved success; why should the future be different ?

I wonder if CIOs have lost their mojo so abruptly ?