Better collaboration
Collaborative workspaces
52 supporters1,940 influence
10 comments · 10 people in the discussion
- Idea→
- Discussing→
- Gaining support→
- Proposal→
- Voting→
- Approved→
- Building→
- In experiment→
- Shipped→
- Measured
Problem
People who share a problem still edit their thoughts alone. Draft proposals bounce between comments instead of a place where the text can change in public.
Why it matters
The synthesis should be watchable. If only the final proposal appears, the hive can't see what was dropped.
Potential solutions
An opt-in workspace on a proposal where the draft is edited in the open and every change is kept.
Proposal #18
Collaborative workspaces
- Problem
- People who share a problem still edit their thoughts alone. Draft proposals bounce between comments instead of a place where the text can change in public.
- Evidence
- Authors said they rewrote proposals from comments but couldn't show the trail. Objectors felt the draft moved without them.
- Proposed change
- Test a shared draft on two proposals. Edits are attributed. The vote still happens in the decision room.
- Expected impact
- The text the hive votes on is visibly the community's text.
- Alternatives
- Keep a single author and a suggestion thread. It's simpler and it's what people say is failing.
- Risks
- A shared draft can stall. The experiment needs a closing time, not an endless document.
- Open questions
- What happens to influence if the draft changes substantially mid-discussion?
- Complexity
- large
- Success metrics
- Participants can point to a sentence they changed, and objectors say the final text answered them.
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.
People who share a problem still edit their thoughts alone. Draft proposals bounce between comments instead of a place where the text can change in public.
Evidence
- On the last proposal I authored, three concerns showed up only after voting opened. They were about sentences I had already changed in private.
- The part I would spend influence on is specific: draft language changed in private and the room saw only the polished version.
- I don't want another feature. I want fewer people stuck with draft language changed in private and the room saw only the polished version.
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 don't need a second Google Doc. I need the proposal itself to remember who changed the risky sentence.
- Before we build “Collaborative workspaces”, write the success metric in the proposal itself.
- Whatever we do with “Collaborative workspaces”, the decision has to stay attached to this thread.
Arguments against
- Shared editing favors the fastest writers. Async comments are slower and fairer.
Alternatives
- Try it on one proposal, not the whole hive. If the draft becomes a battleground we'll know quickly.
Open questions
- Does the workspace replace Hive Intelligence, or does the synthesis sit beside the draft?
Treat “Collaborative workspaces” as a problem statement: People who share a problem still edit their thoughts alone. The leading suggestion is: An opt-in workspace on a proposal where the draft is edited in the open and every change is kept. Why it matters here: The synthesis should be watchable.
Community discussion
I don't need a second Google Doc. I need the proposal itself to remember who changed the risky sentence.
Shared editing favors the fastest writers. Async comments are slower and fairer.
Try it on one proposal, not the whole hive. If the draft becomes a battleground we'll know quickly.
On the last proposal I authored, three concerns showed up only after voting opened. They were about sentences I had already changed in private.
Does the workspace replace Hive Intelligence, or does the synthesis sit beside the draft?
Before we build “Collaborative workspaces”, write the success metric in the proposal itself.
The part I would spend influence on is specific: draft language changed in private and the room saw only the polished version.
I don't want another feature. I want fewer people stuck with draft language changed in private and the room saw only the polished version.
Whatever we do with “Collaborative workspaces”, the decision has to stay attached to this thread.
I keep running into this around draft language changed in private and the room saw only the polished version. “Collaborative workspaces” is the name I would have used.
Join the hive to add to this thread.