Case Study: Setting the Direction Early in an IT Transformation

The most expensive phase of an IT transformation is the one where everyone is busy but nobody agrees where the program is going. We were brought into a multi-year uplift at exactly that point: initiatives everywhere, direction nowhere.

The client

An established enterprise beginning a broad technology uplift covering infrastructure, security and ways of working, with several vendors already engaged and more proposals arriving weekly.

The challenge

Each initiative made sense in isolation; together they competed for the same people, budget and change windows. Without a target architecture and an agreed sequence, the program was on course to spend heavily and change little.

What we did

• Ran a current-state assessment focused on what actually blocks the business, not on cataloguing every imperfection
• Defined a target architecture and operating model — deliberately small enough to be understood by every stakeholder
• Sequenced the roadmap so foundational work (identity, network, environments) landed before the initiatives that depend on it
• Selected a handful of visible quick wins to build credibility while the foundations were laid
• Established a single decision forum with the authority to say no, so priorities stopped being relitigated

The outcome

The program moved from a collection of proposals to one funded roadmap with an agreed sequence. Duplicate initiatives were merged or stopped, and the early wins bought the patience the foundational work needed. Most importantly, decisions made once stayed made.