LaunchDarkly

My main use case for LaunchDarkly is managing the controlled rollout of capability in my in-house application named Escrow Navigator, a conversational assistant that helps the escrow team retrieve and interpret order information and documents. My use case includes enabling new document upload capability, introducing support for additional file formats, and allowing users to ask questions about newly uploaded documents without selecting them again. As a Lead Business Analyst, I define rollout requirements, document acceptance criteria, and coordinate validation with development, QA, and business stakeholders, focusing on feature behavior and release readiness rather than SDK implementation.

LaunchDarkly helps us manage the rollout of new features by using feature flags and user tagging, which are the most valuable capabilities for our workflow. These capabilities allow us to make a capability available to a pilot group while other users continue with the existing experience. For example, when introducing questions about newly uploaded files, we can enable the capability for designated testers, allowing them to validate upload status, document processing, conversation association, and citation before we expand access. This gives us a practical way to gather feedback on a complete business workflow.

LaunchDarkly has positively impacted our organization by helping our team introduce new capabilities through controlled phase releases, making features available to selected users, gathering feedback, and validating business requirements before expanding access. This improves coordination between business development and QA teams and gives us greater control over release readiness. The main organizational benefit is increased confidence when introducing changes while limiting the number of users exposed to potential issues.

We are currently tracking logs in Power BI to see how much feedback we are receiving, and negative feedback has recently been decreasing. We are more focused on UAT, allowing selected testers to validate newly uploaded questions, citation accuracy, and process status against defined acceptance criteria, which contributes to a greater impact on ROI in our project.

We have seen great improvement in metrics such as token input and output, and latency has shown significant improvement, particularly in the production environment.

The best features LaunchDarkly offers include giving us more flexibility in controlling technical deployment with business readiness. A feature can be deployed while access remains limited to the user responsible for validating it. For Escrow Navigator, this supports phase validation for document upload and processing changes, allowing business users to review the experience while QA checks acceptance criteria before broader availability. The main benefit is better control over feature exposure and release coordination, although we have not formally qualified the financial benefit.

The flexibility helps our team when rolling out features by enabling us to roll out a feature to a lower environment and disable it in a higher environment after some time, allowing us to manage features without conducting a major deployment.

Regarding the feature flag, in the UI, if we have enabled a feature such as giving feedback, but we want to hide that feature, using LaunchDarkly, we can disable that flag, and it will reflect in the UI immediately. We also manage document upload and document review features via flags, with LaunchDarkly helping us by providing more flexibility in coordinating technical deployment.

I use LaunchDarkly with GitHub. Our development team utilizes LaunchDarkly alongside GitHub, where GitHub manages our project source code and pull requests while LaunchDarkly controls the availability of features implemented behind flags. This allows teams to merge and deploy code, enabling capability for selected testers before a wider rollout. My role focuses on requirements and UAT validation while the development team handles technical integration.

From a business validation perspective, I would find a consolidated comparison of flag settings across environments helpful. Understanding differences in configuration and targeting when reviewing a feature in dev, UAT, and production is important, along with clear business descriptions, ownership information, and visibility into flags that are ready for retirement. This would make release review easier for stakeholders who do not work with technical configurations every day.

If there are links to documentation available, that would be really helpful, especially from a knowledge transfer perspective.

I have been using LaunchDarkly for around one to two years.

LaunchDarkly is currently stable, and we have not faced any issues with reliability or downtime.

From our project perspective, LaunchDarkly has supported our feature management across environments and pilot user groups without accessibility issues. As usage grows, maintaining clear flag ownership, naming conventions, and cleanup practices becomes essential. I have not personally conducted load testing, and my assessment is based on business validation and release activities.

We have not faced issues with customer support, as we have raised tickets and received solutions within the expected SLA timeframe. I also coordinate internally with the development and platform teams who handle any vendor escalations, leading to a good experience overall.

I rate customer support an eight out of ten.

Prior to LaunchDarkly, we used an in-house tool that managed feature availability through application configuration settings and coordinated deployments. This led to difficulties as enabling a feature for selected pilot users required additional deployment or configuration work. LaunchDarkly gives us a centralized way to manage feature availability and targeting, making phased rollout much easier to coordinate.

We previously used an in-house tool for delegated feature management that managed feature availability. My assessment of LaunchDarkly focuses on its support for our requirements in controlled rollout, pilot testing, and business validation, as we no longer need multiple deployments across environments for managing feature access. LaunchDarkly enables us to disable features for users from its settings without the need for deployments.

