Member Tags
Member tags lets group members add a label to their profile to give other members more context on who they are or their role in the group. It helps spark group activation when users are more familiar and connected to one another.
Problem
When first being added, group members don’t have enough context about each other to recognize or relate — especially in medium and large groups where people aren't connected IRL. They lack a group identity that invites other users to reach out, connect or ask questions.
Solution
Users can set a short, optional "member tag" per group (e.g. "Zara's Mom," "Grade 1 Teacher,") that appears alongside their name in message bubbles and the member list — visible to all group members, editable anytime, and automatically shared with new joiners.
Impact
Exceeded adoption goals:
+0.12% US group sends/DAU
+0.09% global group sends/DAU
0.4–0.7% of user-group pairs add a member label within the first 2 months of launch
My role
Naming
Product framing
Entry point strategy
Awareness, education
e2e content
UXR strategy
Privacy, integrity alignment
GTM language, positioning
How my strategy shaped the feature and achieved product goals
Framing through content strategy
Challenges/constraints
The group space has many competing ‘titles’ for a member; push name, About, and username. Getting the framing right was critical to distinction, comprehension, and adoption.
Content was the only way to show the users what the feature is, how to use it, and why it matters.
UXR
I partnered heavily with UXR to understand not just user need and how they wanted to use the feature, but how they were already thinking about it. This research-grounded approach — mapping users' existing mental models around identity, group membership, context-sharing and barriers to conversation — directly informed the content framework: the name, the ghost text, the main copy, and the education flow. Rather than imposing a top-down framing, I used UXR insights to close the gap between how users naturally understood the feature and how we needed them to understand it to meet product goals.
Strategy
I crafted the content positioning to draw clear, intentional distinction. Member tags are group-specific context, not a nickname, not a global identity — a distinction that required precise, consistent language with an instructional tone across every surface. It guided users toward the intended use case (group-specific context, not a nickname) while actively preventing misuse. Every surface — ghost text, main copy, onboarding prompts — was designed to reduce the learning curve and accelerate time-to-value.
Transparency was also key. Knowing user sensitivity around privacy, it needed to be very clear where and how a member tag would appear. I included a preview, linked a Help Center Article, and had explicit language in the flow to ensure transparency.
Naming
Name-storm → iteration/crit →XFN alignment→ content review → UXR → leadership review
What was NOT chosen and why
Member label: ecosystem inconsistency. “label'“ was used in an organization feature on WhatsApp Business Messaging.
Headline, Tagline: Implies a username or alias — suggests replacing identity rather than adding context.
Bio: Signals long-form, permanent, global self-description
Name tag: Too easily conflated with your actual name / pushname. The word "name" pulls users toward identity, not context — exactly the misuse we were trying to prevent.
Member role: Implies admin-assigned, structural roles. Too narrow and hierarchical.
I designed a UXR plan to test the primary options.
GTM
I partnered closely with PMM on getting the language right - I shaped the language that appeared in WhatsApp's public blog post and socials and ensured it reflected deliberate content decisions made in UI.
I made direct changes to not include competing language that we use for About, continuing the distinction on through external channels.
Entry point
This was make it or break it for a new feature. I strongly advocated for contextual, in-the-moment entry points over a broadcast system message — prioritizing education at the right moment rather than noise.
I worked closely with PD and XFN to align on surfaces that would drive adoption without cluttering the experience, and battling Eng constraints and ecosystem compatibility.
The final entry points — member list and post-join FMX card — directly served the product goal of faster group onboarding by meeting users at the two highest-intent moments: joining a group and exploring who's in it. This contributed to exceeding adoption benchmarks and the feature's impact on group sends/DAU.