6 IT Trends & 15 New Habits for CIOs & Their Teams

The CIO/ITD In Crisis.

Harvard Business Review blogger, Jim Stikeleather, posted recently  The CIO in Crisis: What You Told Us – a few particular points caught my attention:

“The best executives I have met have had a great understanding of how to use technology to gain competitive advantage and improve operations. They also worked with the CIO to help them to understand the business. They worked together to identify the technologies that could improve the company’s competitive advantage versus technologies that were needed to support the business. Once this was done, the executive leadership and CIO focused on implementing technologies that improve the company’s competitive advantage”.

All the parts of the organization have to come together and build a common language to discuss their markets and their enterprise. They need to have a common appreciation of each other’s purpose. The CIO must step up and mentor the C-suite on the potentials, possibilities, threats and opportunities of information technology..”.

If IT and the CIO come to the party talking like engineers, only offer convergent lines of thought(analytical, rational, quantitative, sequential, constraint driven, objective and detailed focus) and don’t offer a more holistic, shaded divergent thinking point of view (creative, intuitive, qualitative, subjective, possibility driven, holistic with conceptual abstractions), then they have missed the point”.

The CEOs were actively aware, concerned, looking at alternatives such as chief digital officers, or creating “not-so-shadow” IT organizations under the CMO”.
For existing CIOs, ask yourself a few questions. Are you generating customer value? Are you (or do you have the potential to be) the best in the world at what you are doing? Are you required to do what you are doing? Using the answers to those questions, what do you need to stop doing, start doing or do differently?..”. [see 15 ways to change the ITD’s habits table later in this post].

In a similar vein, according to a recent CIO event run by Forrester Research: “The IT department of 2020 could disappear as a separate entity and become embedded in departments throughout the entire organization“.
This article posits that the need for change is now undeniable, and that CIOs are looking for practical steps for creating new habits in their teams. These new habits, developed now, will help prove the continuing need for a central Enterprise IT Department.


History & Trends.

The demise of the IT Department is not a new  prediction, it was first suggested in 2004 by Nicolas Carr in his book ‘Does IT Matter?‘ and again in 2007 when Chris Anderson published his ‘Black Wire – White Wire’ article. This post talked about how corporate IT was being over-taken by consumer-IT. Later, in January 2008,  Nicholas Carr famously pronounced “The IT department is dead” referring to the up-take of utility computing since his 2004 prediction. 

Since then, others made further observations about emerging IT trends that appear to strengthen those predictions. Today, around six hard trends are well established. They sit within an umbrella trend we described as ‘Externalization’ back in 2007. Later, in ‘Flash Foresight‘ Daniel Burrus explains how he identified many of the established technology trends and why they are ‘Hard’ trends rather than passing fads. More recently,  in his book ‘Agile Architecture Revolution‘, Jason Bloomberg talks about understanding the enterprise as a Complex System – a System-of-Systems. His book is architectural guide to help IT Departments respond to the Externalization trend and, at the same time, it highlights the need for a change in mindset within the IT community.

In parallel, John R. Rymer of Forrester Research coined the phrase ‘Business Technology’ (BT) to describe the ever-increasing reliance on information technology by businesses of all types to handle and optimize their business processes  and the need for a more integrated & holistic approach to the use of business-embedded information technology.  Here’s what Wikipedia says about BT

The increasing use of the term business technology in IT forums and publications is due to an emerging school of thought that the potential of information technology, its industries and experts, has now moved beyond the meaning of the term. Specifically information is seen by some as a descriptor not broad enough to cover the contribution that technology can make to the success of a business or organization“.

Focus on Externalization and BT.


Acceptance of the Externalization trend, and a deep appreciation of ‘Business Technology’ theme, provide the canvas, on which, we can sketch-out the ways in which the IT Department must change to survive. Probably most importantly, the CIO needs to find the time to think strategically: from ‘Whac-A-Mole-IT-Management’  to strategic, Business-Technology leadership. Thinking strategically means the CIO needs to develop a deep appreciation of  the various ‘markets’ his/her team serve, as both a supplier, and a broker of services, to those markets. Such markets exists within and outside the enterprise and are made up of customers, suppliers, intermediaries and other stakeholders. All with differing values and requiring different sensitivities to protect and enhance trust relationships.

How to prepare for the inevitable change.

At my current company, we use the ‘BT’ label help position our five-year vision & strategy. It helps frame the discussion about the many areas of change required: cultural, technological, procedural, organizational & regulatory. BT is not, however, a new name-tag for the IT department – it represents the new thinking required across the whole business. It might seem ironic, given the predictions, that it was our CIO who initiated the discussion – I suspect, however, this will often be the case: the CIO is frequently the only C-level executive who has a holistic understanding of both the breadth and depth of the business.

