Is IT4IT the solution to broken IT processes?

Simon Hall
4 min readMar 26, 2020

Article written with input from Kaj Burchardi and Dries Hannes

IT4IT is a framework from The Open Group (the makers of TOGAF) that promises to help harmonise fragmented IT tooling landscapes, integrate systems and fix processes. However, it is often regarded as complex and a bit archaic. Can it be applied effectively in practice?

What is the IT4IT framework?

IT4IT is a generic framework and reference architecture to help structure and optimise the IT value chain end-to-end; i.e. from the forming of an idea to a piece of code operated and monitored in production. By thinking of it as a value chain as opposed to individual capabilities (e.g. backlog management and incident management), the framework is set out to help bring all IT processes together.

Source: IT4IT reference architecture from The Open Group

For example, consider a DevOps team working in a mid-size organisation. They will often need to interoperate with other IT teams such as infrastructure, service management, help desk, enterprise architecture and more; all of these interactions open up areas of friction and inefficiencies. IT4IT helps bring the units together to ensure data is harmonised, handovers are smooth, interactions are well thought out and that nothing is left unconsidered.

IT4IT is not a replacement for other frameworks, e.g. ITIL and TOGAF, but rather aims to integrate them into a holistic model for the IT value chain

Source: IT4IT reference architecture from The Open Group (with Prince2 replace by SAFe for project portfolio)

Raw IT4IT is often too complex to have meaningful discussions outside of the architecture cohort

In my experience, the raw IT4IT framework is too abstract and complex to be immediately useful for wider discussions (outside of the core architecture community). It’s a daunting task to explain the reference architecture below to someone uninitiated.

Source: IT4IT reference architecture from The Open Group

While the framework is great at ensuring that nothing is overlooked, it needs to be simplified to ensure meaningful discussions.

A good starting point is documenting the main platforms supporting the IT4IT value chain and key interactions

A good way of simplifying the framework for a first IT4IT analysis and transformation is to document which key platforms support which parts of the IT4IT value chain. This does not be a complete analysis to offer a first overview of what tooling and platform are used to support the various parts of the value chain. The output can be used to harmonise systems and design processes between them.

Example of how the IT4IT framework can be simplified to highlight main technology platforms and key interactions

IT4IT can be an enabler for DevOps ways of working, and deliver serious benefits to both IT and the wider organisation

An IT enabler is a foundational and reusable asset that can be used to accelerate transformation efforts, e.g. by improving engineering productivity, driving automation and enabling code re-use. Cloud, CI/CD, and containers are all typical examples of enablers.

In the same way, IT4IT can be thought of as an IT enabler. By harmonising tooling, fixing broken processes, integrating systems and harmonising data the effectiveness of the IT organisation can skyrocket. IT4IT also enables DevOps by more seamlessly integrating Development and Operations.

Introducing IT4IT and optimising the IT value chain can help unlock significant business benefits including:

To capture the benefits, the framework needs to be interpreted, customised and simplified

Simply introducing the framework is not enough to capture any benefits. No reference model alone has magically rationalised and integrated systems; it needs to be interpreted and simplified for the specific problem you want to solve, and translated to your organisation’s context.

Transformation success is 10% framework, 20% customisation and 70% implementation and people change management

True business impact is only archived when the behaviours of people and systems change. This is typically the hardest part and a problem not directly solved by a framework. The focus must hence be on customising the framework to best support implementation and change management e.g. to determine the org. structure, data architecture, or integration architecture.

The core ideas of the IT4IT frameworks are applicable to most, if not all, organisations. Implemented right, you too can capture the benefits, and help structure and optimise your organisation’s foundational IT capabilities. IT4IT is, or at least can be, a part of the solution to broken IT processes.

--

--