0-TO-1 BUILD
Microsoft
78% CSAT
A Teams community beta and a Slack community started with no structure, planning, roadmap, issue tracking, or content. Everything had to start from scratch.
I built and launched both in 90 days, using Agile methodology and owning product development strategy and lifecycle, customer success, and support. In the process, I formalized my rapid build and launch approach as the 90-Day Launch framework.
80% onboarding health score, a leading indicator of onboarding success
COMMUNITY GROWTH + ADVOCACY
Chia Network
32% developer community growth in one quarter
Chia hired me to revitalize its developer community. I built an engagement strategy that connected upskilling webinars, developer demos, AMAs, office hours, social media, recognition, and advocacy.
Alongside that growth work, I built Chia’s first Champions program from 0-to-1, recruiting and training members to mentor new contributors, answer questions, and create useful technical content.
The programs gave developers more ways to learn, participate, and contribute while making better use of the expertise already in the community.
32% community growth in one quarter • 90% Champion retention • 2× volunteer pool • 50% faster time to first GitHub PR
TEAM LAUNCH
Techstars
Launched 5 months ahead of schedule and within budget
Techstars needed a gated community for more than 1,000 accelerator alumni, most of them technical founders, and a junior team with no previous community-building experience needed to deliver it while juggling competing priorities.
I led the team from discovery through deployment using my 90-Day Launch framework, designing, testing, and refining the UX, navigation, onboarding, and member experience in sprints. The broader company became beta testers, creating an early feedback loop before launch.
The community launched in six weeks.
1,000 members onboarded • 60% activation • 45% 90-day retention • 76 NPS
TURNAROUND
ForgeRock
2× membership in one year
A once-thriving support community appeared to be languishing. The proposed fix was to bring more employees into the community to answer customer questions and resolve issues before they became support tickets.
Discovery revealed something different: members were comparing approaches, sharing implementation knowledge, exploring products, and learning from one another. It had organically become a community of practice.
I redesigned the experience around the value customers were already creating through peer learning, contribution, knowledge sharing, and member-led programming.
Community-generated content consumption grew from 0% to 40% • 15+ practitioner contributors