Back in May this year, I posted about the work we were doing to establish a BT Vision. This has since been developing gradually and is gaining acceptance across the IT senior leadership team, but more importantly, with C-Level executives.

Recently, I was invited to share, with a large multinational conglomerate, some of the more tangible changes we’re implementing  Our vision & journey towards ‘BT’, and our response to the the ‘Externalization‘ trend set the context for the discussion. Here’s the list of ‘contrasting behaviors‘ I shared: 

15 ways to change the IT Department’s habits

Old Habits
 New Habits
1.The department of ‘No’
2.Products focus
3.Internal SLAs
4.IT Strategy
5.Cyber security tooling
6.CAPEX-first mentality
7.Solution-focused technology architecture
8.Product standardized IT portfolio management
9.Governance of large IT projects
10.IT Cost Centre management
11.Internal procedures & methods
12.‘Family’ of IT vendors
13.Gadget-focused innovation
14.Periodic, internally-focused, measurement
15.Technology focus
1.The department of qualified ‘Yes’
2.Services focus
3.Services internal/external ecosystem –SLA-chains
4.Integrated BT strategy
5.Cyber security culture
6.Balanced, outcome-focused, investment
7.Adaptive, value-focused,  Enterprise Architecture
8.Principle-led architecture & standards-based integration
9.Company-wide, joined-up,  BT-governance
10.BT services broker, innovation-lead and advisory
11.Internal & external engagement
12.Consumer-driven, ecosystem of suppliers
13.Customer-story-based innovation
14.Constant, external & internal, feedback-loops
15.Focus on information value & risk

We’ve made good progress on many of the 15 points, but I’d say the most compelling for the business are: 1) The department of qualified ‘Yes’,  4) Integrated BT strategy, 5) Cyber security culture, and 13) Customer-story-based-innovation. I’m pleased to see these seem resonate with the observations made in the HBR article mentioned above.


Will the IT department will be dead by 2020?

Will the need for a central IT department go away by 2020? No, not in our case at least, but it does need to rapidly adapt and evolve and  we believe those  that don’t will become side-lined. We are seeing, however, other businesses taking a different view: there does seem to a dangerous, frustration-with-the-ITD, pattern emerging where IT departments are being split-up into LOB sub-teams, without considering the need for, holistic, enterprise-wide thinking.

Maybe the IT Department label won’t exist by 2020, but many organizations will require a team that focus on the value of the digitally enabled world that balances agility, resilience, security and cost across the whole enterprise. For these companies, dispersed and unbridled IT (use of consumer-led technologies and commoditized services) would lead to unprecedented levels business risk: operational, financial, commercial, reputational and regulatory. [post addendum: FUD alert! See my response to Nick Gall’s comment].

My hunch is that, once the hype has died down, the Externalization trend will actually strengthen the need for strategic, less operationally-focused, ‘Office of the CIO’ within organizations. I’m sure, however, such an entity will be unlike today’s ‘Operationally-focused’ IT shop, by 2020.

Addendum

Since posting, I was asked where VPEC-T fits in the context of the move towards BT. VPEC-T is a tool for the sense-making of complex systems-of-systems. It deals with the complexities of plurality (e.g.multiple value systems and multiple types of event). Moreover, it is used for sharing stories about such systems which helps: reach common understanding, ensure completeness and make trust explicit. These considerations will be increasingly important in the diverse and emergent world of BT. It’s most applicable to ‘New Habits’ 5,7 & 12-15.
Here’s an example of the preparation for a VPEC-T workshop based on a real session I ran earlier this year – it might help explain plurality need.

What Happened to the Fine Art of Business Analysis? – Revisited 2013

Link: http://taotwits-too-big-to-tweet.blogspot.com/2013/05/what-happened-to-fine-art-of-business.html

From Taotwit's Too-Big-To-Tweet

Back in 2008, I wrote a paper on Business Analysis. Recently, I’ve been revisiting this subject in my day-job and this made me realise how little things had changed and inspired me to write this post, which is, basically, the original article re-written, with additional thoughts (in italics).


The role of the Business Analyst has never been more important but needs refocus on Information Systems not the technical solution. Many of us can recall a time when a distinction was made between the hardware and software supporting the business and the information used by the business – there was a clear difference between IT, to describe the former, and IS to describe the latter. 
IS stood for Information Systems: 
IS: The landscape  of business  information used by people within an organisation 
and how they use information to deliver business outcomes. 

