When Transformation Outlives Its Relevance …. It deserves a Graceful Sunset for the success of the next one

 

Organisations are generally good at starting transformations. They know how to launch programs, announce aspirations, appoint sponsors, create steering committees, engage partners, design roadmaps, allocate budgets, and communicate with bold intent. 

The language of beginnings is familiar: digital-first, future-ready, agile, resilient, customer-centric, AI-enabled, globally competitive, sustainable, simplified, transformed.

But organizations are far less comfortable dealing with another equally important and frequently emerging question:

What to do when a transformation no longer deserves to continue?

Not because the original ambition was wrong. Not because the people involved failed. Not even because the transformation produced no value.  But because the assumptions that shaped the chosen path have changed.

And this question is becoming increasingly urgent.

The rise of AI is redrawing the economics of work. Supply chains are being redesigned around resilience, redundancy, and regionalization. Geopolitical tensions are influencing technology choices. Organizations are revisiting questions of self-reliance, sovereignty, data localization, vendor dependence, and strategic autonomy. Business models that appeared compelling a few years ago are being re-examined in light of new risks and possibilities.

In such an environment, many ongoing transformation programs may not be wrong in their purpose but outdated in their design.  They may not be able to withstand the honest question: 

If we were not already doing this, would we start this program today?

And relevance decay is the new risk that traditionalprogram governance structures are not designed to handle. 

This powerful question moves the discussion away from sunk cost and toward current relevance. It separates loyalty to the original ambition from attachment to the original vehicle. It allows leaders to ask whether a program should be accelerated, repositioned, merged, paused, or consciously closed. 

Any honest assessment of transformation portfolio will throw-up some programs that deserve closure before they consume more attention and resources. 

How Leadership manage these closure candidates matters a lot!

The convenient response!

Organizations often choose a softer path.  They do not cancel the program.

They simply reduce its feed.

Budgets reduce. Reviews become infrequent. Resources move elsewhere. Leadership attention shifts to the next priority. Teams sense the loss of sponsorship before anyone formally acknowledges it.

So the program is not officially cancelled. It is simply deprived of oxygen.

This quiet starvation feels convenient because it avoids a hard conversation. But it carries a deeper cost, because when leaders do not explain what has ended, people construct their own explanations — and those are rarely as generous as leadership would have intended. 

The program is never formally closed, so its lessons are never formally captured. It simply fades, taking its learning and its goodwill with it.

The emotional residue matters more than many leaders realise.

Employees lose trust in future announcements; teams become reluctant to emotionally commit again, middle managers learn that priorities are temporary, and future programs inherit accumulated skepticism.

The next transformation program does not start with hope. It starts with memory.

Why Leaders Choose Silence?

The answer is rarely lack of intelligence.  It is usually a combination of psychology, politics, identity, and organizational discomfort.

Grace framework recognizes five structural forces push leaders toward slow starvation rather than explicit closure.

1. Sunk cost entrenchment: The program has consumed capital, goodwill, and political credit. Acknowledging failure means writing off those costs publicly. The instinct is to keep the program nominally alive while quietly withdrawing resources, preserving the fiction that something may yet be salvaged.

2. The accountability vacuum: Transformationprograms have clear ownership of delivery. Almost noorganization assigns  explicit ownership of termination. When the closure decision belongs to no one specifically, it belongs to no one at all. Theprogram enters a state of distributed neglect.

3. Personal reputational exposure: The sponsor of a program is personally associated with its ambition.Terminating it on their watch risks being read as an admission of poor judgment. The game-theory outcome is coalition silence: each member privately knows the program is failing, but none will move first.

4. The new initiative provides cover: When a new priority emerges, it is convenient to let the old program die by distraction rather than decision. Resources migrate. No one formally closes what no one formally abandons. The program becomes vestigial.

5. The program as organisational symbol: Some programs acquire symbolic weight entirely separate from their instrumental value. Terminating them feels — and is sometimes experienced by others — as an act of cultural destruction. Closing it disrupts a narrative without offering a replacement.

A graceful sunset is possible 

Organizations that handle closure well tend to focus on the following three areas: 

1. Emphasize that the WHY survive, while Howexpires: 

