The Short Answer
A Champions network serves as the distribution backbone for organizational adoption. Users naturally turn to their colleagues before opening a support ticket, and they trust peer advice more than executive announcements. This network leverages that dynamic instead of fighting it.
However, a Champion without dedicated time, a defined role, and genuine influence on priorities is an empty title. These three elements determine if the network will last a year or fade away within a quarter.
Who Fits — And Who Doesn't
| Criteria | Why It Matters | Red Flag |
|---|---|---|
| Peer Trust | Determines if they're approached at all | Appointed because they were available |
| Business Process Expertise | Enables correct, not just technical, answers | System knowledge without understanding workflows |
| Genuine Willingness | A voluntary role fosters commitment | Forced appointment by a manager |
| Direct Manager's Support | Determines if there will be time for the role | Verbal agreement only |
A common mistake is choosing the most technical user. They’ll provide precise answers nobody asked for and won’t recognize when the real problem is an illogical process.
Written Role Definition
Without a written definition, the role is interpreted as "the person who's shown problems." The definition includes four responsibilities:
- Local Support — First-line response to team questions and documenting recurring issues.
- Feedback Collection — Conveying roadblocks and needs to the central forum, including things no one is officially reporting.
- Pre-Release Testing — Participating in UAT and testing changes before release to the team.
- Change Communication — Verbally explaining what has changed, using the team's language.
Alongside responsibilities, the time allocation is also defined: four to six hours weekly during the launch period. If the direct manager hasn't approved this allocation in writing, the role will disappear at the first sign of pressure.
The Central Forum is the Core
A bi-weekly 45-minute meeting with a fixed structure: what came from the field, what was fixed from the previous meeting, what's releasing soon, and one open question. The first two items are the engine — a Champion who sees their submitted request implemented and communicated in their name will bring five more requests. A Champion who submitted three requests that disappeared will stop submitting.
The forum also serves as an early warning channel: recurring complaints heard there only reach the Dashboard two months later. The connection to measurement is detailed in Salesforce Adoption Metrics.
What Benefits Are Provided
Incentives that work, in order of proven effectiveness:
- Influence — A standing place in determining priorities for the next release.
- Early Access — Seeing changes before everyone else, and the authority to say "not yet."
- Executive Exposure — Presenting findings to management quarterly.
- Development — Funding for Salesforce certification or conference attendance.
- Recognition — Named acknowledgment in updates for any fix resulting from their input.
Monetary rewards are rare and not essential. What kills networks is a lack of influence, not a lack of bonuses.
The Network's Role in Launch and Routine Operations
In the two weeks following Go Live, Champions are the first line of support in the field, so they receive training a week before everyone else. The structure is described in Salesforce Role-Based Training.
In routine operations, the role changes: onboarding new hires, identifying accumulating friction, and testing changes before release. Here, the network transforms from a launch mechanism into a maintenance mechanism that prevents regression and feeds the fixes discussed in Salesforce UX Simplification.
Signs of Decline and What To Do
| Sign | Common Reason | Fix |
|---|---|---|
| Declining forum attendance | Requests aren't implemented | Release two fixes from their list immediately |
| Champion asks to resign | Workload pressure in primary role | Renew the allocation with the manager |
| No new requests | Network has become just a broadcast channel | Open a discussion on roadblocks, not updates |
| All requests from one team | Partial representation | Add Champions in missing areas |
Measurement
Three metrics suffice: number of issues raised through the network per quarter, their implementation rate, and the adoption gap between teams with an active Champion and those without. This gap is the budgetary justification for the entire program. The network itself is a component within Salesforce Change Management Plan.
Summary
Choose based on trust, not technical knowledge; formalize time allocation in writing with the direct manager; hold a bi-weekly forum where requests are genuinely implemented; and reward with influence. A network that feels it is changing the system will last for years; a symbolic network will disappear in a quarter.