A Project managers perspective of Optimizely.
Overall Satisfaction with Optimizely Feature Experimentation
Our team uses it as a core part of our release and Validation process across client projects, not just internally. Currently, we are working with a whale client, a bank, and we've leveraged feature flags to test different credit card recommendation engines in prod without risking the live customer base. That has solved a longstanding problem of all-or-nothing releases, where any new algorithm introduced carried a huge rollback risk.
Pros
- We can do feature flag based rollouts with surgical control.
- It's good at progressive delivery in compliance-heavy sectors.
Cons
- We currently can't correlate feature flagged experiments with Salesforce CRM data.
- We have a huge, noteworthy ROI case study of how we did a SaaS onboarding revamp early this year. Our A/B test on a guided setup flow improved activation rates by 20 percent, which translated to over $1.2m in retained ARR.
Do you think Optimizely Feature Experimentation delivers good value for the price?
Yes
Are you happy with Optimizely Feature Experimentation's feature set?
Yes
Did Optimizely Feature Experimentation live up to sales and marketing promises?
Yes
Did implementation of Optimizely Feature Experimentation go as expected?
No
Would you buy Optimizely Feature Experimentation again?
Yes
Using Optimizely Feature Experimentation
| Pros | Cons |
|---|---|
Like to use Technical support not required Consistent | Slow to learn Lots to learn |
- A/B testing feels natural
- targeting and segmentation - it's so intuitive to define audiences
- Integration with CI/CD pipelines
- Experiment setup for multi-environment projects can get pretty tedious. When we're running parallel tests across staging and live environments, syncing the configurations is anything but intuitive
- The permission system is a bit rigid
Yes - The mobile SDKs are well supported which allows us to run experiments inside mobile apps rather than only on web. It's good enough.
However there's so much inconsistency with the SDKs when variations increase
However there's so much inconsistency with the SDKs when variations increase


Comments
Please log in to join the conversation