Mandate: Establish a design system and shared standards across teams while keeping creative flexibility.
Scope: UX leadership across financial SaaS experiences; cross‑functional collaboration with Product and Engineering.
Levers: Strategy & Roadmaps, designops, Research Integration, cross_functional
Results: Higher consistency and faster delivery through reusable components; clearer alignment between research insights and planned work.
Design system foundations
Reusable components & tokens
Research → roadmap loop
Mandate & Constraints
Multiple product teams needed a consistent UX language without slowing delivery. Stakeholders wanted visible quality gains and faster iteration, without stifling product‑specific needs.
Decision Framework
Standards with Escape Hatches
Default to the system, but document when and how to deviate responsibly.
Evidence over Preference
Use research and usage data to inform component priorities and patterns.
Design‑Engineering Parity
Component specs, tokens, and a shared backlog so design and code stay in lockstep.
Plays I Ran
Component Library
Developed reusable components with tokens and accessibility guardrails; documented usage patterns.
Governance Light
Introduced review touchpoints and a lightweight intake process to keep consistency without bottlenecks.
Research‑to‑Roadmap
Integrated customer insights into planning, influencing component priorities and design decisions.
Partnering with Engineering & Product
Aligned on specs and delivery sequencing; paired early to de‑risk complexity and ensure parity.
Outcomes & Signals
More consistent product experiences across teams through shared components and tokens.
Faster delivery paths as teams pulled from a vetted component set.
Roadmaps better informed by customer research and usage feedback.
Evidence
Alert Banner — component spec (public-safe)
Component page showing the four alert states with guidance, properties, and tokenized colors for consistent implementation.
UNIFY design system site (public-safe)
Docs home with release notes and component list; establishes the why, what’s included, and links to examples.
Solution overview — lifecycle & value props
Solution page using UNIFY layout components to communicate lifecycle, goals, and value propositions consistently.
What I'd Do Next
Component adoption metrics and dashboards to inform backlog and deprecations.
Partner toolkit for embedding system updates into product team rituals.
See More Work
Browse the case study list or read about how I lead
