Integrations
Hear a decision where the team already is
38 supporters1,010 influence
10 comments · 10 people in the discussion
- Idea→
- Discussing→
- Gaining support→
- Proposal→
- Voting→
- Approved→
- Building→
- In experiment→
- Shipped→
- Measured
Problem
Teams live in Slack. Hive decisions arrive, if at all, as a link without the problem, the options, or how long is left. People click through already late.
Why it matters
We keep asking members to remember another room. The decision should arrive with enough context to act.
Potential solutions
A Slack message when a vote opens and when it is about to close: problem, options, time, and a link that lands in the decision room.
Proposal #25
Hear a decision where the team already is
- Problem
- Teams live in Slack. Hive decisions arrive, if at all, as a link without the problem, the options, or how long is left. People click through already late.
- Evidence
- Supporters who also use Slack voted later and more often asked what the options were in the thread.
- Proposed change
- Post the decision itself into Slack: problem, options, countdown, link. No tally before you vote.
- Expected impact
- The people already arguing about the work can enter the decision on time.
- Alternatives
- Email only. It works for some and it is easy to bury.
- Risks
- A Slack post can become the vote. The commit has to stay inside Hive so influence stays accountable.
- Open questions
- Which workspace is allowed to mirror a decision, and who connects it?
- Complexity
- medium
- Success metrics
- Supporters connected to Slack vote before the last 12 hours more often than those who aren't.
The draft is open for discussion before a vote begins.
Hive Intelligence · community synthesis
Synthesis
Drawn from the discussion. Not a decision.
Teams live in Slack. Hive decisions arrive, if at all, as a link without the problem, the options, or how long is left.
Evidence
- Our team has a channel called #hive-decisions. It is just links. Half of them get a reaction and no vote.
- The part I would spend influence on is specific: teams saw a bare link and opened Hive after the vote had already narrowed.
- I don't want another feature. I want fewer people stuck with teams saw a bare link and opened Hive after the vote had already narrowed.
Community sentiment
- Demand is specific. Supporters keep returning to the same broken moment, not a vague wish list.
- The objection is about scope. Concerns are less “never do this” and more “don’t do it in a way that drowns the problem.”
- People brought proof. Evidence comments describe real sessions, not hypothetical users.
Arguments for
- Bring the problem to the team. Don't bring the tally. The tally is how a room tips.
- Before we build “Hear a decision where the team already is”, write the success metric in the proposal itself.
- Whatever we do with “Hear a decision where the team already is”, the decision has to stay attached to this thread.
Arguments against
- If Slack becomes the debate, the hive's transcript goes missing. The message has to point back, hard.
Alternatives
- Start with a closing-soon ping only. An opening ping might train people to ignore us.
Open questions
- Can a team subscribe to a theme, or only to ideas they already support?
Treat “Hear a decision where the team already is” as a problem statement: Teams live in Slack. The leading suggestion is: A Slack message when a vote opens and when it is about to close: problem, options, time, and a link that lands in the decision room. Why it matters here: We keep asking members to remember another room.
Community discussion
Bring the problem to the team. Don't bring the tally. The tally is how a room tips.
If Slack becomes the debate, the hive's transcript goes missing. The message has to point back, hard.
Start with a closing-soon ping only. An opening ping might train people to ignore us.
Can a team subscribe to a theme, or only to ideas they already support?
Our team has a channel called #hive-decisions. It is just links. Half of them get a reaction and no vote.
Before we build “Hear a decision where the team already is”, write the success metric in the proposal itself.
The part I would spend influence on is specific: teams saw a bare link and opened Hive after the vote had already narrowed.
I don't want another feature. I want fewer people stuck with teams saw a bare link and opened Hive after the vote had already narrowed.
Whatever we do with “Hear a decision where the team already is”, the decision has to stay attached to this thread.
I keep running into this around teams saw a bare link and opened Hive after the vote had already narrowed. “Hear a decision where the team already is” is the name I would have used.
Join the hive to add to this thread.