Coaching, enablement & running a guild
Your success metric is other people's capability.
You scale by making others better, not by doing the work yourself. That means coaching champions, building enablement people actually use, and running a community of practice that compounds knowledge across teams and BUs.
Key ideas
- 1
Teach to scale: coach champions and pair-program rather than taking the keyboard. The win is when teams ship AI features without you in the room.
- 2
Run a community of practice (a guild): a biweekly cross-BU forum to share patterns, demos, problems and decisions. It's your main scaling lever.
- 3
Enablement that sticks: short docs, office hours, templates and runnable examples beat long courses no one finishes.
- 4
Champion model: recruit one enthusiastic engineer per team, give them tools, air-cover and recognition; they multiply your reach.
- 5
Facilitate well: surface dissent, keep it neutral, and drive every session to a documented decision or takeaway.
Coaching over doing
- Ask questions and pair, rather than solving it for them.
- Create a champion onboarding kit so the role is repeatable.
- Recognize champions publicly — recognition sustains volunteers.
Running the guild
- Light, regular cadence (biweekly) with a simple format: demo + pattern + decision.
- Rotate presenters across teams/BUs so knowledge spreads.
- Capture patterns and decisions somewhere durable and searchable.
Watch
Reading checkpoint
Finished the ideas above? Bank the reading progress before applying them.
Do the work
0/4 · 0%Test yourself
What's the strongest sign your enablement is working?
Go deeper
Playbook · 35 min
How to make your project AI-driven
A field guide for real teams with real repos
27 chapters · progress saves automatically