How to structure a change management model for a large organization

A change management structure for an organization of seven thousand people should include a core team of two to four people setting strategy, plus a distributed change network of roughly one champion for every fifty to one hundred employees, weighted toward the divisions facing the most disruption. Prosci's benchmarking research, gathered from more than a decade of studies across thousands of organizations, found that projects with excellent change management effectiveness were six times more likely to meet or exceed their objectives than those with poor change management. Getting the network's size and composition right matters more than almost any other early decision.

This is exactly the question showing up in change management communities right now. A team of two, tasked with rolling out a new scheduling system across an entire organization for the first time, is trying to figure out how many champions to recruit, how to represent every role and division without the network becoming unmanageable, and how to build something that can be reused for the next change initiative and the one after that. The questions are good ones, and they have concrete answers.

How many people should be on a change network?

There is no universal headcount, but there is a useful ratio. Most established change practices recommend one champion for every fifty to one hundred employees in the affected population, adjusted based on how disruptive the change is and how geographically or functionally spread out the workforce is. For an organization of seven thousand people, that lands somewhere between seventy and one hundred forty champions. That sounds like a lot until it is compared to the alternative: two people trying to field questions, objections, and edge cases from seven thousand individuals with no intermediaries.

The ratio is a starting point rather than a formula to follow blindly. A finance department rolling out a scheduling change that barely touches their workflow needs far less coverage than a frontline operations team where the new system changes how every shift gets built. Weight the network toward the divisions where the change bites hardest, and thin it out where the change is background noise.

Why two people cannot run change management for thousands alone

McKinsey's research on organizational transformations is widely cited for a reason: roughly seventy percent of change initiatives fail to fully achieve their stated goals, and a lack of employee engagement and management support are consistently named among the top reasons why. A two-person team, no matter how skilled, cannot personally engage seven thousand people. The champion network exists to solve exactly this bottleneck. Champions do more than pass information downward. They are the organization's early warning system, surfacing the niche concerns, workflow quirks, and local resistance that a central team sitting outside those departments would never see coming.

The core team's real job is building the structure, training the champions, and creating a feedback loop that gets information back up the chain fast enough to act on. Prosci's ADKAR model, one of the most widely used change frameworks, breaks individual change into five stages: awareness, desire, knowledge, ability, and reinforcement. A champion network's most valuable function is diagnosing where each part of the organization is stuck in that sequence. A department that is aware of the change but has no desire to adopt it needs a very different intervention than one that wants to adopt it but lacks the knowledge to do so.

Building a network that surfaces real concerns

A network only surfaces niche concerns if champions actually trust each other and trust the central team enough to say the uncomfortable thing out loud. This is where most formal change management rollouts quietly fail. Organizations recruit champions, hand them a slide deck and a schedule of monthly check-ins, and then wonder why the feedback that comes back is polished and generic instead of specific and useful.

The fix is structural, not motivational. Champions need four things.

A clear mandate that names exactly what they are responsible for surfacing, rather than a vague instruction to be a point of contact.

A reporting rhythm frequent enough to catch problems early, typically every two weeks during an active rollout rather than monthly.

A direct line to the core team that does not route through their own department's management chain, so concerns about leadership decisions can actually get voiced.

Enough psychological safety within the network itself that a champion from a small division is as willing to speak up as a champion from a large one.

That last point is the one most structures overlook, and it is where the hierarchy problem creeps back in even inside a network designed to flatten it. A champion network built entirely through org charts and email introductions tends to reproduce the same power dynamics as the organization it is meant to serve. People frequently ask how to avoid this, and the honest answer is that champions need a shared experience that puts them on equal footing before they are asked to work as equals.

This is a problem Morrison Alley has spent twenty-five years designing for. When teams are placed inside an unfamiliar, high-stakes scenario together, hierarchy loosens on its own, and the person who never speaks up in a meeting is often the one who solves the problem in the room. A change network built through that kind of shared, immersive experience arrives at its first real rollout already knowing how to work as one unit, rather than as a hundred individuals who happened to attend the same training session.

The research behind formal change management structures

Prosci's studies, drawn from over a decade of practitioner surveys, consistently show that active and visible executive sponsorship is the single largest contributor to change management success, ranked above every other single factor including strong project management. A champion network without visible executive backing tends to be treated as optional by the very departments it is trying to reach. For a first-time formal rollout, this means the two-person core team's first job is securing a specific, named executive sponsor who will show up, in person or on video, at the first champion kickoff and at key milestones, before the network itself gets built.

Kotter's eight-step change model, developed from research on dozens of corporate transformations, similarly places forming a powerful coalition as the second step, right after establishing urgency. The lesson from both bodies of research is the same. The network's authority has to be granted from above and demonstrated visibly, not assumed because a list of names exists on a slide.

A champion network without visible executive backing tends to be treated as optional by the very departments it is trying to reach.

Scaling the model beyond the first project

A structure built only to survive one scheduling rollout will not scale. To build something reusable, the core team should separate the network's people from the network's process. The people recruited as champions for the scheduling project may rotate out once it stabilizes. The process, meaning the reporting cadence, the escalation path, the training curriculum, and the feedback templates, should be documented as a standing capability the organization can reactivate for the next initiative without starting from zero.

This is also the moment to decide whether champions are a standing role or a rotating one. Standing champions build deep institutional memory but risk becoming a permanent layer of bureaucracy. Rotating champions keep the network fresh and spread the skill of change leadership more widely across the organization, which tends to matter more for a company running its first formal change initiative and hoping to make change competency a broader organizational muscle rather than a specialty owned by two people.

Where experiential learning fits into change management

Documents, training decks, and reporting templates handle the mechanics of a change network. They do not build the trust that makes the mechanics work. A champion network is, structurally, a brand-new cross-functional team, often the first time these particular hundred people have ever been asked to collaborate at all. Traditional training rarely gets that team functioning quickly, because it fails to engage adults the way they actually learn: through action, reflection, and immediate real-world application.

Morrison Alley builds that team cohesion through custom, hands-on experiences rather than another session in a conference room. When a newly formed change network is placed inside a scenario that mirrors the complexity of the rollout they are about to lead, something shifts. Contributions start coming from unexpected places. The person from a small regional office starts driving the conversation as readily as the person from corporate headquarters, because the scenario does not care about org charts. That shift, built once inside a shared experience, is what champions carry back into the check-ins and the hard conversations with their own departments.

Getting started: a practical structure

For a two-person team starting from zero, the sequence that tends to work is this. Secure a named executive sponsor first. Size the champion network using the ratio of one champion per fifty to one hundred employees, weighted by disruption level. Recruit champions with a clear written mandate rather than an informal ask. Build the network's first real trust through a shared experience rather than a shared inbox. Then document the process separately from the people involved, so the structure survives past this first rollout.

A formal change management model, done well, becomes an organizational asset that outlasts any single project. The scheduling system will eventually be old news. The network of people who learned how to surface problems early, speak up across hierarchy, and work as one unit under pressure does not have to disappear with it.

The research on experiential learning and team performance referenced here is set out in full, with sources, on our Why It Works page.

← All field notes