Clone Solutions
Template

Champion Charter

A one-page agreement that names each department's Clone Champion and sets their remit, time, support and how success is measured.

What this is for

Adoption does not happen because a tool is available. It happens because someone inside the team shows people how, answers the small questions and brings problems back before they become complaints. The Clone Champion is that person. This charter makes the role real: protected time, a clear remit, a manager who agreed to it, and a way to recognize the work.

When to use it

In the Discover week of each department rollout, as soon as the Champion is named. Review it at the end of the pilot and every quarter after. Power users in the cohort use a shorter version (sections 1, 3 and 5).

Who's involved

  • Champion: one per department, a respected practitioner, not necessarily a manager.
  • Champion's manager: agrees to the time commitment.
  • Business owner: sponsors the role in the department.
  • Change & Enablement Lead: coaches the Champion and runs the Champions council.

How to fill it in

  1. Pick the Champion with the business owner. Look for credibility with peers and curiosity, not seniority.
  2. Fill in the role details and time commitment. Agree the hours with the manager before the conversation with the Champion is final.
  3. Choose the responsibilities that apply. Delete the rest rather than leaving them vague.
  4. Set three to five measures from the list in section 4.
  5. Sign, then add the Champion to the Champions council and the certification track.

The template

1. Role details

FieldEntry
DepartmentFinance & Accounting
ChampionPriya N., Senior AP Specialist
Manager
Business owner
Clones in scopeAP Intake Clone, Month-End Close Clone
Start date
Time commitment4 hours per week in rollout months; 2 hours per week after
Charter review datesEnd of pilot; then quarterly

2. Why this department, why now

Two or three sentences from the business owner on the problems the department's Clones address and what success looks like for the team.

Example: Invoice intake takes our team about 30 hours a week of retyping. We want that time back for vendor relationships and close accuracy. Success is fewer late payments and a faster close, with nobody's job at risk.

3. Responsibilities

  • Complete Champion certification before department launch
  • Join the pilot as the first daily user and log feedback every day of the pilot
  • Answer setup and how-to questions from the team (first line of help)
  • Hold weekly office hours for the first month after launch (30 minutes)
  • Publish proven workflows and prompts to the department's shared library
  • Attend the bi-weekly Champions council and bring the top three issues and wins
  • Nominate a win story or "Clone of the Month" candidate each month
  • Flag anything that looks unsafe, wrong or off-policy to the business owner and InfoSec the same day
  • Give input on autonomy promotion reviews (does the team trust the Clone at the next level?)

4. Measures of success

Pick three to five. Targets are set with the business owner.

MeasureBaselineTargetSource
Weekly active users in department080% of team by day 60Adoption Dashboard
Questions answered within one business dayChampion log
Workflows published to the library5 by day 90Library
Average Power Rating of department ClonesPortal
Override rate on department ClonesAudit log review
Team confidence score (pulse survey, 1–5)Survey

5. Support the Champion gets

  • Certification training and a named coach on the Clone team
  • Early access to new skills and Clones before department rollout
  • A direct channel to the Implementation Engineer for defects
  • Recognition: Champion spotlight, leaderboard, and a note to their manager each quarter
  • Time protected by the manager, recorded here: __ hours per week

6. Boundaries

  • The Champion is not the department's IT support or the Clone's owner. The business owner stays accountable for the Clone's work.
  • The Champion does not approve new connections or autonomy promotions. They give input; InfoSec and the business owner decide.
  • If the time commitment is not being protected, the Champion raises it at the Champions council and the Change Lead takes it to the business owner.

Good looks like

  • The manager signed, and the hours actually appear in the Champion's calendar.
  • Measures are numbers with a source, not "drive adoption".
  • The Champion is a peer the team already asks for help. Assigning the most junior person rarely works.
  • One Champion per live department, every time. Coverage gaps show up as adoption gaps within a month.
  • Common mistake: treating the charter as paperwork after week 1. Review it at end of pilot and quarterly.

How Clone helps

The Enablement Clone drafts the charter from the Department Opportunity Brief, tracks certification progress, and prepares the Champion's monthly summary for the council. The Project Clone tracks charter status per department in the portal, so steering sees Champion coverage across all live departments at a glance.

Sign-off

RoleNameDateDecision
ChampionAccepted
Champion's managerTime approved: ___ hrs/week
Business ownerApproved
Change & Enablement LeadApproved