If leaders have been doing “Why sharing” of the program well, explaining closure becomes easy. Much of the difficulty around closure comes from a confusion between the program and the purpose. Organizations assume that stopping the initiative means abandoning the ambition. Usually it does not.

Business may still need speed, the customer may still need a better experience, the enterprise may still need resilience. What has changed is the path.

A transformation is a means, not an end — and one of the quieter disciplines of transformation leadership is ensuring that people are committed to the purpose, not imprisoned by the program.

2. Acknowledge learning and separate it from embarrassment

Graceful closure should document and commit to memory: What the Program Leaves Behind.  A program may fail as an implementation vehicle but succeed as a learning vehicle.

A technology program leaves platforms, data, architecture decisions, and vendor relationships — its closure needs asset harvesting. A process program leaves routines, controls, and managerial habits — it needs learning consolidation. A talent program leaves expectations, trust, and emotional investment — it needs careful redeployment and honest communication. A culture program leaves beliefs, language, and identity — it needs the preservation of meaning.

The residue differs, by the program, bum us answer the question: 

What must survive this closure?

Framed that way, closure stops being an act of subtractionand becomes an act of stewardship — deciding deliberately what to carry forward rather than lettingeverything dissolve by neglect.

3. Honour contributors: Stand the People Test 

There is one signal that reveals, more honestly than any town hall or strategy deck, how an organization truly treats transformation outcomes: what happens to the people associated with a discontinued program.

If a program closes and the people who carried it are quietly sidelined, if sponsors are embarrassed andcontributors are left to explain the outcome defensively, the organization has taught its most capable people a precise and lasting lesson: transformation risk is career risk, and the next difficult initiative is not worth volunteering for. 

But if contribution is acknowledged, talent is redeployed with respect, and learning is visibly valued, the message is the opposite — that difficult transformation work is honored here, even when the path changes.

Those who carried a discontinued program become the organisations memory. They become either its future champions or its future cynics, and they shape the corridor conversations and the emotional climate around every initiative that follows. 

A graceful sunset is not complete until the peopledimension has been handled with dignity. Organizationsthat erase contributors create fear.  Organizations that honour contributors create resilience.

Transformations Closure design respects Context

Formal closure does not require theatrical communication.  It requires thoughtful communication.  The goal is not to dramatize the ending. Nor is it to hide it behind vague language.

As mature leaders, closure management execution must be calibrated to the specific context in which the organisation operates. A graceful sunset in a family-owned business requires different emphasis from one in a publicly listed conglomerate. A closure by a new CEO carries different permissions and risks from one executed by the CEO who launched the program. An Asian-origin firm requires cultural coding that a Western firm does not. Most importantly, the state of business decides the level of accommodation for such public acknowledgement of closure.

In an age shaped by AI disruption, geopolitical uncertainty, supply-chain redesign, sovereign technology choices, and accelerated business model shifts, more transformations will outlive the assumptions that created them.

Organizations must learn how to close one chapter without damaging belief in the next.

A graceful sunset is not surrender.  It is stewardship.

And perhaps that is what sustaining relevance ultimately requires:

Not only the courage to begin transformation, but also the wisdom to end, redirect, and renew it without leaving scars that the future must carry.

The Mirage of the Well-Written

 Beautifully crafted messages that lack depth, consistency, a binding theme, or contextual relevance are becoming easier to spot — and harder to ignore. They land on our desks with increasing frequency. Polished. Fluent. Empty.

It made me pause. What is behind this phenomenon?

The answer, I suspect, lies not in the tool being used but in a quiet abdication happening inside organisations — one that leaders are yet to name, let alone address. 

Effectiveness, in any meaningful sense, is the product of several things done right together. It demands clarity of purpose before a single word is written. It demands honest engagement with context — the kind that cannot be shortcut. It demands the discomfort of genuine contemplation, the discipline of choosing, and the courage to close. It demands collaboration that is real, not performative. And at the end, when the tide has settled, it demands a reckoning with conscience — a quiet, private audit of whether what was done was right, not just effective.

Communication sits within this chain. It gives form to thought. When done well, it is a multiplier. But it is not the chain itself. 

Here is what AI has changed: it has made the last step — the giving of form — extraordinarily easy. So easy that a generation of professionals is beginning to mistake the output of that step for the output of the entire process. A well-formatted document feels like a completed thought. A fluent summary feels like a resolved problem. The casual reader is convinced. And sometimes, so is the author.

