Monday, 05 July 2010 00:00

The CIO's Role in Project Failure

Rate this item
(0 votes)

CIO nameplate: Who should the CIO report to?

A couple months ago I asked the question, "Who should the CIO report to?" on the LinkedIn's CIO Magazine Forum. Surprisingly, over 100 people responded, so many that the group's moderator moved the discussion to the jobs section. Maybe they were tired of the attention this old, beat-up subject was getting. I surely did not think responses would be quite as passionate as they were. However, my interest lay in another area, not in the answers to the direct question, rather the reasoning behind them.

The Question Behind the Question

To insure getting the desired detail, I framed the query further. In the months prior to posting, I had participated in a roundtable discussion with a number of CIOs of $500M+ companies. This topic came up and a few felt adamant that the CIO should report to the CEO. However, as the discussion evolved, most softened their stance. In the end, there were two general groups of thought, both relatively close in concept:

  1. The CIO needs to be a respected peer of others reporting to the CEO, regardless of the actual reporting structure for the CIO.
  2. The reporting structure needs to be set up based on the technical prowess of the CEO. However, there was a wide diversity of reasons—technophobic CEOs, older risk-averse companies, and corporate cultures opposed to having a non-core competency reporting to the CEO.

The responses to the CIO group posting were about the same—primarily that CIOs should report to the CEO, the next most popular choice was the CFO, and a smattering of COOs and CTOs. Finally, a few folks who refered to who the person was and how well they understood the business. Feel free to join the group review the responses.

It Depends on the CIO

The latter group interested me—it depends on the CIO. The majority that said CIOs should report to the CEO seemed to feel this would give the CIO the credibility to do the job. This is problematic. If you lack the leadership skills, IT competency, or business knowledge to earn respect of the C-level peers, how will reporting structure change that? Rightfully so, if the CIO does not deliver value to the business, he or she will be fired. The only way to deliver value is to understand the business. Not IT, the business.

On the other hand, if you have that knowledge and the CEO's direct reports still fail to recognize you, there is a problem. Reporting to the CEO will not fix that; the cultural problem needs fixing first.

Dilbert's Boss' Visionary Leadership, Dilbert © April 17, 2004, United Feature Syndicate, Inc.

Failing Projects

Now the other angle, the view inside IT. In generalities, IT budgets allocate two-thirds to keep the lights on and one-third to deliver business initiatives. Understanding the value of Forrester's MOOSE (Maintain and Operate the Organization, Systems, and Equipment) is simple—keep everything running all the time. There is only a minimal requirement to understand the inner workings of the business. Analogous to the power company, you need to know the amount of power to supply and little about how it is used.

The other third, initiatives, is quite different. Building or implementing new systems requires business process knowledge, comprehension of business goals, and the variables that affect them. It requires embedding knowledge of multiple processes into a system that can be easily modified in concert with ever changing business environment. This requires IT to understand how the business runs, rather than how many neat features are in a new application.

Lose site of the business and IT managers start making stupid decisions. People second guess management, architects begin thinking the goal is delivering technology, and project managers cannot differentiate between critical scope and nice-to-haves. The Garage SyndromeTM reigns, projects start to fail, moral diminishes and the organization spirals downward. The business loses trust in IT's ability to help streamline its operations.

Want to read more?

Strategy, alignment, communication of goals is not easy. Our Vision To Value white paper talks about focusing your team on the key strategic corporate goals and ensuring everyone in your organization knows the direction.

The CIO's Role

The solution is the CIO. If the CIO understands the business' issues and demands his or her direct reports do the same, the organization's attitude, culture, and drive will change to deliver solutions with a business focus. Everything, including projects, runs better since the focus is away from implementing an application and centered on solutions for the business. This top-down attitude engages everyone in the project's chain of command to understand what is critical to quality.

The reporting structure of the CIO is irrelevant. It is the CIO's complete and thorough understanding of the business that makes the CIO and the IT organization relevant.

Read 10242 times

