I created a design system to support the efficient modernization of 70+ enterprise applications.
The design system was intentionally built to support the unique business needs of each application while maintaining a consistent user experience across the broader enterprise suite, enabling product teams to modernize mission critical systems more efficiently while maintaining consistency, compliance, and long-term scalability.
Scope
150+ enterprise applications assessed
Impact Area
70+ applications scheduled for modernization
Timeline
4 month discovery + phased delivery
Background
The Forest Service operates a large, complex ecosystem of enterprise applications supporting Forest Service operations. Many of these systems had not been modernized in decades, resulting in overlapping functionality, rising maintenance costs, accessibility risk, and inconsistent user experiences.
Our team set out to not only replace aging applications, but to rethink how technology could better support the Forest Service mission.
My work focused on creating the UX foundation needed to enable that transformation at scale.
Discovery
Transformative change driven by research
Before designing solutions, the team conducted a four-month discovery effort to understand the ecosystem holistically.
What we learned
Why a Design System Was Necessary
With 70+ applications slated for modernization, consistency could not be enforced one application at a time.
The design system became the mechanism to:
- Reduce redundant design and engineering work
- Establish a shared UX and implementation language
- Embed accessibility at the system level
- Enable faster, more predictable delivery across teams
Process
1. Plan & Organize
To support 70+ applications under one brand, I designed a scalable system using consistent, token-driven foundations, eliminating the need for app-specific themes:
- Established design system architecture
- The intent is that designers will pull the foundational layers into local libraries to build app-specific files while inheriting shared standard
- Established guiding principles used for both design and development decisions:
- Flexibility – support diverse business needs
- Accessibility – WCAG compliance by default
- Speed – enable faster design and development through reuse
- Agreed on a collaborative approach built alongside developers
2. Assess UI Patterns
Key activities
- Reviewed common enterprise SaaS patterns
- Identified best practices worth standardizing
- Noted inconsistencies and anti-patterns to avoid
- Used findings to inform component behavior and interaction patterns
3. Establish Foundations
Key activities
- Identified common UI elements and UX patterns
- Established the visual language:
- Typography scales
- Color palettes with accessible contrast
- Iconography standards
- Spacing and layout rules
4. Build Library
Key activities
- Designed components in parallel with engineering
- Tested components for accessibility
- Refined components based on implementation feedback
5. Establish Governance
Key activities
- Established a centralized ownership model with a dedicated design team
- Communicated how teams could access and use the system
- Collected feedback from real usage
- Prioritized updates and improvements as adoption grew
Design System in Action
In addition to the agency's survey, we built additional tools to support the entire trails network.
Next Steps
Align tools with real workflows
Understanding the disconnect between leadership and field crews helped us shift the focus from compliance-driven design to user-centered solutions.
Simplify to Scale
Reducing complexity in the form and automating backend logic helped standardize data while easing the burden on field users.
Build for the Full Ecosystem
Designing tools for managers, field crews, and partners ensured stronger collaboration and more complete data capture.