The director of pharmacy for a fourteen-site retail chain had done everything right at the flagship store. She had earned the staff's trust, built real demonstrated competency, and the prior-authorization workflow, abbreviated PA throughout this program for prior authorization, was running fast and clean, with the verification discipline holding. Then she tried to copy that success to the other thirteen sites by sending each one the same training deck and the same policy memo she had used at the flagship, and within two months she had thirteen different outcomes, most of them bad. Two sites were quietly not using the tool at all. Four were using it but rubber-stamping the output, the exact failure the flagship had avoided. Several had invented their own undocumented workarounds. The director was baffled, because the flagship proved the program worked, and she had shipped the same materials everywhere. What she had missed is the central truth of scaling a pharmacy AI program across sites: a program does not spread through documents, it spreads through people, and the people who carry it are champions, peer leaders embedded at each site who make the safe practice real where the work actually happens. This lesson is about building that coalition of champions, why it is the only mechanism that scales a verification-first culture across sites, and how a strategist cultivates it deliberately rather than hoping a policy memo will do the work that only a person can do.

Why Documents Do Not Scale a Culture

The director's mistake was assuming that what worked at the flagship was the materials, when what actually worked was her: her presence, her credibility, her daily reinforcement of the verification-first culture, her visible celebration of catches, her honest answers when staff hit the tool's limits. None of that was in the training deck. The deck and the memo were the visible artifacts of a culture that lived in a thousand small human interactions she had at the flagship every day, and when she shipped only the artifacts to the other sites, she shipped the shadow of the culture without its substance. This is the first thing a strategist scaling across sites must understand: a verification-first culture is not information that can be transmitted in a document; it is a set of habits, norms, and trusted relationships that exist only where someone embodies and reinforces them, which means scaling the culture requires putting a someone at each site, not a document.

The reason this matters so acutely in pharmacy is the same reason the whole program holds the safety bar so high: the failure modes are silent and the stakes are a patient. A site that receives a policy memo but has no one embodying the verification discipline will drift toward the path of least resistance, which under the gravity of a busy day and a tool that is right often enough means rubber-stamping the output. Nobody at that site is doing anything obviously wrong; they are following the workflow, hitting their numbers, processing the PAs. The drift is invisible until the day a fabricated criterion reaches a payer or a wrong dose reaches a patient, and by then the culture that would have caught it never existed at that site, because a memo cannot embody a culture and there was no person there to do it. The director's four rubber-stamping sites were not staffed by careless people; they were staffed by people who never had what the flagship had, which was not a document but her, and the absence of a person to carry the culture is exactly the gap a champion fills.

A pharmacy AI program does not spread through documents; it spreads through people. A verification-first culture lives only where someone embodies and reinforces it, which means scaling it across sites requires a champion at each site, not a better memo.

What an AI Champion Is, and Is Not

An AI champion is a peer leader embedded at a site who carries the verification-first culture into the daily work of that site, and each part of that definition matters. They are a peer, which means they are a working pharmacist or technician at the site, not a corporate trainer who flies in and leaves, because the credibility that carries a culture comes from being one of the staff, doing the same work, facing the same pressures, and being trusted as someone who genuinely understands the job rather than someone imposing a program from outside. They are a leader, which means they have the informal authority and the willingness to set the norm at their site, to be the person who visibly verifies, who celebrates a colleague's catch, who answers the question when someone hits the tool's limit. And they carry the culture, which means their job is not primarily technical but cultural: to make the safe practice the normal practice at their site, in the thousand small interactions a remote director cannot have.

It is equally important to understand what a champion is not. A champion is not necessarily the most technically sophisticated person at the site, and choosing champions purely for technical skill is a common error. The competence that makes a champion is the verification-first discipline combined with the peer credibility and the willingness to set the norm, which is a different and partly social competence. A brilliant technician whom colleagues do not trust or respect makes a poor champion; a solid, well-respected pharmacist who embodies the verification discipline and whom colleagues naturally turn to makes an excellent one, even if their raw technical skill is not the highest at the site. A champion is also not a deputy enforcer or a snitch; framing the role that way poisons the peer credibility that makes it work. The champion sets the norm by embodying it and helping colleagues, not by policing them and reporting them, and a strategist who turns champions into enforcers destroys the very mechanism they were trying to build, because a peer who has become an informer is no longer a trusted peer.

