Making complexity feel effortless.
Designing a luxury vehicle shopping experience connecting vehicle discovery, pricing, and different paths to ownership.
Outcome
Tab-based financing experience launched on Genesis.com, serving nine Genesis models across cash, lease, and finance options.
my role
Art Director — Product UI/UX
timeline
One-year product initiative
See the decision that protected scalability
Overview
Challenge
Discovery
System
Boundaries
Experience
Impact
Leadership
Reflection
overview
9 Genesis models · Cash / Lease / Finance · Desktop + Mobile
The experience served the nine Genesis models available at the time, with variations for electric vehicles. The focus was on bringing these parts of the shopping journey together while maintaining the visual quality and attention to detail expected from Genesis.
Beyond the beautiful cars.
Shopping for a luxury vehicle involves more than finding the right model. There's inventory, pricing, financing, trade-ins, and a series of decisions that all need to work together.
At INNOCEAN USA, I worked as an Art Director focused on Product UI/UX, as part of a four-person design team. My work covered desktop and mobile interfaces, payment interactions, conditional pricing states, and design QA.
challenge
One experience. A lot of moving parts.
The project involved connecting vehicle discovery, inventory availability, pricing, financing, and the next steps toward ownership.
Each payment path came with its own requirements. Pricing varied depending on the retailer, incentives, location, and availability. Customers could continue online or connect with a retailer or Genesis Concierge.
The challenge was finding the right balance between the information customers needed, the business rules behind it, and a clean, intuitive interface.
Simplified from the team's DRS flow.
My approach started with understanding how those pieces worked together. I collaborated with Product, Finance, Engineering, Marketing, and QA to work through the requirements, explore interaction patterns, and refine the designs through multiple rounds of feedback.
One journey, three paths, several next steps
design
One vehicle. Three ways to buy.
Designing the financing experience.
The financing section was one of the more involved parts of the project. Cash, lease, and finance each required different calculations, inputs, and offers. We needed a way to accommodate all three while keeping the experience familiar and easy to navigate.
Exploring the options. I worked through radio buttons, separate cards, and tabs for payment selection. We also explored ways to highlight the selected state, focusing on visibility, clarity, and how the interaction worked within the Genesis visual system. The options went through internal exploration and review with the Finance team.
Working through the details. One of the bigger discussions was incorporating trade-ins into the payment calculations. It introduced additional inputs, financial considerations, and interface states. After reviewing the options, the team agreed that trade-ins were necessary for a more complete shopping experience.
Selection continued downstream
Decisions reopened during onboarding when the experience didn't prepare customers for implementation.
2
The iterations
1
The shipped experience
Flexibility had a lifecycle cost
Configuration choices multiplied complexity across CMS, QA, Engineering, and delivery.
The problem
The final direction. Finance approved the tab-based approach. Keeping cash, lease, and finance visible together gave customers a clear view of their options, with each tab presenting the controls and information relevant to that payment method.
1
From design to launch. The approved tab-based financing experience launched on Genesis.com, serving the nine-model lineup with variations for electric vehicles.
2
The explorations
1
The problem
journey
Theme selection was only one moment in a larger journey
Discovery showed us that choosing a theme wasn’t an isolated decision. It connected what customers understood about the product with what Sales, onboarding, and Implementation needed to deliver it successfully.
The selector had to support the decision in front of the customer—and the work that followed it.
system
Designing the collections and the selector as one system
The Theme Selector needed a coherent product model to recommend. At the same time, the collections needed shared principles before customers could meaningfully compare them.
While I worked with the UX Lead on the selector workflow, I directed the design team in defining the collection systems—translating Product and Engineering requirements into a framework that could work consistently across themes.
The work came down to three strategic decisions.
Audience, not trends
LeaseLabs served properties with very different audiences, markets, and business needs. I introduced persona-based thinking to define what each collection needed to support—from content and functionality to voice, visual expectations, and level of configuration.
The personas were product-planning tools, not decorative profiles.
Standardize foundations, not identity
Themes shared structural foundations—component behavior, responsive rules, and implementation standards—while typography, color, imagery, composition, and voice gave each collection its own identity.
Consistency belonged in the system. Differentiation belonged in the experience.
Build in parallel
We didn't finish the collections and then design a selector around them. The selector helped define what customers needed to understand and compare, while the collection systems determined what the product could meaningfully organize, recommend, and configure.
customer journey
the shared product foundation
delivery system
different experiences. one scalable product.
Boundaries
More flexibility would have made the product less scalable
As we defined the Theme Selector, one idea seemed especially attractive: let customers mix and match components across themes.
From a customer perspective, it sounded like more freedom. But when we evaluated the idea across Engineering, QA, CMS, Implementation, and Product, the trade-off became clear.
Every additional combination created complexity that had to be designed, built, tested, supported, and explained downstream.
What if customers could combine these?
one coherent theme
one component from another theme
the system starts becoming custom again
the boundary
Personalize the experience. Protect the system.
I recommended that customers personalize within a selected theme rather than mix components across themes. This gave them meaningful control over the parts of the experience that expressed their property and brand, while protecting component relationships, responsive behavior, accessibility, product quality, and operational scalability.
This wasn't about limiting choice for the sake of simplicity. It was about putting flexibility where it created value without transferring unnecessary complexity into Engineering, QA, CMS, and Implementation.
impact
The product model turned repeated custom decisions into a reusable system—giving customers a clearer path to the right website while making delivery more predictable for the teams behind it.
What changed
Scale +
adoption
The platform grew to 42 property sites as additional themes were built on the shared foundation.
of new clients chose the premium Theme option over a fully custom build.
PRODUCT FOUNDATION
8 core themes · 11 flexible containers · 20 shared design tokens
A reusable foundation across color, typography, patterns, components, and responsive behavior
On nearly every site we launched, I also checked color contrast and type legibility
10 premium Plus Layout templates personally designed and delivered
Speed + delivery
Average delivery time for theme-based sites
Theme-based sites reduced the path from initial Sales contact to delivery from roughly eight weeks to five.
Component reuse reduced UI issues found during QA by an estimated 20%.
Business+ operations
Shared components and systems reduced repetitive Design and Engineering work.
Reusable foundations helped support more properties and larger portfolios without proportionally increasing Design and Implementation effort.
The framework supported premium themes that later became part of the RealPage platform.
After the first collection themes launched, Google Analytics and LogRocket showed us what was working, and we adjusted the early designs
The result wasn't simply a faster way to build websites. It was a more repeatable way to turn LeaseLabs' expertise into a product.
leadership
What I led
I led a team of nine designers through hiring, onboarding, coaching, and critiques, and rebuilt our critique culture around structured sessions that brought designers and developers together earlier.
As the initiative expanded, my role grew from defining the original premium direction into product strategy, design systems, cross-functional discovery, and team leadership.
My focus shifted from designing every answer to creating the direction and shared foundations that helped the team make stronger decisions together.
Connecting strategy, systems, and people to build a product customers can trust.
shared product direction
Connected the collection strategy to the broader product ecosystem.
I helped shape how collections, the Theme Selector, customer journey, and implementation model worked as parts of one product rather than separate initiatives.
Directed the shared foundations across collections
I translated Product and Engineering requirements into reusable structures and standards while preserving the distinct identity of each collection.
DESIGN SYSTEMS
Helped teams see the complete lifecycle
Working with the UX Lead, I brought together perspectives from Product, Sales, Engineering, QA, Customer Success, Implementation, and Design to uncover dependencies and trade-offs across the experience.
PRODUCT DIRECTION
CROSS-FUNCTIONAL DISCOVERY
TEAM ALIGNMENT
Created a framework designers could make decisions within
I translated product constraints and strategic principles into briefs, system guidance, design reviews, and shared standards—giving the team room to explore while keeping the product coherent.
PRODUCT BOUNDARIES
Protected the parts of the system that needed to remain stable
I recommended configuration boundaries that preserved meaningful customer choice while protecting component relationships, product quality, and operational scalability.
The goal wasn't to make every decision myself. It was to create enough clarity for the team to make strong decisions—and enough structure for the product to scale.
still hands-on
Alongside product strategy and team leadership, I stayed close to the craft—designing production-ready templates while helping establish the systems they shared.
For the supporting system callout:
8 core themes · 11 flexible containers · 20 shared design tokens
reflection
What this project reinforced
I started by designing one premium website template. As the work expanded, so did the problem—from a single experience into a system connecting collections, customer choice, reusable components, Sales, onboarding, and implementation.
The most important decision wasn't how an individual theme looked. It was understanding where the product should remain flexible—and where constraints created greater value.
The experience reinforced something I still bring to product work today: the interface is only one part of the problem. Stronger decisions come from understanding the system around it—the people, dependencies, and trade-offs that determine whether an experience can work at scale.
the beginning
a premium template
collections
system
selector
what it became
a reusable product foundation
Understand the complete system.
Make the trade-offs visible.
Give teams enough clarity to build the right thing together.
NEXT
CHAPTER
Designing premium digital experiences inside the Genesis ecosystem
Enterprise standards, complex delivery requirements, and premium customer journeys across automotive products.
case study coming soon

