IT…What’s in a Name?

We have a serious “labelling problem” with IT. A few years ago, I was in Melbourne, Australia delivering a lunchtime address on “Meeting the Challenge for IT-Enabled Change” to CEDA (The Committee for Economic Development of Australia). CEDA’s membership includes business and political leaders, and their speakers include CEOs and Prime Ministers, so I saw this as a chance to really get my message across to the “right audience”. However, before starting, I asked for a show of hands from everyone from the IT function – about 90% of the hands went up. Seeing IT in the title, the CEOs had sent their IT guys.

When I started working in this field in 1963, what is now generally referred to as the IT function was described using terms such as Automatic Data Processing (ADP), Electronic Data Processing (EDP), and Computer Services. Over time, this has evolved to Information Systems, with the Data Processing (DP), or Computer Centre Manager role evolving to that of the CIO. Regardless of the name, when we use the term IT, it is the “T” that gets most of the attention, and, as in the case of the CEDA example, leads business leaders including CEOs to assume that anything to do with IT is the domain of the IT function.

While naming may appear to be a cosmetic or semantic issue it is much more than that. Names both create perceptions and carry baggage. The IT name, rightly or wrongly, is, as discussed above,  perceived as being about technology, which usually immediately leads to thinking about the costs of technology, and the name also carries a lot of baggage resulting from the long litany of “failed IT projects”.

It’s not just the non-IT folks that have to change here. On another occasion, I was facilitating a workshop around Value Management with members of the Seattle Chapter of the Society for Information Management (SIM). After the conversation had gone yet again one down a technology “bunny hole”, I made the comment that the organization’s name was SIM, not SIT. In Canada, we have the Canadian Information Processing Society (CIPS) – I guess that’s a bit better but processing doesn’t quite capture it. In Australia, and in the UK, they have the Australian and British Computer Societies  – that’s even worse! I can remember, several lives ago, interviewing a senior business manager to find out his requirements for a new system – he stopped my line of questioning, saying “What’s this all got to do with you computer guys?”

A few years ago, Forrester and HP tried to address this name issue by introducing the term Business Technology – the problem here is that they got rid of the wrong word. It’s not the technology that’s important – that’s not worth more than you could get for it on eBay, it is the change that the technology both shapes and enables that is important, change of which the technology is only a small part. Much, if not most of that change is enabled by better access to better information and better use of that information, increasingly, turning it into knowledge.

Let’s review a few other terms – data, information, knowledge and, yes, wisdom:

  • Data is just “stuff” – stuff that has to be collected, stored etc.
  • Data + meaning = information which can be acted on
  • Information + experience = knowledge which can result in better informed actions
  • Knowledge, over time, becomes wisdom which can become “conventional wisdom”, or just plain old “common sense”

