How would you measure the success of Optimizely's Feature Flags?

Introduction

Measuring the success of Optimizely's Feature Flags requires a comprehensive approach that considers multiple stakeholders and metrics. To effectively evaluate this product success metrics problem, I'll follow a structured framework covering core metrics, supporting indicators, and risk factors while considering all key stakeholders.

Step 1

Product Context

Optimizely's Feature Flags is a powerful tool that allows developers and product managers to selectively enable or disable features in their applications without redeploying code. This capability is crucial for implementing progressive rollouts, A/B testing, and managing feature releases.

Key stakeholders include:

1. Developers: Seeking to streamline deployment and reduce risk
2. Product Managers: Aiming to control feature releases and gather user feedback
3. Business Leaders: Looking to optimize product performance and user satisfaction
4. End Users: Expecting a stable, feature-rich application experience

User flow typically involves:

1. Feature implementation: Developers code features behind flags
2. Flag configuration: PMs or developers set up rules for flag activation
3. Runtime evaluation: The system determines whether to show features to specific users
4. Monitoring and analysis: Teams track feature performance and user interactions

Feature Flags align with Optimizely's broader strategy of empowering teams to experiment and iterate quickly. Compared to competitors like LaunchDarkly or Split.io, Optimizely's offering is often seen as more integrated with their experimentation platform.

In terms of product lifecycle, Feature Flags is in the growth stage. It's gaining traction among development teams but still has room for expansion and refinement.