Scaling Beta Adoption

Designing an Opt-in Framework for Genesys.

  • Feature:
    Opt-in (go to market)
  • Role:
    Product Design Manager
  • Time:
    60 days
  • Company:
    Genesys

  • Overview:
    As a CX platform, we often need to to roll beta testing for big features before general availability.

  • Team Size
    Seven people (designers, product managers, engineers and researchers)
  • Problem:
    For a specific feature going live on the platform soon, we needed a certain number of beta participants to be able to collect data and fix issues before GA. Because of sweeping changes and customers being risk-averse, the product team struggled to find the right number of people willing to participate in this beta.

Challenges

The project the designer was assigned to had already been announced publicly, with a delivery date shared across teams – adding pressure and reducing the margin for delay or retraining.

There was no internal alignment on how much we should prioritize customer needs versus end-user needs, especially given our limited resources.

Our internal objectives conflicted with customer expectations: we aimed for an easy opt-in process but intentionally made opt-out more difficult, leading to friction.

The feature had broad UI and UX impacts, requiring tight collaboration across multiple teams to maintain consistency and minimize disruption

Mindmap

What I did

Collaborated closely with a designer, mentoring him to rapidly prototype key flows and spark productive conversations that clarified internal priorities and trade-offs.

Mapped dependencies across multiple teams and worked proactively to align timelines, responsibilities, and design impacts to ensure a smooth rollout.

Introduced configuration and permission controls, giving customers the ability to define which user groups could access the opt-in functionality – increasing their sense of control and security.

Partnered with engineers to work around system limitations, such as long reload times and lack of native support for opt-in behavior, ensuring feasible implementation paths.

Since toggling opt-in states triggered full page reloads and reset UI states, we focused on transparency – adding contextual messages, error states, and lightweight notifications that clarified what’s happening without disrupting workflows.

Flows

Results

  • Organizational Impact:
    Successfully piloted the first opt-in beta model within the company – setting a precedent and playbook for how future feature rollouts can engage early adopters more effectively.

  • Product Impact:
    Increased beta participation by 35%, enabling the product team to gather critical insights earlier and improve stability before general availability.

Increased beta participation by

35 %

Beta participants

109

Want to know more and see some screens?

This project is currently under NDA – for this reason, I can’t share here any visuals, wireframes or prototypes. 

Contact me on rick@rocharca.com to see some live results of this case study!

Scroll to Top