The champion role
The role consists of three behaviors that reinforce one another.
Most of this fits naturally inside the work you are already doing. The difference is a small amount of additional intention about where your discoveries are posted and how your answers travel.
What this should cost you
Set expectations with yourself and with your lead. The activities below are intended to fit inside a normal working week, and the role should remain a multiplier on your existing work rather than an additional support responsibility.Share what you discover
Your own experience is the most persuasive material your colleagues will encounter, because it is specific to the codebase, workflows, and problems you all share. Documentation tells people what is possible; your posts show them what is actually working in your environment.What is worth sharing
The most useful posts describe a technique a colleague can reuse tomorrow rather than an outcome that is already complete. Techniques compound as they spread through a team; status updates do not. Examples of reusable techniques:- “I learned that @-mentioning a directory works. Pointing it at
@src/components/and asking which were missing tests surfaced two I had overlooked.” - “Plan mode (
Shift+Tab) shows exactly which files will be touched before any edit is made, which is why I am comfortable using it on shared code.” - “I configured a Stop hook so I receive a desktop notification when a long task completes. Configuration is in the thread.”
- “Running
/initgenerates aCLAUDE.mdfrom the repository so the assistant stops re-asking about our conventions.”
Where to share it
Post wherever your team already reads. The goal is to place examples in the path of normal work rather than to create a destination.The format that works
A screenshot accompanied by a single line of context, or a brief before-and-after description, is generally the right level of detail. Keep each post short enough that someone scrolling past still absorbs the point. A long write-up tends to be saved for later and forgotten, whereas a short post with a screenshot tends to be copied and tried. The example posts below illustrate tone and length; adapt them rather than copying verbatim.Be the person people ask
Once you have shared a few examples, questions will follow. This is where the champion role has the greatest leverage, because a good answer to one person frequently unblocks several others who are watching the same channel.Answer with a prompt rather than an explanation
When a colleague asks how you accomplished something, the most useful response is the prompt you actually used. They will learn more from running that prompt against their own problem than from any description you could write, and it gives them something they can act on immediately.Point at the feature rather than the documentation
A response such as “Try plan mode, pressShift+Tab until you see it” is more useful in the moment than a link to the documentation. If the person needs more depth later they will find it on their own; right now they need the single thing that unblocks them.
Questions you are likely to hear
Grow the circle
The objective is not to build a program or to own a rollout. It is to establish a small number of lightweight habits that allow momentum to continue after you have stopped actively driving it. When questions in the channel are being answered by people other than you, the role has done its job.Patterns that tend to work
Thirty-day playbook
If a loose plan is helpful, the sequence below reflects what tends to work across most teams. Adjust freely to fit your context.1
Week 1: Seed the channel
Create the channel, pin the Quickstart, and post two or three of your own examples with the prompts included.Signal that it is working: a few colleagues react or reply, and at least one question is asked in the channel.
2
Week 2: Start the rhythm
Start the weekly show-and-tell thread, answer every question publicly, and share one custom skill or
CLAUDE.md snippet.Signal that it is working: someone other than you posts an example of their own.3
Week 3: Pair and consolidate
Offer two or three short pairing sessions and consolidate the most common questions and answers into a pinned FAQ message.Signal that it is working: you see repeat usage, with the same colleagues returning rather than trying once and stopping.
4
Week 4: Hand off
Identify a second champion and share a brief summary of what is working and what is not with your lead or administrator.Signal that it is working: questions in the channel are being answered by people other than you.