Product · 2017 — 2019
Zalo Group Messaging — Connectivity for families, coworkers, and large communities
- Role
- Product Manager, Zalo
- Year
- 2017 — 2019
- Team
- Designers, mobile + server engineers, QC, research, data
- Timeframe
- ~2 years, many parallel scopes
Summary
Release after release across expression, moderation, and coordination, so that a five-person family chat and a community sitting at Zalo's 1,000-member ceiling both worked on the same surface.
Problem
One surface had to carry very different intents: families wanted warmth and play, workplaces wanted clarity and accountability, and large communities needed admins who could keep the signal clean without reading every message. All of it shipped alongside everything else the messaging app was doing.
Approach
Run three tracks at once — express, moderate, coordinate — with a small core of designers, client and server engineers, QC and data, most of whom spanned more than one track. Ship small, watch the metrics and the support tickets, iterate the next sprint. Keep the heavy admin controls one tap deep, where the people who need them can find them and everyone else never meets them.
Outcomes
Express
Reactions & richer replies
Moderate
Admin tools, approvals, permissions
Coordinate
Mentions, polls, reminders, smarter notifications
Process
- 01
Express
Reactions and lighter-weight responses so groups could acknowledge without adding noise — designed with the messaging design team, tuned with data.
- 02
Moderate
Admin tools, member approval, and granular group permissions, built tightly with server and QC so large rooms behaved predictably under load.
- 03
Coordinate
Mentions, polls, reminders, and a notification model tuned to importance, reworked over several releases against engagement data and interviews.
"Every win came from a default that took work off the group — one fewer obligation to keep up with, one fewer call an admin had to make by hand. The same small group of teammates carried that context across dozens of small bets."