Notification Center: designing a platform-wide feature that users said they didn't want

Notification Center is a generic, reusable component that surfaces every notification from every domain across the platform. built for internal advisors, external advisors, and bank partners.

Role

UX Designer — sole designer

Duration

~3 months; not yet launched. a phased pilot rollout is planned

Team

Product Owner, backend engineers, frontend engineers

Industry

Mortgage & financial services

Users

Everyone on the platform; internal advisors, external advisors, and bank partners

Tools

Figma, Miro, Figma Make

Role

UX Designer — sole designer

Duration

~3 months; not yet launched. a phased pilot rollout is planned

Team

Product Owner, backend engineers, frontend engineers

Industry

Mortgage & financial services

Users

Everyone on the platform; internal advisors, external advisors, and bank partners

Tools

Figma, Miro, Figma Make

Notification center
For confidentiality reasons, I can't publish the detailed designs here.

Notification center
For confidentiality reasons, I can't publish the detailed designs here.

Impact

Notification Center hasn't launched yet, so there's no usage data to report. The plan is to roll it out to a small set of pilot groups first, gather real usage and feedback, and then expand it out to the rest of the platform's users.

Notification Center hasn't launched yet, so there's no usage data to report. The plan is to roll it out to a small set of pilot groups first, gather real usage and feedback, and then expand it out to the rest of the platform's users.

Challenge

Unlike most projects, the demand for Notification Center didn't come from users. it came from stakeholders. They were convinced the feature had real value: a single, generic component that could surface every notification from every domain across the platform in one place.

Users, on the other hand, hadn't asked for it and weren't convinced they needed it. The challenge wasn't just designing the component, it was figuring out what would actually make it valuable enough that advisors would want to use it, rather than building something stakeholders wanted and users would ignore.

This was a push, not a pull — nobody asked for Notification Center. The real design problem was proving it deserved a place in a day advisors already felt was full enough.

This was a push, not a pull — nobody asked for Notification Center. The real design problem was proving it deserved a place in a day advisors already felt was full enough.

Approach

01

01

Discover: Aligning stakeholders, users, and every domain on the platform

Discovery started with a stakeholder session to align on terminology and understand how they envisioned Notification Center working in the future. From there, I ran an interview with five advisors to understand how they would actually use a notification center and what would make it genuinely useful to them, rather than just another thing competing for their attention. Because Notification Center pulls in notifications from every domain on the platform, I then met individually with the product owners of each domain to find out which notifications they wanted to surface and which ones actually mattered. the input needed to decide what belonged in the component at all.

02

02

Design & test: Designing for clarity at a glance

With users skeptical of the feature's value going in, the design had to earn its place immediately; clean and noticeable at first sight, with nothing that felt like added noise. I used Figma Make alongside standard wireframing and prototyping to work through the component's states and behavior.

03

03

Launch & irritate: Piloting before a platform-wide rollout

Notification Center hasn't launched yet. The plan is to release it to a handful of pilot groups first, learn from how they actually use it, and iterate before rolling it out more broadly across the platform.