This is the mirage of the well-written.

The danger is not that people are using AI. The danger is that the time and cognitive effort AI frees up is not being redirected into the harder, less visible work that precedes communication. It is simply being reclaimed as comfort. The drudgery tax — the friction of real thinking, of sitting with a problem long enough to understand it, of pressure-testing assumptions, of choosing when there is no clean answer — is being quietly avoided. And because the output still looks credible, no alarm goes off.

For leaders and managers, this is not a technology problem to be managed. It is a standards problem to be led.

Our teams are watching what we reward. If fluency is being mistaken for rigour, if presentation is substituting for preparation, if the polished deck is closing conversations that should still be open — they will optimise accordingly. They are rational. They will take the path that appears to work.

The cognitive habits being formed now — or lost now — will define the quality of judgment our organisations can call upon for the next decade. The capacity to think under pressure, to hold contradictions long enough to resolve them honestly, to do the unglamorous work of genuine analysis — these are not soft skills. They are the load-bearing structures of every good decision ever made.

AI will not blunt those capacities. Allowing them to go unexercised will.

The question worth sitting with is not how much AI our teams are using. It is whether the time being saved is being reinvested in the work that cannot be delegated — or whether it is simply disappearing into the comfort of a document that reads well and means less than it seems.

That distinction is worth our attention. It may be the most important leadership judgment of this moment. 

Beyond Communication

The seven dimensions of genuine effectiveness 

01 — Clarity

Clarity of Purpose

Before a single word is written or a meeting called, there is the question that most professionals skip: what, precisely, am I trying to achieve? Not a broad direction. Not a category of intent. A specific, testable outcome. Clarity is the first discipline — and the one most easily bypassed when tools are available that can generate plausible-looking output from vague input. AI will fill the gap where clarity should be. The output will look coherent. It will not be.

 

02 — Context

Context

Every problem sits inside a situation — with history, stakeholders, constraints, and competing interests that shape what is possible and what is wise. Context cannot be searched for and appended. It is built through immersion, through questions that feel inefficient, through paying attention to what is not said. A document produced without genuine contextual understanding will be technically fluent and situationally blind. Discerning readers will notice.

 

03 — Contemplation

Contemplation and Choosing

Between understanding a problem and acting on it lies the most uncomfortable territory: the space where one must hold competing options, resist premature resolution, and choose. System 1 thinking — fast, pattern-matching, satisficing — is always available and always cheaper. The discipline of genuine deliberation, of sitting with a decision long enough to understand its second-order consequences, is not. AI can model options. It cannot bear the weight of choosing on your behalf — and if you ask it to, you should not be surprised when the choice reflects no one's judgment.

 

04 — Construct & Communicate

Construct and Communicate

This is where AI performs extraordinarily well — and where its contribution must be understood precisely. Communication gives form to thought. A well-constructed argument, clearly articulated, is a genuine asset. But form amplifies what is already there. It does not create substance from its absence. When AI is used to construct and communicate after the prior three dimensions have been done with rigour, the result is powerful. When it substitutes for them, the result is the mirage: impressive in appearance, hollow under examination.

 

05 — Collaboration

Collaboration

Genuine collaboration — the kind that surfaces assumptions, challenges direction, and builds shared ownership — is one of the most cognitively demanding activities in organisational life. It is also one of the easiest to simulate. A meeting can be held without thinking together. Feedback can be solicited without being absorbed. Consensus can be declared without being earned. The question for leaders is not whether their teams are collaborating, but whether the collaboration is real — whether it is changing the thinking, not just the documentation.

 

06 — Closure

Closure and Completion

Effectiveness requires the discipline of ending — of making the final call, closing the loop, and moving forward with commitment. This is harder than it sounds in environments where optionality is valued and accountability is diffuse. The temptation is to let a well-written summary substitute for a decision. It does not. Closure is an act of will, not of writing.

 

07 — Conscience

Conscience

