Built the programming and rituals; the community grew to 13k active members in a year.
See the full storyProof of work
Support was answering the same handful of questions forever, and the answers lived in ticket threads nobody else could find. I turned them into content that scaled — guides, runnable examples, and a search path that reaches people at the moment they are stuck.
Built the programming and rituals; the community grew to 13k active members in a year.
The community was quiet and disconnected, a channel people joined once and then muted. I gave it a reason to show up — regular programming, visible answers to real questions, and enough consistency that turning up became a habit rather than an event.
Delivered 5 talks and the follow-up content; measured adoption of the feature rose after each.
The docs were an afterthought bolted on at the end of every release, owned by whoever had the least to do that week. I made them a product with a real owner, a review step inside the release, and a bar that changes had to clear before they shipped.
Turned the top tickets into guides and examples; repeat questions on those topics fell 40%.
Cut complexity until what's left is obvious — then ship it.
Off the clock
Practical bits
Unlock with a company account to message directly and reveal:
Jump back to the board with this background already filtered in.
