Let’s look together at a few basics for leading, as CIO, the digital transformation of your company.
For a CIO, transforming the company and moving to a new IT system is a complex task. Resistance to change, staff training, business continuity: the challenges are many. Yet it is your job to lead this transformation.
Understanding the CIO’s role
The CIO is responsible for the strategic management of IT resources and for aligning them with the company’s objectives. They choose which technologies to adopt, oversee operations and ensure data security. Even when the company has a CISO, the CIO remains responsible for implementing security.
The CIO stands at the crossroads of strategy, executive management, the business units and the technical teams. The role goes far beyond technology.
The challenges of a transition
Resistance to change is one of the most common obstacles. Employees may feel overwhelmed by the new system or worry about its effects: new skills to learn, the impact on jobs. So you need to communicate clearly, share the information that reassures, and actively involve the teams.
Business continuity is the other major challenge. IT systems carry the company’s operations, and any interruption hits productivity and profitability. Careful planning, a thorough risk assessment and suitable mitigation measures keep disruption to a minimum.
Steering the roadmap over time
The information system is a significant asset for the company, a technical and information heritage to be managed over the long term. In my view, it is not a pile of applications but a complex system that must remain coherent as a whole.
“An information system is not a pile of applications, but a system that must remain coherent.”
Hence the importance of the IT master plan and how it is prepared: clear objectives, aligned with the company’s; a detailed understanding of the impacts at every level; a forecast of resources; and finally, convincing the decision-makers, to win their support.
Once the transition is prepared and the existing set-up assessed, the detailed roadmap follows: key stages, timescales, resources and responsibilities. It must be realistic in terms of time, budget and means, include milestones to measure progress, and plan fallbacks in case of delays or the unexpected.
Sharing it with all stakeholders and getting their agreement is essential: it ensures a shared understanding of the objectives and makes coordination between teams easier.
Finally, the company’s context is always moving. The CIO must be able to adjust the IT master plan without ever straying from the underlying trajectory: the structuring medium- and long-term objectives set for the information system. If that trajectory has to change, it is the IT master plan itself that needs reviewing. Every adjustment is therefore made with the strategic vision in mind.
Relying on a framework
To evolve the architecture of their information system, a CIO benefits from adopting a framework that helps govern IT and align it with the business. The IT master plan sits, after all, at the boundary between the IT department, the business units and executive management.
Enterprise architecture offers an approach I find valuable. The TOGAF framework (The Open Group Architecture Framework) provides a method, the ADM, in several stages:
- analyse current and future needs in depth, and set objectives aligned with the company’s strategy;
- develop an architecture master plan that gives a clear view of the target architecture;
- adapt the architecture principles and build detailed models to guide transition planning, under rigorous governance;
- implement step by step: first the architecture framework itself, then incremental changes run as architecture projects.
Applied iteratively, for each architecture project, the ADM cycle lets you build the IT master plan and keep it alive over time, from the architecture vision through to the actual roll-out of change, both functional and technical.
Preparing an IT master plan or an IT transition? See our interim CIO support.




