There are a lot of jokes about being a CIO—it is one of the toughest professional level jobs and has a high turnover rate (average is barely 24 months according to Public CIO Magazine 2009)—hence the moniker “Career Is Over.”
Depending on the organization, CIO’s may be up against a host of daunting challenges—the fast pace of technological change, an organizational culture that can’t or doesn’t want to keep up, resource constraints, inflated expectations, vague requirements, and shifting priorities.
On top of these, the CIO is typically last in the executive pecking order, and so carries less authority than his/her peers. This is the subject of an article in the Wall Street Journal, 24 May 2010, called “Why CIOs Are Last Among Equals.”
According to the article, “most CIOs don’t have the broad business understanding, strategic vision and interpersonal skills that it takes to runs a company.”
The authors call out the following common CIO deficiencies:
While, of course, these deficiencies do not apply to all CIOs—i.e. they are generalities—they are indicative of where as a profession IT and leadership need to focus on and look for ongoing improvement.
Clearly, IT leaders must be not only experts in the technology and operations, but must become true strategic leaders of the organization, able to formulate a way-ahead, articulate it, build consensus around it, and drive it to a successful execution. Keeping the proverbial IT “lights on” is no longer a viable CIO option.
What got us into this situation?
In my opinion, the notion of promoting for technical skills alone is mistaken. Rather, we need a holistic approach that emphasizes what I call “The Total CIO,” which is broad-based and includes the people, process, AND technology skills to truly see the big picture, and know how to drive real change.
While technology operations is critical for keeping our organizations running, they must be supported by strategic IT functions, such as those that I have called for in “The CIO Support Services Framework” including: enterprise architecture, IT governance, project management, customer relationship management, IT security, and performance management.
I believe that the leadership skills of “The Total CIO” and the strategic support functions of “The CIO Support Services Framework” will drive us to successfully progress our organizations, “earn our daily keep,” and achieve the right to peer parity based on executive skills and competencies that are expected and necessary.
| Insightful Visionary | Able Pragmatist |
| Savvy Value Creator | Relentless Cost Cutter |
| Collaborative Business Leader | Inspiring IT Manager |
At an enterprise architecture conference a number of weeks ago, the audience was asked how many of you see yourself as technology people—about half raised their hands. And then the audience was asked how many see yourselves more as business people—and about half raised their hands. And of course, there were a handful of people that raised their hands as being “other.”
Then the dialogue with the audience of architects proceeded to regardless of whether you consider yourselves more business-oriented or more technology-oriented, either way, enterprise architects must get the vision from the business people in the organization, so the architects can then help the business people to develop the architecture. It was clear that many people felt that we had to wait for the business to know that their vision was and what they wanted, before we could help them fulfill their requirements. Well, this is not how I see it.
From my experience, many business (and technology) people do not have a “definitive vision” or know concretely what they want, especially when it comes to how technology can shape the business. Yes, of course, they do know they have certain gaps or that they want to improve things. But no, they don’t always know or can envision what the answer looks like. They just know that things either aren’t working “right” or competitor so and so is rolling out something new or upgrading system ABC or “there has just got to be a better way" to something.
If we plan to wait for the business to give us a definitive “this is what I want,” I think in many cases, we’ll be waiting a very long time.
The role of the CIO, CTO, as well as enterprise architects and other IT leaders is to work with the business people, to collaboratively figure out what’s wrong, what can be improved, and then provide solutions on how to get there.
Vision is not a business only matter—it is a broad leadership and planning function. IT leaders should not absolve themselves of visioning, strategy, and planning and rely only on the business for this. To the contrary, IT leaders must be an integral part of forging the business vision and must come up with an enabling “technology vision” for the organization. These days, business is more and more reliant on technology for its success, and a business vision without thought and input from the technology perspective would be superficial at best and dead of center at worst.
Moreover, visioning is not an art or a science, but it is both and not everyone is good at it. That is why open communication and collaboration is critical for developing and shaping the vision for where the organization must go.
Early on in my career, in working with my business counterparts, I asked “What are you looking to do and how can I help you?” And my business partner responded, opening my eyes, and said, “You tell me—what do you think we need to do. You lead us and we will follow.”
Wow! That was powerful.
“You tell me.”
“What do you think we need to do.”
“You lead us and we will follow.”
The lesson is simple. We should not and cannot wait for the business. We, together with our operational counterparts, are “the business”. Technology is not some utility anymore, but rather it is one of the major underpinnings of our information society; it is the driving force behind our innovation, the core of our competitive advantage, and our future.
One thing we all really like to hear about is how we can do more with less. This is especially the case when we have valuable assets that are underutilized or potentially even idle. This is “low hanging fruit” for executives to repurpose and achieve efficiencies for the organization.
In this regard, there was a nifty little article in Federal Computer Week, 15 Jun 2009, called “Double-duty COOP” about how we can take continuity of operations (COOP) failover facilities and use them for much more than just backup and business recovery purposes in the case of emergencies.
“The time-tested approach is to support an active production facility with a back-up failover site dedicated to COOP and activated only during an emergency. Now organizations can vary that theme”—here are some examples:
Load balancing—“distribute everyday workloads between the two sites.”
Reduced downtime—“avoid scheduled outages” for maintenance, upgrades, patches and so forth.
Cost effective systems development—“one facility runs the main production environment while the other acts as the primary development and testing resource.”
Reduced risk data migration—when moving facilities, rather than physically transporting data and risk some sort of data loss, you can instead mirror the data to the COOP facility and upload the data from there once “the new site is 100 percent operational.”
It’s not that any of these ideas are so innovatively earth shattering, but rather it is their sheer simplicity and intuitiveness that I really like.
COOP is almost the perfect example of resources that can be dual purposed, since they are there “just in case.” While the COOP site must ready for the looming contingency, it can also be used prudently for assisting day-to-day operational needs.
As IT leaders, we must always look for improvements in the effectiveness and efficiency of what we do. There is no resting on our laurels. Whether we can do more with less, or more with more, either way we are going to advance the organization and keep driving it to the next level of optimization.
The last thing any executive should be doing is getting caught up in the weeds of management. The executive needs to lead and define the organizational strategy and the management team needs to execute. The executive is the link between what needs to get done (stakeholders’ needs) for the stakeholders and getting it done (management execution) through the organization’s people, process, and technology.
How does the executive perform this linking role?
Not by looking myopically inside the organization, and not by jetting around the globe shaking hands and kissing babies. Peter Drucker said “ The chief executive officer (CEO) is the link between the Inside that is ‘the organization,’ and the Outside of society, economy, technology, markets, and customers. “
In Harvard Business Review, May 2009, A. G. Lafley the CEO of Proctor & Gamble see’s that the CEO’s job is to “link the external world with the internal organization.”
The executive is the bridge between inside and outside the organization. And by having one foot in each, he/she is able to cross the artificial boundaries and bring vital stakeholder requirements in and carry organizational value back out.
Lafley breaks down the CEO’s role into four key areas, which I would summarize as follows:
To me, the Drucker-Lafley view on the CEO as a bridge between boundaries inside and outside the organization, can be extended a step down in the organization to other “chief” roles. The CEO’s vision and strategy to deliver value to the stakeholder to the role is fulfilled in part by the chief information officer (CIO) and chief technology officer (CTO). Together, the CIO and CTO marry needs of the business with the technology to bring them to fruition. Within the organization, the CIO is “outward” facing toward the needs of the business and the CTO is “inward” facing to technology enablement. Together, like two sides of the same coin, they execute from the IT perspective for the CEO.
Similarly, the chief enterprise architect (CEA), at the next rung—supporting the CIO/CTO, is also working to span boundaries—in this case, it is to technically interoperate the organization internally and with external partners The chief enterprise architect works to realize the vision of the CEO and the execution strategy of the CIO/CTO.
The bridge the CEO builds links the internal and external boundaries of the organization by defining stakeholders, scope, business strategy, and organizational culture. The CIO/CTO build on this and create the strategy to align business and technology The CEA takes that decomposes it into business, information, and technological components, defining and linking business functions, information flows, and system enablers to architect technology to the business imperative.
Three levels of executives—CIO, CIO/CTO, and CEA, three bridges—inside/outside the organization, business/technology sides of the organization, and business process/information flows/technologies within. Three delivery mechanisms to stakeholders—one vision and organizational strategy, one technical strategy and execution, one architecture plan to deliver through technology.
Too many organizations espouse good service, but very few actually excel and deliver on the promise.
However, one company is so good at it that it serves as the role model for just about all others--that company is The Four Seasons.
The Wall Street Journal, 29 April 2009 reviewed the book “Four Seasons” by Isadore Sharp, the luxury hotel’s founder.
Here are some things that I learned about customer service from this:
- Customer Service means reliability—“a policy of consistently high standards.” At Four Seasons, anyone who has visited the chain around the world [83 hotels in 35 countries]…can attest to its reliability. To be reliable, customer service is not just raising and holding the bar high-- having high standards for quality service--but this must be institutionalized through policy and delivered consistently—over and over again. You can’t have a bad day when executing on customer service. Fantastic customer service has to always be there, period!
For The Total CIO, this type of reliability means that we don’t focus on technology per se, but rather on the customer’s mission requirements and how we can consistently deliver on those in a sound, secure, and cost-effective manner. CIO leaders establish high standards for customer service through regular performance plans, measures and service level agreements. Reliable customer service is more than a concept; it’s a way of relating to the customer in every interaction to consistently exceed expectations.
- Customer Service means innovation—“The things we take for granted now during our hotel stays-comfortable beds, fluffy towels, lighted make-up mirrors, fancy toiletries, and hair dryers-made their first appearances at the Four Seasons…likewise for European-style concierge and Japanese-style breakfast menus, in-hotel spas, and the possibility of residence and time-share units.”
For The Total CIO, technology changes so fast, that innovation is basically our middle name. We never rest on our laurels. We are always on the lookout for the next great thing to deliver on the mission, to achieve strategic competitive, to perform more cost effectively and efficiently. Advantage. Moreover, we reward and recognize customer service excellence and innovation.
- Customer Service means valuing people—“Follow the golden rule. Workers are vital assets who should be treated accordingly…at the Four Seasons, those who might otherwise be considered the most expendable ‘had to come first,’ because they were the ones who could make or break a five-star service reputation.”
For The Total CIO, people are at the center of technology delivery. We plan, design, develop, and deploy technologies with people always in mind—front and center. If a technology is not “user-centric”, we can’t employ it and don’t want it—it’s a waste of time and money and generally speaking a bad IT investment. Moreover, we deliver technology through a highly trained, motivated, empowered and accountable workforce. We establish a culture of customer service and we reward and recognize people for excellence.
- Customer Service means solving problems—“Turning the top-down management philosophy on its head, Mr. Sharp authorized every Four Seasons employee to solve service problems as they arose to remedy failures on the spot.”
For The Total CIO, leadership is fundamental, management is important, and staff execution is vital. It is the frontline staff that knows the customer pain points and can often come up with the best suggestions to solve them. Even more importantly, the IT customer service representatives (help desk, desktop support, application developers, project managers, and so on) need to “own the customer” and see every customer problem through to resolution. Yes, it’s nice to empathize with the customer, but the customers need to have their problems fixed, their issues resolved and their requirements met.
The Total CIO will make these customer service definitions his and his organization’s modus operandi.
In building our teams, leaders need to understand themselves and how they relate to others. Some common instruments that help to do this are the Myers-Briggs Type Indicator (MBTI) and Strength Deployment Inventory (SDI). Myers-Briggs classifies people according to their preferences for introversion/extroversion, sensing/intuition, thinking/feeling, and judging/perceiving. Similarly, the SDI charts people according to their altruism, assertiveness, and analytic. Both of these give people insight into their own personalities as well as provide a typology for those we work with.
MIT Sloan Management Review, Winter 2009, provides yet a new profile to categorize the support network of leaders in “Profiles of Trust: Who to Turn To, and for What”.
The profiles of people in the CIO’s support (“trust”) network comprise 8 types that “reflect differing combinations of the three facets of trust—ability, integrity, and benevolence.” They are as follows:
“Executives are likely to build a support network based on different types of relationships with different people (who span the above eight profiles).” For example, when actionable advice is needed, those with high ability and integrity will be called upon. When looking for emotional or political support, those high in benevolence and integrity are especially valuable. And when looking for raw information, the “average Joes” with all three attributes in moderation are there to assist.
Of course, the specific people called upon for their subject matter expertise will vary according to the occasion and the needs of leadership. And regardless of who is called upon, and when, to provide their support, everyone serves a vital purpose.
So to me, what it important here is that everyone in a diverse workforce is infinitely valuable. And while no one person or type of person can do everything, everyone can do something. Those executives who build the breadth and depth of talent around them will have the human capital assets to thrive in any situation.
It was nice to see a book today that brought this topic home; it is called “G-d is My CEO” by Larry Julian.
The premise of the book is that “we usually want to do the right thing, but often succumb to the short-term, bottom line demands of daily business life.”
Julian states: “The bottom line had become their G-d. It was insatiable. No matter how hard they worked, it was never enough, nor would it ever be enough.”
As I see it, people have two faces (or more) and one is their weekend persona that is family and G-dly oriented and the other is the one for the rest of the week—for business—that is driven by materialism, accomplishment, and desire for personal success.
This is where the test of true leadership comes into play.
We can and must do better in our business lives by “doing the right thing regardless of the outcome” and “expanding the definition of success from making money to making a difference.”
BUT, BUT, BUT…
We’re all experts at making excuses, why we need to be successful in business, achieve results, make lots of money, get the next promotion (and the next and the next) and that “the end justifies the means; you get to the outcome regardless of how you accomplish it”!
In Information Technology, it’s no different than in any other business function. It’s a competitive environment and most of the time, people’s raw ambitions are somewhat obscured (but still operating there) and occasionally you see the worst come out in people—not working together (like system operating in stovepipes), or worse criticizing, bad-mouthing, and even back stabbing.
As a CIO or CTO, we must rise above this and lead by a different set of principles. To this end, I like the “Servant Leadership” doctrine put forward by Julian.
In short, the servant leader, leads by example and puts people first and in essence, spiritually elevates the baser ambitions of people.
The servant leader is “one who serves others, not one who uses others. He/she “serves employees so they can serve others.”
“When we [as leaders] serve others, we help them succeed” and thereby we can accomplish the mission even better than pure individual greed ever could.
WOW!
The CIO/CTO can lead people, modernize and transform the enterprise with innovation and technology, to accomplish the mission better than ever and we can do it by integrating spirituality and kindness to people into what we do every day in our working lives.
Unfortunately, IT organizations are often run not by elevating people and making them significant, but instead by running them into the ground. The mission is demanding the latest and greatest to stay competitive. The technology is changing rapidly. IT specialists are challenged to keep up with training on new hardware, programming languages, systems development and project management techniques, best practice frameworks, and so forth, The Help Desk and Desktop support people are routinely yelled at by the customers. Security and privacy issues are a constant threat to operations. IT is denigrated as a support function, whose people don’t understand the business; IT is viewed as a utility and it’s people often pushed out for outsourcing.
Truly, in this type of demanding and challenging environment, it is tough for any IT organization and its people to maintain their dignity and spirituality. But that is precisely where the CIO/CTO must lead and demonstrate humanity and care for people. The true IT leader will impose structures to create order out of chaos and in so doing elevate people as the critical asset they truly are to the organization.
Here’s some ways we can do this:
Through these and other servant leader examples, we can integrate our spiritual and material lives and be the types of leaders that not only deliver, but that we can really be proud to be.
For a CIO, leadership can be even more challenging because of the balance needed between the business and technical aspects of job and the need to communicate to those two communities in their respective languages and to be able to translate between them. Often, sitting in meetings I see the best intentioned IT folks often talking techie “right past” their business counterparts and the business folks discussing mission to IT people who may never have been outside the confines of the IT environment.
As the CIO, it’s key to bridge the divide and help the business and IT communities in the organization work together and learn to speak and understand each other. Only this way, can the IT folks understand the business requirements and the business folks understand the technical solutions being proposed.
To accomplish this, the CIO should have the business and IT people work together in integrated project teams (IPT’s), tiger teams, task forces, and so on to accomplish IT projects, rather than the business just being consulted at the beginning of the project on the requirements, and handed a “this is what we thought you wanted” deliverable at the end.
Further, the CIO should appoint business liaisons or customer relationship managers to routinely work with the business, understand their needs and work to address them—until completion and satisfaction. The business liaisons need to “own the customer” and should not just be a pass-through to the help desk with no follow up, closure, or performance measurement
Where appropriate, I think it is even a good idea to collocate the business and IT people together, rather than in their separate fiefdoms and functional silos to so they really become a cohesive team—sharing business and IT knowledge and working together to implement an IT enabled business.
Of course, the CIO should encourage training, field trips, work details, and other cross-pollinating initiatives.
Finally, a robust enterprise architecture and IT governance helps to effectively bring the business and IT people together to jointly build the plan and make the decisions, so that it is not one side or the other working in a vacuum or imposing little understood requirements or solutions on the other.
In the book, The New CIO Leader by Boardbent and Kitzis, one of the basic premises is that “every CIO will follow one of two paths:” as follows:
--either they will be a “chief technology mechanic,” narrowly focused on IT to the exclusion of the business.
- or they will be a “new CIO leader,” where “IT is at the heart of every significant business process and is crucial to innovation and enterprise success.”
To be the new CIO leader, and truly integrate IT into the very fabric of the mission, you need to “weave business and IT strategy together” and also integrate the business and IT people to work effectively together.
Of course, this starts with building a high-performing IT organization, but must also involve regularly reaching out to the business at every opportunity and including them as full partners in build effective and efficient enterprise architecture planning, IT governance, and full systems life cycle execution.
In my opinion, the new CIO leader, does not think just IT, but lives and breathes the business and does everything in their power to bring the two not just in alignment, but in true partnership.
How important is this?
As Broadbent and Kitzis state: “If you don’t think like a constantly ‘re-new-ing’ CIO, you may be on our way to becoming an ex-CIO.
