The 3-line Slack that gets faster answers

Most Slack messages that sit unanswered for six hours share the same problem. They’re not rude. They’re not unimportant. They’re just too much work for the reader.

The person on the other end opened your message, saw three paragraphs, had four other Slacks queued up, and decided to deal with yours later. Later became never.

A three-line Slack fixes this.

The format

Line 1: what you need. Line 2: the context they need to answer. Line 3: what you’ll do if they don’t respond.

That’s it. No preamble. No “hey hope you’re having a good week.” No “circling back.”

Example: you need a decision

Bad:

“Hey! Hope you had a good weekend. Quick question — I’ve been working on the Q2 onboarding flow and I’m kind of stuck on whether we should gate the email verification step or not. I looked at the old docs but couldn’t find a clear answer. Wondering what you think? Let me know when you have a sec 🙂”

Good:

“Need: your call on gating email verification in the Q2 onboarding flow. Context: old design gated it, new PRD doesn’t specify. [doc link] Default: I’ll keep it gated unless I hear back by EOD Thursday.”

Same information. 80% less cognitive load for the reader.

Example: you need a doc review

Bad:

“Hi! Would love your thoughts on this draft when you get a chance. No rush. Let me know if you have any feedback or see anything off! [link]”

Good:

“Need: 10-minute review of this draft before I send it to legal Friday. [link] Context: I’m specifically worried about the scope section and whether the risks are framed right. Default: I’ll send it Friday 2pm ET as-is if I haven’t heard back.”

The second version is faster to read and easier to act on, because the reviewer knows exactly what you want them to focus on.

Example: an access or intro request

Bad:

“Hey, wondering if you could intro me to the data team? I have some questions.”

Good:

“Need: intro to someone on the data team who owns the customer dashboard. Context: I’m trying to understand how a metric is calculated for a doc I’m writing. Default: I’ll ping #data-help if I don’t hear back by tomorrow.”

Why the “default” line works

The default line is the unlock. Three things happen:

1. It removes urgency performance. You’re not making them feel bad for not responding instantly. They can deal with it when they have a minute.
2. It protects you from blocking. If they don’t respond, you keep moving. That’s not aggression — that’s a pro.
3. It forces you to decide what you’d do without them. Half the time, you realize you didn’t actually need the message.

The default doesn’t have to be “I’ll proceed.” It can be “I’ll ping someone else.” “I’ll ask in the next standup.” “I’ll assume yes.” “I’ll escalate to [manager].” Any default is better than “I’ll wait and hope.”

When to use a thread vs. a channel vs. a DM

Same three-line format. Different surfaces.

Public channel: use when the answer is useful to other people, or when you want visibility on the question. Trade-off: slower responses, because nobody owns it.

Thread under an existing message: use when your question is scoped to something already under discussion. Keeps the channel clean.

DM: use when the person is the specific owner, when the question is sensitive, or when you need speed. Trade-off: the answer stays with you — nobody else learns.

A simple rule: if you’d be happy for five other people to see the answer, use a channel. If not, DM.

How to handle “I’ll get back to you”

You’ll get “I’ll check and get back to you” a lot. Half the time they won’t. That’s not malice — it’s just life.

Two moves:

1. Confirm the default still applies. “Sounds good — I’ll proceed with X at 2pm ET unless I hear otherwise.”
2. If the default doesn’t cover it and you haven’t heard back by the deadline, send a one-line bump. “Checking in on this — I’m going to proceed with X at 3pm unless you want me to hold.”

That’s the entire follow-up protocol. No “just circling back,” no apology. One line, bump the default forward, keep moving.

What to strip from every Slack

These phrases make you look junior and they slow everyone down:

• “Hope you’re having a great week” at the start
• “Sorry to bother you”
• “Whenever you get a chance” without a default
• “I was wondering if…”
• “Does that make sense?”
• “No rush!” (the reader knows)
• “Just checking in”
• “Circling back” (same message, lower confidence)

Strip all of them. You’ll be surprised how little is left, and how much clearer it is.

What works across cultures

One note for foreign professionals or people moving between companies: the three-line Slack can feel abrupt if your previous workplace was more formal. It isn’t. American office Slack norms reward brevity. A well-formatted direct message is read as respectful of the reader’s time, not rude.

The pleasantry you skipped was costing the reader a beat of cognitive work. Removing it is a favor.

The 2-minute rule for deciding whether to Slack at all

Before you send, ask: can I answer this myself in two minutes?

• Check the doc, the channel search, the last meeting’s notes.
• Check the shared drive.
• Check whether you already asked this person two weeks ago and forgot.

Half of “I need to ping someone” moments dissolve in two minutes of looking. The other half are genuine and deserve the three-line format.

If you’re the manager on the receiving end

When your team sends you messy Slacks, respond to the format, not just the content. A quiet push in a 1:1 — “Hey, when you send me stuff like that, can you put the ask in the first line? Makes it way faster for me to respond” — will change their habits across every recipient they have.

Edge cases

• Incidents and real emergencies: skip the format. Page the on-call. Three lines is for non-urgent work.
• A genuinely complex problem: don’t force it into three lines. Send a short “need your brain on this — I’ll set up 15 min?” Slack and schedule a call.
• Executive or external audience: the format still applies, but warm the tone a notch. “Hi [Name] — need your call on X. Context: [one sentence]. I’ll default to Y by Tuesday unless you prefer otherwise.”

Do this today

Pick your last five Slack messages that asked for something. Rewrite one of them in the three-line format. Notice what you removed.

For the update rhythm that means most of your asks get anticipated instead of asked, use the Status update template. For deciding email vs. Slack in the first place, see Should you send an email or a Slack?.