Eric

As COO of a fast-growing company, I spend a lot of time noticing what stopped scaling. Last month it was Slack. Put a few hundred people in a channel and Slack stops being a conversation and starts being noise. So here is how Warp communicates, in 4 pillars: 1/ Threads, always. Reply in the thread, not the channel. One topic per thread, and if the conversation shifts you start a new message. A channel should be readable by someone who joined it five minutes ago. 2/ Communicate concisely. Ayush wrote our Bottom Line Up Front doc in December and it comes down to one thing. The ask or the conclusion goes in the first line, context after. Batch your thoughts into one message instead of five short ones back to back. Easier to read, easier to search, less noise for the people it wasn't for. 3/ Channels over DMs. If the answer could help someone else now or later, it goes in a channel. DMs are for private or sensitive things only. A customer issue debugged in a DM helps exactly two people. Three months later someone solves it again from scratch. 4/ Close the loop. If you're tagged and don't react, the sender has to assume you didn't see it. 👀 is seen and on it. ✅ is resolved. 👍 is an FYI that needs nothing. Banter is exempt. None of that needs threading or batching. Public channels let people self-serve instead of asking the same question twice. That runs both ways: before you ask, search. The answer is often already sitting in a channel, and we protect deep work here, so an avoidable ping that pulls someone out of focus is a cost the whole team pays. And at an AI-native company, your channels are also what your agents read. A decision buried in a DM is invisible to every person and every agent who needs it later. As far as the company is concerned, it never happened. We're 70 people today and will be a few hundred soon. If you want to join us as we scale, we have 20 open roles right now. Link in the comments to apply.