Tuesday, January 30, 2007

IT Governance!!! (Now, doesn't that sound fun?)


CEOs, CFOs, and Boards often say they need better "governance" when they refer to their IT investments; the term causes IT leaders nausea and engenders much eye-rolling. However, the root cause of those comments is almost always related to a failing of IT leaders to align IT capabilities with business strategies. This mis-alignment prompts questions of value around IT and leads to comments like, "What are we getting for our spend in IT?", "Why does this new system X cost so much?", and, "Those IT guys never deliver what they said they would". This situation results in a slowing of investment in IT over the long term, a general view that IT fails to deliver on it's promises, and will ultimately slow the overall growth of the company.

IT leaders who succeed, teach and inform their business colleagues of the need for IT investment and share the "big picture". If IT and business leaders were aligned on how IT investments were to be made and more visibility provided to ensure value and follow-through on both IT and business commitments, "governance" wouldn't be a concept that senior business leaders would feel a need to apply to IT.

The "smoke and mirrors" nature of IT investments, combined with the size of spend in IT, (ranging from 1% to as much as 15% of revenues depending on size, industry, growth strategies, etc), makes the business feel that IT is complex, "out-of-control" and therefore in need of better "governance". The truth is that IT investment is seldom vastly out of line at the "total spend" level. The sense of "out-of-control" usually has 2 contributing factors that are really alignment issues:

1. Most businesses don't have a solid relationship with IT leaders (no blame here, just fact). They don't spend time understanding how IT works outside their business area. And, IT leaders have failed to build relationships that would more easily facilitate that exchange of valuable perspective.

2. Most businesses don't have a meaningful mechanism or process for measuring the value of an IT investment, neither during business case construction nor after completion of the project; this factor would lead any business leader to question whether value was delivered associated with an investment. IT doesn't stand alone is this area; most capital projects are funded based on compelling business case delivery and championship/sponsorship by a vocal senior leader, then the "value realization" effort is seen as rehashing history and often not worth the effort."Hey, let's just focus on how we're going to make the next big idea work".

The "punch line" is that we as IT-savvy leaders need to better educate CEOs and Boards to foster environments where business leaders, (SBU leaders), are challenged to compete on who delivers the most value using IT. John Chambers, CEO of Cisco, brings his SBU leaders together to report on "IT Value Accomplishment" every quarter. He, and select Board members, hear from each SBU leader on how they've aligned with IT leaders to deliver shareholder value and true competitive advantage with new and emerging technologies. Wow! This forum creates intense competition around IT business case delivery.

Focusing the spotlight on the Business/IT relationship in this type of forum is a HUGE catalyst for alignment between IT capabilities and business strategies. You just don't hear the magnitude of questions and complaints related to technology value at Cisco you hear at other companies.

--juddd

IT Cost Allocation -- Why do we beat ourselves so?

Yesterday, I was talking with a Finance VP from a ~$30USD retailer who's the "IT Controller".  The topic of the conversation was IT cost allocation options.  She has been charged by the CIO to figure-out how enterprise-type IT spend should be allocated.  OK so far?  Well...  We discussed a few options: 
 
1.  Do allocate anything.  Keep all spend centrally tracked to allow the greatest control and accountability. 
2.  Allocate everything.  Only retain that spend which is infrastructural in nature.
3.  Allocate all capital projects to the P&L the project will support and retain all other spend to allocate across the enterprise.
 
We quickly settled on option #3 as the most likely.  Then we talked about how the "enterprise spend" should be allocated.  This is important because P&L owners don't like to be charged for anything they can't see return on.  Well...  Companies have to have HR systems, Finance systems, and Supply Chain systems to execute the business model.  The company has to pay for them; think "condo fees".  
 
So, couple of options there...  Allocate on a per employee basis.  Allocate on a % of revenues basis.  Or, allocate on a geographic/SBU basis.  Several factors to consider here.  To what extent will you be burdening the new growth areas of the company to pay "condo fees"?  Will you crush or stifle growth?  How much technology "utility" is mapped directly to an employee, e.g. traders, insurance agents, doctors offices, etc?  And, how is the enterprise structured related to SBUs...loose holding company or tightly governed unit of interoperating units?
 
This CO is not able to map technology to the employee per se.  They are in a HUGE growth mode with lots of folks working on new growth areas with little to no revenue associated with the strategies...yet.  And, they have a significant need to invest in IT in geographies where they're just entering...  Which option do you think they chose?  We'll allocate costs on a % of revenue basis to ensure we don't crush new growth.  Additional rationale is that IT is a growth enabler.  You would expect the highest benefit from IT to be felt where revenues are largest today. 
 
Neat conversation!  (I get to do this all the time!  Cool!)  --juddd

1st Mobile Blog - juddd

Consulting requires travel... Which can offer some thrilling vistas. -juddd