Back home
EXIT RULES / CASE STUDY
Reducing Journey Bloat by 72% with Automated Exit Rules
Reducing Journey Bloat by 72% with Automated Exit Rules


01 / Overview
Exit Rules addressed a core platform gap for logic configuration in automated subscriber journeys.
MY ROLE
Product Design Lead
Conducted UX research, led migration of previous treatment to new design implementation.
CORE TEAM
Product Management, Journeys Engineering
COLLABORATORS
Product Marketing, Client Strategy
02 / The challenge
Journeys are automated series of emails triggered when a subscriber takes an action, like someone abandoning their shopping cart. Marketers set conditions that remove a subscriber if they become ineligible along the way (e.g. a purchase is made). Clients had to set repetitive exit conditions every time they wanted to add custom logic, resulting in very bloated logic that was frustrating to navigate.
03 / Research & key decisions
This feature was critical for platform parity with competitors, was a major blocker for large enterprise contracts, and was upvoted as a product feature request 75 times. Safe to say we had conviction!
As the design lead, I defined the following UX goals:
Reuse existing platform patterns to reduce cognitive load for this new journeys interaction and leverage existing components to minimize engineering scope.
Ensure the entry point is discoverable while clearly communicating that exit rules are evaluated continuously throughout the journey.
Make transition to automated exit rules seamless for users, minimizing required journey edits and making the feature easy to adopt.
EARLY EXPLORATIONS
Version 1: I placed the entry point via journey trigger settings, opening a drawer to configure exit rule logic.


Automated Journey page with a drawer to configure exit rules logic.
Ultimately, the drawer was too crowded to support complex logic, and the entry point implied exit rules were tied to the trigger.
04 / PRODUCT EXECUTION
We placed the entry point in the page header, where other journey settings lived. Exit rules are extremely important for journey operations, so we believed it deserved prime real estate. Clicking it opens a fullscreen view where users build combinations of exit logic. This reused an existing rule-building tool from elsewhere in the product, so it felt familiar to users and required less engineering scope.
We also added a "mega-selector" component to our design library that allows users to first select a category, and then surfaces the relevant options per category. One menu, tonnnns of options.


Exit rule condition builder with a "mega-selector" to choose product or subscriber conditions.


Adding multiple rules to apply to exit subscribers.
Now that exit rules were handled at the top-level, the reporting surface needed to be clear about subscribers removed due to an exit rule. Separating exit rules into its own widget helps marketers:
Better understand journey performance
Distinguish intentional exits from other removal reasons (data issues, unsubscribes) to optimize accordingly


Users can easily view exit logic without it clouding the journey map.


Metrics for exit conditions are stored in the performance drawer.
The trade-offs behind the design
Every project has scope changes and technical hurdles, but I believe navigating these is where a product designer shines. These are the moments we advocate for the user, while helping our product partners arrive at a solution.
01 / Planning for future complexity
Challenge: The initial engineering scope covered only simple exit conditions, but I knew we would eventually add more complex ones. We needed a solution we could build quickly while setting us up to expand when resources became available.
This project began in early 2024, long before any email content generation service was popular in the market. My engineer and I wrote our own taxonomies, and I dug in the weeds with him to prompt and iterate the model. Major startup energy!
How I approached it: I placed the exit rule builder in its own fullscreen modal. While this added slight friction away from the main journey map, it avoided introducing another pattern later. Users would only need to learn the pattern once.
This project began in early 2024, long before any email content generation service was popular in the market. My engineer and I wrote our own taxonomies, and I dug in the weeds with him to prompt and iterate the model. Major startup energy!
05 / Outcomes & reflection
Within one week of launch, journeys using exit rules saw a median 72% reduction in branches needed. By removing repetitive branching, exit rules cut journey bloat and make journeys easier to navigate. This also closed a commonly cited gap in enterprise contracts. Today, 3,000+ unique users have adopted exit rules, with over 26,000 feature interactions.
Next project
Back home
EXIT RULES / CASE STUDY
Reducing Journey Bloat by 72% with Automated Exit Rules
Reducing Journey Bloat by 72% with Automated Exit Rules


