A short essay on how we work, why the lifecycle has four stages, and what we mean by “landed.”
Most consulting firms sell a strategy. We sell a landing. The distinction sounds like a slogan; it is, in fact, the difference between a programme that changes a P&L and one that ends with a steerco congratulating itself.
After twenty years inside European transformations, we have come to a simple view: the strategy is rarely the problem. The problem is the half-second between approval and execution — the moment a thoughtful document becomes a real demand on real managers in a real organisation that does not stop running while you change it.
We are accountable to outcomes & adoption, not slide decks.
Advolium exists because the two of us got tired of the alternatives. The Big Four hand you a beautiful target operating model and a pyramid of analysts to draft the policies — but the partners who won the pitch are not in the room when the change has to land. Freelance networks give you one excellent operator — until that operator is unavailable, or until the problem turns out to need a different kind of excellent operator.
We work in a different way. Two senior partners. One bill. Tech, transformation, change and AI in one team. We carry the engagement from first conversation to sustained operation. We are deliberately small because we want to be deliberately accountable.
Every engagement, regardless of scope, moves through the same four stages. The proportions vary — a six-week diagnostic is mostly stage one; an embedded partnership is mostly stages three and four — but the sequence is the discipline.
Read the business honestly. Separate the real problem from the one that has been described in the steerco. Stage one is mostly conversations — with the people who own the work, the people who fund the work, and the people the work will be done to.
The output is a short, written diagnosis: the actual problem, the credible options, and the proposition for what stage two should design. It is the document we are willing to be argued with about.
Executive interviews, programme reviews, evidence-gathering, board-grade synthesis.
A 20–40 page written diagnosis. A “say no” option. A draft brief for stage two.
Whether the work is worth doing, and at what scale.
Architect the target. Technical architecture, operating model, organisational design, programme plan — all together, by the same team, with the constraints of the company that has to live in it.
We design backwards from adoption. A target that cannot be landed is not a target; it is a slide. So we test every design choice against three questions: who runs it, how do they learn it, and how will we know it is happening.
Target architecture, operating-model design, capability mapping, programme planning, sponsorship modelling.
An integrated target, an adoption-tested plan, named owners, and a baseline that stage four can be measured against.
Whether the company can absorb the change at the speed proposed.
Stand the programme up. Govern, sequence, contract, staff. Move from intent to motion. We run the transformation office, sit in the steerco, hold the workstreams to the calendar.
This is the stage where most programmes lose their narrative. The kick-off was confident; the design was clear; then real life — sales targets, regulatory deadlines, the quarter — intrudes. Mobilize is the discipline of holding the design intact while reality pushes back.
PMO, governance, vendor management, escalation, sponsor coaching, first-wave deployment.
A steerco that knows the truth. A programme that meets its calendar. A first cohort live and measured.
Whether the change is moving, in run-rate terms, against the baseline.
Land it. Embed the change inside the line until the new way is the only way. Then leave. This is the stage that almost no consulting firm sells, because it is unglamorous and it requires patience — which is precisely why we sell it.
Sustain looks like: managers using the new tools without thinking about them, the steerco being asked to disband, and Advolium being uninvited from the regular meeting because the team owns it now. That is success.
Adoption tracking, manager enablement, governance hand-down, capability transfer, programme close.
Sustained adoption, measured. Capability inside the line. A written close-out. An honest retrospective.
Whether the change has “landed” — in adoption, in P&L, and in the daily behaviour of managers.
Not values. Operating decisions. They are what makes the model work and what would make it fail if we relaxed them.
If you have a piece of work that needs an advisor who is going to be in the room when it ships — not just when it is approved — let's talk.
Start a conversation