Why every project gets exactly one thread

Early on, people asked us for channels. Separate conversations for design, billing and logistics seemed sensible, and every other collaboration tool offers them. We built a prototype and tested it with twenty teams for a month.

What we saw

With channels, decisions were scattered. A hirer would approve a change in one place and the designer would never see it in another. People started repeating themselves to be safe, which defeated the point.

What we kept

One project has one thread. Files, approvals, milestones and messages all appear in time order. You can filter the thread to show only files or only approvals, but there is only one place to look.

The trade-off

Large projects get long threads. We handle that with pinned decisions and a summary at the top that either side can edit. It is not perfect. We think it fails less often than the alternative, and we will keep measuring.