How to stop decisions dying in Slack threads

Someone asks “thoughts on X?” Fourteen replies arrive. The topic changes. Nothing was decided, and in three weeks nobody will be able to find the thread to check. Here is what a decision actually needs — and how to run one in about sixty seconds.

The anatomy of a decision that dies

Decisions don't fail in Slack because people disagree. They fail because nobody was ever asked to choose between fixed options by a fixed time.

It was never a question

Someone shared a link and asked for thoughts. Fourteen people gave thoughts. Nobody was ever asked to choose.

The options drifted

By reply nine there are six options, two of which are combinations of earlier ones, and nobody knows which set is live.

No deadline, so no urgency

Everyone intends to come back to it. The channel moves on. The thread is four scrolls up by lunchtime.

Nobody owned it

The team reached rough agreement and moved on. Six weeks later nothing has happened and everyone assumed it was someone else's.

No record

It was decided, probably. Finding the message means searching for a word you hope somebody used.

The five elements

Every decision that closes on its own has all five. Remove any one and it reverts to a thread.

1. A clear question

“Thoughts on the pricing page?” is not a decision, it is an invitation to a thread. “Do we ship the pricing page on the 14th or the 21st?” is a decision.

2. Defined options

Two to five, written down before anyone responds. Open-ended questions produce opinions; fixed options produce a choice.

3. A method

How preferences turn into a result. Single choice for most things. Ranked choice once there are three or more real contenders and you care what people could live with.

4. A deadline

A decision without a deadline does not get made late — it does not get made. Put a date on it and say what happens when the date arrives.

5. A named owner

One person, named before the vote, accountable for the follow-through. “Someone should pick this up” is how a decided decision quietly becomes an undone one.

The 60-second decision framework

QuestionRewrite it until it can be answered with a choice rather than an opinion. If it starts with “thoughts on”, it is not there yet.
OptionsTwo to five, written down before anyone responds. Include the status quo as an explicit option if it is genuinely on the table.
MethodSingle choice by default. Ranked choice once three or more options are real contenders. Approval when several answers are acceptable. Dot voting when you need intensity, not direction.
Deadline24 to 48 hours for most things. Say explicitly what happens when it passes.
OwnerOne name, before the vote. Not a team, not “whoever picks it up”.

You can run this by hand. Pin the message, tally the replies, set yourself a reminder, and write the outcome somewhere findable. It works — right up until the week you are too busy, which is also the week the decision mattered most.

Doing it manually, and where that breaks

Pin the messageWorks until the channel has eleven pins and nobody reads any of them.
Keep a decision docWorks as long as someone fills it in. In practice that is about six weeks after the person who set it up moves on to something else.
Set a calendar reminderWorks for the deadline. Does nothing about chasing the four people who haven't answered.
Announce the outcome in the channelWorks for the people online at the time. It is not a record — it is another message to search for later.

The structured way

A tool matters for the parts that depend on somebody remembering: enforcing the deadline, chasing non-responders, and writing the record.

Verdo is one way to do this. Type /verdo and a modal asks for the question, the options, the deadline and an optional owner; voting is single choice under a majority or consensus rule. It sends one DM at 24 hours and one at 1 hour before the deadline, to non-voters only, closes at the deadline, applies the authority rule you picked, posts the result, and files a searchable record. 30 days later it asks the owner one question: did this work?

The framework matters more than the tool. If you take nothing else from this page, take the five elements and run them by hand.

Five decisions every Slack team should formalise

Not every decision needs this. These five are the ones that get relitigated.

Vendor selection

Expensive, hard to reverse, and the one you will be asked to justify. A majority rule fixed in advance, and a named owner on the contract.

Scope trade-offs

Cut, defer or ship. The decision that most needs a record, because it is the one that gets relitigated in the retro.

Hiring calls

Anonymous mode matters here — seniority in the room skews an open vote. Consensus, so one strong objection blocks it.

Launch timing

Everyone has an opinion and someone has to pick. Short deadline, a majority rule, and one named owner who carries it.

Budget allocation

Dot voting shows intensity, which is the information you actually need when everything is somebody's priority.

Frequently asked questions

How do you make decisions in Slack without endless threads?

Replace the open question with a structured one. Write the question so it has an answer, list the options before anyone responds, pick a method for turning preferences into a result, set a deadline, and name one person accountable for what happens next. The thread stops being the decision-making mechanism and becomes the discussion around it.

Why do Slack decisions get lost?

Because a channel is a stream, not a record. Nothing in Slack distinguishes the message where a decision was made from the four hundred around it, there is no deadline forcing a conclusion, and reactions are not a tally. The decision does not get overturned; it just becomes unfindable, which in practice is the same thing.

What is the 60-second decision framework?

Question, options, method, deadline, owner. Write the question so it can be answered with a choice. List two to five options. Pick single choice unless there are three or more real contenders, in which case use ranked choice. Set a deadline you would actually enforce. Name one person accountable. If you cannot do all five in a minute, the decision is not ready to be made.

Do I need a tool for this?

No. The five elements work in a pinned message with a manual tally, and plenty of teams run exactly that. A tool matters when you want the deadline to enforce itself, the non-responders chased without you doing it, and the record to exist without anyone remembering to write it.

How long should a decision deadline be?

Long enough for everyone to see it in their working hours, short enough that it stays urgent. For a distributed team that usually means 24 to 48 hours. Anything past a week has no deadline in practice — people will respond in the last hour whatever you set.

Or type /verdo and let the tool enforce it.

The five elements, in a modal, with the chasing and the record handled for you.

Start 7-day free trial See pricing Add to Slack

7-day free trial. Card required. Cancel anytime during the trial with no charge.