Slack spent two years and six iterations getting Threads right

Threads sit so close to the heart of Slack that head of design Joshua Goldenberg called them 'an escalated case' — too core to the product to get wrong.

Around six significant iterations of the prototype over nearly two years of unhurried exploration, tested internally while being polished for public consumption, then shipped to every team at once — paying customers and free users alike.

Threaded conversations shipped to all Slack teams as Threads; during the two-year process Slack's usage grew eightfold to 4 million daily active users.

Threaded conversations sound mundane — bundling a message and its replies in one place has existed since dial-up bulletin boards, and shows up in Facebook, Twitter and Gmail. But when Slack's users started asking for the capability, the company concluded it wasn't something it 'could whip up in a jiffy'. What followed was nearly two years of unhurried exploration and around six significant iterations of a prototype, run internally while the public version was polished.

The reasoning was philosophical as much as practical. Slack never operated on Mark Zuckerberg's 'move fast and break things' principle; it thrived by offering tools that 'feel fully baked from the get-go', with fit and finish closer to consumer apps than to business software. Goldenberg said threads are 'so close to the heart of what Slack is that they might be an escalated case'. VP of product April Underwood framed the trap: 'It kind of seems like this is a solved problem... But not in the context of work.'

When Threads finally rolled out in January 2017, it went to every team — paying and free — and bore only partial resemblance to threading elsewhere, rebuilt around how work conversations actually behave. The patience had been affordable: while Slack noodled, its usage grew eightfold to 4 million daily active users.

Core features compound: threading touches every conversation in the product, so a botched version would degrade everything.

The 'solved problem' was a false friend — threading patterns from social products don't transfer to workplace communication.

Internal dogfooding across six iterations let Slack find the work-native shape without burning public trust on half-baked changes.

For features at the core of your product, speed is the wrong metric: iterate internally until it feels fully baked, then ship to everyone at once.

Threads shipped to every Slack team in January 2017, both paying and free tiers, completing a two-year design process the company presented as a case study in how its designers approach product development.