Community Overview
I co-lead Microsoft's 250+ member Content Design Community. A group that size doesn't hold together on good intentions and a distribution list — it holds together on programming people actually want to show up for.
That's the part I own. Our learning programming is how 250+ designers keep learning together while the ground keeps moving underneath all of us, and it's built from three pieces that do different jobs.
The Alignment Challenge
Microsoft content designers support everything from Office to AI. That's a lot of ground to cover, and AI is not exactly holding still while we cover it. Keeping up means constantly learning, rethinking strategy, and applying new skills in real time.
A community this size has a second problem on top of that one: people quietly solving the same problem in six different orgs and never finding out about each other. Good work gets done twice and learned from once.
And here's the part that kept tripping everyone up. The gap was never understanding AI — plenty of smart talks and docs had that covered. The gap was the distance between "okay, I get it" and "I can actually do this, on my project, this week." That's a much shorter sentence and a much harder problem, and no amount of slides was going to close it.
How I Built the Network
Three strands, each aimed at a different failure mode:
Learning Jams
Hands-on working sessions where people bring real projects. This is where "I understand" turns into "I shipped it."
Demos & works in progress
A standing forum to show what you're building before it's finished — so the six people solving your problem find each other early.
Speakers, in and out
Programming that brings in voices from inside Microsoft and well outside it, so the community isn't only talking to itself.
Inside the Content Engineering Learning Jams
The Jams are the flagship, and the most structured of the three. As our org started treating content engineering as a real part of the practice, the way we learned together had to change too. Four goals, and every session gets measured against them:
Shared practice
One content engineering practice across the org, not a dozen local dialects.
Reliable cadence
Learning you can count on showing up, not a one-off that never repeats.
On-demand help
Resources and support that are there when you hit the wall, not a quarter later.
Reusable patterns
Standardized patterns anyone can pick up and run with.
The whole point is to give content designers the skills, fluency, and resources to shape AI products with confidence. Since nobody starts in the same place, the Jams run at three fluency levels and meet designers where they already are:
-
LVL
1 Start here For anyone who wants in. You don't need to be an expert to participate, because the structure does that work for you. -
LVL
2 Keep up as the discipline moves Support and equip designers with the latest skills as content engineering keeps evolving underneath everyone. -
LVL
3 Lead the thinking Advanced designers stop being attendees and start being thought leaders, sharing their own ideas, concepts, and approaches.
Why a Jam isn't just another learning series
- It goes after the gap between "I understand" and "I can actually do this on my current project" — which is where most learning series quietly give up.
- No heavy prep. Show up, open your laptop, and bring whatever you're actually working on.
- The structure is provided, so you don't have to be an expert to get something out of it.
Community Signals
The programming is designed so the evidence shows up in people's actual work rather than in a post-session survey: patterns getting reused across orgs, designers shipping AI work they'd have punted on a quarter earlier, work-in-progress demos turning into collaborations, and the advanced folks turning into the ones running sessions.