How to Identify and Develop Champions

Identifying champions well is a matter of looking for the right combination of traits rather than the single trait of technical skill. The strategist looks for the professional at each site who already embodies the verification discipline, who is naturally careful and skeptical of confident output, who is respected by their peers and whom colleagues already turn to with questions, and who has some appetite for the role rather than being conscripted into it unwillingly. These people often already exist at each site, informally; the pharmacist everyone asks about a tricky interaction, the technician who is known for catching the errors others miss. The strategist's job is often less to create a champion from scratch than to recognize the person already playing that role informally and to formalize, support, and equip them.

Developing champions means investing in them beyond the general staff training, giving them deeper competency, more context about the program's goals and the reasoning behind the verification discipline, and the standing to act as the site's reference point. It means connecting them to each other across sites, so that the champions form a network that shares what is working, surfaces problems, and reinforces each other, which is itself a powerful mechanism because a champion who feels alone at their site is fragile, while a champion who is part of a coalition of peers facing the same challenges is resilient and continually re-energized. It also means giving them air cover from leadership: the explicit backing that lets a champion spend the time the role requires and that signals to the rest of the site that the champion's norm-setting carries the organization's support. A champion without that backing is asked to set a norm with no authority to do so, which is an unfair and usually failing position. The strategist who identifies the right people and then genuinely develops and supports them builds a coalition; the strategist who anoints champions in name only, without the investment, builds nothing but a new title.

Champions as the Scaling Mechanism

The reason champions are the answer to the multi-site scaling problem is that they solve the exact thing documents cannot: they put a person who embodies the culture at each site, which is the only thing that actually makes the culture real where the work happens. The director with fourteen sites cannot be present at thirteen of them; she can be present at one. But fourteen champions, one at each site, developed and supported and connected to each other and to her, can carry the verification-first culture into all fourteen sites simultaneously, each in the specific texture of their own site, which a centralized program never could. The coalition of champions is the mechanism that turns a single successful flagship into a network of successful sites, because it replicates the thing that actually made the flagship work, a present person embodying the culture, rather than merely replicating the artifacts that were only ever the surface of it.

This also makes the program durable in a way a director-dependent program never is. A culture that lives only in the director is fragile: it depends on her continued presence and attention, and it does not survive her moving on or being pulled to other priorities. A culture carried by a coalition of champions distributed across the sites is resilient, because it is embedded in many people and many sites rather than concentrated in one, and it continues to function and even to spread as champions develop new champions and as the norm becomes self-sustaining at each site. The strategist who builds a coalition is not just solving the immediate scaling problem; they are building the distributed, durable cultural infrastructure that lets a verification-first practice survive and grow beyond any individual, which is what it means to genuinely embed AI safely in an organization rather than to run a program that depends on one person's heroics. The coalition is how the culture stops being something the director does and becomes something the organization is.

The Coalition as Feedback and Early Warning

A coalition of champions is not only a mechanism for spreading the culture outward; it is also a mechanism for sensing what is happening across the sites and catching problems early, which is a benefit a strategist should deliberately harness. Because the champions are embedded in the daily work at each site and connected to each other and to leadership, they form a network that surfaces the tool's emerging failure modes, the workflow friction points, the places where the verification discipline is straining under pressure, far faster and more honestly than any top-down reporting ever would. A champion who notices the tool starting to fabricate a new kind of criterion, or who sees colleagues beginning to drift toward rubber-stamping under a staffing crunch, can raise it through the coalition before it becomes a patient-safety event, which makes the coalition an early-warning system as valuable as it is a culture-spreading one.

