Symptoms
Let's start with the leadership story that organisations love to tell about themselves. It is the story of good judgment under pressure. The team assessed the facts, weighed the options, made a call, and moved forward. Once the decision becomes embedded in process, policy, operating rhythm, and management language, it begins to harden into something more than a choice. It becomes part of the company’s internal mythology. This is how we do things here. This is what good looks like. This is the model that got us this far.
That story feels stable. Respectable. Earned. Until the world changes.
Then comes the more difficult test. Not whether the organisation can make a decision, but whether it can revisit one without treating revision as betrayal. Whether it can allow that information to challenge a model that once made perfect sense. This is where many organisations begin to wobble. They say they value learning. They say they prize agility. They want curiosity and innovation. Yet the moment new evidence begins to threaten an old assumption, the room tightens. The language becomes strangely ceremonial. We must be careful not to overreact. This system has served us well. Let us not create confusion. We do not want to throw the baby out with the bathwater.
What often sits beneath that language is not wisdom, but attachment. The symptoms rarely arrive as collapse. Teams begin to work around a process that no longer fits. Customers start tripping over language, policies, or journeys that used to make sense in a different context. The frontline begins to absorb the friction through extra explanation, apology, and improvisation. Defects start to repeat in familiar patterns. Edge cases stop behaving like exceptions and start becoming previews. Good people begin compensating manually for a design the organisation is too attached to reopen. Everyone can feel that the current model no longer fits as cleanly as it once did, yet nobody wants to be the first to suggest that the old answer may no longer deserve protection.
This is one of the great hidden burdens placed on the frontline in many organisations. They are asked not only to deliver the system, but to absorb the pain created by its outdated assumptions. They must soften the policy, explain the friction, rescue the process, and translate yesterday’s logic into something survivable for today’s customer.
Diagnosis
The starting line matters because it is not a call to erase the past or to behave as though earlier decisions were foolish. It is a call to recognise that good judgment has a shelf life when the conditions around it shift. The strongest organisations are the ones that can say, with maturity and without melodrama, we made the best decision we could with what we knew then, and now that we know more, we must think again. That sentence should be far easier for companies to say than it usually is.
The problem is that decisions do not live only in documents. They attach themselves to effort, pride, identity, ownership, and memory. A policy is never just a policy after enough time has passed. It becomes proof of competence. A process becomes evidence that somebody once solved something difficult. A structure, once stabilised, begins to feel almost moral. To question it can sound, in the wrong room, like questioning the intelligence or credibility of the people who built it.
This is where organisations get into trouble. They confuse updating a model with insulting its authors. Changed direction with loss of authority. They confuse revisiting an earlier call with admitting weakness. What should have been a normal act of organisational maturity starts to feel emotionally radioactive.
If a business wants to know whether the starting line is calling, it should look less at the sanctity of the original design and more at the effort now required to prop it up. How much manual intervention is holding this process together. How many explanations are needed for what should be intuitive. The number of defects that are being managed downstream instead of redesigned upstream. The list of small compensations being made by people with the least formal power. And how many customers are encountering a version of the organisation that still reflects old constraints, old assumptions, or old technologies long after the world has moved on.
Resistance
Resistance remains powerful because decisions carry emotional residue.
Time pressure is one reason. Many teams are so busy running the machine that the idea of rethinking the machine feels almost insulting. They do not have spare hands or spare hours. They are exhausted already. To revisit an embedded decision can feel like a luxury reserved for people with lighter diaries and cleaner dashboards.
Then there is status. If a senior leader, a respected function, or a successful team built the current model, challenging it may feel politically risky. Nobody wants to appear disruptive for the sake of it. Nobody wants to be cast as ungrateful toward a model that once delivered results. Add sunk effort to that, and the emotional weight grows heavier still. It is painful to admit that something which took months or years to build now needs scrutiny rather than reverence.
But perhaps the deepest resistance is psychological. Many organisations still carry a distorted idea of what leadership looks like. They equate leadership with consistency, decisiveness, and being seen as right. By that logic, revisiting an old decision feels like damage. In truth, leadership is often the opposite. It is not the performance of permanent correctness. It is the discipline of becoming more accurate as the environment changes. It is the willingness to let learning alter direction before pride makes the cost unbearable.
People are not foolish for struggling here. They are human. The issue is that many organisations have never built a healthy relationship with revision. They still treat rethinking as embarrassment instead of evidence of maturity.
Incision
This is where the work begins.
First, organisations must separate revision from blame. They need language that lowers the emotional temperature of rethinking. A company that cannot say, that was the right call with the information we had then, and this is the right reconsideration with what we know now, will struggle to learn at the pace reality now demands. I keep coming back to that sentence because it protects dignity without protecting stagnation. It allows people to respect the past without becoming trapped inside it.
Second, they must teach their people that changed information is a legitimate trigger for changed action. New data, new technologies, repeated defects, altered customer behaviour, and widened organisational capability all have implications. If the business has learned something material, it should not have to pretend otherwise for the sake of continuity. Not every rethink is panic. Not every revision is overcorrection. Sometimes the strongest sign of competence is the refusal to make people keep carrying a design whose logic has expired.
Third, the frontline should be repositioned, not as the shock absorber for outdated systems, but as a source of live design intelligence. The people closest to customer friction often know first when the starting line is calling. Which scripts feel increasingly absurd. Can identify the policies that require too much translation. They know which exceptions are no longer exceptional. And which repeated defects point to something more structural than a queue spike or a training gap. If the organisation wants to rethink well, it must learn how to listen to these signals before the pain becomes too expensive to ignore.
Fourth, formal review points help. Many organisations wait far too long because they only reconsider a design when failure becomes impossible to deny. That is an unnecessarily bruising way to learn. Better to create recurring moments where teams are expected to ask harder questions. What assumptions no longer hold. What are we defending out of habit rather than logic. Call out the repeated frictions are customers and teams absorbing on our behalf. If we were building this today, knowing what we know now, would we design it this way. Those are not rebellious questions. They are signs of a mature operating system.
Fifth, rewards matter. If leaders are praised only for smooth continuity, few will volunteer to reopen a settled model. If managers are measured only on local stability, they will naturally protect the familiar. But if the organisation visibly values those who use evidence to update an operating model before it degrades, revision becomes more credible. People begin to see that loyalty is not the same as preservation. Sometimes loyalty to the purpose requires disloyalty to the form.
And this is the real point. The starting line is not calling because the past was foolish. It is calling because the future has supplied new information, and good judgment is supposed to move.
In practical terms, this means organisations need to get more comfortable with disciplined returns to first principles. Not dramatic reinvention for its own sake. Or strategic costume changes. But dodging chaos disguised as boldness. A real return to the starting line asks simple but serious questions. What problem are we actually trying to solve. What has changed since we first designed this process, policy, structure, or journey. What burden is the current model placing on customers or teams. What are we now asking humans to compensate for that the system itself should have evolved beyond. And what would we build now if we were not emotionally obliged to preserve the past.
These questions are not airy. They are operational. They determine whether the business is still learning or merely administering its own mythology.
Prognosis
If a company learns how to revisit well, several things begin to change. Defensiveness softens. The frontline becomes more useful as a sensing function rather than merely a delivery layer. Repeated friction becomes a source of direction instead of background noise. Leadership becomes more credible because it is more honest. Old assumptions lose their sacred status. Most importantly, the organisation becomes better at redesigning itself before the market, the customer, or the defect trend forces a harsher correction.
That is the deeper responsibility of leadership in a shifting environment. Not simply to invent the future, but to stop making humans compensate for the past.
Sometimes the bravest decision in an organisation is not to defend the model that got you here, but to admit that what once made sense may no longer deserve protection. The real risk is not going back to first principles. The real risk is forcing customers and frontline teams to keep absorbing the cost of assumptions that have already expired.