Better collaboration
A transcript of every decision
51 supporters1,860 influence
10 comments · 10 people in the discussion
- Idea→
- Discussing→
- Gaining support→
- Proposal→
- Voting→
- Approved→
- Building→
- In experiment→
- Shipped→
- Measured
Problem
After a vote, newcomers see the outcome and not the argument. They can't tell why the product looks like this, so they re-open settled questions.
Why it matters
A product with no memory asks its community to relitigate. Trust drops each time we do.
Potential solutions
Publish a short decision transcript: the problem, the options, the winning case, and a link back to the thread.
Proposal #15
A transcript of every decision
- Problem
- After a vote, newcomers see the outcome and not the argument. They can't tell why the product looks like this, so they re-open settled questions.
- Evidence
- Repeat proposals tracked the same problem within six weeks when the original thread was hard to find.
- Proposed change
- Attach a one-screen transcript to every closed decision and link it from the shipped feature.
- Expected impact
- New members can see why something exists before they spend influence asking again.
- Alternatives
- Rely on the raw comment thread. It is complete and too long to orient anyone.
- Risks
- A transcript can sand off a real objection. Keep arguments against in the text.
- Open questions
- Who is allowed to edit a transcript after the vote?
- Complexity
- medium
- Success metrics
- Fewer duplicate ideas on problems that already have a decision.
The draft is open for discussion before a vote begins.
A product specification exists for what comes after the decision. It is a brief, not code.
Hive Intelligence · community synthesis
Synthesis
Drawn from the discussion. Not a decision.
After a vote, newcomers see the outcome and not the argument. They can't tell why the product looks like this, so they re-open settled questions.
Evidence
- Proposal echoes show up most on mobile and notifications. People never found the first thread.
- The part I would spend influence on is specific: new members were reopening decisions they couldn't see the reason for.
- I don't want another feature. I want fewer people stuck with new members were reopening decisions they couldn't see the reason for.
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
- I want to point at a decision the way I point at a changelog, except the reason is the point.
- Before we build “A transcript of every decision”, write the success metric in the proposal itself.
- A smaller version of “A transcript of every decision” could tell us if we even framed the problem correctly.
Arguments against
- If the transcript is written by staff, it will sound cleaner than the room was. Label it as a synthesis.
Alternatives
- No alternative has been spelled out. The author’s suggestion is the only concrete path on the table.
Open questions
- Does a rejected idea get a transcript too? The no is part of the history.
Treat “A transcript of every decision” as a problem statement: After a vote, newcomers see the outcome and not the argument. The leading suggestion is: Publish a short decision transcript: the problem, the options, the winning case, and a link back to the thread. Why it matters here: A product with no memory asks its community to relitigate.
Community discussion
I want to point at a decision the way I point at a changelog, except the reason is the point.
If the transcript is written by staff, it will sound cleaner than the room was. Label it as a synthesis.
Proposal echoes show up most on mobile and notifications. People never found the first thread.
Does a rejected idea get a transcript too? The no is part of the history.
Before we build “A transcript of every decision”, write the success metric in the proposal itself.
The part I would spend influence on is specific: new members were reopening decisions they couldn't see the reason for.
A smaller version of “A transcript of every decision” could tell us if we even framed the problem correctly.
I don't want another feature. I want fewer people stuck with new members were reopening decisions they couldn't see the reason for.
Whatever we do with “A transcript of every decision”, the decision has to stay attached to this thread.
I keep running into this around new members were reopening decisions they couldn't see the reason for. “A transcript of every decision” is the name I would have used.
Join the hive to add to this thread.