This feedback function is also what keeps the program honest and improving rather than ossifying around the original flagship design. The flagship's workflow was right for the flagship; the other sites have different volumes, different payer mixes, different staffing, and the champions are the ones who can tell the strategist what is actually working and what needs to adapt, which prevents the program from rigidly imposing a template that fits one site onto thirteen that differ. A strategist who listens to the coalition learns continuously about how the program is really functioning across the network, and a strategist who builds the coalition as a genuine two-way relationship, where champions both carry the culture outward and carry intelligence back, has built something far more powerful than a distribution channel for policy memos. The coalition becomes the nervous system of the multi-site program, sensing and adapting and spreading at once, which is exactly the living infrastructure a verification-first culture needs to stay safe as it scales.

Building the Coalition Is the Strategist's Highest Leverage

The lesson of the fourteen-site director is that scaling a pharmacy AI program is not a distribution problem to be solved by shipping better materials but a human-coalition problem to be solved by building champions, and a strategist who internalizes that difference has the key to taking a single success across an organization safely. The director who shipped a deck to thirteen sites got thirteen drifts; the director who develops, supports, and connects a champion at each site gets a network of sites where the verification-first culture is genuinely real because a trusted person embodies it where the work happens. Building that coalition is the strategist's highest-leverage move at the multi-site scale, because it is the only move that actually replicates what makes a site succeed rather than replicating the surface artifacts that succeed at nothing on their own.

Carry forward the image of the four sites that were rubber-stamping the output, staffed not by careless people but by people who never had what the flagship had. The director's instinct was to send them a better memo; the right move was to give them what the flagship actually had, which was a present person embodying the culture, a champion. A strategist who sees that clearly stops trying to scale a culture through documents and starts building the coalition of peer leaders that is the only thing that scales it, and in doing so builds a program that is not only broader but more durable, more self-improving, and more genuinely safe than any centralized effort could be. This completes the change-management arc of this chapter: trust is the gate, training builds the competence, and champions spread both across the organization and keep them alive. The strategist who has earned the trust, built the demonstrated competency, and cultivated the coalition of champions has done the real work of pharmacy AI change management, which is not installing a tool but building the human system that uses it safely, everywhere it runs.

Key Takeaways

• A pharmacy AI program does not spread through documents; it spreads through people. What made a flagship site succeed was not the training deck but the present person embodying the verification-first culture in a thousand small daily interactions a memo cannot transmit.
• A site that receives a policy memo but has no one embodying the verification discipline drifts toward the path of least resistance, which under a busy day and a mostly-right tool means rubber-stamping; the drift is invisible until a fabricated criterion or wrong dose reaches a payer or patient.
• An AI champion is a peer (a working pharmacist or technician at the site, credible because they do the same work), a leader (with informal authority and willingness to set the norm), who carries the culture by making safe practice the normal practice locally.
• A champion is not necessarily the most technically sophisticated person; the right competence is the verification discipline plus peer credibility plus willingness to set the norm, and a champion must never be turned into an enforcer or snitch, which poisons the peer credibility that makes the role work.
• Identify champions by recognizing who already plays the role informally, the person colleagues turn to, who embodies the discipline and is respected; the job is usually to formalize and equip an existing informal leader, not to create one from scratch.
• Develop champions with deeper competency and context, connection to each other across sites so they form a resilient network rather than isolated individuals, and explicit leadership air cover so their norm-setting carries organizational support; anointing champions in name only without investment builds nothing.
• Champions are the scaling mechanism because they put a culture-embodying person at every site at once, replicating what actually made the flagship work; they also make the program durable, surviving and spreading beyond any individual rather than depending on one director's presence.
• The coalition is also a two-way feedback and early-warning system: embedded, connected champions surface emerging failure modes and drift faster and more honestly than top-down reporting, and they tell the strategist what must adapt so the program improves instead of rigidly imposing one site's template on all.
• Building the coalition is the strategist's highest-leverage move at multi-site scale and completes the change-management arc: trust is the gate, training builds competence, and champions spread and sustain both, turning a verification-first culture from something the director does into something the organization is.