Building an Internal AI Champion

1. Every Rollout That Works Has One

Watch enough AI rollouts at firms and a pattern shows up that has nothing to do with the tool. The ones that stick have a champion. The ones that fade do not.

It is the single most reliable predictor. Same software, same training, same plan: the firm with one person who owns the effort gets adoption, and the firm that left it to a committee gets a fade. The reason is simple. Training teaches a skill, but the skill dies the first time someone hits friction with no one to ask. The champion is the someone. They turn a workshop into a habit by being there in the weeks after, when the energy would otherwise drain.

This is also the most common reason rollouts fail, which is covered from the failure side in why AI rollouts fail at investment firms. Here we take the positive case: how to build the role that prevents it.

2. What the Champion Is (and Is Not)

The champion owns adoption. In practice that means a specific set of jobs: build and maintain the firm's setups and prompts, field the questions people are too busy or too proud to send to a vendor, find the next workflow worth winning, and keep the wins visible to the people who fund the effort.

It is just as important to say what the role is not. It is not a second job bolted onto a full plate with no time attached. It is not the most senior person, who has neither the hours nor the proximity to the daily work. It is not the IT lead by default, because the hard part is adoption, a human problem, not integration, a technical one. And it is not a committee. A committee is how firms pretend to assign the role without assigning it, and everyone being responsible is the same as no one being responsible.

The cleanest way to think about it: the champion is the owner from the operating model made real. The broader question of where ownership of AI should sit at the firm is who should own AI at your firm. The champion is how that ownership shows up on the ground.

3. How to Pick One

The instinct is to pick by title or by department. Both are wrong. The right champion is chosen on three traits, and seniority is not one of them.

Respected. When this person says a tool is worth using, people believe them. That credibility is the engine of adoption, and it cannot be granted by an org chart. A second-year analyst the deal team trusts will move adoption further than a partner who is rarely in the work. Genuinely interested. They already play with the tools on their own time. You cannot assign curiosity, and a reluctant champion is worse than none, because the effort inherits their reluctance. Credible on the real work. They know the firm's actual workflows from the inside, so the setups they build fit how the work is really done, not how a diagram says it is done.

Notice what is missing: senior, and technical. The best champion is often a mid-level person on the deal team who is good with the tools and trusted by their peers. Pick for respect, interest, and credibility on the work, and the title will matter far less than you expect.

4. Resourcing and Protecting the Role

The fastest way to kill a champion is to name one and change nothing else. The title without the time is a setup for failure, and it burns the most willing person you have.

Two things have to be real. The first is time, protected and explicit. If the champion is a deal-team member, a slice of their week has to come off the deal clock and be defended when a live process tries to swallow it. Adoption work always loses to a deal unless someone with authority rules that it does not. The second is air cover. The champion will ask people to change how they work, and some of those people outrank them. Without a partner visibly standing behind the effort, the first pushback ends it. The sponsor does not run the program. The sponsor makes it safe for the champion to.

This is the part firms skip, and it is the part that decides the outcome. A champion with a title and no protected time is not a champion. They are a volunteer the firm is quietly setting up to fail.

5. The Champion's First 90 Days

The first ninety days set whether the role builds momentum or stalls. The shape is the same discipline that governs any rollout: narrow, deep, and evidence first.

First month. Pick one workflow, on real work, where errors are cheap and the saving is felt. Build the setup for it, get a small group genuinely using it, and watch where they get stuck. The goal is not breadth. It is one workflow done so well that the people on it would object if you took the tool away. Second month. Measure the win in hours and quality, in language a partner believes, and show it. Then take the proven workflow to the next team or the next adjacent job, spreading by demonstration rather than decree. Third month. Standardize what worked into shared setups so the firm inherits the win instead of rebuilding it, and line up the next workflow.

The mistake to avoid is going broad in week one. A champion who tries to help everyone with everything helps no one with anything. One deep win, made visible, buys the credibility and the air cover to do the next.

6. From One Champion to a Center of Excellence

One champion is the start, not the end state. As adoption spreads, the role grows in a predictable shape, and it helps to see where it leads.

You do not need a center of excellence on day one, and naming one before a single workflow has been won is the same mistake as buying a system before a pilot has paid off. The center is what one good champion grows into, after the wins, not the thing you announce instead of them.

7. The Failure Modes

The role fails in three recognizable ways, and all three are about the setup around the person, not the person.

The wrong person. A champion chosen by title or by department, who is neither trusted on the work nor genuinely interested. The effort inherits their distance from the work, and the setups they build fit a diagram rather than a desk. No time. The most common failure: a real champion with a real plate and no hours carved out. The deal clock wins every week, the adoption work slips, and the most willing person you had quietly burns out. No backing. A champion with no partner behind them. The first time they ask someone senior to change a habit, the pushback ends it, because they have responsibility without the authority to use it.

Read the three together and the lesson is plain. Picking the champion is the easy half. Protecting the role is the half that decides whether it works, and it is the half firms skip.

8. When You Do Not Have One Internally

Sometimes the honest answer is that no one inside the firm fits, or no one can be spared. A small fund with a lean team and a full deal calendar often cannot pull a trusted person off the work for a quarter, and forcing it produces a part-time champion who fails slowly.

In that case the role is filled from outside. A fractional AI lead does exactly what the internal champion would: builds the setups, runs the first workflows, fields the questions, keeps the wins visible. The difference is they start on day one with the experience already in hand, and a good one has a second job built in, which is to grow the internal champion alongside them and hand the role over as the firm's own bench fills in. The aim is not a permanent dependency. It is to borrow the role until you can run it yourself.

That outside-champion role is what an AI Operating Partner is, and the fastest way to find out which workflow the champion should win first is an AI Readiness Sprint.

9. Measuring the Champion's Impact

Judge the champion by adoption, not by activity. How many sessions they ran or messages they answered tells you they were busy, not that the firm changed.

The real measure is whether the workflows the champion touched are genuinely being done the new way now, by the people who own them, without being reminded. The off switch is the honest test: turn the tool off for a workflow the champion drove, and if the team is upset, it stuck. If no one notices, it did not, whatever the activity log says. Track that one workflow at a time, and you will know within a quarter whether the role is working, long before any year-end review.

This is the same yardstick the whole rollout is measured on, laid out in measuring AI adoption, and it is why the champion's other standing job is keeping the firm current as the models change, covered in keeping your team current on AI. Adoption is not a launch. It is a habit, and the champion is who maintains it.

10. Where to Start

Name the champion this week, and pick for respect, interest, and credibility on the work, not for title. If the only honest candidate has no spare hours, that is the real problem to solve first, before any training or tool.

Then protect the role: carve out the time explicitly, put a partner visibly behind it, and point the champion at one workflow to win deeply in the first month. The role lives or dies on the protection, not the appointment.

If no one inside fits, or no one can be spared, borrow the role. An AI Operating Partner runs it from day one and builds your internal champion alongside, and a Guided Launch rolls the firm out one function at a time with the champion built in.