The Feature WhatsApp Deliberately Chose Not to Build.

It’s not a missing feature. It’s a deliberate design decision, and the reason behind it teaches us something profound about how great products are built.

The question nobody asks

Think about it for a second. WhatsApp has over 2 billion users. The engineers there are brilliant. They could build threads tomorrow if they wanted to. So why haven’t they?

Meanwhile, Slack and Google Chat have made threads almost a religion. You reply inside a thread. You organize inside a thread. Your whole work life lives inside threads.

Same concept — messaging — two completely different approaches. And both of them are exactly right.

It all starts with who is in the room

Imagine two rooms. In the first room, it’s you and your friends chatting about weekend plans. Conversations jump around. Someone says something funny, someone else responds four messages later. Nobody cares about the “structure.” You just talk.

Now imagine the second room. It’s a cross-functional team of 40 people: logistics, finance, sales, customer support, all in one channel. Someone posts “Client X shipment delayed.” Within seconds, five different people start replying about five different things: invoice, driver, warehouse, customer call, escalation route.

Without threads, that channel becomes a wall of noise in minutes. With threads? Every reply stays attached to its parent. Every decision is traceable. Nothing drowns anything else out.

This is the difference. Not the technology. The people in the room.

“Design is not about what you build. It’s about who you’re building it for and what they actually need to do.”

What happens when you swap the UIs?

Let’s run a thought experiment. What if WhatsApp adopted Slack’s full thread UI?

Suddenly, your mother has to choose between “reply in thread” and “reply in chat.” Your cousin’s group for planning a birthday party now has seven nested threads. Someone accidentally creates a thread for “lol okay” and now everyone is confused about which thread is the “real” conversation. Casual messaging becomes a cognitive chore.

AI can copy the UI. It can’t copy the thinking.

We live in a world where AI can generate a beautiful, pixel-perfect interface in seconds. But here’s what it cannot do: sit across from your user, watch them struggle, and ask, “Wait — why are they even trying to do this?”

AI can reproduce form. It cannot replace the judgment that decides which form belongs.

A designer who only copies UIs is a very skilled tracer. They can reproduce what they see, but they cannot answer the real question: why does this UI exist for these people in this context?

WhatsApp’s simplicity is the ambition. Slack’s threads are the solution. Both came from designers who understood their users at a level deeper than the screen.

“Anyone can redraw the map. The designer’s job is to understand the territory.”

THE LESSON

A great UI is not a visual — it is a decision. Before you place a single component, ask: who is this person, what are they trying to do, and what would genuinely get in their way? The designer who skips that question and goes straight to Figma is not doing design. They are doing decoration. Understand your user first. The right UI will almost design itself.