Defense analytics · Design system · NDA

I rebuilt the design system behind a defense procurement platform.

I'm the sole designer on a platform for public defense contract and budget data. I own the design system and design the program pages, export tools, and navigation. The prototype below recreates a program page I designed. The program and all its data are fictional.

ClientDefense analytics platform (NDA)
My roleSole designer, system owner
SystemDesign System 2.0 · light + dark
TimelineMar 2026 · ongoing
DocumentedAnatomy · states · behaviors · edge cases
30component families, including charts and filters.
691design tokens in 7 collections, with light and dark themes.
8chart families mapped to engineering's Recharts library.
FIG. 01 · Program entity page Fictional data
I recreated the program overview with its budget breakdown, Requested vs Enacted chart, and contract details. Scroll inside the frame and hover over the chart to see the figures. Only Overview is available in this prototype. All data is fictional.

The same color meant different things on different screens.

The users work across defense acquisition: budget analysts, program staff, and industry teams. They need to read budget lines, appropriation types, and contract vehicles across ten fiscal years at a time. When I joined, components had become inconsistent and colors had different meanings across screens.

I started by auditing the existing product to see what I needed to keep and what needed to change.

I defined shared rules for color, charts, and program pages.

I reserved specific colors for budget categories.

I kept the interaction color out of charts and gave chart series a fixed color order. The three budget category colors appear only in the Color of Money card. Each category keeps its color wherever that card appears.

Missing figures need to stay visible.

I designed the Requested vs Enacted tooltip to show the request's base and reconciliation amounts, the enacted figure, and the difference. Where enacted figures aren't available, the line stops and the tooltip says "no data." Showing $0 there would imply a known amount.

FIG. 02 · Chart library specimens Fictional data
Six examples from the chart library's eight families. I mapped the shared style tokens and ten-color palette to engineering's Recharts library. The waterfall shows the adjustments between requested and enacted amounts. The treemap groups vendors to keep the chart within five tiles.

One page per program

I put the program's identity and owner first, followed by its budget and the companies receiving contracts. Recent news and solicitations sit below. Additional tabs hold the detail. I shortened long descriptions with a "Read more" link and used deadlines like "due in 3 days" so readers don't have to calculate the time left.

Worth admitting

I'm still measuring whether the system reduces one-off components and questions about color in design reviews. I also want to see whether another designer can use it without me in the file. I don't have measured results to share yet.

Design System 2.0 is in production.

Entity pages, the briefing export with source citations, and the new navigation have shipped using the system. The engineering team implemented the chart standards in Recharts. I'm continuing to work on the platform.