When Go-Live Is Not the Finish Line

By Belinda Annette Komuntale

If you have recently launched a major transformation initiative, you may have already marked the milestone. The system is live. The policy is gazetted. The press conference happened. And yet, something feels unresolved.

That feeling is usually correct.

Across East Africa’s public and private institutions, transformation initiatives regularly reach go-live without achieving the outcomes they were designed for. Implementation and transformation are not the same thing. The visible milestone is not the outcome. And in the distance between what was launched and what was actually adopted, institutions quietly absorb costs that most of them never stop to calculate.

In my years working on public financial management reform and institutional change across East Africa, I have seen this pattern repeat itself with remarkable consistency. The launch happens, the fanfare subsides, and the real work of making the change stick either begins in earnest or it does not begin at all.

What Is the Trap of False Completion?

The moment a new system goes live or a policy is gazetted in East Africa’s public institutions, a familiar sequence follows. There is a launch event: the ribbon cutting, the press conference, and what I have come to call the launches and the lunches.

Hierarchical and institutional cultures reward visible achievement heavily. The energy concentrates on the visualisation of success rather than its substance.

Declaring an initiative complete at go-live is, many times, a calculated strategic move: to comply with the budget, to meet the schedule, and to demonstrate progress to stakeholders. The leaders claim a victory. But the outcomes of the milestone have not been achieved, and the people the change was designed to affect have not yet been supported to work differently.

By the time you mark a milestone, you should be able to track the intended outcomes, the benefits, and the data should be telling a real story.

Many organisations define project success by whether key delivery milestones have been achieved. Ask yourself which of these measures your organisation uses:

• Was the system delivered on schedule?
• Did the implementation stay within budget?
• Was the policy approved and gazetted?
• Did the project go live as planned?

These are all important measures of project delivery. They tell you whether the project was executed effectively, but they do not tell you whether the organisation has actually changed.

The questions that determine whether a transformation has truly succeeded are different:

• Are employees consistently using the new system or process?
• Have leaders adopted new ways of making decisions?
• Are citizens or customers experiencing better outcomes?
• Have the desired behaviours become part of everyday work?
• Are the expected benefits being realised?

A project can be delivered on time, within budget, and according to scope and still fail to achieve its intended outcomes. Systems can go live, policies can be approved, and training can be completed, yet people continue working exactly as they did before.

This is what I call the trap of false completion: mistaking project completion for organisational change.

A Practical Lesson from a Large-Scale Digital Transformation

A large-scale digital transformation in the public sector that I supported in East Africa illustrates this clearly. The programme was developed in collaboration with a range of internal and external partners, with the initial phase focused on migrating institutional users to a new digital platform.

When an ambitious go-live timeline was set before operational readiness had been fully established, the team faced a critical choice: treat the compressed timeline as a crisis or use it as a catalyst to prioritise user adoption alongside technical delivery.

The team chose the latter. Here is what that looked like in practice:

• Resolved remaining system gaps through intensive testing within two weeks
• Segmented the user base to onboard cohorts with the highest readiness and capacity first
• Brought early cohorts into small group sessions, walked them through the platform, and addressed specific concerns directly
• Demonstrated clearly what daily operations would look like under the new way of working
• Used the first cohort’s successful onboarding as the basis for a credible public demonstration of progress

The lesson was not about the timeline. It was about what happens when adoption is treated as equal in urgency to technical delivery. A difficult moment became a credible milestone because the team invested in people readiness at the same time as resolving technical gaps.

That is a choice every leadership team can make, regardless of the delivery pressure they face.

Institutions need to learn to compute the cost of false completion and integrate it into their action plans. These are the real issues that affect outcomes.

The true cost of false completion extends beyond budgets and timelines. It includes:

• Lost return on technology investments
• Additional training and retraining costs
• Duplicate manual processes running alongside new systems
• Delayed realisation of intended benefits
• Stakeholder fatigue that undermines future initiatives
• Reputational damage for institutions and their leaders

The Adoption Gap: What It Looks Like on the Ground

You may have experienced this yourself. You walk into an organisation that has recently gone live with a new system. You see the posters in the lift, the values framed in the corridor, the strategy visualised in modern language, and the benefits of the new system beautifully laid out on the walls.

