Description:
We use Groups extensively to run both open and closed product betas. Groups work well for this because they let us embed Skilljar tutorials/live training schedules via widgets, control access to sensitive/pre-release features, let PMs post directly to participants, and let participants share feedback through posts — all in one contained space.
The gap is idea management. When a PM converts a beta participant's post into an Idea, it moves entirely out of the Group and into the general Ideas space. For closed betas especially, this is a problem: the idea (and its status updates) is no longer visible to the people who raised it, and it's disconnected from the confidential context it came from. Participants lose visibility into whether their feedback was actioned, and PMs lose the ability to close the loop from within the same space they're already using to manage the beta.
What we'd like: a way for Ideas to live in — or be visibly synced with — the Group they originated from, so that:
- Beta participants can see the status of ideas raised during the beta without leaving the Group
- PMs can convert a post to an Idea (or link a post to an existing Idea) without losing the Group context
- This works for closed/private Groups just as well as open ones, respecting the same access controls
Why it matters: Idea tracking is currently the one piece of the beta feedback loop that breaks the otherwise-seamless Group experience, and it's a growing pain point as we scale the number of concurrent betas we run through Groups.