Early in a transformation, everyone looks for the champion. The person inside the company who carries the change when nobody from outside is in the room. The instinct is to find the most enthusiastic person available and convince them.
That instinct is wrong often enough to be worth examining.
The people who turn out to carry change were rarely won over by a good demonstration. They had tried something before, been let down, and carried that disappointment quietly. When they finally saw something that worked, they needed no convincing. They recognized the difference immediately, because they had felt the absence of it.
Why enthusiasm is a weak signal
Enthusiasm is easy to produce and it correlates with the wrong things. A person who responds well to a new initiative may be responding to novelty, to the attention, to a good presentation, or to the fact that supporting a leadership priority is sensible. None of those survive the first month of real implementation.
Three specific failure modes follow from picking the enthusiastic person.
Enthusiasm has no standard behind it. A person excited about a change has nothing to compare it against. When the implementation produces an uncomfortable finding, there is no internal reference telling them this is still better than what came before.
Early support is cheap and late support is expensive. Backing an initiative in a kickoff costs nothing. Defending it in month four, when it has created work for a colleague and a deadline has slipped, costs something real. Those are different behaviours and the first does not predict the second.
Enthusiasts tend to be positioned away from the work. The person most available to be excited is frequently the person least affected by the process in question, which means they cannot speak to it with authority when it is challenged.
What a prior disappointment actually produces
Someone who evaluated something before and watched it fail to land holds three things that cannot be manufactured.
A specific account of what went wrong
They can tell you exactly why the previous attempt failed, in detail, with examples. That account is a requirements document. It names the conditions under which the new attempt will also fail, from someone who has observed those conditions directly.
A standard they already decided mattered
This is the part that produces conviction. The person has established, independently and before anyone arrived to pitch them, what adequate looks like. When something meets that standard they are not evaluating a proposal, they are confirming a judgment they already made. The resulting advocacy is theirs rather than borrowed.
Credibility with the people who will be affected
A colleague who was skeptical before and is now supportive carries weight that an enthusiast never accumulates. The team knows this person has rejected something in this category previously, which makes their current position informative.
| The enthusiast | The person let down before | |
|---|---|---|
| Basis of support | The proposal looks good | It meets a standard they already set |
| Behaviour under a setback | Support softens | Support holds, if the standard still holds |
| Credibility with peers | Neutral | High, they have rejected this category before |
| Quality of their requirements | General | Specific, drawn from a failure they watched |
| What they need from you | Convincing | Evidence against their own criteria |
| Risk | Fades when it gets hard | Withdraws permanently if the standard is missed |
The bottom row is the cost of this profile and it is worth stating plainly. A person whose support rests on a standard will withdraw it the moment the standard is breached, and they will not come back. That is the same property that makes their support valuable.
How do you find them?
They do not volunteer, because quiet disappointment does not announce itself. Five approaches, in order of reliability.
1. Ask what was tried before
The direct question in any early meeting: has this been attempted here before, and what happened. The answer names the previous initiative, and the person who gives the most detailed answer is frequently the one who was closest to it.
2. Listen for the detailed objection
In a room where most feedback is general, one person raises a specific concern about a specific mechanism. That specificity usually comes from having watched that exact mechanism fail. The objection is a signal rather than resistance.
3. Look for the person maintaining a workaround
Someone who built a spreadsheet, a small internal tool or a manual process to compensate for a gap has already diagnosed the problem and acted on it with the resources available. They have the most direct evidence about the gap and the strongest interest in it closing properly.
4. Ask who the team escalates to informally
The person colleagues go to when something breaks holds the operational authority that matters, which is separate from the org chart. Their support is read by the team as a technical judgment rather than a political one.
5. Notice who stayed quiet in the kickoff
Silence in a room where enthusiasm is expected is informative. Some of it is disengagement. Some of it is a person who has seen this before and is waiting to see whether this time is different.
What they need, and what they do not
The handling is different from the handling of an enthusiast, and getting it wrong converts the strongest potential advocate into a permanent skeptic.
| They need | They do not need |
|---|---|
| Evidence against their own stated criteria | A general pitch |
| A direct answer about the previous failure | Reassurance that this is different |
| Their objection taken seriously on the record | Their objection smoothed over |
| Early visibility of something unflattering | Curated good news |
| A say in scope | A role in the communications plan |
| An explicit commitment on the standard | Enthusiasm |
The fourth row is the one teams get wrong most often. Showing this person an uncomfortable early result builds their support, because it demonstrates that the standard is being applied honestly. Curating the first results to look good removes the only thing that would have convinced them.
How conviction forms
Why prior disappointment produces durable advocacy
| Stage | What happens | What it leaves behind |
|---|---|---|
| Attempt | Something was tried and did not land | A detailed account of the failure |
| Reflection | The person works out why | A standard for what adequate means |
| Dormancy | The standard sits unused, quietly | A specific objection, ready |
| Recognition | Something meets the standard | Conviction, with no convincing needed |
| Advocacy | They defend their own judgment | Credibility with peers |
Nothing in this sequence is produced by a presentation. The standard was formed before anyone arrived, which is what makes the advocacy durable and what makes a breach of it final.
Working with them through the programme
Six practices, covering the period after the initial recognition.
1. Write down their standard, in their words
Whatever they said adequate looks like, record it and refer back to it. This becomes the acceptance criteria that matters most inside the organization, and it has the advantage of having been authored by someone who will still be there in a year.
2. Give them the first uncomfortable finding before anyone else
Not the flattering one. The finding that creates work for somebody. Their reaction to it tells you whether the standard is being met, and their involvement at that moment is what makes their later defence of the programme credible.
3. Let them carry the objection internally
When a colleague raises the concern this person raised in week one, they are better placed to answer it than anyone from outside. They have the answer and they have the standing.
4. Do not ask them to sell
Advocacy that comes from defending a judgment holds. Advocacy performed on request looks like what it is, and it costs them the credibility that made them useful.
5. Name what changed from the previous attempt, specifically
Not that this is different. Which mechanism is different, and why that addresses the thing that failed. They will test this claim and a general answer fails the test.
6. Tell them early when something is going to miss
A missed standard disclosed late ends the relationship. Disclosed early, with what is being done about it, it usually survives. This is the single highest-risk moment in the engagement.
Programme management guidance treats this as a named practice. ISO 21502 identifies stakeholder engagement as a distinct activity with its own ownership, separate from delivery, because engagement that is left as a byproduct of delivery does not happen. ISO 9001 requires organizations to ensure people are aware of their contribution and of the implications of not conforming, which is a formal way of stating that participation without understood purpose produces compliance rather than commitment.
Why the pattern is so common
The reason this profile exists in almost every organization is that most large companies have attempted something in the same category before. Transformation initiatives accumulate. A programme is launched, it produces partial results, attention moves, and the people who were closest to it absorb the outcome and go back to work.
Those people are still there. Each failed or stalled initiative left a group of individuals with a specific account of why it stalled and a standard they derived from it. From the outside, this looks like an organization resistant to change. From the inside, it is a population of people who have each developed criteria and are waiting to see whether anyone meets them.
That accumulation is measurable. At Mercado Libre, a discovery cycle found more than 600 initiatives already overlapping in the organization before the cycle began. Six hundred overlapping initiatives means a large number of people who have been through one, and a correspondingly large number of quietly held standards about what would have to be different.
Where Horizon fits
Horizon is an AI-powered continuous discovery platform. Its relevance to finding internal champions is incidental to its purpose and reliable in practice, because the questions it asks surface exactly the people this guide describes.
Discovery Cycles run AI-led interviews with everyone in a function, asking what they do, where they wait, what they fixed themselves and what they would warn a new colleague about. The third question identifies the people maintaining workarounds, which is the most dependable signal in the set. The fourth surfaces the detailed objection, from people who would not raise it in a room.
The Insights Dashboard holds findings with traceability to the inputs behind them, which matters here because a champion's own account appears in the evidence rather than as a secondhand summary. The Initiatives Dashboard assigns named owners to initiatives, and the people identified through those questions are frequently the right names.
At Mercado Libre, a cycle interviewed 2,000 employees across five countries in four days, covering 100% of the functions in scope against under 1% under manual sampling, and surfaced the 600-plus overlapping initiatives alongside 24 new ones with 2.3 million dollars in projected savings and 76 full-time equivalents avoided. Census coverage is what makes the quiet person reachable, since a sampled exercise reaches the people who are available and the person who stayed silent in the kickoff is rarely on that list. These figures describe one engagement and they are evidence rather than a guarantee.
The question worth asking any provider: does your method reach the people who did not volunteer, and can you tell me who in this organization has tried to fix this before?
Checklist for identifying an internal champion
- Has anything in this category been attempted here before, and what happened?
- Who was closest to that attempt, and are they still at the company?
- Who raised a specific objection rather than a general one?
- Who is maintaining a workaround, a spreadsheet or a small internal tool for this gap?
- Who do colleagues escalate to informally when this process breaks?
- Who stayed quiet when enthusiasm was expected?
- Can that person state what adequate would look like, in detail?
- Has their standard been written down in their own words?
- Have they seen an unflattering early result?
- Does the programme have a specific answer to why this attempt differs from the last one?
Question 7 is the test. A person who can describe the standard is a champion. A person who is simply disappointed is not, and the difference is whether the reflection happened.
Common mistakes
Choosing the most enthusiastic person. Enthusiasm is cheap to produce, carries no standard, and softens at the first setback.
Treating a detailed objection as resistance. The specificity came from having watched that mechanism fail, which makes it the most valuable input in the room.
Curating the first results. The honest application of a standard is the only thing that converts this profile, and curation removes it.
Asking them to advocate. Support that comes from defending their own judgment holds. Performed advocacy costs them the credibility that made them useful.
Claiming this time is different without naming the mechanism. They will test the claim, and a general answer confirms their prior conclusion.
Disclosing a missed standard late. Early disclosure usually survives. Late disclosure ends it permanently, and this profile does not return.
Relying on volunteers to find them. The person who matters here did not raise their hand, which is part of the profile.
FAQ
Who makes the best internal champion for enterprise software?
Usually someone who evaluated something in the same category before and watched it fail to deliver. They hold a specific account of why it failed, a standard they derived from it independently, and credibility with colleagues who know they have rejected this category before.
Why is the most enthusiastic person a poor choice?
Because enthusiasm has no reference point behind it. When an implementation produces an uncomfortable result or a deadline slips, there is no internal standard telling that person this is still better than the alternative, so support softens exactly when it is needed.
How do you identify someone who was let down before?
Ask what was tried previously and listen for the most detailed answer. Look for the person maintaining a workaround for the gap, the person who raised a specific rather than general objection, and the person colleagues escalate to informally. Note who stayed quiet when enthusiasm was expected.
What does this kind of champion need from a vendor or programme?
Evidence against their own stated criteria, a direct answer about why the previous attempt failed and what is mechanically different now, and early visibility of unflattering findings. They do not need reassurance, and curated good news actively works against you.
What is the risk of relying on this profile?
Their support rests on a standard, so it ends when the standard is breached, and it generally does not come back. The mitigation is disclosing a likely miss early, with what is being done about it, rather than after it happens.
Can an organization have too many of these people?
An organization with many of them has a history of initiatives that produced partial results, which is common in large companies. That is a difficult starting position and a workable one, because each of those individuals holds specific criteria rather than general skepticism, and criteria can be met.
Conviction comes from having felt the absence
The person who carries change inside an organization is rarely the one who responded best to the proposal. It is the one who knows precisely what inadequate feels like, decided some time ago what would have been enough, and has been waiting without saying so.
That makes the first question of any engagement a question about history. What was tried here before, who was closest to it, and are they still in the building.
See it. Fix it. Lead it.