First Report — three new features for a decade-old security portal.
Lead UI (supporting UX) on a six-week engagement: add a new subscription model, in-app feedback surveys, and parent/child account support to an existing security-monitoring portal — making each feel native to a long-running design language.
Snapshot
What I shipped
Problem
The portal monitored personal accounts (email, phone, credit, banking, social insurance) for breaches. The client needed three new features layered into a design system that had calcified over a decade.
What I did
Rebuilt the UX flows with the dedicated UX designer to integrate new features. Created a limited component guide for client alignment. Ran three week-long sprints producing fi-fi responsive layouts.
Outcome
New features that read as native to the existing system, parent/child accounts cleanly architected for the subscription model, and mobile designs that gave the client a clear next-step for responsive build.
The hard problems.
Parent/child + subscription = an architecture decision, not a UI one.
The client's ideal subscription model needed to support a primary account paying for and managing multiple child accounts — including kids' accounts with different visibility rules. The UX needed to make permissions legible to non-technical users without leaking the underlying account hierarchy. The frame: think of it like a family plan, not a B2B admin console.
Designing for a non-responsive portal.
The existing portal was desktop-only, but the new features had to scale to mobile contexts (especially the feedback surveys). Designing mobile-first against a design system that had never seen a small viewport meant choosing which patterns to break and which to translate.
Fresh UI in a 10-year-old DS.
The challenge wasn't making the new components feel new — it was making them feel like they'd always been there. The component guide isolated the few places we earned a real visual departure from the legacy system, and held everything else to existing tokens.