Role: Community Content Coordinator
Duration: 5 Months
Tools: Khoros · G-Suite · Canva · Jira
The Google Cloud Community was relaunched in the summer of 2021 to serve Google users, partners, and employees.
When I joined, the community had 3–4K members, largely inherited from the previous legacy community, with limited engagement and little organization.
The goal was to establish clear structure, consistency, and high-quality content to grow the user base and boost engagement.
What problem existed?
· No clear posting or content strategy
· No structured newsletters
· No consistent visual identity
· Lack of organized event promotion
· No documentation of processes or operational flow
Why it was important:
Without organization or strong communication, the community could not scale, retain users, or deliver value to partners and customers. Community structure was essential for credibility, engagement, and long-term growth.
I owned the content and newsletter workflow, including:
Creating and managing two bi-weekly newsletters: Google Cloud and Google Workspace
Collaborating with engineering to gather platform fixes, releases, and updates
Highlighting upcoming events and activities
Producing high-quality Canva graphics for every newsletter
Building a monthly Leaderboard based on Khoros engagement metrics
Introducing structure and consistency to content cadence
Documenting all processes in Jira (tickets for every action)
Preparing operational procedures and training materials
Transitioning established workflows to an internal Google employee
Research
Audited existing content, legacy user behavior, and Khoros analytics
Identified gaps in posting frequency, structure, and communication
Reviewed platform issues and update patterns with engineering
Planning
Created a bi-weekly content cadence for both newsletters
Designed a consistent visual template in Canva
Developed a structured layout: updates → releases → events → leaderboard
Organized event information and community highlights
Execution
Designed engaging, on-brand newsletter graphics
Gathered platform updates from engineering teams
Summarized releases, fixes, and new features
Calculated user engagement metrics for the Leaderboard
Posted newsletters on a consistent bi-weekly schedule
Ensured all tasks were documented via Jira tickets
Maintained communication across cross-functional teams
Collaboration
Engineering teams · Community leads · Product specialists · Google Cloud & Workspace teams
I created and implemented:
A structured, reliable bi-weekly newsletter system for two product lines
High-quality, visually appealing newsletter graphics
A repeatable content cadence that improved community rhythm
A Khoros-based Leaderboard to highlight active members
Full documentation of all workflows in Jira
Training materials to pass the process to Google employees
A scalable structure that supported long-term growth
✔ Community Growth
User base grew from 3–4K to 15K in just 5 months
Increased visibility and credibility due to consistent content cadence
✔ Engagement Boost
Leaderboard encouraged ongoing participation
Bi-weekly updates kept users informed and returning
Clear structure improved user navigation and trust
Regular updates on platform fixes (based directly on user feedback) built trust and demonstrated strong community listening, showing members their voices were being heard
✔ Operational Improvements
Newsletter production became predictable and efficient
Jira documentation created transparency and accountability
Process handoff ensured long-term sustainability