Selection Framework


As the lead facilitator, I initiated and guided an idea generation workshop to align UX and Platform teams on needs, use cases, and availability related to the prompt component ecosystem. The goal was to uncover areas where we could consolidate functionality, deprecate redundant code, and increase adoption of Canvas maintained tokens, ultimately streamlining our design and development approach.

  • Cross-Product
  • Design System Migration
  • Framework Design
  • Component Deprication


Intro image
To support product teams with greater clarity and flexibility, I proposed three standardized prompt component offerings: baseline, configurable, and enterprise. Each aligned to Canvas tokens and available in both React and XpressO enviroments. This structure allows teams to adopt the right level of functionality for their use case while ensuring consistency, reducing redundancy, and maintaining system standards.


Overview

Prompted by insights from the Suggestive ML Prompt initiative, we identified significant variation in how the prompt component was implemented across the product suite: multiple versions in separate repositories with overlapping yet inconsistent functionality. Many teams defaulted to the most complex, multi‑select version—resulting in overuse and friction. The Selection Framework consolidates these patterns and standardizes usage.


Role

Lead Designer

Timeline

2024-2025

Partners

Platform PM/Dev, Product PM/Dev, Design System

Surface

Web / Mobile




Impact at a Glance

20k+ tasks enhanced
3 framework offerings
75m+ users effected


Process

Problem

Teams frequently chose an over-powered multi-select component even when it was unnecessary, leading to friction, inconsistency, and code sprawl across the platform.

  • Multiple inconsistent implementations across development.
  • Overuse of complex multi-select patterns.
  • Lack of clear usage guidance.
  • Code duplication and maintenance burden across product.

Approach

A systematic methodology to unify patterns and create a scalable framework that teams could easily adopt and implement consistently. Promote and prototype specific product use cases for a seemless adoption path and zero product downtime.

  1. Lead and facilitate an idea generation workshop in order to extract needs, wants, and team availability across UX and Platform.
  2. Expose areas of opportunity to combine functionalities and deprecate redundant code/components while getting as many Canvas maintained tokens into the prompt component as possible.
  3. Surface a more intuitive way for App Developers to select which component offering they should be utilizing.
  4. Least disruptive path to product teams and Platform development.