Related items

  • Filling Execution Gaps

    Executives define vision, strategy, and goals to advance the business. Projects enable companies to meet those goals. Between strategy and projects, there is a lot of work to be done—work that lays the foundation for the projects’ success. Through experience and research, six common gaps exist in organizations that inhibit project success—absence of common understanding, disengaged executive sponsors, misalignment with goals, poor change management, ineffective governance, and lackluster leadership.

  • Get Recognized as a Leader: Four Core Leadership Actions

    Leaders make decisions. This requires a core set of actions to gather the best information, hear out the concerns of others, and making a decision that everyone will follow—even if they do not necessarily agree with the decision. This session covers the four core leadership actions (listening, dialog and discussion, selling a vision, and elimination of blame) that are critical in your journey as a leader. We discuss and practice these actions in small role-playing groups.

  • Build Your Leadership Style: Six Leadership Strategies

    As project managers, you need to change your leadership style based on the situation. The need for a situational style is more important in project management than in nearly any other business position. Commanding the six core strategies—directive, expert, consensus, engaging, coaching, and affiliative—allows you to build the style most appropriate for the conditions surrounding project.

  • Strategy-Execution Gaps

    The statistics on strategy execution are dismal:

    • 59% of middle managers fail at resolving conflicts in corporate strategy.
    • 45% of middle managers cannot name one of the top five corporate goals.
    • 64% of cross department/functional issues are poorly resolved.

    And maybe as you could expect from this:

    • 53% of companies cannot react timely to new opportunities.

    You do not need to be a rocket scientist to know that this trajectory is not going to launch most companies’ latest strategic plans successfully. In fact, these data might make you feel that middle management would be better suited as test dummies for the next generation of manned space-vehicle. Granted, the data show there is a dearth of leadership in middle management, but executive tier has a culpable hand.

  • Process Mapping

    Process is at the core of any business. It makes work predictable, repeatable, and transferable. Without it we cannot scale our businesses. However, process can be a bane to making progress. Processes that work for a $10 million company have difficulties supporting a $30 million company. Trying to scale them to a $300 million company will not only fail but not address the issues that larger companies have that were never dreamt of in a smaller organization. Processes need to be discarded, revamped, and built—all of that without creating an overburdening bureaucracy.

    Anytime you need to go someplace, you first have to know where you are. Processes are never static and your company's current state is probably far from where you think it is. Hence, the first step is mapping out you company's current state followed by defining the future state. This is more than a logical map of the process; it must also include physical maps. Whether your process is solely to provide a service (say, website development) or physical (say, manufacturing) there are logistical issues that complicate the process flow. Without fully understanding those nuances, future state processes will not reach the desired efficiencies.

    For more information about process mapping fill out the form to the left and we will get in touch with you.

Leave a comment

Filling Execution Gaps

Available Worldwide

Filling Exectution Gaps cover

Filling Execution Gaps is available worldwide. Below are some options.

 

PG DirectLogo
Limited Time Price $20.99
Amazon logo
Book or Kindle
Flag of the United States Canadian Flag Flag of the United Kingdom Irish Flag Deutsche Flagge
Drapeau Français Bandiera Italiana PRC flag
Japanese flag
Bandera de España
Flag of India
Bandera de México
Bandeira do Brasil
Flag of Australia
Vlag van Nederland
DeG Press Logo
Barnes and Noble Logo
Books a Million Logo
Booktopia Logo
Worldwide: Many other
book sellers worldwide.

Rescue The Problem Project

Internationally acclaimed

Image of RPP

For a signed and personalized copy in the US visit the our eCommerce website.

Amazon logo
Buy it in the United States Buy it in Canada Buy it in the United Kingdom
Buy it in Ireland Buy it in Germany Buy it in France
Buy it in Italy Buy it in the PRC
Buy it in Japan
Book sellers worldwide.

Upcoming Events

Other's References

More Info on Project Recovery

Tell me More!

Please send me more information
on fixing a failing project.

Sitemap