LARNELLE CHAMBERSPRODUCT & SYSTEMS DESIGN
Mobile DesignBankingCase Study

Helping transition a large-scale banking product to a stronger, more consistent design system.

1M+Downloads
4.6★Google Play Rating
75+NPS
Overview

I supported the ongoing improvement of the NCB mobile app by helping the product design team transition key experiences into the new design system, creating missing components, and contributing to testing and design quality across the rollout. My work focused on making the app more consistent, easier to scale, and more reliable for both designers and customers.

As the NCB mobile app evolved, different features and journeys had been designed and updated over time by multiple teams. That created a familiar enterprise problem: parts of the product worked well individually, but the overall experience risked becoming visually and structurally inconsistent.

My contribution was centered on helping the team move more of the app into the new design system in a practical, usable way. Rather than owning the full redesign end to end, I played a systems-focused support role: guiding designers through the transition, creating new reusable components where gaps existed, and helping validate the quality of what was being shipped.

My Role
  • Design System Adoption
  • Component Design
  • Quality Support
  • iOS + Android
The Challenge

The app was serving a large, active customer base across iOS and Android, so even small inconsistencies had an outsized effect on usability, trust, and delivery speed.

  • Legacy patterns and newer patterns were coexisting
  • Not every required mobile use case was fully covered by the new design system yet
  • Designers needed support translating existing work into the new system without slowing delivery
  • Feature teams needed reusable components and clearer guidance to avoid one-off solutions
  • Testing and quality checks were important because banking flows have little room for confusion or error

In short, the challenge was not just to make screens look better. It was to help the team build with more consistency and confidence.

01

Helped designers transition to the new design system

One of the biggest needs was helping assigned designers apply the new system in real product work. A design system is only useful if teams can actually use it without friction.

  • Map older patterns to updated system patterns
  • Identify where existing screens could be standardized
  • Reduce avoidable variation in layouts, controls, and interaction patterns
  • Make design decisions that aligned more closely with the shared system
02

Created new components and filled system gaps

As teams applied the new design system to real banking flows, gaps naturally appeared. Some mobile-specific needs were not yet fully supported by the available component set.

  • Reusable mobile UI patterns
  • Clearer states and behaviours
  • Consistency across iOS and Android contexts
  • Better alignment between product needs and the design system library
03

Supported consistency across the app

Large banking products often become fragmented when different teams solve similar problems in slightly different ways. I helped reduce that fragmentation by reinforcing shared patterns and encouraging reuse over reinvention.

  • Component usage
  • Spacing and layout consistency
  • Hierarchy and information clarity
  • Standardization of common UI patterns
  • Stronger alignment between visual design and system rules
04

Contributed to testing and design validation

Because this was a banking product, quality and clarity mattered at every step. I supported testing and review efforts to help ensure that the updated designs held up in practice.

  • Reviewing flows before handoff or release
  • Checking that new components worked as intended in context
  • Identifying inconsistencies or friction points
  • Supporting validation of designs against expected behaviour and quality standards
Outcome and Impact

My work helped strengthen the app in a few key ways. First, it made it easier for designers to work within a more unified system instead of creating isolated solutions. Second, it expanded the design system through real product needs, which improved its usefulness over time. Third, it supported a more consistent and polished customer experience across the app.

The broader product continued to perform strongly, with 1M+ downloads, a 4.6★ rating on Google Play, and 75+ NPS. While those outcomes were the result of a larger team effort, my contribution helped support the consistency, scalability, and design quality behind that experience.

This project reinforced something I care about deeply: strong digital products are not improved by isolated screens alone. They improve when teams can work from a shared system, close gaps thoughtfully, and keep quality high as the product evolves. For a mobile banking experience, that kind of behind-the-scenes design systems work can have a meaningful effect on both delivery and customer trust.

Snapshot
1M+Downloads
4.6★Google Play Rating
75+NPS