Why Rushed Transformation Approvals Unravel, and a Simple Fix

Here is a pattern we keep running into when talking with leaders about digital change: the big transformation decision gets made in one charged meeting, usually right after an impressive presentation, and then spends the next eighteen months quietly unravelling. Recognise the scene? Plenty of leadership groups do, and the cure turns out to be gentler than the disease. Let’s diagnose what goes wrong when a DevOps transformation is approved on the spot, and then walk through a remedy: a planned cooling-off gap ahead of every weighty, pricey or sticky commitment.

The symptom: a yes that nobody quite remembers agreeing to

Ask people months later how a major engagement began and you often hear vague answers. “We had a workshop, everyone was excited, and the budget was released.” Nobody is sure who weighed the downsides. The programme has a start date but no real exit conditions, the scope has quietly doubled, and the people expected to change their daily habits first heard about it when the contract was already signed.

Look closer and you will usually find the same early warning signs:

• the decision followed a persuasive pitch within hours rather than days;
• a deadline, such as a fiscal-year budget or a limited-time rate, was cited as the reason to move now;
• the objections raised in the room were answered with enthusiasm instead of evidence;
• the quiet engineers who would live with the result were not asked until afterwards.

The diagnosis: pressure beats judgment in the room

Why does this keep happening to smart people? Because a meeting is a social event. There is momentum, status, and a very human wish not to be the person who deflates the mood. Add a presenter who is skilled at making the future look easy, and the safest-feeling move for anyone is to nod. Excitement is not a flaw; it just makes a poor adviser for choices that are expensive to reverse.

The deadline is the second culprit. Fiscal calendars, quarterly targets and seasonal discounts are real, but they belong to the organisation’s paperwork, not to the problem being solved. A pipeline that has been slow for three years will still be slow next Thursday. Treating the date as part of the problem rather than a wrapper around it is where many programmes first go wrong.

The remedy: a deliberate pause, written into the process

The treatment is simple enough to explain in a sentence. Ahead of any call that is weighty, pricey or sticky, insist on a fixed gap, a night for moderate choices and a weekend or more for big ones, between “we understand the proposal” and “we commit.” During that gap nobody sells and nobody lobbies. People read, reflect, and write down what worries them.

The part that makes it stick is making it a rule rather than a favour. If the pause depends on one brave person speaking up, it will vanish the first time a senior sponsor is impatient. Put it in the governance document: any engagement above a stated size is subject to a minimum interval before approval. Everyone then asks for time the same way, with no embarrassment attached.

What the pause should produce

A pause with no output is just a delay. Ask for three small artefacts by the end of it.

1. A one-page restatement. In the plainest words you can find: what is changing, for whom, over what period, and what it costs.
2. A list of open questions. Not objections for their own sake, only the things nobody could answer yet, with a name beside each.
3. A list of exit conditions. Under what circumstances would we stop or shrink this work, and who gets to say so?

Our own engagement write-ups on this site lean on the same idea of explicit stages; for instance, the piece on how a consulting engagement moves from assessment through to enablement describes why clear phases beat a single giant leap. A cooling-off interval slots naturally in front of the first phase.

Applying it to a cloud migration decision

Take a concrete case. A company is told that moving its workloads to a new cloud setup should start this quarter, with a partner who can begin on Monday. The pitch is persuasive, the partner is capable, and the team is tired of the old data centre. This is exactly the setting where the pause earns its keep.

During the wait, the leadership group might reread an overview such as the one explaining where consultants fit into moving to the cloud, then ask practical questions. Which systems carry hidden dependencies? What does the team have capacity for while the migration runs? If the first wave stalls, what is the cost of stopping? These are dull questions compared with the demo, and they are the ones that decide whether the programme succeeds.

A side note on information sources

People who decide quickly often do so because they believe more research is impossible, when it is merely unglamorous. A little reading during the pause goes a long way. And when you read, remember that directories and comparison sites are starting points. The footer of BestDentalHospitals, a site where dental hospitals in many countries are listed side by side for international patients, tells readers that the content is purely informational and no substitute for a dentist’s judgment. The attitude is worth borrowing: gather what is on offer, then take time away from the listing before you act on it.

Pushback to expect, with replies

“We will lose momentum.”

Momentum built on a rushed decision is borrowed against future rework. A pause of a night or two costs a trivial amount of calendar time compared with the weeks that a wrong turn burns. Besides, a team that has had time to digest a plan often moves faster once it starts, because the questions have already been asked.

“The vendor needs an answer today.”

Sometimes true, often a negotiating posture. A professional partner will understand a request for a short interval, particularly if you explain that it is a standing rule rather than a doubt about them. If the offer genuinely expires, you now know how much weight to give it.

“Our people will think we cannot decide.”

Say the opposite out loud: this is how decisions get made well here. Announce the date on which the answer will arrive. A visible deadline for the decision itself reassures people that the pause leads somewhere.

“Surely the leadership team already thought it through.”

They thought about it in the meeting, which is not the same as thinking it over. The pause separates the two, and the second is where the useful doubts live.

A short worked example

Imagine a mid-sized retailer weighing a large pipeline-modernisation programme. On Tuesday the proposal is presented. On Tuesday evening, the programme sponsor receives a one-page restatement. By Wednesday noon, five people have each written one concern, among them a platform engineer worried that the first release window collides with the holiday trading season, and a finance analyst who notes that the contract has no clause for scaling the work down. On Thursday the group meets for forty minutes, adjusts the start date, adds an exit clause and approves a smaller opening phase. Nothing dramatic happened, and a handful of expensive surprises simply never appeared.

How to start next week

You do not need a transformation office to try this. Pick the next decision that would be hard to reverse, tell everyone involved that it will be decided on a particular day at least one night away, and ask for the three artefacts described earlier. Afterwards, spend a few minutes comparing the first draft of the proposal with the final one. The differences are your evidence that the pause is worth keeping.

Broader strategy pieces, like our look at how consulting support can make a large organisation more agile, are useful companions for the thinking you will do in that quiet interval. Good change is rarely hurt by a night of reflection; it is hurt by the kind of confidence that cannot survive one.

Kabir Malhotra