The Pause That Launches Your Transformation
What looks like slowing down is the run-up.
A university spent six months negotiating the contract for a major new system. Six months of lawyers, terms, and pricing. What nobody used that window for was getting ready. The people who would run the system, the data that would have to move into it, the operations that would have to bend around it, all of it sat untouched until the ink was dry.
Then the project kicked off, and they were behind from the first week. Not because the plan was wrong or the team was weak. The readiness work that could have happened over those six months had not, so now it was competing with delivery instead of clearing the way for it.
This is the pattern I see most frequently. When the pressure is on, the instinct is to move. Get the team in a room, pick the platform, set the date, and start. A readiness assessment, in that moment, sounds like a box to tick before the real work begins.
I believe it is the real work. And skipping it is the most expensive shortcut in transformation.
Starting and being ready are not the same thing. The pause you skip at the start is the one you pay for at the end, at many times the price.
Why does doing feel safer than pausing?
Because of how the brain handles pressure. You have a fast, automatic way of thinking that runs on almost no effort, and a slower, deliberate one that takes real work to hold. Daniel Kahneman spent much of his career showing how the two trade off. Under load, the fast one wins. It reaches for action, because doing something feels like control, and sitting with an open question feels like exposure.
So the pause gets cut at the exact moment it matters most. Not because leaders are careless, but because a brain under pressure is built to move first and think later. The instinct that feels like decisiveness is often the fast brain avoiding the harder question - are we ready for this?
What does skipping it cost?
The cost is more than most leaders expect, and it surfaces later than they think, when it is hardest to fix. When a project fails in delivery, the cause is usually already there in how it started. The cracks are set early and stay hidden until everyone is committed and moving.
“Of more than 16,000 major projects, only 8.5% came in on budget and on time, and just 0.5% delivered on budget, on time, and on the benefits promised.” - Bent Flyvbjerg, How Big Things Get Done, 2023
Flyvbjerg, who built a database of major projects over decades, reduces the fix to four words: think slow, act fast. Plan deliberately, then move quickly. Most organizations do the reverse. They think fast and act slow, and pay for it across the whole life of the project. Budgets overrun. Timelines slip a quarter at a time. Benefits that were promised to the board never arrive. The team burns its energy on rework instead of the work, and adoption stalls because the people were never brought along. The problems you did not look for at the start do not disappear while you sprint past them. They wait, and they compound.
I say choose your hard. Pay for readiness at the front, or pay for the absence of it later, with interest.
What is a pause, really?
Not a stop, and not dead air while the clock runs. The university had six months. The time was there. What was missing was the intent to use the opportunity to set the course and pave the way.
A real pause is deliberate work. It is the one moment you widen the view and take in the whole terrain before you commit to a route, and it asks the questions the plan quietly assumes away.
How is change viewed here, after the last few initiatives landed the way they did?
What is the true capacity to take this on right now, on top of everything else?
Where are the data and the systems genuinely ready to move, and where are they not?
Where are the people – are they ready?
A plan lives on paper. Readiness lives in people, and in the data and systems the plan takes for granted. You can hold a flawless plan and an organization nowhere near ready to carry it, and nothing on the slide will tell you so. The readiness pause is how you find out while it is still cheap to know.
You can call the readiness work a nice-to-have if you want to. The teams that treat it that way are the ones who end up three months into delivery, scrambling to fix what a proper assessment would have caught before day one.
How does a pause become a launch?
This is the part most leaders never consider. The pause does not only measure readiness. It starts to build it.
The moment you ask the people who will live inside a change where they stand, before the tool is chosen and the date is set, something shifts. Being asked lowers the threat. It turns a change happening to someone into a change they have a hand in shaping. You cannot ask people if they are ready without beginning to make them ready.
So the time you spend getting ready is not time lost. It is time spent early instead of late, and it comes back to you as speed once delivery starts, because the organization is already moving with you rather than bracing against you.
A springboard only launches you because you press it down first. That press is the run-up. Skip it and you are just stepping off the end of the board.
Before your next big change, do not ask how fast you can start. Ask how much of a run-up you gave it. That answer will tell you more than the launch date ever will.