Reinforcing my belief in parallel universes, a day after I had taken a first cut at this post, and the terms above, I came across  this explanation via Andy Blumenthal, Division Chief, US Department of State (not verbatim) from Dr. Jim Chen. I include this here both to reinforce, and provide a more elegant version of my efforts.

  • Data: This is an alphanumeric entity and/or symbol (ABC, 123, !@#…)
  • Information: This is when entities are related/associated to each other and thereby derive meaning. (Information = Data + Meaning)
  • Knowledge: This is information applied to context. (Knowledge = Data + Meaning + Context)
  • Wisdom: This is knowledge applied to multiple contexts. (Wisdom = Data + Meaning + (Context x N cases)).

In both of these versions, information is the linchpin. Data feeds it and knowledge and wisdom come from it.

So, back to the name. Increasingly today, the role of the CIO, and of their function is being questioned. There is also discussion on changing the meaning of CIO to Chief Innovation Officer. While certainly an improvement on some other proffered meanings including “Career Is Over” and “Challenge Is Impossible”, I don’t believe this is either necessary or wise. The CIO should be the Chief Information Officer, but their role, and the role and name of their function must change – moving from providing infrastructure to being a broker of services (both internal and external – and increasingly external). With this new role, Business Units must accept responsibility for defining the requirements for, meaningful use of, and value creation from these services, with the CIO (and their function) as a trusted partner, helping the other parts of the business:

  • optimize value from existing services;
  • be aware of and understand new value opportunities shaped and  enabled by current, new or emerging technologies,and the scope of business change required to realize value from those opportunities; and
  • evaluate, prioritize, select and execute those opportunities with the highest potential value such that overall business value is maximized.

The two key words here are information and services, so let’s forever drop the term IT function, and refer to it as the Information Services function. This is certainly not earth-shattering – I have worked in and for Information Services functions in the past, and quite a few are still called that today. But, for whatever reason, we have adopted as common usage the term IT function (all too often just abbreviated to IT) – it’s time to put that name, and all the baggage it carries, behind us and move on.

Finally, I am not suggesting we totally eliminate the term IT – there are and always will be the technology aspects, and a there is technology industry. But that is on the supply side. On the demand side, the focus should be on the use of that technology – on Information Services.

Getting Information Management Right

A couple of recent articles by Thomas Wailgum in CIO.com got me thinking – yet again – about information management (IM – for more on IM see Enterprise IT or Enterprise IM?). The first, Information Wants to Be Free, But at What Cost?, makes the point that the more information that enterprises continue to exponentially collect, the more difficult and expensive it’s going to be for them to understand and disseminate that information. The second, The Future of ERP, Part II, makes the case for change in that after four decades, billions of dollars and many huge failures, big ERP has become the software that no business can live without—and the software that still causes the most angst.

In The Information Paradox, and every time I present or discuss the topic of getting real value from our increasingly significant and complex investments in IT-enabled change, I use the slide below to explain how the way we use IT has evolved.

Slide1

When I started in this business, back in the early 60s, most, if not all commercial applications of IT were automation of existing tasks – where the focus was on doing the same thing more efficiently. I call this the appliance era – applications were stand-alone and very little business change was required (as illustrated by the pie chart on the slide). You could essentially have be given the application for Christmas – plug it in and it would do the job.

In the next era, which emerged during the 70s, things became  more complex. We moved beyond automation of tasks to creating, storing, distributing and manipulating information. The focus here was on effectiveness – using information to do things differently and to do different things. You now had to worry about what information was needed, by whom, where, when and in what form – and people had to be trained and incentivized to work differently. Appliances now had to work together in an integrated way, and the way business was done had to change – I call this the rewiring era.

In the next era, which emerged during the 80s, we began to see what I heard a Northrop Grumman CIO describe as “game changing plays” – changing the rules of existing industries and creating new ones. I call this the transformation era. While the changes might not be possible without the technology, the bulk of the effort required to achieve the desired outcomes involves changes to the business – including the nature of the business, the business model, business processes, peoples roles and skills, organizational structure, physical facilities and enabling technology. Those appliances – now ranging from “mainframes” to smart-phones – have  to work together in an integrated way, not only within an enterprise, but outside it – on a global basis.

Unfortunately, while our use of IT has evolved – our management of it has lagged. In far too many cases, the focus is still on the IT appliance  – “plug it in and the value will flow”. Those days are long gone. We are not today simply dealing with appliances – or with simple appliances – we are dealing with massive organizational and cultural change – transformational change. Change that is enabled by technology, but of which technology is only a small part.

The more that I have though about this, and talked about it, the more I feel that one of the sources of the perceived and real failure of investments in IT-enabled change to deliver the expected business value is that we have still not got the information piece right. (Note that in the following comments, I may appear to, and indeed do, to a certain extent, use the terms data, information and knowledge somewhat loosely. This is not because I do not understand the difference – or at least have an opinion on it – but because terminology in common use doesn’t always make a clear distinction, and I don’t want to bog this post down with that discussion.)

While the amount of data we store continues to grow – Gartner predicts that the amount of enterprise data will grow 650 percent during the next five years, a recent Forbes Insights survey of more than 200 executives and decision makers at top global enterprises found that nearly one-quarter of the respondents cited the availability of timely data as one of the top barriers to aligning strategy and operations today. In an earlier post, The Knowing-Doing Gap,  I quoted James Surowiecki, from his book, The Wisdom of Crowds, where he said “…information flows – up, down and across organisations – are poor, non-existent or “filtered” in all directions, decisions are made by a very few with inadequate knowledge and information, and there is limited buy-in to whatever decisions are made.” So, with an enormous and growing amount of data being collected, at considerable cost, why haven’t we got it right? I would suggest that there are a number of reasons for the current state of affairs:

  1. Knowledge is power
  2. Not knowing what information is relevant
  3. Too much information
  4. Bad data
  5. System complexity
  6. Go with the gut

Let’s examine each of these.

Knowledge is power

Building on the Surowiecki quote referenced above, Sir Francis Bacon was (among) the first to say that “Knowledge is power”. Peter Drucker expanded on this saying “Today knowledge has power. It controls access to opportunity and advancement.” This presents a cultural and behavioural barrier to sharing information and to getting it to (all) the people who need it – one that should not be under-estimated.

Not knowing what information is relevant

In another life, I led a lot of what we then called Information Resource Planning assignments. We would interview key stakeholders in an enterprise to find out what information they required. Once we had their requirements, I always asked one final question: “If you had this information, what would you do differently?” Very few people could answer this question or had even thought about it. Enterprises need to take an outcome and role based approach to identifying and meeting information requirements. Expanding on my earlier question, we need to ask: ” Based on the outcome(s) we want to achieve, what decisions/actions need to be taken, who needs to take them, and what information do they need – where, when and in what format – to take them, and what information do we need to know that things are working as they should be?”

Too much information

Today we are drowning in information and, as per the Gartner prediction above, it is only going to get worse. Even if the information that we require is available, it may be lost in the sheer volume of information – the information noise. This noise level is only going to increase. If we are to cut through this noise to what is relevant, it is even more critical to take an outcome and roles based approach to defining information requirements. We will also need to beyond the traditional reporting metaphor and simple, or simplistic dashboards to much more sophisticated, yet intuitive (see “System complexity” below) analytical and data visualization tools.

Bad data

One of the biggest risks to organizations is “bad data quality.” Results from Scott Ambler‘s September 2006 Data Quality Survey show that 46% of data have some data sources that are a “complete mess” or the data itself has serious problems. In an April 2009 data quality PRO survey of Data Quality in Business Intelligence, 42% of respondents reported minor issues, 50% reported major issues, and 4% didn’t know –  leaving just 1% reporting no problems. A 2007 Accenture CIO survey claimed that the costs of compromised data quality are clear—billions of dollars squandered each year due to mistakes, manual processes and lost business. Of the CIOs surveyed,  29 percent said that they had minimal or limited data quality efforts in place, even for critical systems, and only 15 percent of respondents believed that data quality was comprehensively (or near comprehensively) managed. Indeed, not a single North America-based organization reported that they have a fully comprehensive data quality program today. Information is only as good on the data it is based on. It will take time to implement workarounds for, and fix the mess that we have created. In the interim,  we need, at a minimum,  to know how credible the information is and what confidence we can have in decisions based on that information.

System complexity

ERPs were promoted as one “solution” to the information management challenge, but have  proven a challenge for many enterprises – see ERPs – Can’t live with them – Can’t live without them!. Where they have been successful, they may have done a good job of integrating data across enterprises, but few would describe them as easy to use. Even if relevant information is available, if it is too complex or time-consuming to get at it, people won’t. While somewhat simplistic, I have often felt, and even more often heard that “if I need to be taught how to use it, I won’t use it.” Again, information needs to be relevant, outcome and role based, and easy to access and understand.

Go with the gut

Business intelligence was identified in the 2009 SIM Trends Survey as one of the top technologies that enterprises were planning to invest in. Research reported by Accenture in 2008 found that close to half (40%) of major corporate decisions are based on “gut feel”.  The reasons for this executives cited most often, which reinforce some of the points above, were: because good data is not available (61 percent); there is no past data for the decisions and innovation they are addressing (61 percent); and their decisions rely on qualitative and subjective factors (55 percent). 23 percent of respondents identified “insufficient quantitative skills in employees” as a main challenge to their company, and 36 percent said their company “faces a shortage of analytical talent.” 39 percent of respondents said that IT capabilities restrictions were a major challenge and 27 percent said there was an inability to share information across organizations within their company. I also wonder if this might not also be a bit of the “cult of leadership” where they believe that they have achieved a level of knowledge/wisdom where they don’t need information to make good decisions.

Information and people are the two most important and, in all too many cases, the most ineffectively utilized assets in today’s enterprises. What information is available to people – be they executives, managers, workers, suppliers, customers or other stakeholders –  the quality of that information, and how they use it is a key part of what determines business success or failure – value creation and sustainment, or value erosion and destruction. This is true both for “business as usual” activities and – even more so – for transformational change. If enterprises do not get the information piece right, their transformational efforts, and their survival, will be in extreme peril.

Reflections on SIMposium09

I had the opportunity to attend and speak at SIMposium09 in Seattle last week. As Seattle is a great town and close to Victoria,  I took the opportunity to take Diane and we both enjoyed Seattle and spent a few very relaxing “Internet-free” days at the wonderful Lake Quinalt Lodge on the Olympic Peninsula after the conference. Having now had time to reflect on the conference, I offer a summary of my thoughts (and in doing so, draw on a number of my earlier posts).

Introducing the sessions on Tuesday, the Moderator, Julia King, Executive Editor of Computerworld, said that what she had taken away from the conference up to that point were three things – people, process and productivity. While productivity – specifically doing more with less – was a common theme, and there was considerable emphasis on people and some on process, I would expand on this somewhat. From what I heard, both through formal presentations, and in informal discussions, the things that I left thinking about, and which I will expand on below were – value (including but not limited to productivity), leadership, innovation (where I would include process), people, and change (specifically management of strategic change). I will talk a bit more about each of these below.

Value

It should come as no surprise that this is my first point. I was pleased that a number of sessions did focus on value, and it was mentioned to varying degrees in others. I was however disappointed when Jerry Luftman presented the results of the 2009 SIM IT trend survey that the word was not mentioned in any of the top ten CIO issues. In fairness, I do understand that in order to plot trends, there has to be some consistency in questions year over year. While it could be argued that the “alignment” question may be a proxy for value (although many people told me they never wanted to hear this question again), and that it is implied in others – I believe we have to make value explicit and  put it front and centre. Certainly, productivity is one aspect of value, but only one aspect – one that tends to focus on doing more with less, and by inference cost. In The Information Paradox, we talked about 3 aspects of value: alignment (NOT the infamous “Aligning IT with the business” topic which, in my mind, makes about as much sense as talking about “aligning our heart with our body”, but rather ensuring that investments are aligned with the enterprise’s strategic objectives); financial worth (which I now refer to as business worth including both financial and non-financial aspects); and risk (both delivery risk and benefits risk).  The Val IT ™ framework further defines value as “total life cycle benefits net of total life cycle costs adjusted for risk and (in the case of financial value) the time value of money”. We need to shift the discussion from the cost of technology to the value of the business change that it enables. We need to create a culture of value in our enterprises.

Leadership

A quick scan of the agenda shows that this was by far the most prevalent topic – not surprising given SIM’s target constituency. There is absolutely no denying that we need more and better leadership – but what do we mean by that? Are we talking about grooming those few who will rise to the corner offices in the top floor of corporate HQ, or are we/should we be talking about something beyond that?  A former colleague of mine, Don Tapscott, used to say (may still say) that “leadership can come from anywhere”. I have been thinking for a while about the “cult of leadership” – in his book, The Wisdom of CrowdsJames Surowiecki identifies one of the challenges is that we put too much faith in individual leaders or experts, either because of their position or track record and that these individuals also become over-confident in their abilities. I don’t want to question the ability and competence of all leaders or experts – while I certainly have seen my share of bad ones, most are good people doing the best they can. However, in today’s increasingly complex and fast-paced knowledge economy, much of which is both enabled by and driven by technology, it is unrealistic to expect individuals, however good they are, to have all the answers, all the time. The reality is that neither position nor past success is any guarantee of future success.

If organisations are to succeed in today’s knowledge economy, they cannot constrain themselves to the knowledge of a few individuals – to put it a more brutal way, they cannot be constrained by the habits or ego(s) of their leader(s)! Organisations must tap into the collective knowledge of all their people – retaining appropriate accountability, based on the law of subsidiarity – an organizing principle that matters ought to be handled by the smallest, lowest or least centralized competent authority. This means locating accountability and decision-making at the most appropriate level, while supporting decisions with broader and more knowledgeable input.

Innovation

We hear a lot about innovation and the potential for CIOs to become Chief Innovation Officers. Interestingly, a number of recent surveys show that executive leadership is disappointed with the lack of innovative ideas from CIOs. But what is innovation? The Oxford Dictionary defines innovation as [t0] bring in new methods, ideas etc. often followed by making change. All too often, we believe that innovation requires new technologies. In a recent Entrepreneur article, Tim O’Reilly, who launched the first commercial website, coined the term “Web 2.0” and was instrumental in the popularization of open-source software, isn’t buying the hype: He calls the era of the I-word “dead on arrival.” “If it is innovative, everybody will know,” O’Reilly says. “Adding words to it does not help.” The current “innovation” overload is the result of folks who don’t know what true invention is trying to pass themselves off as trailblazers. He’s seen companies throw away great ideas because it wasn’t immediately obvious how to make money from them. Then smaller companies and entrepreneurs would come along and play with the idea, just because they’re passionate about it. And they would be the ones to unlock the idea’s potential and grow into the money. While new technologies do indeed enable new methods and ideas, they are not necessary for innovation. Innovation is equally powerful, and often easier, by simply coming up with new and creative ways of using existing technologies.

People

Ultimately, it is people who lead, people who innovate, and, as a result, people who create value. Over the last few decades, much has been said and written about empowering the people within an enterprise – unfortunately little of that talk and writing has translated into reality. As James Surowiecki says, “Although many companies play a good game when it comes to pushing authority away from the top, the truth is that genuine employee involvement remains an unusual phenomenon.” As a result of this, information flows – up, down and across organisations – are poor, non-existent or “filtered” in all directions, decisions are made by a very few with inadequate knowledge and information, and there is limited buy-in to whatever decisions are made. As Peter Senge says in The Fifth Discipline Fieldbook , “…under our old system of governance, one can lead by mandate. If you had the ability to climb the ladder, gain power and then control that power, then you could enforce…changes…Most of our leaders don’t think in terms of getting voluntary followers, they think in terms of control.” I should add here, based on Monday’s closing keynote “It’s about the People”, given by Bill Baumann, Vice President of Information Technology for REI, that REI does appear to be one enterprise that does understand empowerment.

In this context, although there was not a specific session on the topic, social networking (including Web 2.0 and crowd-sourcing etc.) was discussed in many of the sessions, and in informal discussions. As I have said before, I am becoming increasingly interested in how social networking, rather than being viewed as a potential problem to be managed within the “traditional” view of governance and management – today still largely based on beliefs and structures that are a hundred years old – has enormous potential to revolutionize governance and management. In doing so, we could truly tap in to the experience of all employees (and other stakeholders) – not be limited to the knowledge/experience of those few anointed leaders or experts. This could actually make the much-abused term empowerment mean something by giving people the opportunity to contribute to/participate in decision-making, actually be listened to and, as a result, re-engage and really make a difference.

Change

The challenge facing enterprises today is not implementing technology, although this is certainly not becoming any easier, but implementing IT-enabled organisational change such that value is created and sustained, and risk is known, mitigated or contained. The creation and sustainment of value from innovation requires understanding and effective management of change in how people think, manage and act, i.e. change in human behaviour. Unfortunately, as we were reminded in one session by Jeffrey Barnes and Cheryl White, studies have shown consistently over the last 25 years that the failure rate of strategic change initiatives is between 85-90%. Let’s look at a number of scenarios where such initiatives can come to a premature halt.

The first of these is implementation by fiat, without an adequately thought out plan and commensurate resources. There is all too often a tendency for executives to believe that once they say something should be done it is – this is rarely the case. I sometimes describe this as the “Star Trek school of management”. Executives, just like Captain Picard, say “Make it so!” – they often don’t fully understand what “it” is or how they will know when they get there, and  the people they say it to all run off with very different ideas of what “it” is creating a lot of activity – often in conflicting directions. As Larry Bossidy and Ram Charam suggest in Execution, The Discipline of Getting things Done, the role of the executive when saying “make it so” is to ensure that no-one leaves the room until the executive is confident that they all understand what “it” is and, when they come back with a plan, that they don’t leave the room until he/she is confident that the plan has a good chance of delivering “it”.

In other cases, organisations take on too much in the first bite – this either results in “sticker shock” with no action being taken or, particularly when, as is often the case – especially in the current environment of short-termism – the time-frame is unrealistic, failure. The opposite can also be true, doing too little and/or taking too long to do it such that patience runs out and/or interest diminishes to the point of backing off.

Also, where progress is being made, success is not always promoted and built on – without demonstrated and recognized success it can be very difficult to maintain the interest and attention of executives to sustain the change initiative, especially one that may take many years, as many, if not most such initiatives can do. This can become particularly evident if a new executive comes on the scene and asks “Why are we doing this?” Without a sound response, this is often followed by “We did just fine without this where I came from!”

Many of these scenarios are exacerbated when insufficient thought has been given to metrics – measurements that must include both “lag” metrics – are we there yet? – and “leading” metrics – are we on track to get there?, as well as tangibles and intangibles. As Faisal Hoque, Chairman and CEO of the Business Technology Management Institute says, “…technology [itself] warrants evaluation with a tangible set of measures. But the majority of what technology actually does falls more into the sphere of the intangibles”. Understanding how those intangibles (often lead indicators) can contribute to tangibles (often lag indicators) is a key part of value management.

John Zackman offered another explanation for the challenge of change when positioning enterprise architecture – in the context of the overall enterprise – as being about managing complexity and change (which I very much agree with). John said “If you can’t describe it you can’t build it or change it.” John’s comments raise a number of  interesting questions which I won’t attempt to answer here.  Is it actually possible to “reverse architect” today’s complex global enterprises that have, somewhat like London’s Heathrow airport, grown ad hoc over time without any underlying architectural framework or design? If not, are they doomed to eventually fail? Will new and emerging enterprises take a more disciplined approach or will they follow the same pattern such that the cycle continues?

For more on the topic of change, go to Managing Change – The Key to Realizing Value and The Knowing-Doing Gap.

I will explore some or all of these topics more in subsequent posts.

Back to the Basics – the Four “Ares”

Well, having now finished with the Sidney Fine Art Show – which was incredibly successful – it’s time to get back to this blog.

As I prepare to head down to Seattle where I am speaking at SIMposium09 on November 9th – just 6 weeks before my 65th birthday – I have been reflecting on the underlying foundation of what I have been doing over the last 20 plus years – what have come to be known as the “four ares”. They have certainly guided my thinking and, since they were published in The Information Paradox, continue to be widely referenced  – sometimes those references are even attributed. The idea came when I was presenting a diagram of, what we then called, the Information Resource Planning approach, to the executive of a large Canadian utility. As I was going through it, one of the executives stopped me, saying: “This is all “gobbledygook” to me – can you just explain it in plain English?” So, I turned the somewhat obtuse and long-winded statements on the chart into the questions each box was trying to address. What had been somewhat of a “talking head” session turned into a lively discussion which resulted in a  successful assignment with very positive outcomes. After that, I applied the same approach to almost everything I was doing including, at the time, DMR’s (now Fujitsu’s) Macroscope methodology – and the four “ares” were born. They have been “tweaked”, but have essentially remained the same for more than two decades.

At the time, I am not sure that I had even thought about the term governance, or could have described what it was. However, over time the two ideas have come together in that, in my view, the ability to continually ensure that enterprises can get positive answers to the four “ares” is the essence of effective enterprise governance. I use the term enterprise governance because, although the origins of the four “ares”, and much of their current application relate to governance of IT, they are equally applicable to the broader enterprise governance view. Indeed, one of the comments/criticisms I have had of both The Information Paradox, and the Val IT™ Framework, is that the term IT should have been dropped, or at least de-emphasized,  as they are both more broadly applicable to any form of investment or, indeed, any form  of asset.

For those of you still wondering what I am referring to, the four “ares” are:

  1. Are we doing the right things?
  2. Are we doing them the right way?
  3. Are we getting them done well?
  4. Are we getting the benefits?

Whenever I am talking with executives, I always have to pause when I get to the four “ares”as they invariability write them down. They are questions that are easy to understand although, unfortunately, not always easy to answer. Indeed, I often feel guilty that they appear too simple. I also feel somewhat guilty about the term “right” in the first two questions. I am not sure that there can always, or even ever be a totally right answer to those questions. However, asking these questions can definitely eliminate a lot of “wrong” decisions. A key point about these questions is that they need to be asked continually. Whilst important to ask them when an initial investment decision is being made, it is equally important to ask them throughout the full economic life cycle of that investment decision. That life-cycle includes a number of stages:

  • Development  – creating the necessary capabilities (hereinafter referred to as assets)
  • Implementation  – delivering the assets
  • Value creation  – adopting and using the assets to achieve the expected level of performance
  • Value sustainment  – assuring that the assets resulting from the investment continue to create value, including additional investments required to sustain value
  • Retirement phase – decommissioning some or all of the resulting assets
The four questions, in order, essentially apply to strategy, architecture, delivery, and value. As illustrated below, they collectively encompass alignment with strategy, business worth, including benefits and costs, and risk – including delivery risk and benefits risk.Slide1

As further illustrated below, within the context of governance of IT, the first and last  questions relate to the “demand” side – business governance of IT, while the second and third relate to the “supply” side – IT governance of IT. Collectively, they represent a complete view of enterprise governance of IT.
Slide2

As we said in The Information Paradox [with some updates], “ Tough questioning is also critical to get rid of silver bullet thinking about IT and lose the industrial-age mind-set that is proving extremely costly to organizations.  Asking the four “ares,” in particular, helps to define the business and technical issues clearly, and thus to better define the distinctive roles of  business executives and IT experts in the investment decision process. Are 1, Are we doing the right things? and Are 4, Are we getting the benefits?  raise key business issues relating to both strategic direction and the organization’s ability to produce the targeted business benefits.  Are 2, Are we doing them the right way?  raises a mix of business and technology integration issues that must be answered to design successful [IT-enabled] change programs.  Are 3, Are we getting them done well?  directs attention to traditional IT project delivery issues, as well as to the ability of other business groups to deliver change projects.”

In Val IT, specifically in version 2.0, we fleshed out these questions and also expanded them to include IT services, assets and other resources (while this is in the context of IT – they could equally well be expanded to include other assets).

1.  Are we doing the right things? The Strategic Question.

  • Are our investments:
    • in line with our mandate and vision?
    • consistent with our business principles?
    • contributing to our strategic objectives, both individually and collectively?
    • delivering optimal benefits at an affordable cost with a known and acceptable level of risk?
  • Are resulting IT services, assets and other resources continuing to deliver value by addressing real business needs and priorities?

2.  Are we doing them  the right way? The Architecture Question.

  • Are our investments:
    • in line with our organisation’s enterprise architecture?
    • consistent with our architectural principles and standards?
  • Are we leveraging synergies between our investments?
  • Are our IT services delivered based on optimal use of the IT infrastructure and other assets and resources?

3.  Are we getting them done well? The Delivery Question.

  • Do we have:
    • effective and disciplined management, delivery and change management processes?
    • competent and available technical and business resources to deliver the required capabilities and the organisational changes required to leverage them?
  • Are services delivered reliably, securely and available when and where required?

4. Are we getting the benefits? The Value Question.

  • Do we have:
    • a clear and shared understanding of what constitutes value for the enterprise?
    • a clear and shared understanding of the expected benefits from new investments, and resulting IT services, assets and other resources?
    • clear and accepted accountability for realising the benefits, and relevant metrics?
    • an effective benefits realisation process over the whole investment economic life-cycle, to ensure that we are maximising business value?
One of the objections we often here to implementing or improving governance practices or frameworks is that we are making it much too complex. There is indeed some truth to this given that the IT industry appears to have single-handedly invented English as a second language, i.e. talking in “techno-speak”. There are also a growing number of what are perceived to be competing frameworks in the marketplace. The four “ares” rise above this and provide a very simple yet comprehensive and powerful set of questions that can be used to help you to start the conversation – a conversation that is long overdue in many enterprises.

Enterprise IT or Enterprise IM?

Reflecting on yesterday’s post CIOs told to scrap enterprise IT departments, I realized that over the last 5 years working with ITGI discussing IT governance, I have myself become a victim of the “IT label trap”. While implicit in everything I have done, I have not made explicit a distinction that I started making with a large Canadian resources company client way back in 1991 – the distinction between information management and information technology. Although I am not sure we even used the term back in those days, what we did, working with the executive, was to put in place effective governance of information.  Governance which separated, and made explicit the differences between managing information and managing the technology used to collect, store, manipulate and distribute it – with the business being accountable for managing information, while the IT function was accountable for managing the technology.

We defined the distinction between information management and the management of information technology as:

  • Information Management is concerned with the “why” and “what” of business requirements, and the “how” of business management processes, but not the technological “how”.
  • The management of Information Technology is concerned with the technological “how” of meeting business requirements, within the guidelines established by the information management processes.

As this information is still proprietary, I will not go into more detail here other than to say that, based on understanding this distinction, we created a vision for the role of information, then went on to develop and implement principles, an overall architecture, roles and responsibilities, and supporting organizational structures. Among other things, this involved Integration of business planning and information systems planning and transfer of a significant portion of the IT budget to line departments.

Fast forwarding now to the “Four Ares” that we introduced in The Information Paradox and which became the basis for Val IT™:

  1. Are we doing the right things?
  2. Are we doing them the right way?
  3. Are we getting them done well?
  4. Are we getting the benefits?

The first and last questions are primarily concerned with information management, while the second and third are primarily concerned with effective management of information technology.

I was reminded of this distinction again in 2005 – just as I was getting involved with ITGI so the IT label hadn’t quite got me – when leading a number of CIO workshops with the Seattle chapter of the Society for Information Management (SIM). The workshops were around the topic of  “Rethinking IT Governance – Beyond Alignment to Integration.” I found that the discussion kept descending into technobabble and had to remind the participants that there might be a reason why the organization was called the Society for Information Management – NOT the Society for Information Technology! I will be making this point again when I speak at SimPosium09 in Seattle in November.

Given the above, I think that what I should have said in yesterday’s blog was that the heading of the article should have been: “CIOs told to scrap enterprise IT departments BUT not an enterprise IM Role”. In the same vein, I also think that Val IT might have been more appropriately named Val IM.

You can be assured that I will be making the distinction between information management and the management of information technology more explicit in the future.

CIOs in the Era of Doing More with Less

A shorter post than usual, but I wanted to  highlight an interesting article by Brian P.Watson in CIO Insight which quotes, among others, Peter Whatnell, CIO of Sunoco and President of the Society for Information Management (SIM).

While quite a bit of the article is about tactical stuff, the quotes below capture the type of thinking we should be looking for from CIOs, and that CEOs should be demanding. These include:

“Most importantly for IT leaders today, doing the right things means focusing on the long-term view—the strategic components of your plan and that of the overall business, not the bits and bytes of whatever hot technology is dominating the IT buzz”. – Brian Watson

“…the opportunity for IT leaders is more strategic than tactical, more business than technology.” – Peter Whatnell, CIO, Sunoco and President, SIM

“When all is said and done, blending a strategic business focus with the right IT decisions could be what separates the CIO wheat from the chaff. Put those skills together, and you’ll become a true partner:  A CIO has to become the internal, go-to expert consultant for every functional head in the organization to help them execute, innovate and enable strategy more efficiently with the right technology.” – Vincent Cirel, CIO, Norwegian Cruise Line

While these quotes are encouraging, we should remember that the requirement for CIOs to be more strategic business partners should not come as a “Eureka” – resulting from the current economic crisis. The requirement has existed for a long time – certainly well over two decades. The difference today is that the consequences of not doing this are much more serious. CIOs and CEOs who do not understand this are putting the very survival of their organizations at risk!

You can be assured that I will be discussing this topic more in presentation at my SIMposium09 in Seattle on November 9th.