How do you release experimental features to early adopters?

Question

Steven Birchall · Accepted Answer

@pablofelgueres haver never used a specialist tool for it.  For the different places I've implemented this, we have defined the different user groups within our CRM (which has varied from Hubspot and SalesForce) and handled the reach out either via email from the Platform or using In-App messaging through something like Intercom.

Any interviews have been done in say Zoom or Google Meet, with them being recorded and then added to Confluence with any respective notes.  Fullstory and MixPanel have been used for viewing how people are using the feature and generating any metric based reports.

Arguably it has been a bit of a mess with all the different tools being used.

Steven Birchall · Answer

Ideal scenario, and what I've done for past products where I've been the PM, is ideally you identify a segment of your user base upon whom the feature is for prior to build and use a group of that segment as part of the research scoping piece.

You then build, based upon those insights, plus any other data points, etc and get it to a space where it is production ready.

As this is happening, you re-engage with the group who were part of the pre-build research group, as well as find users who fit the target segment, but were not contributors, and invite them to take part of the pilot.

Once the feature is in Production (as a dark feature) you enable for the opted in users and conduct whatever monitoring, feedback processes, etc and then take those insights back into the PDLC process.

Steven Birchall · Answer

@pablofelgueres thanks for sharing, will definitely check it out.  Anything that can simplify the process is definitely welcomed.

Pablo · Answer

@stevenbirchall This makes a ton of sense, it's like:

1. Hypothesis
2. Reach out to target users for research and scoping
3. Build
4. Pilot with target users
5. Feedback and repeat

Specially for engaging with target users and asking for opt in, which tools did you use or recommend?

Pablo · Answer

@stevenbirchall This is super interesting ! Thanks a ton for the detailed response. I'm asking because I think this could be streamlined with less pieces. You could probably go from 3-7 tools to one thing that encompasses: - release engineering, scoping, reachout, and metrics You've given me the idea of adding a CRM connector ! I am building a demo, just posted a video on a new community on reddit: https://www.reddit.com/r/goupstr...

Pablo · Answer

What is your workflow to test a new raw feature to users?

How do you release experimental features to early adopters?

Replies