The last dimension is the quietest — and in many ways the most important. It is the private reckoning that follows when the problem is solved and the tide has passed: did I act rightly? Were my values intact? Was anyone diminished by how I operated? Conscience does not announce itself during the work. It surfaces in reflection. Leaders who do not create the conditions for this reflection — in themselves and in their teams — will find that effectiveness, over time, becomes something they are no longer proud of.

 

A quick self check: For each dimension, mark your honest rating on two scales — how good you are at this (Capability), and how satisfied you are with the time you invest here relative to what you know it deserves (Time Investment). The gap between the two is where your work lies.

A Call to Leaders and Their Teams

The seven dimensions above are not a framework to be presented in a deck. They are a map of where effectiveness actually lives — and where, under the gravitational pull of available tools, it is quietly being abandoned.

The obligation of leadership in this moment is not to restrict what tools teams use. It is to hold the standard of what good work requires — and to ensure that the next generation understands the difference between a document that is well written and a problem that is well solved.

The cognitive sharpness required for the first six dimensions — clarity, context, contemplation, genuine collaboration, decisive closure, and an honest conscience — is not a given. It is a muscle. Muscles that are not used atrophy with time,  That is law of nature! 

Reflection for self and team members:

The dimension I have been most avoiding: 

 

The time AI has saved me — where has it actually gone? 

 

One concrete change I commit to: 

 

Date of next honest review: 

 

 

Effectiveness is not the output. It is the integrity of the process that produced it.

The Governance Slide Deserves Better From customary slide to living practice

The governance slide is a customary part of every transformation program charter. It appears near the end of the presentation — mostly to be received rather than interrogated. 

It passes without contest, or at most some suggestions on names to be included, seldom who to exclude, in the governance structure.   It does this partly through familiarity — three boxes, three frequencies, multiple arrows pointing upward, a structure that resembles what everyone has seen before — and partly through the comfort of its deliverables. 

A governance structure, once approved, demands tangible evidence of its own existence: calendar invites to meetings that include everyone who carries influence over the program, whether or not they hold direct accountability for it; minutes that record discussions and file them; status reports that confirm the forum met and the slides were presented. These artefacts are not nothing. They create a paper trail. They satisfy assurance requirements. They give the impression that the program is being watched.

The question the slide does not invite — and that the room has rarely developed the habit of asking — is whether any of this watching actually governs anything.

What Governance Actually Is

Governance is not a structure to be designed and filed. It is a set of acts — best described in verbs — that either happen or do not. 

Every governance tier shares three universal acts regardless of its level. It must decide — not note, not discuss, not explore, but reach a conclusion with a named owner and a committed date. At every meeting, it must account for what it decided at the last. And it must communicate conclusions precisely enough that they survive interpretation by people who were not in the room. When a forum notes rather than decides, the verb has changed. So has the nature of what is happening. The verb is the test. 

Besides, the verbs to be part of three tiers include  

Steering Committee —  Sensing · Legitimising · Protecting · Re-calibrating.

Senses shifts in the external environment before they reach the program team. Legitimises the program's mandate in forums it cannot access. Protects the conditions the program needs — shielding it from shifting organisational priorities. And re-calibrates: this is the only tier with the standing and perspective to ask whether the governance design itself remains fit as the program evolves. 

Program Review —  Surfacing · Prioritising · Redirecting.

Surfaces uncomfortable variance early enough for corrective action to still matter — not after it has been managed locally for weeks and arrived upward already softened. Prioritises when demands exceed capacity. Redirects — issues corrective action, resolves the impasses the Core Team could not, and re-establishes what the next period must deliver.

Core Team —  Executing · Flagging · Integrating.

Executes against the integrated plan. Flags problems before local workarounds begin to disguise systemic risk. Its meeting has failed when it becomes a status report. It is working when it is a short, honest, forward-looking account of what is committed and what stands in the way.

The Assumptions Behind the Slide — and What Needs Contesting?

Governance does not fail because the design is wrong. It fails because the design mistakes a simplification for a reality — and no one takes responsibility for managing the distance between them. 

There are five assumptions about the operating context and human that need reality test:

Assumption 1 — Issues arrive pre-classified and can be cleanly routed to the appropriate tier.

Reality:  They cannot. Issues exist on a continuum. A decision about delaying a workstream by two weeks is simultaneously operational in execution terms, tactical in resource terms, and strategic in stakeholder-signalling terms. What gets decided where, needs to be guarded to avoid extremes in terms of all decisions seen important enough to rise to the top or left to core team to guess.   

