Designing clarity into complexity. I partner with product, engineering, and business stakeholders to transform data heavy systems and intricate workflows into intuitive, scalable enterprise experiences.
With over 10 years of end-to-end UX leadership across enterprise software and regulated environments, I specialize in translating ambiguous, data rich challenges into design systems and workflows that scale and that real users actually adopt.
Role based interfaces, multi-step processes, and high stakes operational tools built for power users.
Aligning design decisions to business goals, technical constraints, and long-term product vision.
Component libraries, tokens, and pattern documentation that drive consistency across product suites.
Stakeholder interviews, usability testing, and workflow mapping that ground design in real-world evidence.
WCAG-aligned, screen-reader-tested experiences that serve every user across enterprise contexts.
Dense information architectures made scannable, actionable, and legible at a glance.
Figma · FigJam · Miro
Jira · Confluence · Notion
AI tools for research synthesis, ideation acceleration, and rapid prototyping.
Each case study reflects a distinct dimension of enterprise UX, from platform wide workflow redesign to systems level design infrastructure to research led transformation. Together, they tell the story of a designer who leads with strategy and ships with precision.
Role based, data heavy enterprise tools with complex workflows redesigned for clarity, speed, and operational accuracy.
A component based design system built from the ground up to drive consistency, velocity, and trust across a multi-product suite.
A research first approach that reshaped usability, accessibility, and product adoption across a critical internal platform.
Role: UX Lead / Product Designer
Context: Enterprise internal operations platform
Users: Analysts, operations associates, and business leads
Constraints: Regulated environment, legacy technical dependencies, 500+ concurrent users
Core operational workflows were fragmented across four disconnected tools, forcing analysts to manually reconcile data across sessions. Error rates were climbing, onboarding new associates took 6+ weeks, and no unified role model existed, every user saw everything, regardless of context. The business risk was measurable and urgent.
Discovery surfaced 14 distinct workflow patterns across three user roles. Stakeholder interviews with operations leads, compliance officers, and engineering architects shaped a design strategy grounded in role based access, progressive disclosure, and task specific information density.
A single platform with three distinct role views, each surfacing only the data and actions relevant to that user's workflow context, reducing cognitive load dramatically.
Complex multi-step workflows were restructured using collapsible panels, contextual drawers, and inline validation, reducing visible complexity without sacrificing power-user depth.
All new components contributed back to the shared design system, ensuring future platform extensions could reuse patterns rather than reinvent them.
Average time on task dropped across all three primary workflow types post launch.
New associate onboarding time reduced from six weeks to two with the redesigned guided workflow experience.
Post launch stakeholder survey rated the redesign as "significantly improved" or better across all measured dimensions.
Role: Design Systems Lead
Context: Multi-product enterprise SaaS suite
Users: Product designers, front-end engineers, product managers
Constraints: 4 active product teams, inconsistent legacy UI, no shared component ownership
Four product teams were designing in parallel with no shared vocabulary. Buttons had six variants. Forms had nine. Color usage was undocumented and inconsistent. Engineering was rebuilding components from scratch every sprint. The result: slower velocity, visual fragmentation, and a user experience that felt like four different products because it was.
Catalogued every unique UI pattern across all four products, 200+ components, 40+ color values, inconsistent spacing scales. Built the case for systemic investment.
Defined a semantic token system for color, typography, spacing, and elevation, giving engineering a single source of truth that mapped directly to Figma variables.
Designed and documented 60+ reusable components with variant states, accessibility annotations, interaction specs, and usage guidance, structured for Storybook handoff.
Established a contribution model, RFC process, and design system office hours to maintain system health and drive adoption across all teams without top down mandates.
One Figma library. One Storybook. One token file synced between design and code eliminating the translation gap that was costing teams 3+ hours per sprint.
Every component shipped with WCAG 2.1 AA compliance documentation, focus states, and screen reader annotations, removing accessibility as a retrofitting burden.
A Confluence-integrated documentation site with usage principles, do/don't examples, and a decision log, keeping the system transparent and trustworthy over time.
Teams reported dramatically reduced handoff cycle time within two sprints of system adoption.
Four quarters post launch, 80% of all new UI was built from system components rather than custom solutions.
All 60+ system components shipped with verified accessibility compliance from day one.
Role: UX Researcher & Designer
Context: Critical internal data management platform
Users: Editors, data stewards, and compliance reviewers
Constraints: Low adoption, high support ticket volume, accessibility gaps, stakeholder skepticism about UX investment
A business critical internal platform had a 34% adoption rate despite being mandatory for data compliance workflows. Users were routing around it, using spreadsheets and email threads instead. The UX was dense, unlabeled, and inaccessible. Leadership needed evidence before approving a redesign. That evidence had to come from research.

