Nº
14

The Hidden Cost of Moving Too Fast

Speed is easy to measure. Its cost is not. A platform delivered in seven months that still hasn't gone live, and what it says about the difference between delivery speed and change speed.
The Hidden Cost of Moving Too Fast

Most programmes that move too fast don't fail at the speed they were moving. They fail later, quietly, when the people who were supposed to carry the change realise nobody waited for them.

Speed is easy to measure: releases shipped, milestones hit, a roadmap that turns green ahead of plan. Its cost is harder to see. It shows up as decisions people comply with but never commit to, because the reasoning stayed in the room. It shows up as systems that go live in a weekend while the way people work takes months to shift. And it shows up in the people whose readiness the plan quietly assumed.

Some years ago, my team built a platform that mapped a country's energy assets, so users could find network capacity and charging points for electric vehicles. Its value depended on the regional network operators sharing their asset data. They were involved from the start, and the build itself was part of bringing them along. The shared assumption was that a product like this would take years, leaving time to settle the hard questions, such as whether that data should be shared or sold.

We delivered it in seven months. It was praised, presented publicly and won a design award. It still hasn't gone live.

Nobody made a careless call. Building fast was a deliberate bet to bring everyone along, and it partly worked. But speed also did something nobody had priced in. It turned a someday question into a today question, and made concerns concrete before the people holding them were ready to resolve them. While they worked through it, the product stood still as the technology around it moved on.

AI sharpens all of this. When building gets faster, the gap between what an organisation can produce and what its people can absorb gets wider, not narrower. The tools have accelerated. People's capacity to rethink a business model, drop a habit or trust a new way of working has not.

None of this is an argument for moving slowly. It is an argument for knowing which speed you are measuring. Delivery speed is how fast you can ship. Change speed is how fast the people around you can absorb what you ship. A fast build can force a decision. It can't make one.

The real question for a programme running ahead of plan isn't how much faster it can go. It's who has to catch up, and what it costs while you wait.

I publish a new article on transformation, delivery and leadership every week here. For AI, subscribe to Decoded, my monthly newsletter where I decipher the news and what it means for leaders.

Reference this article as 
Nº 
14