Back

Back

Banana Stand - A design system case study

A scalable design system to improve consistency, speed, and product quality across Retention.com’s ecosystem.

Role

Product Design Lead (Design System Owner)

Industry

B2B. Ecommerce

status

Retention.com

Year

2023

Describe this image here

Challenge

Retention.com was growing quickly and the UI started to drift. Similar components looked and behaved differently across screens, and new features often introduced new patterns instead of reusing existing ones. The product still worked, but it felt less cohesive and it slowed teams down because we were repeatedly re-deciding basic UI and rebuilding common patterns.

What I needed to solve was not just consistency. It was scalability. We needed a shared system that made it easier to ship fast, keep quality high, and avoid UX regressions as the product evolved.

Success looked like this:

  • A consistent experience across core workflows

  • Reusable components that reduced repeat work

  • Templates that helped teams ship faster with fewer design decisions

  • A system that could expand without becoming chaotic

Process

I focused on clear messaging, a strong visual hierarchy, and a calm layout. The structure was designed to guide users from understanding the service to taking action, while keeping the interface minimal and distraction-free.

Describe this image here

Outcome

The final website communicates value clearly, feels modern and professional, and supports lead generation through a focused and structured layout.

Describe this image here

Back

Banana Stand - A design system case study

A scalable design system to improve consistency, speed, and product quality across Retention.com’s ecosystem.

Role

Product Design Lead (Design System Owner)

Industry

B2B. Ecommerce

status

Retention.com

Year

2023

Describe this image here

Challenge

Retention.com was growing quickly and the UI started to drift. Similar components looked and behaved differently across screens, and new features often introduced new patterns instead of reusing existing ones. The product still worked, but it felt less cohesive and it slowed teams down because we were repeatedly re-deciding basic UI and rebuilding common patterns.

What I needed to solve was not just consistency. It was scalability. We needed a shared system that made it easier to ship fast, keep quality high, and avoid UX regressions as the product evolved.

Success looked like this:

  • A consistent experience across core workflows

  • Reusable components that reduced repeat work

  • Templates that helped teams ship faster with fewer design decisions

  • A system that could expand without becoming chaotic

Process

I focused on clear messaging, a strong visual hierarchy, and a calm layout. The structure was designed to guide users from understanding the service to taking action, while keeping the interface minimal and distraction-free.

Describe this image here

Outcome

The final website communicates value clearly, feels modern and professional, and supports lead generation through a focused and structured layout.

Describe this image here

© 2026 · Ebere Ekeledo

© 2026 · Ebere Ekeledo