Hero Carousel Redesign

Rebuilding the main hero experience for scalability, usability, and impact

My contributions: Design system unification and contribution, workshop facilitation, user testing, product strategy, UX/UI design, accessibility

Context

The web platform underwent a complete site redesign and needed a new hero carousel component that is responsive.

Problem

The inconsistent hero carousel designs on Pluto created implementation hurdles for engineering. The current design is also unable to handle various content metadata and as the result, negatively impacts the overall user engagement, making it feels less premium and out of sync with the new redesign.

Solution

A unified hero carousel design capable of handling various metadata permutations while maintaining a consistent and premium look across all breakpoints. This solution streamlined engineering efforts, allowing for easier implementation and scalability for future updates.

Impact

From testing, we saw a 20% increase in engagement in the treatment group (new hero carousel group) in comparison to the controlled group.

Experiment Results

Experiment
Results

The following data tracks the performance of the two hero carousel designs:
Control: Older hero carousel design
Treatment: New hero carousel design that was previously delivered
Results: Users are not engaging with the new hero carousel and out of those that do engaged, about half of those users are engaging further with its content

Hypothesis

Hypothesis

Hypothesis

Hypothesis

Hypothesis

After reviewing the experiment results, we hypothesize that users weren't interested in engaging with the hero carousel because the new designs lacked the peek-ahead tiles present in the control group. I've since gone back to the drawing board to incorporate these tiles into the new designs, ensuring they're responsive across various screen sizes.

After reviewing the experiment results, we hypothesize that users weren't interested in engaging with the hero carousel because the new designs lacked the peek-ahead tiles present in the control group. I've since gone back to the drawing board to incorporate these tiles into the new designs, ensuring they're responsive across various screen sizes.

After reviewing the experiment results, we hypothesize that users weren't interested in engaging with the hero carousel because the new designs lacked the peek-ahead tiles present in the control group. I've since gone back to the drawing board to incorporate these tiles into the new designs, ensuring they're responsive across various screen sizes.

After reviewing the experiment results, we hypothesize that users weren't interested in engaging with the hero carousel because the new designs lacked the peek-ahead tiles present in the control group. I've since gone back to the drawing board to incorporate these tiles into the new designs, ensuring they're responsive across various screen sizes.

After reviewing the experiment results, we hypothesize that users weren't interested in engaging with the hero carousel because the new designs lacked the peek-ahead tiles present in the control group. I've since gone back to the drawing board to incorporate these tiles into the new designs, ensuring they're responsive across various screen sizes.

Additional Issues

Additional Issues

Additional Issues

Additional Issues

Additional Issues

There are several hero carousel designs implemented across different pages that are not able to handle the various permutations of metadata (see below). The new design should unify all existing designs, consider each Pluto pages unique needs, and create a new hero carousel component that can handle various metadata scenarios and future features such as premium and locked content.

There are several hero carousel designs implemented across different pages that are not able to handle the various permutations of metadata (see below). The new design should unify all existing designs, consider each Pluto pages unique needs, and create a new hero carousel component that can handle various metadata scenarios and future features such as premium and locked content.

There are several hero carousel designs implemented across different pages that are not able to handle the various permutations of metadata (see below). The new design should unify all existing designs, consider each Pluto pages unique needs, and create a new hero carousel component that can handle various metadata scenarios and future features such as premium and locked content.

There are several hero carousel designs implemented across different pages that are not able to handle the various permutations of metadata (see below). The new design should unify all existing designs, consider each Pluto pages unique needs, and create a new hero carousel component that can handle various metadata scenarios and future features such as premium and locked content.

There are several hero carousel designs implemented across different pages that are not able to handle the various permutations of metadata (see below). The new design should unify all existing designs, consider each Pluto pages unique needs, and create a new hero carousel component that can handle various metadata scenarios and future features such as premium and locked content.

