Experimentation Approval Flow

Web app
Problem
Currently, any user with publish access can launch an experiment at any time, which can lead to misaligned dependencies and lack of communication. Additionally, there is no governance process for the activation of experiments to prevent misalignment between internal and external teams.
Goals
The goals of this project are to connect our existing approval flow for launching experiments, ensuring that only authorized users can activate them to prevent misalignment between internal and external teams. We aim to enhance communication regarding the status and dependencies of experiments.

What is the BEESOne Experimentation Tool ?

BEESOne is a collection of internal and partner tools for BEESĀ Customer, a global digital B2B platform for small business owners. One of these tools, called Experimentation, is used to centralize all BEES customer app experiments, such as A/B tests in the company.

The goal is to make experiments more accessible, faster, and scalable for the entire company. It helps make data-driven decisions by comparing multiple versions and measuring their impact on user behavior and performance metrics.

01 Gathering Research

To inform the design of the new governance process for experiment activation, I researched user workflows and identified pain points related to misalignment and communication. I also examined benchmarks to understand best practices in experiment governance.

A crucial aspect of my research was analyzing BEESOne's Approval Flow tool, which enables users to view, approve, and reject requests from other internal tools. This helped me understand how our existing tools connected to Approval Flow and how to integrate this experience into the Experimentation Platform.

02 Iterations and Testing

I began by making iterations to include the Approval Flow, then spoke with existing users to gather their feedback. We discovered that the number of actions on the review page was overwhelming, hindering users' navigation through the approval process.

To address this, I validated the necessity of each action. While all actions were confirmed as essential, their presentation needed refinement. I reorganized the visual hierarchy by grouping related actions, utilizing spacing and color cues, and prioritizing high-importance tasks, which helped reduce cognitive overload.Next, I focused on the statuses.

User testing revealed confusion around their labels and quantity. I refined the naming conventions and streamlined the statuses, ensuring that each stage in the approval process was clearly understood. These iterations led to a more intuitive interface, making the approval process more efficient and user-friendly.

03 The Final Designs

To inform the design of the new governance process for experiment activation, I researched user workflows and identified pain points related to misalignment and communication. I also examined benchmarks to understand best practices in experiment governance.

A crucial aspect of my research was analyzing BEESOne's Approval Flow tool, which enables users to view, approve, and reject requests from other internal tools. This helped me understand how our existing tools connected to Approval Flow and how to integrate this experience into the Experimentation Platform.

04 What We Learned

Throughout this project, we learned that simplicity and clarity are key to an effective approval flow. Users were initially overwhelmed by the number of actions and statuses, highlighting the importance of a clean visual hierarchy. Iterating on the design to prioritize key actions and streamline statuses significantly improved user experience.

Additionally, we discovered that users value real-time updates, which led to the future consideration of adding notifications for approvals and rejections. Engaging with users early and often in the process helped ensure the design aligned with their needs, ultimately creating a more intuitive and efficient approval system.

Next Steps

We will continue to monitor user feedback and analyze usage data to identify areas for improvement. Additionally, we plan to add notifications to the notification center for when items are approved or rejected.