If you've tried managing an internal IT department as a bona fide business you already know that you can't take that very far, for the obvious reason that your IT department isn't a business
But with these benefits come pitfalls, especially if you take the IT-is-like-a-business approach to extremes. If you've tried managing an internal IT department as a bona fide business you already know that you can't take that very far, for the obvious reason that your IT department isn't a business. It is, after all, a part of a business: a significant contributor to a value chain, not a self-contained value chain of its own. And the harder you try to create a separate value chain for IT, the harder it becomes for the IT department to become integrated with the business of which it is truly part.
A strategy founded on running the IT department like a business will reach a natural point of diminishing returns, if it hasn't already. Innovative companies have moved to the next-generation strategy, in which the CIO's purpose is not necessarily to run a traditional IT department at all. Her primary role is to provide corporate leadership to business functions which are investing in and exploiting IT in the context of their business strategies and operating plans.
The Pitfalls of Running IT as a Business
The drive for IT departments to manage themselves in more businesslike ways followed the technology-centric strategies that effectively ended once the 21st century got into its stride. People learned — often the hard way — that technology deployment alone does not guarantee business success. And they have been putting those lessons into practice ever since. As executives called time on deploying IT at potentially any cost, technology-centric strategies gave way to ones founded on IT operational efficiencies: IT departments would deliver more for less.
The benefits of running an IT department in a more efficient, businesslike way are well known. The department's purpose is clear to its staff and stakeholders: People know what IT is accountable for, and what it isn't, and therefore how to organize their own part of the business to get the most from technology. The IT department's internal processes become ever-more efficient, costing progressively less with no loss of value to the business units which fund them. Any activity that contributes to the department's purpose and processes — but is not core to them — is constantly market-tested to find and exploit the best sourcing option, whether that be in-house or outsourced.
However, alongside the benefits of running the IT department like a business, there are also risks and pitfalls. The most damaging to the CIO's longer-term strategy is any attempt to run the department as a separate business rather than just running it in a more businesslike way. ---pb--- There's a world of difference between running the IT department "like" a business, and trying to run it "as" one. It's amazing how one word can fundamentally alter strategy. Running IT like a business means adopting a businesslike mindset, processes and financial disciplines. Running it as a business means competing for revenue and investment in an open market, and going bankrupt if you run out of cash to cover your liabilities.
What happens if a CIO attempts to run her department as a business? Colleagues in other departments will perceive that the IT department wants to be treated like a supplier. If the CIO's chosen business is primarily to be a provider of operational IT services, then that what is her "customers" expect her to concentrate on. In that case, contributing to corporate and business strategies will be a heroic, uphill battle rather than the IT department's core contribution to the enterprise. The prevalence of heroic how-we-in-IT-contributed-to-strategy stories in the media offers us insight into how much IT's strategic contribution is currently considered exceptional, rather than its stock-in-trade.
The IT department might find another pitfall if it tries too hard to run itself as a business. The company's business units will be reluctant to fund any material investment by IT in anything that looks like branding, marketing, selling or upgrading the management systems that support the IT department's own productivity. Why should they? One of the primary cost advantages of an internal department is that it doesn't require all the capabilities a real supplier needs to compete in the open market. So the CIO is caught. She has placed herself in competition with bona fide external suppliers but without access to the investment that they have in order to compete as an equal.
In the long term, the IT department will find itself in a corner from which escape becomes ever more difficult. It lacks the means to compete with real IT suppliers and has separated itself from the business that it is meant to be part of. It wants to be taken seriously in the world of strategy, yet its primary business is operational. This is when taking "IT department as a business" too far seriously undermines the next generation strategy for IT.
From Efficient to Strategic
After the technology-centric strategy, then the efficiency-centric one, the strategic IT focus is now on exploiting technology to create new business value. Today's successful CIO is one that is primarily valued as leader of a corporate strategy in which the company is an "expert customer" of IT. Managing operational delivery of IT services in a businesslike way is simply expected, if the CIO still does it at all.
Unless the company is already an expert customer of IT, its people will need strategic leadership from trusted colleagues who do not have a vested interest in supplying technology services. If the IT department is behaving as a business supplying operational IT services, then who can everyone trust to provide the strategic leadership that the next generation of IT strategy demands? ---pb--- A CIO who is trying to run the IT department as if it were a separate business will need to rethink her operating model. What have others done in such circumstances? They have divided their department's activities into two groups: core capabilities and services. Core capabilities are those IT-related activities that the company must have in-house and that make the company an expert customer of technology. Services are the activities that the company can choose to either keep in-house or outsource. Naturally, the CIO's own activities should be included under core capabilities rather than services.
Having divided her IT department's activities into these two categories, the CIO can benchmark her company's core IT-related capabilities against the models that other innovative companies are using. In particular, the company should excel at true enterprise architecture (not just its technology components) and investing in business change. Together, these are the engine of strategic investment and value creation, both for IT and everything else. And they should be supported by robust sourcing to spend that investment wisely. The CIO may find her IT department's strategic influence is low because these core capabilities are weak, missing or not integrated enough with their equivalents in the wider company.
Having explored the company's strengths and weaknesses in its core capabilities as a customer of IT, the CIO faces a major choice. Does she primarily develop the necessary capabilities within the IT department, or elsewhere in the company? If IT is perceived to be operating as a supplier, the first of these options is not realistically open to her. Therefore the CIO is faced with developing the core capabilities outside of the IT department. As she is the executive leader of those capabilities, which means she may need to give up day-to-day control of IT service delivery and concentrate on corporate strategy.
That is indeed what some CIOs have done. They have established a corporate-level team that develops and leads the company's strategy and capabilities as an expert customer of IT, with no accountability for day-to-day delivery of IT services. Instead, accountability for IT operations is in the hands of a CTO or equivalent, who reports to an operations executive such as the COO. Depending on the extent of which IT services are outsourced, the IT operations function may one day report to the Chief Sourcing Officer.
This model, which separates the corporate strategy for IT from operational service delivery, may not suit everyone. But as we explore the options for maximizing IT's strategic contribution, it's essential to know it exists.
Chris Potts advises companies on corporate and IT strategy as a director with the IT consultancy Dominic Barrow. Reach him at firstname.lastname@example.org.
Join the CIO Australia group on LinkedIn. The group is open to CIOs, IT Directors, COOs, CTOs and senior IT managers.