Change management initiatives fail most often not because tools or plans are wrong, but because no one inside the organization owns the outcome. Every successful transformation has an internal champion — someone who believes in the change, drives adoption daily, and absorbs friction so the rest of the team moves forward.
We have been implementing Tarkie, our field operations automation software, for a decade now.
One thing we have learned in that time?
You can have the best tools, the most responsive support team, and a well-funded implementation plan. But if no one inside the company champions the change, progress will be painfully slow.
We have run dozens of implementations across industries — logistics, construction, utilities, services. The pattern that separates the ones that succeed from the ones that stall is almost never the technology. The technology works. The pattern is always about people. Specifically, about one person.
Why change management keeps failing the same way
Most organizations approach change management as a project. There is a kickoff. There is a rollout timeline. There is a training plan. There is a support contract.
All of that is necessary. None of it is sufficient.
What organizations consistently underestimate is the informal leadership that has to happen every day between the official project meetings. The conversation in the team chat when someone says the new system is confusing. The nudge when a colleague quietly defaults back to the spreadsheet. The moment when a real business result comes out of the new process, and someone makes sure it gets noticed.
That work does not happen inside a project plan. It happens because one person decides to own it.
The gap in most change management strategies is not the rollout. It is the absence of someone inside the organization who has made the change their personal cause.
The moment things moved
Recently, we had a client who had been on-and-off with their Tarkie implementation for months. Check-ins happened. Plans were updated. Timelines were reset. But things kept moving in circles.
Then, someone new joined their team.
He understood what automation could do for their operations. He believed in it. He pushed the agenda. He made it clear to his colleagues — not through a memo, but through his daily behavior — that this was the direction they were going.
Suddenly, things moved fast.
Not because the software changed. Not because our support approach changed. Because one person stepped in and owned the outcome.
That is what a champion does. And that is still worth paying attention to, because it keeps being the deciding variable in every implementation we run.
What a change champion actually does
A champion in a change management context is not just someone who supports the initiative. Support is passive. A champion is active.
Here is what that active role looks like:
Speak the business case in the team’s language
Most change management communication travels top-down and arrives in generic terms. “We are implementing a new system to improve efficiency.” That sentence means nothing to the field coordinator who is already stretched, or the supervisor who has been doing things the same way for five years.
A champion translates. They know the specific frustrations their team carries every day, and they can show — concretely — how the change addresses those frustrations. “Remember when you had to call the office three times to confirm a delivery? This fixes that.” That specificity is what builds belief where it actually matters: at the team level.
Absorb the friction so others do not have to
Early-stage automation adoption is full of rough edges. There are forms that need adjusting. Workflows that need refinement. Processes that feel slower before they feel faster. New users hit those edges and form opinions quickly — usually negative ones, unless someone manages the experience.
A champion absorbs that friction. They escalate what needs fixing before it becomes a reason to give up. They protect the team from feeling like they are on their own with a system that is not ready. They make the rough edge a temporary problem to solve rather than a permanent reason to go back.
We see this in Tarkie deployments consistently. The implementations where someone from the client’s side is actively feeding back issues, pushing for resolutions, and keeping their team steady through the rough-edge period are the ones that graduate to full adoption. The ones where no one is playing that role tend to plateau.
Make the old way slightly harder to reach
This is less obvious than the first two, but it works.
A champion gradually shifts the team’s default behavior toward the new system. Not through mandate. Through small structural nudges. The shared tracker is now in Tarkie. The daily submission comes from the app. The operations report pulls from the system. The old workaround is still available, but it is no longer where the team naturally goes.
This is how lasting habit change works in organizations. The environment changes before the mindset fully catches up. The champion is the person who changes the environment.
Celebrate early wins visibly
When a field coordinator submits a verified report in half the time, that story needs to be told. Not as a corporate announcement with a press release tone. As a real story, shared in the group chat, brought up in the next team briefing, mentioned to the department head.
Visible wins build the internal case faster than any formal training. They show colleagues that the change is not theoretical. It is working. And they give the champion social proof to keep pushing.
At Olern, where we design learning programs for organizations in transition, we track this pattern across cohorts. The programs that achieve lasting behavior change are almost always supported by someone inside the organization who is actively linking learning to visible results. Without that link, adoption plateaus even when the content is strong.
Who the champion needs to be
The champion does not have to be the CEO. In most successful implementations we have seen, it is not.
Effective champions show up at every level — IT leads, operations managers, department heads, frontline supervisors who just happen to believe in what the change can do. What they share is not title or rank. It is ownership. They feel the change management effort as their responsibility, not as something being done to their team by a vendor or an executive.
The one place a champion cannot live is somewhere isolated from the day-to-day work. A champion who is not in the flow will not hear the doubts early. They will not know where the resistance is forming. They will not be credible when they address it.
Change management frameworks talk a great deal about executive sponsorship, and that matters. But executive sponsorship is not the same as a champion. A sponsor gives permission. A champion gives momentum. Both are needed, and confusing one for the other is a common failure mode.
The role of leadership in finding and supporting champions
Leaders have a specific job in this dynamic: identify the potential champion early, give them the information and authority they need to do the work, and protect their time.
This last one is important. A champion who is also carrying a full operational workload without any relief will burn out before the adoption curve completes. If the organization is serious about the change, the champion’s contribution needs to be recognized and resourced — not just expected on top of everything else.
At MobileOptima, when we begin a new implementation, one of the first questions we ask is: who inside your organization is going to own this? Not who is the project contact. Who is the champion? If no clear name comes up, we flag it as the highest-priority gap before we finalize the plan.
The tools, the training, the timeline — all of those can be adjusted mid-implementation. The absence of a champion is harder to fix once things are already moving.
What to do this week
If you are running a change management effort right now, ask yourself honestly: who is the champion?
Not who is the project sponsor. Not who signed the contract. Who is the person inside the organization who believes in this, talks about it with colleagues, and takes it personally when progress stalls?
Name the champion. If you have someone in mind, make that role explicit. Tell them what you are asking of them. Give them the information they need, the escalation path when things need fixing, and the visibility to celebrate wins.
Brief the champion on the friction points. Do not wait for them to discover the rough edges on their own. Walk them through the known issues, what is being done about them, and what the team should expect in the first 30 days. A champion who understands the full picture is more effective than one who is surprised by the same complaints their team is.
Create a visible win in the first two weeks. Work with the champion to identify one process that the new system will visibly improve, get that result, and make sure the team sees it. Early visibility sets the tone for everything that follows.
Tools are powerful.
But leadership is what makes them work.
Frequently Asked Questions
What is a change champion in change management? A change champion is someone inside an organization who actively drives adoption of a new system or process. Unlike a project sponsor, who provides approval and budget, a champion works at the team level — translating the business case, absorbing friction, and making the change feel real to the people doing the daily work.
Why do change management initiatives fail without an internal champion? Without a champion, the informal gaps in a change management plan go unfilled. Training covers the technical side, and a project sponsor provides authorization, but neither addresses the day-to-day doubts, workarounds, and resistance that build up at the team level. A champion is the person who closes those gaps in real time.
Does the change champion need to be a senior leader? No. Effective champions appear at every organizational level — operations managers, IT leads, department heads, and sometimes frontline supervisors. What matters is ownership and proximity to the daily work, not title or rank. A champion isolated from the team’s day-to-day is less effective than one working alongside the people being asked to change.
How do you identify a potential change champion inside your organization? Look for someone who already engages with the change positively, has credibility with the team being affected, and is close enough to daily operations to hear resistance early. They do not need to be the most senior person in the room — they need to be the most trusted person in the workflow.
What is the difference between a change sponsor and a change champion? A sponsor gives permission — they authorize the initiative, provide budget, and signal organizational commitment. A champion gives momentum — they work inside the team, translate the rationale into practical terms, and drive adoption day by day. Both roles are necessary, but confusing one for the other leads to programs that are approved but not adopted.
How long does it take to see results when a strong change champion is in place? In Tarkie implementations where a clear champion engages from the start, teams typically shift from on-and-off adoption to consistent use within four to eight weeks. The variable is not the technology — it is how quickly the champion can get the team through the rough-edge period of early adoption and to their first visible win.
Are you running a change initiative right now? I would be curious to hear who your champion is — and what has made them effective.
