Pushpay · ChMS · NDA

Groups:
the rebuild that reshaped the design system

A like-for-like rebuild of the Groups feature in ChMS on Prism, until a board condition turned it into the mandate to modernise the entire design system.

My role

UX Designer. Led the first pass across all Groups sub-tabs, then owned Messages through release. Partnered with the US UX Manager and engineering.

Scope

1 feature · 7 sub-tabs · rebuilt on Prism 1.0

Focus areas

Product UX Prism Modernisation Design-to-code

The brief

A like-for-like
rebuild.

The Groups page in ChMS ran on old styles that predated Prism, Pushpay's design system. The brief was maintenance: rebuild it like-for-like on Prism 1.0, alongside the US UX Manager. No new features.

The work

7 sub-tabs,
one pass.

I designed the first pass across every Groups surface (dashboard, participants, files, messages, settings, needs, and events/calendars), all rebuilt on Prism components. Another designer then took the designs forward; I stayed on Messages through to release. It's shipping now.

Dashboard Participants Files Messages Settings Needs Events / calendars

Before / after screens: coming soon.

The catalyst

A board that
wanted more.

The board approved the rebuild with one condition: consistent, but not modern enough for where the product needed to go. They wanted a modernised UI alongside the consolidation.

That condition became the mandate for our 2026 design system work: modernising the UI, tokens, and architecture at the foundation, so every product built on top would inherit it. See the design system modernisation →

Where it led

The trigger for
a platform.

Consuming the design system on a real product surfaced how much legacy debt it still carried. That gap justified investment in a dedicated design system team: the platform work I now lead.

Read the Design System Platform case →

Next case study

The Design System Platform →
↗