Subscribe
Sign in
How to you gate your beta rollouts?
We've actively got our beta live in the world but am curious what ways you've found to be most effective for both use data collection (self reported or otherwise) and gating access?
9
Replies
Best
Simona O'Neill
The most amount of user data and feedback we got was through our Discord channel and support chat. For non self reported data we use Mixpanel.
Report
Share
Launching soon!
@simona_o_neill3 very interesting - Do you use that data to determine what your roadmap looks like?
@simona_o_neill3 roughly how many users were giving you good feedback in Discord?
I ask because we are currently finding the right balance between trusting our deep domain expertise and listening to user feedback when it's a significant number of users.
@dzaitzow Yes we certainly listen to what our users want the most and prioritise certain feature rollout.
@matty_reed Well it wouldn't be such a significant number as of yet because we are still in beta. We're talking probably around 50 people who actively gave feedback.
Intrigued by their gating strategy - curious if they prioritize collecting user data (surveys) or controlled access (invites access) for their rollout.
Launching soon!
@jaxon_smith3 are you talking about a specific organization or rollout? or just a general inquiry?
Setting up a feedback form with a special section for unicorn sightings—oops, I mean beta user experiences—has worked wonders for us! Remember, gating access is key; it's like serving exclusive tech magic to the right wizards at Hogwarts! 🧙♂️✨