Integrations
Let other tools show our roadmap
29 supporters640 influence
10 comments · 10 people in the discussion
- Idea→
- Discussing→
- Gaining support→
- Proposal→
- Voting→
- Approved→
- Building→
- In experiment→
- Shipped→
- Measured
Problem
Teams that depend on Hive still explain the roadmap in slides. The live story of what we're deciding doesn't travel.
Why it matters
A public roadmap that can't be seen where work happens gets summarized by whoever has the slide deck.
Potential solutions
A read-only embed of Exploring, Deciding, Building, Testing, and Shipped, with links back to the idea.
Proposal #22
Let other tools show our roadmap
- Problem
- Teams that depend on Hive still explain the roadmap in slides. The live story of what we're deciding doesn't travel.
- Evidence
- Members pasted screenshots into other tools because there was no other way to show a decision in progress.
- Proposed change
- A read-only embed that always links back to the original idea and discussion.
- Expected impact
- The roadmap stays a story about the community, even when it's seen somewhere else.
- Alternatives
- A PDF export. It would be stale on purpose.
- Risks
- Embeds can leak a vote in progress. Hide option totals the same way the decision room does.
- Open questions
- Do we allow the embed on public sites, or only signed-in tools?
- Complexity
- medium
- Success metrics
- Referral visits from embeds to idea pages.
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.
Teams that depend on Hive still explain the roadmap in slides. The live story of what we're deciding doesn't travel.
Evidence
- I counted eleven stale screenshots of our roadmap in one workspace. The newest was nine days old.
- The part I would spend influence on is specific: the roadmap was being copied into slides and going stale the same day.
- I don't want another feature. I want fewer people stuck with the roadmap was being copied into slides and going stale the same day.
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
- If I can't show my team the decision, I end up translating it, and the translation drops the dissent.
- Before we build “Let other tools show our roadmap”, write the success metric in the proposal itself.
- A smaller version of “Let other tools show our roadmap” could tell us if we even framed the problem correctly.
Arguments against
- An embed that shows live vote totals will cause bandwagons outside the room.
Alternatives
- No alternative has been spelled out. The author’s suggestion is the only concrete path on the table.
Open questions
- Can an embed deep-link to the transcript once a decision closes?
Treat “Let other tools show our roadmap” as a problem statement: Teams that depend on Hive still explain the roadmap in slides. The leading suggestion is: A read-only embed of Exploring, Deciding, Building, Testing, and Shipped, with links back to the idea. Why it matters here: A public roadmap that can't be seen where work happens gets summarized by whoever has the slide deck.
Community discussion
If I can't show my team the decision, I end up translating it, and the translation drops the dissent.
An embed that shows live vote totals will cause bandwagons outside the room.
Can an embed deep-link to the transcript once a decision closes?
I counted eleven stale screenshots of our roadmap in one workspace. The newest was nine days old.
Before we build “Let other tools show our roadmap”, write the success metric in the proposal itself.
The part I would spend influence on is specific: the roadmap was being copied into slides and going stale the same day.
A smaller version of “Let other tools show our roadmap” could tell us if we even framed the problem correctly.
I don't want another feature. I want fewer people stuck with the roadmap was being copied into slides and going stale the same day.
Whatever we do with “Let other tools show our roadmap”, the decision has to stay attached to this thread.
I keep running into this around the roadmap was being copied into slides and going stale the same day. “Let other tools show our roadmap” is the name I would have used.
Join the hive to add to this thread.