Skip to content
Case study

WhatsApp: designing for the groups inside your groups

A product-design exercise run through the CIRCLES method.

Designs a tightly-scoped feature for close-tie communication — and, more importantly, says no to the obvious 'add a feed' answer that would break what WhatsApp is.

Role
Product teardown — feature design
Timeline
Design exercise
Year
2025
Domain
Messaging · Product design
CIRCLES methodPersona designPrioritization (RICE)

The prompt

Improve connection on WhatsApp — without making it Instagram.

The trap in this question is the broadcast answer: add Stories, add a feed, add discovery. WhatsApp's value is that it's the opposite of a feed — it's the small, trusted, close-tie graph. Any 'engagement' feature that imports public-social mechanics is a strategic mistake dressed as growth.

I run it through CIRCLES — Comprehend, Identify the user, Report needs, Cut through prioritization, List solutions, Evaluate tradeoffs, Summarize — because the structure forces the no before the yes.

Comprehend & Identify

Who, and which job

  • Comprehend: WhatsApp wins on ubiquity and trust, not on time-spent. The right goal is depth of connection, not minutes.
  • User I'd serve: the person whose closest relationships live in a few specific group chats — family, three best friends, a partner — that are noisy and lossy.
  • The unmet need: the important moments in those small groups get buried under logistics and forwards. There's signal, but no way to hold onto it.

List & Cut

The feature, and the ones I rejected

  • Shipped idea — 'Moments' inside a chosen close group: a lightweight, opt-in shared space where a small group's photos and milestones are kept, separate from the message stream. Private by construction, no audience, no metrics.
  • Rejected — a public Stories feed: imports vanity mechanics and the comparison loop WhatsApp is valuable for *not* having.
  • Rejected — algorithmic discovery of people: violates the trust model; the close graph is the product.

Tradeoffs

Evaluate

Chose

Scope to existing close groups only

over A network-wide social surface

Keeping it inside groups you already chose preserves the trust that makes WhatsApp WhatsApp. Growth that erodes the core asset isn't growth.

Chose

No likes, no view counts, no reach

over Engagement-maximizing social mechanics

The moment you add an audience and a number, you've built the comparison machine people came here to escape. The absence is the feature.

Summarize

The recommendation in one line

Deepen the close-tie graph WhatsApp already owns; refuse every feature that turns a private message into a public broadcast. The strongest answer to 'add engagement' here is a disciplined, scoped no.

Next · case study

Flipkart: the return that costs twice

Reducing return rate without quietly making returns harder.

Continue