Improve in-product guidance for Feature Flags
Problem to solve
Often, solutions for feature flags are complex and hard to get up and running with, and they are not typically bundled or well integrated with CD solutions. It's also unclear how to get started, not just from a technical standpoint but in terms of the organizational change to how to think about delivery. Beyond using the feature, we need to add guidance on how to use feature flags in a team.
We want to make feature flags easier to understand and start using for these personas; each has unique perspectives and we should help each of them with getting started from their POV. Developers are coming from a perspective where they want to safely release changes to production; Ops teams are coming from a perspective where they need control in case of issues. Both end up at the same place, but start in very different ones. We need guidance that covers both of these entrypoints and leads to the same conclusion.
Delaney, Development Team Lead, https://design.gitlab.com/research/personas#persona-delaney
Devon, DevOps Engineer, https://design.gitlab.com/research/personas#persona-devon
Update the feature flags landing page/list page, link to new materials/content about "How can I get the most out of feature flags?" Create two separate perspectives: Ops and Dev to account for the different initial perspectives in play.
What does success look like, and how can we measure that?
This should lead to further adoption of the feature (and more teams being successful with it.)