All currently implemented hero carousel designs are incompatible with the new Pluto web redesign, each with its own specific reasons.

All currently implemented hero carousel designs are incompatible with the new Pluto web redesign, each with its own specific reasons.

Metadata Permutations Consideration

Metadata Permutations
Consideration

Before figuring out the exact dimensions for the hero carousel, a thorough understanding of how the metadata can change is critical. Outlined in red below, are ways that the metadata block can mutate across a variety of content types.

A few examples of how each permutation might differ from one another in the hero carousel

A few examples of how each permutation might differ from one another in the hero carousel

Mobile Considerations

After understanding how much space this component might require to handle various metadata permutations, I needed to consider how it'll work on mobile devices since smaller screens have limited real estate.

Iterations of mobile and tablet hero carousel designs

Iterations of mobile and tablet hero carousel designs

Iterations of mobile and tablet hero carousel designs

Designs

Designs

Designs

Designs

Final designs is able to contain all metadata permutations across a wide array of content types. The final designs can display all metadata permutations across a wide array of content types. On smaller devices, only the most pertinent information will be shown, helping users make a quick watch decision.

Final designs is able to contain all metadata permutations across a wide array of content types. The final designs can display all metadata permutations across a wide array of content types. On smaller devices, only the most pertinent information will be shown, helping users make a quick watch decision.

Final designs is able to contain all metadata permutations across a wide array of content types. The final designs can display all metadata permutations across a wide array of content types. On smaller devices, only the most pertinent information will be shown, helping users make a quick watch decision.

Final designs is able to contain all metadata permutations across a wide array of content types. The final designs can display all metadata permutations across a wide array of content types. On smaller devices, only the most pertinent information will be shown, helping users make a quick watch decision.

Retro

My main challenge with this project was unifying a high-traffic component into a flexible system that could support a diverse range of content types. This push for flexibility meant I had to think systematically, accounting for a wide range of use cases while prioritizing consistency, scalability, and maintainability. Collaboration was key; working closely with product, programming, SEO, and accessibility teams helped me understand platform constraints and broader strategies, ultimately leading to the final solution.

My main challenge with this project was unifying a high-traffic component into a flexible system that could support a diverse range of content types. This push for flexibility meant I had to think systematically, accounting for a wide range of use cases while prioritizing consistency, scalability, and maintainability. Collaboration was key; working closely with product, programming, SEO, and accessibility teams helped me understand platform constraints and broader strategies, ultimately leading to the final solution.

My main challenge with this project was unifying a high-traffic component into a flexible system that could support a diverse range of content types. This push for flexibility meant I had to think systematically, accounting for a wide range of use cases while prioritizing consistency, scalability, and maintainability. Collaboration was key; working closely with product, programming, SEO, and accessibility teams helped me understand platform constraints and broader strategies, ultimately leading to the final solution.

CN

PRODUCT DESIGNER

CN

PRODUCT DESIGNER

Crafting experiences.
Delivering results.
Powered by design & data.

Problem Solver

User Research

Strategy

UX UI

Design Systems

Avid Snowboarder

LA

CURRENTLY

Pluto TV | Paramount

Product Designer

PREVIOUSLY

Digital Karma

Product Designer

Clinwiki

UX Researcher

copyright 2025

Crafting experiences.
Delivering results.
Powered by design & data.

Problem Solver

User Research

Strategy

UX UI

Design Systems

Avid Snowboarder

LA

CURRENTLY

Pluto TV | Paramount

Product Designer

PREVIOUSLY

Digital Karma

Product Designer

Clinwiki

UX Researcher

copyright 2025

Crafting experiences.
Delivering results.
Powered by design & data.

Problem Solver

User Research

Strategy

UX UI

Design Systems

Avid Snowboarder

LA

CURRENTLY

Pluto TV | Paramount

Product Designer

PREVIOUSLY

Digital Karma

Product Designer

Clinwiki

UX Researcher

copyright 2025