5 Myths About IT Transformation That Are Quietly Killing Your Projects
- ainsowen
- Apr 27
- 3 min read
Most IT transformation programmes don't fail because of bad technology. They fail because of assumptions that go unchallenged — assumptions that sound reasonable, feel familiar, and get nodded through in every kick-off meeting.
At Owen Consultancy, we've worked across complex transformation programmes for years. The same myths show up again and again. Here are five of the most damaging — and what to do instead.
Myth 1: More data means better decisions
Most transformation programmes are drowning in data. Dashboards, reports, metrics — all readily available. Yet decisions still get delayed. Why?
Because the challenge was never access to information. It's clarity, confidence, and ownership.
We've seen teams add more reporting instead of making a call, wait for 'one more data point', and use data to support decisions they've already made. At some point, progress depends on judgement — not another dashboard.
The fix: Agree on who owns each decision and what 'good enough' information looks like before a programme starts. Data should inform decisions, not defer them. |
Myth 2: Consensus means alignment
Agreement in the meeting doesn't always translate to action afterwards. We've seen projects where everyone 'agreed' — yet priorities quietly diverged the moment people left the room.
Consensus can look like nods around the table, no visible objections, and a decision recorded in the minutes. Alignment looks like clear ownership, consistent messaging, and decisions being upheld when challenged.
Projects don't stall because people disagreed. They stall because people agreed... without committing.
The fix: After every key decision, confirm who owns it, who needs to communicate it, and what happens if it gets challenged. Agreement is the start of alignment, not the end. |
Myth 3: Green status means healthy delivery
Some of the most fragile projects we've seen were confidently reporting green. Status updates can hide unresolved dependencies, quiet resistance, and decisions being deferred rather than made.
On paper, everything looks under control. In reality, momentum is quietly eroding.
The fix: Good delivery isn't just about reporting progress — it's about creating an environment where issues are raised early, even when it's uncomfortable. Make it safe to report amber. |
Myth 4: Speed equals progress
In transformation, the pressure to 'move fast' is constant. But speed without clarity often creates rework, misaligned expectations, and late-stage surprises.
We've seen slower starts deliver faster outcomes — simply because everyone knew what success looked like, who owned decisions, and what wouldn't be done.
The fix: Clarity doesn't slow delivery. It prevents false starts. Invest time upfront in defining scope, ownership, and success criteria — then move fast with confidence. |
Myth 5: The technology is the transformation
A new system doesn't change how people work. A new platform doesn't fix a broken process. Technology enables transformation — it doesn't deliver it.
The real work is in the people: their understanding of why things are changing, their confidence in using new tools, and their belief that leadership will support them through the disruption.
The fix: Treat change management as a delivery discipline, not an afterthought. If your programme plan doesn't include time for adoption, training, and communication — it's not complete. |
If any of these feel familiar, you're not alone.
These patterns show up in every complex programme — across sectors, sizes, and budgets. The difference between programmes that recover and those that don't is usually how quickly these conversations get surfaced.
If you'd like a confidential conversation about a programme you're running or inheriting, we'd be glad to help. Get in touch at info@owenconsultancy.co.uk or visit www.owenconsultancy.co.uk.
Comments