IT, in contrast, meant: 
IT:  The  hardware  and  software  technology  that  automates  or  otherwise  supports 
information processing. 

This distinction between these two concepts is all but lost, and the disciplines associated with Information Systems (such as Business Analysis and IS Architecture), are have become too obsessed with IT. 

Read more

What Happened to the Fine Art of Business Analysis? – Revisited 2013

Link: http://taotwits-too-big-to-tweet.blogspot.com/2013/05/what-happened-to-fine-art-of-business.html

From Taotwit's Too-Big-To-Tweet

Back in 2008, I wrote a paper on Business Analysis. Recently, I’ve been revisiting this subject in my day-job and this made me realise how little things had changed and inspired me to write this post, which is, basically, the original article re-written, with additional thoughts (in italics).


The role of the Business Analyst has never been more important but needs refocus on Information Systems not the technical solution. Many of us can recall a time when a distinction was made between the hardware and software supporting the business and the information used by the business – there was a clear difference between IT, to describe the former, and IS to describe the latter. 
IS stood for Information Systems: 
IS: The landscape  of business  information used by people within an organisation 
and how they use information to deliver business outcomes. 

IT, in contrast, meant: 
IT:  The  hardware  and  software  technology  that  automates  or  otherwise  supports 
information processing. 

This distinction between these two concepts is all but lost, and the disciplines associated with Information Systems (such as Business Analysis and IS Architecture), are have become too obsessed with IT. 

Read more

TOGAF Good or Bad? – Definitely Ugly!

I’m struggling with the value of TOGAF on my current assignment.

Background:


·        We have a need to develop architectural thinking up the ‘food-chain’ to the C-level to help inform business strategy.

·        The IT Leadership want to focus on: agility & resilience (fast response and ability to thrive under constant change), security, value-for-money and continuously improving User Experience

.

·        Unusually for a private company, we are not currently focused on competition (we are a monopoly) nor inefficiency (labour cost – we rarely ‘let people go’).


·        We have established business-engaged governance mechanisms around Cyber Threat, however, there’s cultural resistance to Western-style Governance practices and methods in other areas.


·        The IT department is mostly seen as a Cost Centre, although we are making some progress here.


·        English is the second language for the vast majority of our employees.


·        Experienced Enterprise Architects are rarer than hen’s teeth in Hong Kong.


·        A few on my team have been trained and ‘Certified’ in TOGAF (mostly before I joined) but they have not actually practiced EA (for a wide variety of reasons) since attending the course.

Observations:


·        TOGAF is hard to comprehend for those whose 1st language is English, so it’s an even greater challenge for my team.

·        TOGAF just tries too hard and ends up failing on a few counts; it’s too comprehensive to be a usable framework and not specific enough to be a methodology. It’s almost a philosophy, but a very incomplete and, at times, dangerously misleading one. This is very hard for my team to make sense of and I find myself having very long conversations with them where we end up agreeing that we reduce or focus on one or two of the TOGAF concepts (usually around a deliverable).

·        TOGAF doesn’t seem to help very much when it comes to the challenges we face around Consumer-led IT.

·        TOGAF does encourage SOA, that would help our agility & resilience goal eventually, but we’re quite a way from developing a genuine component-based, shared-services architecture due to the business organisation, culture and funding mechanisms. And we can’t wait for those to change to be able meet our agility & resilience needs.

·        It’s fair to say,TOGAF training does help introduce newbies to some important EA perspectives and does help with common terms and concepts, but it requires a lot of additional buddy-work with an experienced architect to become useful and, what’s worse, it conveys the wrong message; ‘Enterprise Architecture is complicated and requires a high intellectual capacity to understand’. The latter being the absolute opposite of what I need to convey across IT and the business; ‘Enterprise Architecture is about joining-the-dots and making things simpler to understand’.

I do continue to put my team through TOGAF Certification. Why? It’s the only credible option here getting newbies up-to-speed on the basics of EA/SA and it helps my staff build their CVs (which is important). I just wish there was a better option that was both less and more:



and


  • more – on the basic mentality required of of an EA (e.g ability to abstract) and why all organizations take a different approach to architecture based on culture, maturity and business priorities.

I sometimes wonder if the authors of TOGAF are motivated to make it more understandable, or, as seems to be the case, keep it obscure and arcane. It certainly felt that way when I was exposed to IAF (Capgemini’s Framework) and its zealots for the first time.

An aside here: in a recent chat with the Chief Architect in a well-known travel company, I said I needed the 80 page version of TOGAF – he laughed and responded that he’d implemented an 8 page version! BTW: all his architects are native-English speakers hired in from abroad.