A new organisation had to launch in 90 days. Where did we start?

A new organisation within a group of companies had to start operating within 90 days. Several legal entities, several locations and around one hundred users needed a coherent IT environment built almost from scratch. Time pressure made it tempting to buy hardware and licences immediately. Instead, we began by organising how the new company would work.

Ninety days is more than a technology schedule

At first, the list of expectations sounded technical: user accounts, computers, network, cloud services, backup, monitoring and support. Every item was needed, but none answered how the new organisation would function after launch. Without that answer, it is easy to build an environment quickly that creates exceptions, unclear responsibilities and costly changes from day one.

We therefore treated the 90 days as a programme to build organisational capability rather than a purchasing project. Technology would implement the agreed operating model. First we needed to establish decision owners, the way IT services would be delivered, a target architecture and common standards. Only that foundation made it possible to launch implementation workstreams in parallel safely.

1. Roles and responsibilities

The first step was to decide who makes decisions, accepts risk, owns systems and data, and performs operational work. We separated the responsibilities of the business, central IT, local support and suppliers. We also defined escalation paths. Every subsequent task therefore had an owner, and the project did not rest on the implicit assumption that the technology supplier was responsible for everything.

2. The IT operating model

Next, we described how IT should operate day to day. This covered requests, users and devices, granting and removing access, change management, incidents, backups and suppliers. We defined points of contact, priorities and expected response times. The operating model bridged implementation and ongoing support: the environment had to be ready to operate, not merely built.

3. Target architecture

Only then did we design the target architecture. The priorities were separating legal entities, shared management mechanisms, secure work across locations, control of identities and devices, data protection and central monitoring. The design described structure, flows and ownership boundaries without deciding every product at the outset. It also separated what was essential for launch from what could be developed after the organisation started operating.

4. Shared standards and ways of working

The final part of the foundation was a common set of rules: workstation standards, access principles, security requirements, segmentation, backup, monitoring, change documentation and minimum requirements for suppliers. Standards reduced exceptions and sped up decisions. The team no longer had to design each solution from scratch; it could apply agreed patterns across further locations and entities.

Five stages of the 90-day plan: roles and responsibilities, IT operating model, target architecture, shared standards, then implementation and operational readiness.
Fig. 1. Organisation before technology: the logic of a 90-day plan.

Technology followed from the design

With the four layers defined, we could choose technologies deliberately and sequence the implementation. The criteria came from the architecture, operating model and agreed principles, not one vendor’s catalogue. Some work — configuring core services and preparing devices, networks and security controls — ran in parallel, but within a common target design.

This approach does not remove deadline pressure or every risk. It does limit arbitrary decisions and gives teams a common goal: an organisation ready to operate, not just systems that have been switched on.

Technology speeds up an organisation. First, though, the organisation must know how it wants to work.