Every consulting engagement leaves something behind. Sometimes it’s a 200-page playbook with charts, frameworks, and process maps. Sometimes it’s a senior planner who knows exactly why the criticality model is set up the way it is, can train new hires on it, and would push back if leadership tried to change it. Twelve months later, you can usually tell which one was the actual deliverable.
The playbook gets shelf-archived. The internal champion outlasts the consultants, the leadership change, the budget reshuffle, and the next reorg. That’s the difference between asset-management capability and asset-management documentation, and it’s usually the line between programs that thrive and programs that quietly die.
What kills implementation continuity
Almost every stalled or failed asset-management program has one of three failure modes upstream:
The consultants left before knowledge transferred
The engagement ended on time. The deliverables were accepted. But the people who actually understood the design left with the engagement. Six months later, when someone needs to adjust a criticality threshold, there’s nobody internal who can explain why the threshold was set where it was.
The original sponsor moved on
A VP championed the program, the rollout went well, and then the VP got promoted, retired, or moved to a different organization. The replacement had no investment in the design, and within a year, the program drifted back to whatever the new leader was comfortable with.
The frontline never owned it
Planners and supervisors were “trained on” the new workflow but never participated in designing it. They tolerated it as long as it was new and visible, then quietly went back to whatever worked before. Adoption decayed without anyone announcing it.
What an internal champion actually looks like
Internal champions aren’t the senior leaders who signed the engagement. They’re usually one or two layers below the executive sponsor: a planning supervisor, a reliability lead, a facilities manager who’s been at the organization for ten years and intends to be there for another ten.
They have three qualities that make them durable:
- They understand why decisions were made, not just what was decided. They can explain the criticality model, the asset hierarchy, the workflow design, and they can defend it when someone proposes changing it for the wrong reason.
- They have the credibility to push back upward. When a new VP suggests reorganizing the program, the champion is the person who can say “here’s why we did it this way, and here’s what we’ll lose if we change it.”
- They train the next generation. New hires learn the program from them, not from a binder. The institutional knowledge transfers without consultants involved.
How to build one (vs. hire one)
You can’t recruit an internal champion from outside. By definition, they have to be internal. What you can do is design your consulting engagement so that someone on your team ends up as one.
That changes how the work gets done. Three shifts:
Co-design instead of present-and-approve
If the consultants design the program and present it for sign-off, you’ll get sign-off but not ownership. If your senior planner sits in every design session and is partly responsible for the choices made, they’ll own the result. The work takes a little longer. The result lasts a lot longer.
Hand off the why, not just the what
Documentation that lists what was decided is the playbook. Documentation that captures why each decision was made is the foundation for someone else to defend it later. Insist on the second kind, even if it takes more pages and more conversations.
Build in a six-month check-back, not a final deliverable
A “final deliverable” is a fiction in asset management. The real test is six to twelve months later, when the rollout has met reality. A short check-in built into the engagement gives the internal champion a chance to ask the questions that only show up after they’ve lived with the design.
The consultant tax you stop paying
The math on a well-developed internal champion is straightforward: every adjustment your team can make without calling the consultant back is a tax you stop paying. Over a few years, that compounds into real money.
The firms that don’t want this for you will tell you that asset management is complex, that the frameworks evolve, that you’ll always need external expertise. Some of that’s true. But the difference between “we’ll consult occasionally” and “we’re on retainer indefinitely” is whether your team is genuinely capable of running the program without us. The firms whose business model depends on the second arrangement are not the firms you want.
How to identify the internal champion in your own organization this quarter
Three questions to ask, in roughly this order:
- Who’s been here long enough to remember the last attempt? Continuity beats novelty in asset management. Your potential champion has probably seen at least one previous initiative come and go.
- Who do other people go to when they have a process question? The informal source-of-truth on your team is your champion in waiting. They’ve already earned the credibility; the work is to give them the structure.
- Who pushes back constructively in design meetings? The person who challenges assumptions early is going to be the person who defends the design later. Skeptical isn’t a problem. Disengaged is.
If you can name that person now, your next engagement should be built around making sure they end it stronger than they started it. The deliverable is the person, not the binder.
