Risk
10/28/2009
07:52 PM
Bob Evans
Bob Evans
Commentary
50%
50%

Global CIO: Hewlett-Packard's Hurd Says Bad IT Means A Bad CEO

Hurd offers a startling observation about how the roots of bad IT almost always reside in the corner office, and he explains how HP attempts to address the needs of both the CEO and the CIO.

Speaking to an audience of C-level execs, HP CEO Mark Hurd said that when he hears top executives tell him that their IT is bad, his first reaction is that the real problem is probably a bad CEO.

In an interview/presentation at last week's Gartner Symposium, Hurd was answering a broad question about the interplay between IT and business processes, and whether HP should be aiming its messages at CEOs focused on business outcomes or IT leaders focused (according to the question) on technology.

Hurd struggled initially with his reply—he clearly wanted the audience to know he and HP are big-picture folks who think about things that their customers' CEOs think about, but he also didn't want his CIO audience to think his standard practice is to go over their heads, and it took him a bit to tie all those threads together, and I'll get to that in a moment. But I want to focus on a startling correlation he made about the role that customer-side CEOs play in situations where a company's IT is bloated, backward, expensive, and ineffective:

"Because I'll tell you, I don't know how many CEOs are in the audience here, but when you show me bad IT—and I meet a lot of CEOs, and do a lot of talks in front of CEOs—and I get a lot of CIOs who tell me how bad their IT is. My first reaction—to be very frank—is it's probably a bad CEO, as opposed to bad IT."

Global CIO
Global CIOs: A Site Just For You
Visit InformationWeek's Global CIO -- our new online community and information resource for CIOs operating in the global economy.

That is a profound insight—I've never heard someone express that type of correlation so directly before: in 99% of the cases where bad IT's an issue, the fall-guy is the CIO, right? IT is the CIO's responsibility, so IT's failure is the CIO's failure, and the CIO's failure means the CIO's ouster, and the CEO is seen as a sharpy for rooting out the ineffective IT guy.

But what Hurd is saying—and yes, I know that Mark Hurd is an extremely smart guy and he certainly knew that the majority of his audience was CIOs, and that they'd get a kick out of such a correlation—is that the deeper fault lies with the top leader in the company, who failed to drive fundamental connections across business processes, applications, and IT. And that if the IT element in that equation is bad, then while the CIO might be guilty, the CEO surely is.

(For more details and analyses on HP's strategy and competitive issues, be sure to check out the "Recommended Reading" list at the end of this column.)

Because as Hurd went on to say about the job of the CEO: "At the end of the day, [the CEO has] gotta get this part [business processes] of the business right to be able to align IT throughout the company. It's no different than aligning your sales organization, aligning your R&D, aligning any other piece of it."

The context of the formulation of Hurd's Corollary—Bad IT = Bad CEO—was intriguing as well, because it came in the midst of a somewhat awkward answer from Hurd about whether HP aspires to move its executive connections within its global customers' C-suites beyond the CIO to the CEO and the LOB heads as Hewlett-Packard's products and services become more intensely intertwined with those customers' business processes and business outcomes.

As Hurd himself says, he gives lots of talks to CEO groups and meets with lots of customers, and it shows: Hurd is a polished and compelling speaker. But this one whole line of questioning—the interplay among his customers of the CEO and the CIO, and whether HP is at a disadvantage in focusing on the IT leader as the primary target versus the businessperson focused on business outcomes—threw Hurd off his game a bit. Here's what he said via my transcription:

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-4720
Published: 2014-12-27
Hillstone HS TFTP Server 1.3.2 allows remote attackers to cause a denial of service (daemon crash) via a long filename in a (1) RRQ or (2) WRQ operation.

CVE-2012-1203
Published: 2014-12-27
Cross-site request forgery (CSRF) vulnerability in starnet/index.php in SyndeoCMS 3.0 and earlier allows remote attackers to hijack the authentication of administrators for requests that add user accounts via a save_user action.

CVE-2013-4663
Published: 2014-12-27
git_http_controller.rb in the redmine_git_hosting plugin for Redmine allows remote attackers to execute arbitrary commands via shell metacharacters in (1) the service parameter to info/refs, related to the get_info_refs function or (2) the reqfile argument to the file_exists function.

CVE-2013-4793
Published: 2014-12-27
The update function in umbraco.webservices/templates/templateService.cs in the TemplateService component in Umbraco CMS before 6.0.4 does not require authentication, which allows remote attackers to execute arbitrary ASP.NET code via a crafted SOAP request.

CVE-2013-5958
Published: 2014-12-27
The Security component in Symfony 2.0.x before 2.0.25, 2.1.x before 2.1.13, 2.2.x before 2.2.9, and 2.3.x before 2.3.6 allows remote attackers to cause a denial of service (CPU consumption) via a long password that triggers an expensive hash computation, as demonstrated by a PBKDF2 computation, a si...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.