Twelve contextual inquiry sessions surfaced a 47 item usability problem backlog. A prioritized journey map was presented to senior leadership as the business case for redesign, shifting the conversation from "should we invest?" to "how fast can we start?"
Reduced the primary navigation from 11 items to 5, organized around user tasks rather than system modules, matching the mental models surfaced in research.
Inline tooltips, progressive onboarding, and empty-state messaging replaced the 40 page PDF user guide that no one read, embedding support where work happens.
22 WCAG violations resolved. Keyboard navigation, ARIA labels, and color contrast corrections made the platform usable for users with assistive technology, for the first time.
A pilot group of 40 users tested the redesign before full release, with structured feedback sessions informing two final refinement sprints before organization wide deployment.
Adoption more than doubled within 90 days of the redesign launch, exceeding the project's stated goal of 60%.
Monthly support tickets related to platform confusion dropped by 61% in the first quarter post launch.
All 22 documented WCAG 2.1 violations were resolved before the redesign shipped to production.
I'm a Senior Product Designer with deep expertise in enterprise UX, the kind of work where clarity isn't optional, where scale exposes every design flaw, and where the user sitting behind that interface is making decisions that matter. I've spent my career in environments where complexity is a given and good design is a competitive advantage.
MS, Industrial/Organizational Psychology — In Progress
BS, Industrial/Organizational Psychology
BS, Information Technology
My dual background in human behavior and technology systems gives me a rare lens: I understand both why people struggle with complex tools and how to redesign them at the system level.
I see the whole before I solve the part. Workflows, data models, user roles, and business constraints are all inputs to design, not obstacles to it.
I don't assume. I ask, observe, and validate. Research isn't a phase I complete, it's a practice I maintain throughout the entire product lifecycle.
I translate design rationale into business language, building alignment across product, engineering, and leadership without losing what makes the design right for users.
Enterprise UX is never simple. My passion is finding the elegant solution inside the complicated problem and defending it when it matters.
Every design decision traces back to a real person doing real work. User needs are not a filter, they are the foundation.
Good design doesn't exist in opposition to business goals. The best work I've done has been where user value and business value are indistinguishable.
Intuition is a starting point, not a conclusion. I use qualitative and quantitative signals to pressure test assumptions and sharpen decisions.
Accessibility is not a checklist item at the end of a project. It's a design constraint I work with from the first wireframe to the final handoff.
I'm actively open to senior product design and enterprise UX opportunities, particularly roles involving complex workflows, data heavy systems, or design systems at scale. If you're building something hard and you need a designer who leads with strategy and executes with care, I'd love to connect.
Complex, data driven platforms where UX strategy drives real business outcomes and user impact.
Cross functional Agile teams where design has a meaningful seat at the product and engineering table.
Regulated industries, internal tooling, or platform scale problems that reward rigorous, thoughtful design process.
Charlotte, NC
msvictoriaussery@gmail.com
704-805-0015
© 2026 Victoria Ussery. All rights reserved.
Senior Product Designer & Scrum Master