blogNotes on calmer, faster teamwork
Anything worth readingover coffee?
How teams talk things through without drowning in it. Written by the people who build Hum, with the numbers we measure and the arguments we had.
Every note.
- Practice
We cancelled the Monday sync. Here is what replaced it.
Forty minutes, eleven people, every week for two years. We stopped it in March and nobody has asked for it back. What we do instead, and the one meeting we kept.
LLena Varga· 7 min read
- Engineering
How the catch-up decides what matters
A morning backlog of 180 messages becomes eight lines. What the catch-up looks for, what it leaves out on purpose, and why it never reads a message you couldn't open.
RRavi Shah· 9 min read
- Practice
Threads are a kindness to the people who weren't there
A channel is a room; a thread is a side conversation that does not make everyone else listen. A short guide to when to reply in a thread, and when not to.
NNoor Haddad· 5 min read
- Product
Quiet hours, and the urgent lane we argued about for a month
Letting anyone break through someone's quiet hours sounds like it defeats the point. Here is how we designed an urgent button that people use about twice a month.
HHana Ito· 6 min read
- Practice
Running support across nine time zones with one channel
Kofi's team answers customers from Accra to Toronto in one #support channel. The handover ritual, the macros, and why they stopped using DMs for escalations.
KKofi Mensah· 8 min read
- Engineering
Huddle notes: what we keep, what we throw away
When a huddle ends, Hum posts the decisions. It does not keep the recording unless you ask. The privacy choices behind huddle notes, written by the engineer who made them.
TTomás Reyes· 6 min read
Want what shipped instead of what we think? Read the changelog
Try the ideas on your own team.
Start a workspace free, set up a #weekly thread, and cancel one meeting. See what happens in four weeks.