Revitalizing Community:
Platform Transition
When a talent community outgrew Slack, I was tasked with overseeing the migration to a custom-built, open-source tool integrated into a proprietary platform. This transition enhanced scalability, cut costs by 80%, and laid the groundwork for an expansion to over 100K members.
My Role
I researched vendors and presented findings to leadership, developed a migration strategy for the community team, and ensured a smooth adoption process for users while maintaining engagement levels and user permissions.
A major focus was creating a comms plan executed by the community team, nurturing Community Champions to moderate migrated channels, and providing information through newsletters and webinars.
I managed dynamics with vendors Slack and RocketChat, coordinating with teams to save €48k in rollover costs.
I worked with product teams to integrate the new platform into the company’s ecosystem, ensuring scalability and alignment with business goals.
Launch, impact, results
💰 80% cost reduction
📈 Scalable to 100K+ members
✅ Stronger integration between community & product offerings.
Project context
Initiated by: Community Team (developer talent community)
Organization Type: Global SME, Private Talent Marketplace
Project Duration: 9 months
Project Sponsor: Head of Community, Director of Talent
PM Methodology: Predictive, with flexibility built in to accommodate Product/Engineering involvement
Project Tooling: Asana, SQL, Slack integrations, Zapier, RocketChat
Challenges & Reflection
The migration was initially soft-launched before key dependencies and timelines were fully aligned, creating early friction within the talent community. I focused on stabilising trust by clarifying scope, sequencing communications more deliberately, and aligning closely with Product once it became clear the migration was tied to a broader platform launch outside the Community team’s control.
The extended timeline became an opportunity. I used it to surface assumptions about what this highly skilled tech community actually needed from a new space and chat function, gathering direct feedback and ensuring those insights informed Product and Engineering decisions.
Successful delivery depended not just on feature rollout, but on representing the community’s voice clearly and credibly within cross-functional decision-making.