It feels like progress.

Then you walk past the visuals and sit with the teams who are actually working with the system every day. The story they tell is completely different.

This is what I call the adoption gap: the space between what exists in organisational documents and what actually happens in practice.

An independent institutional review of one organisation revealed this gap in measurable terms. The review began with the assumption that the platform had been successfully implemented and that its core functionality was available to users. The question was not whether the technology worked, but whether people were actually using it as intended.

Only 56 percent of the system’s functionalities were in active use. Of the remaining 44 percent, a significant portion were not optional features. They were mandatory.

The outcomes the system had been built to deliver were locked inside features that no one was touching. They were never going to be realised.

This is the real risk of superficial change management. Without a structured post-implementation review, the gap between what a system was designed to achieve and what is actually happening can remain invisible for years.

The adoption gap has recognisable symptoms. Look for signs such as:

• Employees continue using legacy processes alongside new systems, particularly where the new process increases visibility or accountability.
• Teams speak the language of change in meetings but revert to old ways of working in their day-to-day activities.
• Leaders assume key system functionalities are being used as intended, when in reality they are underutilised or bypassed altogether.
• Strategic priorities are visible in presentations and on office walls, yet the behaviours required to deliver them have not changed.

Technology is fast-forwarded. Behaviour stays in the past.

If nobody helps people see a future in which the new way of working strengthens rather than threatens their relevance, the system will inevitably be bypassed.

Why Leaders Look in the Wrong Direction When Change Stalls

When transformation loses momentum, the instinct is to search for active resistance: a blocking executive, a cynical team, or an unyielding culture.

In practice, something much quieter is usually happening.

What looks like resistance is often the accumulated weight of change fatigue, structural gaps, and an organisational culture of silence.

A comprehensive culture survey commissioned during a major change initiative illustrated this pattern clearly.

The institution had been through an extended period of structural shifts: multiple strategic cycles, system overhauls, and policy updates. The people living through it were exhausted, and a leadership transition brought renewed pressure to demonstrate immediate progress.

The independent survey results revealed a striking internal disconnect:

• Senior management rated the organisation as healthy and the transformation as highly successful.
• Frontline employees gave ratings close to those of leadership, heavily shaped by caution about the consequences of candid feedback.
• Middle managers said the exact opposite: change fatigue, unaddressed structural gaps, and poor performance on the very issues the transformation was designed to fix.

In organisations where hierarchy is strong and psychological safety is limited, people often report what feels safe to say rather than what leaders most need to hear. As information moves upward, uncomfortable realities are softened, filtered, or left unspoken.

The people closest to operational reality are often those whose insights never reach the executive table. As a result, leaders may believe a transformation is succeeding while the adoption gap continues to widen beneath the surface.

The significance of these insights lay in the fact that they were independently corroborated by external stakeholders. Clients reported the same patterns that middle managers had identified: delayed responses, slow decision-making, and unresolved operational bottlenecks.

Unlike internal employees, external partners had no incentive to protect organisational hierarchies or internal narratives. Their experiences therefore provided independent validation that the challenges identified by middle management reflected operational reality rather than isolated perceptions.

That is not active resistance. It is a system of silence created by hierarchy, organisational anxiety, and a lack of psychological safety that prevents operational realities from reaching those responsible for leading the transformation.

In highly structured environments, people comply outwardly with authority. What manifests instead is covert non-compliance: polite deference, slow turnaround times, and manual workarounds that mimic cooperation. It is passive resistance, shaped by culture and survival instinct.

Programmes also frequently stall not because of a lack of trained practitioners, but because abstract change frameworks fail to translate into applied diagnostic practice. When friction points arise, the instinctive institutional response is to issue a directive. Directives alone do not shift culture. Leaders must prepare the environment, address human behaviour, and make the path to the new way of working feel safer than reverting to legacy habits.

Five Actions to Take After Go-Live

The period immediately following implementation is the most critical and the most neglected phase of any transformation. Here are five actions that determine whether the change takes hold.

1. Redefine what success looks like

Go-live is a transition point, not a conclusion. Shift your indicators away from purely technical delivery and focus heavily on adoption metrics.

