Skip to content
hum

NNoor Haddad

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.

5 min read

Picture #design on a Tuesday. Mina asks whether the onboarding confetti should stay. Twelve people have opinions. If they all answer in the channel, the next person to open #design scrolls past twelve messages about confetti to find the one thing they came for.

If they answer in a thread, the channel shows one message with “12 replies”. The people who care open it. Everyone else moves on. That is the whole idea, and it is a small act of courtesy to whoever reads the channel next.

Reply in a thread when

  • You are answering one specific message, not the room.
  • The answer will take more than one back-and-forth.
  • Only some of the people in the channel need to follow along.
  • It is a detail: a bug's steps to reproduce, a copy tweak, a file version.

Post in the channel when

  • You are starting a new topic.
  • Everyone in the channel needs to know, today.
  • A thread reached a conclusion. Send it back to the channel with one click, so the outcome is visible without the debate.

Confetti: keep or drop? Thread for opinions please.

Decision from the thread: dropped. The progress bar stays.

Twelve replies later, one line goes back to #design with “Also sent to channel”.

The thread etiquette we use at Hum Labs

Start the thread with enough context that someone arriving cold can follow it. End it with a decision or an owner. If a thread passes 30 replies, it probably wants to be a huddle: start one from the thread and the notes will land back in it.

“The test for a thread is simple: would the person who reads this channel tomorrow thank you for keeping it out of their way?”

Ada Okoro, Product Manager for threads

What Hum does to help

You only get notified about threads you wrote in or were mentioned in. Long threads remember where you stopped reading and mark new replies with a rose line. And the catch-up reads threads too, so a decision buried in reply 14 still reaches you. See how threads work.

Worth your 5 minutes?

N

Noor Haddad · Head of Writing, Amman

Edits every word in the product. Writes about how Hum Labs works for the blog.

Meet the team

Talk it through in Hum.

Channels for the work, threads for the details, huddles that take their own notes. Free for teams up to 10.