Governance & Enablement · Field note 005
Building an AI community of practice
Employees rarely adopt a new capability just because it exists. Adoption happens when knowledge moves through relationships people already trust — which makes the community, not the tool catalog, the real adoption engine.
The learning network organizations skip
Most organizations underestimate how much of real adoption runs through informal learning networks rather than official channels. A Community of Practice gives that informal exchange a place to happen on purpose — people trading prompts, templates, lessons learned, and cautionary tales instead of rediscovering the same mistakes independently.
Formats that outperform training decks
Office hours
Low-stakes, recurring time to bring a real problem instead of a hypothetical one.
Demonstrations
Members showing what actually worked, including the parts that didn't at first.
Peer mentoring
Adoption spreads faster through a trusted colleague than through a training module.
Communities work best anchored to practical outcomes. Members sharing real examples beats a slide deck of theoretical possibilities almost every time.
Office hours reveal real blockers
A recurring office hours slot does something training decks can't: it surfaces what people are actually stuck on, instead of what the program assumes they need. That feedback is worth more than another round of enablement content, because it can directly shape training, documentation, platform improvements, and governance guidance that people will actually run into.
Training teaches concepts. Enablement helps someone apply a concept to the work already on their desk. The strongest communities lean toward enablement — demos, prompt libraries, templates, working sessions, and lightweight coaching grounded in real tasks rather than generic tool tours.
Community as a sensor network
- Community of practice
- Office hours + demos + pattern library
- Center of excellence
- Guidance, templates, training
The compounding benefit
Communities improve the platform, not just adoption
The long-term value isn't only faster adoption. A healthy community becomes a feedback loop — the fastest signal an organization has for where governance is too slow, where architecture is missing a pattern, and where the platform roadmap should actually point next.
Questions worth asking
- What topics actually generate engagement, versus what leadership assumes people want to hear about?
- How does the community's feedback reach the people who own governance and platform strategy?
- Who are the natural champions already doing this informally, and how do you support them without formalizing the life out of it?