Feature Flags User Survey
Purpose
This issue's purpose is to get insight regarding User needs and behaviours for feature flags and an invitation for our users to participate in the survey and/or user interviews.
Questions
- Describe what is a Feature Flag in your own words.
- Are you currently using feature flags?
- How are you currently using Feature Flags?
- What tools do you use them with?
- How do you manage your Feature Flags?
- How would you like to change the management of Feature Flags?
- What’s working well?
- What’s not working well?
- What would you change?
- What is missing that would make handling feature flags easier?
- What strategies are you using on your current implementation?
- What’s working well?
- What’s not working well?
- What would you change when it comes to rolling them out to users? How do you currently monitor your Feature Flags?
- What is the most important information you need about them?
- How do you get that information?
- Who, if anyone, do you share it with?
- How do you use this information in conjunction with other monitoring information?
- When in your current process do you need to disable Feature Flags?
- How do you do this? (manually or automatically)
- When do you currently define how they are disabled?
- What would you change about that process?
- Are your feature flags temporary (experimental) or permanent(enable features for specific groups)?
- Who is currently in control of Feature Flags?
- What do they get to do with them?
- Who should be able to have control over Feature Flags?
- Who should be able to turn them on/off?
- Who should be able to create/delete them?
- How does the current permission system work for your needs?
- What changes would you like to see to the permission system?
- How granular do you need it to be?
- How do Feature Flags work across your current environments (dev, prod, testing)?
- Do you use the same Feature Flags across all of them?
- Do you use some Feature Flags for some environment(s) and not the other(s)?
- What do you think of being able to define the environment and then the strategy for a Feature Flag?
- How would this impact your ability to do your job?
- Should the strategy be set first and then the environment added? If so, why?
- Are you doing A/B testing?
- How many experiments so you have?
- How do you keep track of them?
- How long does an experiment last (on average)?
- How do you remove the feature flag?
- How do you currently handle incomplete features in production?
TODO checklist (survey creation)
(accordingly to UX Research survey process)
-
The Product Manager drafts the survey -
The UX Researcher reviews and provides feedback on the survey draft -
The UX Researcher enters the survey in Qualtrics -
The UX Researcher opens a Recruiting request issue and assigns it to the relevant Research Coordinator -
The Research Coordinator distributes the survey to a sample of participants -
After the survey is closed, the UX Researcher updates the Recruiting request issue. -
Product Manager and UX Researcher work collaboratively to synthesize the data and identify trends, resulting in findings. -
UX Researcher creates issues in the UXR_Insights project documenting the findings. -
UX Researcher updates the Problem validation research issue with links to findings in the UXR_Insights project and, if applicable, unmarks the Problem validation research issue as confidential before closing it.
Edited by Nadia Udalova