ITSM Strategy in Days, Not Months

A traditional ITSM strategy engagement follows a familiar rhythm: a round of stakeholder workshops, a maturity assessment conducted practice by practice, weeks of consolidating notes into a framework, a roadmap built and re-built in a spreadsheet, and finally a steering committee meeting to bless it. Three to six months later, you have a strategy document — for an organisation that has usually moved on from several of its original assumptions by the time it lands.

None of that process is wrong. The thinking it's trying to capture — where are we today, where do we need to get to, what's the gap, what's the sequence — is exactly the right thinking. The problem is how long it takes to produce it, and how much of that time is spent on mechanics rather than judgement.

What actually takes the time

Most of the delay in a traditional ITSM strategy engagement isn't thinking time — it's coordination and transcription time. Scheduling workshops around a dozen stakeholders' calendars. Manually scoring maturity against a framework, practice by practice, then reconciling disagreements between assessors. Rebuilding the same roadmap template from a previous engagement, then re-costing it by hand. None of that is where the real value gets created, but it's where most of the elapsed time goes.

What compresses, and what doesn't

A disciplined, repeatable method changes the shape of the timeline without skipping any of the real decisions. Scoping which ITIL practices are actually in play, assessing current maturity against a clear model, setting a realistic target, running the gap analysis across people, process, technology and data, and producing a costed and scheduled roadmap — all of that can happen in days when the framework is already built and the inputs are gathered efficiently, rather than reinvented from scratch for every client.

What doesn't compress — and shouldn't — is the judgement. Deciding the right target maturity for this organisation, at this point in its lifecycle, with this appetite for change, is a human call. So is getting genuine executive sponsorship, and sequencing the roadmap around what the organisation can actually absorb. Speed belongs in the analysis and roadmap production. It has no business replacing the conversations that decide what the strategy is actually for.

Why the speed matters

A strategy that takes six months to produce competes with six months of organisational drift — new leadership priorities, a budget cycle, a reorg, a platform decision made in the meantime without it. A roadmap produced in days arrives while the business case that triggered the work is still the one everyone remembers, and while the appetite for change is still live. The strategy doesn't have to win an argument against its own staleness before anyone's acted on it.

That's the real case for speed here. Not cutting corners — removing the mechanical delay that was never adding value in the first place, so the time that's left goes entirely into the decisions that actually determine whether the transformation works.