By the time a milestone is reached, you should actively be tracking system usage rates, functionality adoption, behavioural shifts, and early benefit realisation. The data should tell a real story, not just confirm that the launch occurred.

2. Invest in people readiness after implementation

Technical readiness alone is never enough. System gaps can often be resolved in weeks. The deeper work involves building user confidence, removing operational hesitation, and showing teams what the new way of working makes possible.

“We worked so hard to remove that fear. And then we built capacity to show them that it’s doable.”

Effective change management must continue well beyond the launch through targeted coaching and ongoing capability building. The moment you assume the training was enough, you have lost the thread.

3. Keep executive sponsors actively engaged

Visible sponsorship cannot end at the launch event. Sustained executive engagement provides implementation teams with the authority to act under pressure and the backing to dismantle institutional roadblocks.

When sponsorship becomes ceremonial post-launch, organisations quietly revert to historical patterns within months. Sponsors need to remain visible, keep the change on the agenda, and address barriers as they surface. Silence from the top is not a sign of progress.

4. Create channels for honest feedback to travel upward

Without structured, psychologically safe feedback mechanisms, you make strategic decisions based on an incomplete picture. Ask yourself honestly: does the feedback you receive reflect true operational realities, or what your teams believe you want to hear?

5. Measure adoption, not just activity outputs

Avoid the trap of tracking training sessions held or communications sent. These do not equal outcomes.

Prioritise proficiency audits, functionality usage reviews, and post-implementation adoption assessments. These are the measures that tell the real story of how deeply your transformation has taken root.

How Reinforcement Sustains What the Launch Creates

Organisations that sustain transformation treat reinforcement not as a final phase, but as a permanent management practice. Reinforcement does not have an end date.

Reinforcement depends on consistent organisational structures and signals that continuously communicate, reinforce, and reward the desired behaviours. Organisations that sustain change typically rely on the following reinforcement mechanisms:

• Decommission legacy pathways. If manual workarounds or paper options remain accessible, teams will default to them. Remove the old path entirely and make the new system the only viable way forward.
• Celebrate behavioural shifts over status. Publicly acknowledge operational staff who champion new frameworks, regardless of rank. When you reward behaviour over title, you rewrite the rules of what it means to succeed in that institution.
• Align incentives with efficiency. Teams that optimise workflows and reduce turnaround times should be celebrated, not penalised. In some East African contexts there is a word for the person who delivers differently: Kajaja, someone whose drive unsettles those around them. Reinforcement means making that person the norm, not the exception.
• Run proficiency audits. Measure how deeply adoption has taken hold, not just whether training was delivered.
• Capture lessons as institutional capital. Embed post-implementation insights into the organisation’s long-term change approach rather than treating them as institutional embarrassment.
• Follow through on high-level directives. Directives backed by visible leadership behaviour and real accountability are a legitimate form of reinforcement. A directive that disappears into the file is not.

Reinforcement means rewriting the unwritten rules of organisational life so that embracing change becomes safer than clinging to the status quo.

Reinforcement is also about recognising every contribution to the success of a change, from the executive sponsor who championed it to the frontline employee who brings it to life every day.

When people at every level feel that their contribution has been recognised and valued, the new way of working becomes something they collectively own rather than something that has been imposed upon them.

Leading Transformation That Lasts

Sustaining transformation in East Africa’s public and private institutions means confronting the hidden dynamics that preserve the status quo: the historical gatekeeping, institutional inertia, and the anxiety that transparent systems might disrupt traditional control structures.

It means demonstrating to people at every level that their relevance and authority are not diminished by change. They are enhanced when they become genuine owners of the new way of working.

In my experience working with institutions across East Africa, the gap between what was launched and what was sustained almost always traces back to three factors:

• Leaders who disengaged after the announcement
• Managers who were never equipped to carry the change into daily operations
• Approaches that had no reinforcement plan beyond the launch

A go-live is a milestone. A gazetted policy is a milestone. The outcome is the behaviour change that makes the milestone meaningful: the data quality that makes the system valuable, the decision-making practices that make the strategy real, and the service experience that makes the investment worth what it cost.

The question every leader should sit with after a launch is not: who is resisting?

The question is: have we made it safer for people to change than to stay the same?

Because until the answer to that is yes, the launch is still the beginning.