The Lonely Mountain — Go-Live Is Not the End of the Story

Here is a structural fact about The Hobbit that most readers forget: the company reaches the Lonely Mountain — the destination, the goal of the whole quest — with nearly a third of the book still to go. The dragon, the treasure, the thing they came for: achieved. And then come the hardest chapters. Lake-town burns. Armies march. Old alliances fracture over the spoils. Thorin, victorious, nearly destroys everything through what victory does to him.

Tolkien understood something that transformation programmes routinely get wrong. Reaching the mountain is not the end of the story. It is where the real story starts.

The battle after the party

I have watched this pattern play out more times than I can count. The technical migration succeeds. There is a go-live celebration with speeches, and the programme team begins to roll off. Mission, officially, accomplished.

Then, within a few months, the battle of five armies arrives. The retained organisation keeps working around the new processes instead of through them, because the old ways are comfortable and nobody is watching anymore. Managers who quietly opposed the model all along, sensing the sponsors have moved on, stop being quiet. New suppliers, measured on contracts written before reality arrived, fall into conflict over every gap between them. None of it appears on a risk register, because the programme that owned the risk register was disbanded at the party.

The unglamorous months after the celebration are where the business case is actually won or lost: renegotiating a supplier boundary, coaching managers who have never worked in the new model, making process adoption somebody’s real job with real consequences. It is far less exciting than the build. It is also where the value lives.

The decade after the decision

In the first post of this series I told the story of a contested platform strategy — moving a large financial-services group off an expensive proprietary Unix platform and onto Intel and Linux, around 2001. I told it there as a story about resistance. Here is the part I left out: winning the decision was the summit, and the summit turned out to be the beginning.

The strategy was agreed in 2001. The actual mountain came afterwards: a hard push to eliminate the old platform within eighteen months, then years of consolidation and virtualisation, wave after unglamorous wave of migrations, long after the strategic applause had faded. Nobody celebrates a migration in year three the way they celebrate a strategy paper in month one. But the value never lived in the decision. It lived in the decade of holding it.

And it held for ten years — through reorganisations, through new architects with new preferences, through my own moves into other roles. Not by luck: the sustaining had been designed in from the start. The decision had been derived together with the people who would have to run it, so no successor ever had an appetite for reversing it. Contested strategies that are imposed get reversed at the first change of the guard. This one outlasted several.

Somewhere in my archive is a photo from those years: my young daughter sitting on a decommissioned server box as we rolled it out of the data centre. That is what year three of a winning strategy actually looks like — a child on a box, a corridor, another migration weekend. Unglamorous, and the whole point.

The treasure is not the decision you win. It is what still stands a decade later — and that is decided in the years after the party, not at it.

What this means for your transformation

Plan past the mountain. The standard transformation budget spends almost everything getting to go-live and almost nothing on the eighteen months after — which is precisely backwards, because that is where the value is decided.

A few rules I now treat as non-negotiable:

1. Fund the period after go-live as a phase, not a contingency. Adoption, stabilisation, and supplier tuning are work packages with owners — not things that happen on their own.
2. Keep sponsors visibly engaged after the party. Resistance waits for the sponsors’ eyes to move. The cheapest counter-measure is for them not to move.
3. Measure adoption, not just deployment. “The system is live” and “people work the new way” are different claims, usually about a year apart.

The summit is not the destination. Sustainable change is. Bilbo’s quest didn’t end when Smaug died. Neither does yours.

“So comes snow after fire, and even dragons have their ending!”
— The Hobbit, Chapter 18

Part 9 of ten in There and Back Again — Transformation Lessons from an Unexpected Journey. Previous: The Arkenstone. Next, the finale: There and Back Again — on bringing the journey’s wisdom home.