Every deployment needs someone whose job is to keep it working.
By the end of this lesson, you'll be able to define the champion's role, hand over a CLAUDE.md worth inheriting, and set up a health check that tells you whether the deployment is still alive at 90 days.
Role Definition
Being a Claude Code champion is a specific role, not a title
A named champion with a clear job description outlasts an enthusiastic team with no ownership. The difference between a deployment that compounds and one that decays is whether someone is actively responsible for it.
What they do
Active maintenance and growth
Maintains and evolves CLAUDE.md files as the codebase and team practices change. Runs weekly office hours or a standing team channel. Onboards new developers. Escalates adoption blockers that need consultant support.
What they don't do
Be the only expert
The champion is not the team's Claude Code help desk. Their job is to build the team's collective capability, not to field every question personally. If they become the sole knowledge holder, the deployment is fragile.
What they need
Documented handoff and escalation path
A populated CLAUDE.md, a custom command catalogue with at least three to five commands, and a clear line to the consultant for issues that exceed their scope. The handoff conversation happens before Day 30, not on it.
What makes a good candidate
Influence plus intrinsic motivation
Senior enough to influence team norms. Technical enough to write CLAUDE.md and evaluate custom commands. Intrinsically motivated, not assigned. The best candidates identify themselves during Phase 2 by engaging deeply without being asked.
The Investment That Compounds
CLAUDE.md is not documentation. It is institutional memory Claude reads every session.
A team that invests 30 minutes a week in evolving their CLAUDE.md files gets compounding returns. Claude's behavior at the start of every session reflects the quality of what the team has written. A generic CLAUDE.md produces a generic Claude. A well-maintained CLAUDE.md encodes the team's conventions, patterns, preferred tools, and domain context, and every developer on the team benefits from every update another developer makes.
Unlike a Salesforce configuration guide that sits in Confluence until someone needs it, CLAUDE.md is active: it shapes Claude's behavior in real time. The champion's job is to treat it as a living artifact, not a one-time deliverable.
The engagement handoff should always include three components in addition to the champion plan: a CLAUDE.md that covers company conventions at the enterprise level, at least one repo-specific CLAUDE.md for the project the pilot cohort worked on, and a custom command catalogue with at least three to five commands documented with frontmatter, parameter descriptions, and example invocations. These are covered in detail in Courses 4 and 5. If the pilot team hasn't built them, that is the work of Phase 3 and the handoff session.
Handoff principle
The quality of a deployment 90 days after you leave is determined by the quality of the CLAUDE.md you hand over.
Check your understanding
Champion enablement: true or false?
Three statements about champion selection and the role of CLAUDE.md in sustainable deployments.
Activity · True or false? Select an answer for each statement.
"The champion should be the most technically advanced developer on the team."
False. Technical fluency matters, but influence and intrinsic motivation matter more. The most technically advanced developer may have unusual workflows that don't generalize to the team. The champion needs to shape team norms, not just be good at the tool personally.
"CLAUDE.md should be finalized and stable before the engagement ends."
False. CLAUDE.md is a living document that should evolve continuously as the team's codebase, practices, and Claude usage patterns develop. "Finalized" is the wrong framing. The handoff should include a CLAUDE.md that is good enough to produce meaningful improvement immediately, plus a clear owner who will evolve it.
"Custom commands are optional at handoff if the team is small."
False. Custom commands encode the team's best Claude Code practices in a reusable form that survives personnel changes. A small team that doesn't invest in commands in the first 30 days typically doesn't build them later, and they lose one of the highest-leverage configuration tools in the stack. Three to five commands is a low bar and should be non-negotiable at handoff.
Key point: The champion role requires influence and motivation, not just technical skill. CLAUDE.md is a living artifact, not a deliverable. Custom commands at handoff are required infrastructure, not a nice-to-have.
Course artifact · Lesson 5 contribution
Delivery Plan Pack
Delivery Plan Pack: Champion plan section
This lesson contributes the champion plan section, the final component of the Delivery Plan Pack.
1.
Name the champion candidate: role, why they are the right choice (influence, motivation, technical fit). Note if they identified themselves during Phase 2 or were selected.
2.
List the three artifacts you will hand to the champion at engagement close: CLAUDE.md (enterprise and repo-level), custom command catalogue (minimum three commands), escalation path.
3.
Write one sentence describing how you will measure champion effectiveness at the 30-day post-engagement check-in. Name the metric or signal you will use.