We definitely see a return on investment, with operational values in easier pilot releases, more focused UAT, and greater control over feature availability, although we have not formally measured financial ROI or confirmed specific amounts saved. The benefits assessed could reduce release coordination efforts and rework, but supporting data is needed to translate them into concrete cost savings.

From a BA perspective, I assess value through the flexibility it provides for controlling release and pilot testing. My role in setup revolves around defining rollout requirements, identifying pilot users, and validating the enabling and disabling of feature behavior in Escrow Navigator, as the development team manages technical integration and configuration.

Compared to our previous approach of managing features through application configuration and deployment, LaunchDarkly stands out by offering more flexibility for controlled release and pilot testing. For Escrow Navigator, its main value is enabling selected users to validate new capabilities before wider availability, fitting projects that need phased rollout and clear release governance, though I have not conducted a formal evaluation of competing platforms.

I would rate LaunchDarkly an eight out of ten.

I chose an eight because of the flexibility I have discussed earlier, along with the capability of supporting multiple environments, which I find good. However, since I am not sure about pricing, I do not give it a ten. In the future, when I have more understanding of pricing, I would definitely want to explore it and potentially change my rating.

In terms of accuracy and reliability, I find LaunchDarkly's capabilities to be really good, as it supports governance and indirectly enables our application changes for certain testers to validate extra data and documents. While it would not directly improve dependence on document extraction or validation, any measured accuracy improvement that is considered ground truth is very helpful for us.

Advice for others looking into using LaunchDarkly includes starting with a small pilot and a clear use case, such as enabling a new capability for selected users before a wider release. I recommend defining flag ownership, naming conventions, and cleanup responsibilities early, including both enabled and disabled behaviors in acceptance criteria during UAT, validating fallback behaviors, while keeping feature targeting separate from application security permissions. Finally, review pricing against expected user measures to assess value.

My main use case for LaunchDarkly is to manage feature flags, enable or disable features without deploying code, and safely test new features across different environments.

I use feature flags in LaunchDarkly to control new features in different environments such as development, SIT, and UAT. First, I enable the features for testing, verify the functionalities, and fix any issues. Once everything is working properly, I gradually enable it for users, which helps reduce deployment risk.

LaunchDarkly helps me improve release management, reduce risk, and quickly roll back features if issues occur, giving me better control over feature releases without the requirement for frequent deployments.

LaunchDarkly helps me maintain control through feature flags and gradual rollouts once the code hits production.

LaunchDarkly has positively impacted my organization by making feature releases safer and more flexible, helping me reduce deployment risk, test new features with specific users, and quickly disable features if any issues occur. Overall, LaunchDarkly is improving my release management and development efficiency and effectiveness.

I have seen improvements in release flexibility and testing efficiency.

The best features LaunchDarkly offers are enabling or disabling features without a deployment and enabling features for specific users or groups.

Targeting specific users or groups helps my team validate a feature before rolling it out more broadly by allowing me to enable a feature for a specific user group first, collect feedback, and validate the functionalities. Once everything works as expected, I can gradually roll it out to all users and release features safely and confidently.

I would also highlight the monitoring and analytics features of LaunchDarkly, which help me track feature performance, identify issues early, and make better decisions during releases. Overall, LaunchDarkly makes feature management easier, faster, and safer.

I think LaunchDarkly could be improved by making the user interface simpler, providing better reporting and analytics, and offering more detailed feature flag monitoring.

I would suggest improving documentation, providing more practical examples, and making troubleshooting easier.

I have been using LaunchDarkly for two months.

Before LaunchDarkly, I mainly relied on traditional configuration-based feature management and a manual deployment process due to the limitations and difficulties I encountered.

LaunchDarkly stood out because of its easy-to-use feature flags, targeted rollouts, real-time updates, and environment management, and this flexibility along with the reduced release risk were the main reasons for choosing it.

I rate LaunchDarkly an 8 out of 10. I give it an 8 because LaunchDarkly provides excellent features, flag management, safer releases, gradual rollouts, and flexibility.

I think LaunchDarkly's AI capabilities should provide strong governance and security, with access control, data privacy, audit logs, and transparency being very important.

Regarding reliability and accuracy, I think LaunchDarkly's AI capability improves productivity by providing safer and more accurate insights.

LaunchDarkly is deployed as a public cloud-based SaaS solution in my organization, which I access through a web platform to manage feature flags across different deployment and testing environments.

I use LaunchDarkly's cloud-hosted SaaS platform, although I'm not completely certain about the underlying cloud provider.