ecaminc.com

  • Increase font size
  • Default font size
  • Decrease font size
Home Blog: Back From Red General Blog CIOs Are Fired For Failing to Provide Business Value
E-mail Print PDF
RSS

CIO Thinking, by Geek and PokeCIOs Are Fired For Failing to Provide Business Value

CIOs have two major responsibilities—keeping IT's lights on (backups, networks, email, etc.) and providing support for business initiatives. Being mediocre at either will make for a short career. Although the respective budgets are normally a 70:30 split, a CIO will be fired in a minute for failing to properly support the 30%. That portion of their budget actually generates the company money. Keeping the lights on is a thankless job. People simply expect networks run, data served, and viruses inoculated. It is expected much as we expect water when turning on the tap. Supporting business initiatives is just as thankless since 60% of projects seem to always be in trouble.

I am not pulling out the pompoms cheerleading to keep CIOs gainfully employed. I like seeing a job done well. Like all good CIOs, I know they need me just as badly as I need them. I bring the contrarian view that projects cannot be commoditized or successfully completed using some formula. Managers find comfort in the idea that ensuring projects stay within their initially defined scope, schedule, and budget means a successful delivery. Unfortunately, it is not quite that simple. Even making project targets does not guaranteed success. Many projects meet their targets and fail to provide adequate value. Poorly understood requirements, even if well defined, deliver solutions with no value. The path out of this is to accommodate change. For too many IT shops, change translates to time and time into money. Without the right mind set, IT will require significant delays and increases in funding.

It is quite reasonable to pay for design changes in anything. The desire is to minimize cost by encountering the changes as early as possible. For most IT projects, the only time the customer sees the value, or lack thereof, of what is being built is near the end of the project when they can work with the product. IT shops need to think like the business. To change this, business solution providers must focus on four basic traits—agility, communication, responsiveness, and cooperation.

Agility

Nothing is static. Business environments change faster than a teenager's clothes before a hot date on Saturday night. Initiatives must change at the same speed. People and the projects must be involved with, accommodate and encourage this change. They need the ability to adapt and change to new business situations.

Look for alternatives for the solution. Do not assume the goal is to make the most robust long lasting system, look for tactical options, objectively propose them, and let management make the decision. Create smaller, more agile projects with highly structured products that are easier to subdivide and build. Reducing complexity improves success rates, expedites delivery, and accommodates change.

Communication

Communication is a Two-Way Street

Communication is a two-way street. Direction comes from above and questions flow the other direction. The longer the communications chain the greater chance for the wrong message being delivered or questions getting garbled answers. Lean, low overhead organizations ensure what is being asked matches what is understood. Too many organizations with layers of management send orders to the troops and never provide the opportunity for questions to be answered. Managers assume that the direction is understood and workers think they are doing what is required to meet the concept.

This is true with the customer, too. Changes cannot be accepted unquestioned. Customers and suppliers must work together to determine the best solution to problems as they arise. Communication and cooperation are critical.

Responsiveness

Being responsive means providing. To respond without provide something is failing to respond. What better to provide than value. Every action should have its focus on providing value. Functional specifications and test scripts are not value; they are tools on the road to providing value. Product provides value. Responsive teams need to supply the customer with examples, prototypes, mockups, or early versions so everyone understands a common view of the goal.

Deliver solid product with only a few features as early as possible followed by rapid deliveries of new versions with more features. This keeps the focus on the value and away from frills.

Cooperation

Nothing is worse than a house divided. Every day project teams struggle to understand requirements, translate those into a product, and deploy that product on the IT infrastructure. They are the translators between the technical and the tangible. The only tool to make this work is cooperation. All problems are rooted in ill-defined requirements, poorly translated needs, and inadequate infrastructure.

Project teams forget they have the luxury of focusing a relatively confined system. The customer and infrastructure teams are less fortunate. They have vastly complex systems. Small alterations in these systems can have ripple effects throughout. Networks must accommodate dozens of varying applications, while customers have the whims of human nature and billions of imaginative minds looking for new ways to conduct business.

Open and honest brainstorming with a concise discovery plan that arrives at quick answers is the solution. People must be praised for resolving issues rather than berated for having to fix their problem.

As the adage goes, people need to do what they say and say what they do. It is no accident that next week's blog, discussing project heroes, will have cooperation as the primary trait of every hero.

Supporting the CIO

Delicious Delicious
Add to Technorati Favorites

CIOs may be fired for non-delivery, but they are really getting a just reward for failing to build an organization that exhibits these traits. They need to band with their peers to build a culture that is agile, communicative, responsive, and cooperative. One where it is everyone's job to ensure every project delivers value.

Tags: , , ,

Previous Blog Next Blog
 

Comments  

 
0 # Guest 2010-02-04 01:59
Great post. The agility and responsiveness sections ring true. As far as agility: We in IT need to be sure our values and behaviors support rather than thwart agility. We should be matching our customer in this regard, and in many cases we don't. For responsiveness, early on one organizations use of Rational Unified Process (no plug or lack of plug intended) the team was so focused on the process that they were planning to celebrate the completion of the first iteration. The problem is the business customer had no idea what the iteration delivered and no one on the IT team could figure it out either.
 
 
0 # Guest 2010-02-06 17:57
I like the post. But I wonder if it all falls on the CIO or is the focus on reducing cost versus increasing profit also a CEO issue.

Here is a link to my post further talking on this subject:

.../are-we-giving-it-conflicting-objectives-in-manufacturing-.html
 
 
0 # coach outlet 2011-02-10 19:57
coach outletThe article is as good as usual and I still have good experience here, thank you for your smart share.
 

Currently comment rights have been restricted to registered users only. Please try registering and logging on.


Who's Listening To Us...

Fortune/CNN Money logo
 
Forefront's logo
 
Logo Oregonian/OregonLive
 
Enterprising CIO's logo
 
Slashdot's logo
 
The CEO Magazine's logo
 

Read and Hear More...


Visualize Your Future

Change how you do business.

Project Failure Insight:

The following blogs regularly have articles on project failure, recovery and good management practices.
Chris Curran
CIO Dashboard
Michiko Diby
Preventing Project Failure
John Estrella
Dr. John A. Estrella's Blog
Mike Krigsman
IT Project Failures on ZDNet
John F. Moore
Random Thoughts of a Boston-based CTO
Roger Sessions
Simple Architectures for Complex Enterprises

Looking to buy the internationally acclaimed Rescue the Problem Project?

Image of RPP

For a signed and personalized copy in the US visit the book's website.

Not in the US? Try one of these book stores worldwide

Amazon logo
Book or Kindle
Flag of the United States
United States

Flag of Canada
Canada

Flag of the United Kingdom Flag of Ireland
United Kingdom

Flag of Germany
Deutschland

Flag of France
France

Flag of Italy
Italia

Flag of the PRC
中國
Flag of Japan
日本の
Barnes and Noble Logo
Book or Nook
Sony Reader Store logo
Sony Reader
Worldwide: Many other
book sellers worldwide.

Recent and Upcoming Events

Suggested Books

Many of these books have reviews in the "Books to Read" section of this site.

The Toyota Way
by Jeffery Liker

Related Items