Assumption 2 — Each tier's information needs are fully met by what rises from the tier below.

Reality:  This is a structural conflict of interest. The people producing the information are also the people being evaluated by it. When independent information accountability is absent, governance is not receiving filtered information — it is governing with structural blind spots that no amount of honest reporting from below can fill. Each tier has independent information obligations of its own to add to what comes from below. 

Assumption 3 — A scheduled meeting cadence is an adequate decision mechanism.

Reality:  It is not. Critical issues arise between sessions. When governance has no out-of-cycle mechanism, they are either resolved informally — by whoever is available, without the right authority — or deferred until delay becomes damage. This is an architectural gap, not a behavioural one. Every governance design needs a named escalation mechanism: a specific trigger, a named person, a defined timeline. The structure existed. The escalation discipline did not.

Assumption 4 — Consequential conversations happen inside governance forums.

Reality:  They happen before them. Positions are pre-negotiated in bilaterals. Coalitions form across tiers between meetings. This is not a governance failure — it is organisational life. The question is whether the formal structure retains enough clarity in its decision rights to remain the legitimate site of consequential decisions, or gradually becomes the place where predetermined conclusions are given procedural cover. Governance that has lost that legitimacy is still meeting. It has stopped mattering.

Assumption 5 — All participants are equally committed to the structure, regardless of seniority, style, or culture.

Reality:  Culture, hierarchy, and organisational history do not disappear because a charter has been signed. The most important variable in any governance system is the behaviour of the most senior person in the room. A governance structure that does not account for the specific leadership style and cultural context of its most senior participants — designing around them, not despite them — is a structure that will gradually become whatever those leaders are most comfortable with.

When the Mechanism Needs Reviewing?

Governance is designed at inception and then treated as settled infrastructure. It is not. There are several signals to infer that governance is failing — and when those signals appear, they call for review without waiting for permission or a convenient moment on the calendar.

The signals are observable and specific. 

• Key participants begin missing meetings or sending proxies without explanation — not once, but as a pattern. 
• Decisions made in one forum are revisited in the next without new information, suggesting that the first forum lacked the authority or the confidence to make them stick. 
• The same category of issue appears on the agenda at all three tiers simultaneously, which means it has not found its appropriate level and the tiers have not been able to route it. 
• Commitments made in governance forums are quietly skipped and no one surfaces the breach. 
• Escalations arrive late — after the decision window has passed — because the escalation mechanism has no teeth or the culture has learned not to use it. 
• Participants arrive without preparation, treating attendance as presence rather than engagement. 
• The minutes record discussion rather than decisions. The information pack looks the same at every tier, compressed rather than differentiated.

The astute architect does not explain them away — they name them, and they convene the people with the authority to redesign what is no longer working.

There is a second, distinct trigger that is almost universally overlooked. When the chair changes at any of the three tiers — when a new Steering Committee sponsor is appointed, when the program director is replaced, when the Core Team lead moves on — the governance mechanism should be explicitly re-endorsed, not passively continued. 

A governance structure designed around one chair's style, instincts, and relationships does not transfer automatically to their successor. The incoming chair brings a different risk appetite, a different relationship with the tiers above and below, and a different understanding of what the forum is for. If the mechanism is not reviewed and re-endorsed with their genuine understanding and commitment — not merely their presence in the next meeting — it will operate on assumptions that no longer hold, governed by a design built for a person who is no longer there.

Leadership change at any tier is a governance reset moment. Treating it as one is the difference between a governance structure that adapts and one that drifts.

When next time the slide appears? 

The governance slide deserves to be designed, not just drawn. Designing it means answering, before approval, the questions the room has learned not to ask: What specific class of decisions belongs to each tier — not as a principle but as a written list? What is the out-of-cycle escalation mechanism when an issue cannot wait? What independent information obligation does each tier carry beyond what the tier below provides? And who is responsible for calling a review of the governance design itself when it is no longer working?

It’s worth spending time on this slide, even if it appears late in the show!

 

This article is part of the PEACE Framework Reflection Series — a set of independent pieces on transformation leadership, each taking one theme and allowing deeper reflection.