01 / Overview
Exit Rules addressed a core platform gap for logic configuration in automated subscriber journeys.
MY ROLE
Product Design Lead
Conducted UX research, led migration of previous treatment to new design implementation.
CORE TEAM
Product Management, Journeys Engineering
COLLABORATORS
Product Marketing, Client Strategy
02 / The challenge
Journeys are automated series of emails triggered when a subscriber takes an action, like someone abandoning their shopping cart. Marketers set conditions that remove a subscriber if they become ineligible along the way (e.g. a purchase is made). Clients had to set repetitive exit conditions every time they wanted to add custom logic, resulting in very bloated logic that was frustrating to navigate.
03 / Research & key decisions
This feature was critical for platform parity with competitors, was a major blocker for large enterprise contracts, and was upvoted as a product feature request 75 times. Safe to say we had conviction!
As the design lead, I defined the following UX goals:
Reuse existing platform patterns to reduce cognitive load for this new journeys interaction and leverage existing components to minimize engineering scope.
Ensure the entry point is discoverable while clearly communicating that exit rules are evaluated continuously throughout the journey.
Make transition to automated exit rules seamless for users, minimizing required journey edits and making the feature easy to adopt.
EARLY EXPLORATIONS
Version 1: I placed the entry point via journey trigger settings, opening a drawer to configure exit rule logic.


Automated Journey page with a drawer to configure exit rules logic.
Ultimately, the drawer was too crowded to support complex logic, and the entry point implied exit rules were tied to the trigger.
04 / PRODUCT EXECUTION
We placed the entry point in the page header, where other journey settings lived. Exit rules are extremely important for journey operations, so we believed it deserved prime real estate. Clicking it opens a fullscreen view where users build combinations of exit logic. This reused an existing rule-building tool from elsewhere in the product, so it felt familiar to users and required less engineering scope.
We also added a "mega-selector" component to our design library that allows users to first select a category, and then surfaces the relevant options per category. One menu, tonnnns of options.


Exit rule condition builder with a "mega-selector" to choose product or subscriber conditions.


Adding multiple rules to apply to exit subscribers.
Now that exit rules were handled at the top-level, the reporting surface needed to be clear about subscribers removed due to an exit rule. Separating exit rules into its own widget helps marketers:
Better understand journey performance
Distinguish intentional exits from other removal reasons (data issues, unsubscribes) to optimize accordingly


Users can easily view exit logic without it clouding the journey map.


Metrics for exit conditions are stored in the performance drawer.
The trade-offs behind the design
Every project has scope changes and technical hurdles, but I believe navigating these is where a product designer shines. These are the moments we advocate for the user, while helping our product partners arrive at a solution.
01 / Planning for future complexity
Challenge: The initial engineering scope covered only simple exit conditions, but I knew we would eventually add more complex ones. We needed a solution we could build quickly while setting us up to expand when resources became available.
This project began in early 2024, long before any email content generation service was popular in the market. My engineer and I wrote our own taxonomies, and I dug in the weeds with him to prompt and iterate the model. Major startup energy!
How I approached it: I placed the exit rule builder in its own fullscreen modal. While this added slight friction away from the main journey map, it avoided introducing another pattern later. Users would only need to learn the pattern once.
This project began in early 2024, long before any email content generation service was popular in the market. My engineer and I wrote our own taxonomies, and I dug in the weeds with him to prompt and iterate the model. Major startup energy!
05 / Outcomes & reflection
Within one week of launch, journeys using exit rules saw a median 72% reduction in branches needed. By removing repetitive branching, exit rules cut journey bloat and make journeys easier to navigate. This also closed a commonly cited gap in enterprise contracts. Today, 3,000+ unique users have adopted exit rules, with over 26,000 feature interactions.
Next project