There is a conversation that happens in almost every long-running transformation, and once you have heard it you start hearing it everywhere.
The recommendation lands. The stakeholders agree with it. Everyone in the room wants the capability. And then someone puts a date on it.
Yes, we want that. I think that’ll be great for 2029.
Meanwhile, the people who would actually build it are looking at the same scope and thinking: this could ship this year. Why are we talking about two or three years out?
That gap between the two clocks is one of the most expensive things in enterprise transformation, and it is worth taking seriously, because it is rarely about the work.
Timelines set by belief, not experience
Ask why an improvement needs three years and the answers sound like planning. Listen closer and they are usually something else.
The dates are being set by people who have never done the implementation and have no experience of how long it actually takes. They believe it will take too long, so they schedule it as if it will. Fear does the estimating, and the estimate then masquerades as a plan.
The belief is not irrational. In organizations that handle sensitive information under heavy oversight, caution is structural. Approval chains, review boards, and controlled release processes exist for real reasons. But controls accumulate, and not all of them keep earning their place. A lot of that bureaucracy is there for good reason. Some of it is no longer serving the organization the way it once did, and nobody has stopped to ask which is which.
Layer on planning culture and the drift compounds. The default estimate for anything new gets calibrated to the most painful project anyone remembers, and stretching a timeline is always safer for the estimator than compressing one. Nobody gets challenged for saying 2029. Say “this year” and you own the risk personally.
The market is running a different clock
The problem is that the timeline conversation does not happen in a vacuum. The same organization scheduling its own improvements for 2029 is being squeezed by customers whose expectations reset annually.
Speed to deliver is the pressure we hear most. The window from receiving a design to producing the first unit, with processes that can produce at scale, keeps collapsing. Customers expect it to keep collapsing. An organization that continues doing business as usual will simply stop meeting those expectations, on a date it did not choose.
That is the quiet asymmetry in every deferred roadmap. The organization experiences its own pace as a choice. The market treats it as an answer. A capability scheduled for 2029 is, from the customer’s side, a capability you do not have.
Give the same class of organization a hard external deadline, an end-of-support date or a contractual cliff, and the same work compresses from years into months. The scope did not change. The organization’s willingness to act did.
Appetite is a variable you can manage
If the difference between a months-long timeline and a years-long one is organizational appetite, then appetite deserves the same management attention as scope and budget. Two levers come up again and again.
Fund the change side of the change. Organizational change management is routinely the first line item cut, because its output is invisible when it works. It is also the workstream that actually addresses the thing inflating the timeline, because the fear lives in people, not in project plans. The pattern repeats across engagements: a client hesitates over funding OCM, steps out on faith, and by mid-program considers it one of the best decisions they made. Not because OCM speeds up technical delivery, but because it reduces the organizational resistance that quietly stretches timelines in the first place. The organizations that skip it keep paying for it in the schedule instead.
Keep discovery running, at every level. Estimates inflate in the dark. Discovery is not a kickoff activity; it is an ongoing one, like peeling an onion. The deeper the organization understands its concerns, incentives, and constraints, the less likely it is to add schedule based on assumptions that turn out to be wrong. What matters to a rank-and-file user is different from what matters to a manager, which is different again from what matters to an executive. A timeline built on one group’s assumptions inherits that group’s blind spots, and usually its anxieties too.
There is a third lever, let early wins recalibrate the clock. When a deliverable lands faster than the organization believed possible, treat it as evidence, and spend it deliberately on pulling the next improvement forward.
Key takeaways
Audit your timeline for fear. For each major milestone sitting years out, ask one question: is this date derived from the work, or from the discomfort? If nobody in the estimating chain has actually implemented the thing being estimated, treat the date as a belief, not a plan.
Price the slow clock. A deferred capability is not free. Its cost is measured in the customer expectations you will miss between now and the delivery date. Put that cost next to the schedule risk you are avoiding and the comparison often flips.
Separate necessary controls from inherited caution. Regulated environments need real governance. They do not need every control they have ever accumulated. Distinguishing the two is itself high-value transformation work, and almost nobody assigns it to anyone.
Invest in appetite, not just delivery. Change management and continuous discovery are how an organization learns to move faster without feeling reckless. They look optional on a budget line. They are usually the difference between this year and 2029.
The organizations that move fastest are not the ones with the least to fear. They are the ones that learned the difference between risks that must be managed and fears that have quietly become policy.