Due to security, no live interface screenshots or proprietary system details can be disclosed.
Nova was a multi-year enterprise UX transformation for a federal defense contractor operating across mission-critical analytics, operational planning, and secure delivery environments. When the work began, there was no formal UX function, no shared design standard, and no unified front-end architecture. Product teams across eight departments were shipping through separate codebases, inconsistent interaction patterns, fragmented workflows, and duplicated implementation effort. My mandate was to build the UX discipline, establish the design-system strategy, create the operating model, and bring a complex application ecosystem under one coherent standard without slowing delivery.
The UX practice was built from zero into a formal delivery function. I partnered with HR to source, interview, hire, and onboard every UX role, then shaped the team into a combined design and UI engineering group of nine: five UX designers and four UI developers.
The role carried full ownership of functional standards, team rituals, delivery quality, and final approval for UX work. Weekly team reviews, 1:1s, performance feedback, annual reviews, mentoring, and direct coaching were used to raise the team's craft level while keeping delivery accountable.
I also owned UX project operations, including backlog prioritization, work assignment, intake discipline, and workflow management through a custom issue-tracking integration built around the team's process. The result was not just a design team, but a functioning UX organization with standards, cadence, and delivery control.
The role held a consistent seat in C-suite and division leadership meetings, representing UX as a strategic function rather than a downstream service. That meant translating design decisions into business value, contract performance, operational risk, development efficiency, and mission impact for non-design audiences.
UX became a leadership-level conversation because the work affected product consistency, delivery speed, training burden, accessibility compliance, and the credibility of software reviewed by senior military and government stakeholders. Final approval for UX work sat here, making the role the quality and standards gate for the entire discipline.
A development background made it possible to operate across design, engineering, and architecture without translation loss. I could evaluate technical constraints directly, contribute to front-end system decisions, and work with engineering leadership as a peer rather than handing off static design intent.
That bridge reduced friction across the organization. Design decisions were shaped with implementation reality in mind, engineering teams gained clearer standards, and product groups had a shared language for discussing interaction quality, accessibility, and system reuse.
I also championed and led the migration to a unified design tooling platform, moving the organization away from legacy workflows and into a shared collaborative environment. By the end of the engagement, 200+ developers and daily active users were operating inside one shared design organization.
A custom internal UX process was designed and documented from the ground up. Rather than importing a generic framework, I created a multi-stage operating model with conditional branch points that adapted to project type, complexity, security constraints, and delivery urgency.
The process was integrated into the organization's existing project management tooling so stakeholders could see where design work stood, what decisions were pending, and how UX deliverables connected to product milestones. That visibility made design more predictable, easier to govern, and harder to bypass.
Nova began with the seed of an established open-source design system, but the requirements of the environment quickly demanded a deeper architecture. The system was reworked so extensively that virtually no original code remained by final release.
The component library scaled deliberately as new microapps were integrated. Each addition was evaluated for reuse, accessibility, implementation cost, and ecosystem impact, preventing the system from becoming a dumping ground of one-off solutions.
Four major versioned releases managed that growth. Each release was triggered when accumulated changes were significant enough to require coordinated adoption across the product ecosystem, preserving consistency across 40+ applications without freezing innovation.
Accessibility was a contractual and operational requirement, not a polish layer. Every component met WCAG AAA where possible, with a hard AA floor on interactive elements so the system could hold up under security, compliance, and field-use expectations.
The color system supported light, dark, and hidden high-contrast modes because different operational environments demanded different visual behavior. Dark mode supported operators working in low-light environments around the clock, light mode served land-based contractors and researchers, and high contrast handled edge cases where maximum visibility was critical.
The token architecture behind those modes was governed through a shared design and development environment, maintaining one source of truth across a 200+ developer organization.
Documentation was treated as part of the product, not an afterthought. I led the documentation strategy and maintenance model across the team, serving two primary audiences: UX designers responsible for product decisions and front-end developers responsible for implementation.
At 150+ pages, the documentation covered component usage, accessibility requirements, interaction patterns, design rationale, and implementation guidance. It gave new contributors a faster path into the ecosystem and gave existing teams a shared standard to return to when decisions became complex.
Across the engagement, tens of thousands of wireframes and mockups were produced, but the larger impact was organizational: UX moved from an absent discipline to a strategic capability with leadership visibility, delivery standards, reusable systems, and a governed operating model.
Nova supported mission-critical applications for target acquisition, payload deployment analysis, and tactical decision-making. The products were used daily by defense personnel and contractors, reviewed by senior military and government leadership, and instrumental in securing significant government contracts. The system gave the organization a way to scale quality across sensitive, complex software without relying on individual heroics or one-off interface decisions.