Back to Executive Insights
Strategy·

What Executives Get Wrong About Transformation Timelines

Most digital transformation timelines fail before they start, not because the technology is hard, but because the plan was built on the wrong assumptions about how change actually moves through an organisation.

J

Jordan

Director & Co-Founder, Bespoke AI Solutions

The Twelve-Month Plan Nobody Needed

Ask most executives how long a digital transformation should take and you'll get a number pulled from a slide deck: twelve months, eighteen months, "this is a multi-year journey." It sounds responsible. It sounds like due diligence. It's usually wrong.

Not because transformation can't take that long — some genuinely should. But because the timeline gets set before anyone has actually looked at the systems, the data, or the people who'll have to use whatever gets built. The number comes from a vendor pitch, a board expectation, or last year's budget cycle, not from an honest assessment of the problem. Everything that follows — the staffing plan, the change management, the board updates — gets built on a foundation that was never tested against reality.

That's the core mistake. Not poor execution. A timeline set in the wrong order.

Why the Big Plan Collapses

Here's the mechanism, step by step. A twelve-month roadmap gets approved at board level before discovery has happened. Budget gets allocated against that roadmap. Teams get told to plan their quarter around milestones that assume integrations will go smoothly, data will be clean, and every department will adopt new tools at the same pace. None of that is true in any organisation with more than a handful of systems.

Three months in, discovery finally happens properly — because it always has to happen, whether it's scheduled or not — and it surfaces what should have been found first: three versions of the customer record living in three systems, a legacy database nobody fully understands, a team that wasn't consulted and now doesn't trust the project. The roadmap doesn't flex. It was presented to the board as a commitment, not a hypothesis. So the team either quietly blows the deadline or ships something half-built to hit the date. Both outcomes cost more than admitting the original timeline was a guess.

The deeper issue is incentive, not competence. Once a date is on a board slide, nobody wants to be the one who moves it. So problems get absorbed quietly, scope gets trimmed without saying so, and "on track" becomes a phrase that means something different in month nine than it did in month one.

The Order That Actually Works

The fix isn't a longer timeline. It's a different starting point. Discovery comes first, properly, before anything is promised. A week spent mapping the real systems, interviewing the people who'll use the result, and finding where the highest-return opportunities sit is not a delay — it's the only way to build a roadmap that survives contact with the organisation.

From there, the roadmap should come with timelines, budget ranges, and dependencies attached to evidence, not optimism. A board-ready roadmap looks very different once it's grounded in what the systems and the team can actually absorb. Some of what we build and integrate moves fast — simple integrations can ship in days. Other work, multi-system builds or custom AI tools, genuinely needs four to twelve weeks, sometimes longer for a full custom build run across discovery, design, development, deployment and support, which averages eight to twelve weeks end to end. The point isn't that fast is always right. It's that the timeline should be earned by the problem, not inherited from a template.

This matters more than it sounds. When a timeline is evidence-based, a board can ask sharper questions and get honest answers. When it's aspirational, every update becomes a negotiation between truth and optics.

What This Looked Like in Practice

On a public safety data project — fragmented records across training and equipment tracking that were slowing decisions and creating compliance risk — the brief wasn't to hit a preset date. It was to find the highest-value fix first. The result was a prototype delivered ahead of expectations, and notably, one that made sense to use without needing training to adopt it. That's the opposite of the big-plan approach: a narrower, evidence-led scope moved faster than a sprawling one would have, and adoption wasn't a separate battle fought later.

That's not a coincidence. Timelines built from genuine discovery tend to outperform timelines built from ambition, because they're not fighting unknowns they didn't see coming.

Questions Worth Asking Before You Set a Date

If you're staring down a transformation timeline right now, a few questions will tell you whether it's grounded or aspirational:

  • Was the timeline set before or after anyone mapped the actual systems and talked to the people using them? If before, treat it as a placeholder, not a commitment.
  • Does the plan assume every team adopts at the same pace? It won't. Some functions will move in days, others will take months, and the plan should say so explicitly rather than averaging it away.
  • What happens to the date if discovery turns up something nobody expected? If the answer is "nothing, we hold the date," the date was never real to begin with.
  • Is the board being shown a single number or a range with dependencies attached? A single number invites false certainty. A range with named dependencies invites honest conversation.

The Takeaway

Transformation timelines don't fail because the work is harder than expected. They fail because the date gets fixed before the problem is understood, and then everyone spends the rest of the project pretending the date was always realistic. Flip the order — understand first, commit second — and the timeline you end up with will actually hold. It might be shorter than you feared. It might be longer than you hoped. Either way, it'll be true, and that's worth more than a tidy number on a slide.

#ai-strategy#technology-roadmap#digital-transformation#leadership
Continue the Conversation

Want to discuss how this applies to your business?

A discovery call is free, takes 45 minutes with a co-founder, and comes with zero pressure. We'll look at your current landscape and tell you honestly where the highest-return opportunities are.