# Enterprise system deprecation

- Client: Capital One
- Years: 2025 to 2026
- Categories: [design systems] [migration]
- Role: Deprecation design lead for the global system libraries
- Team: Capital One, Enterprise Design System
- Scope: Five current libraries, 4 legacy libraries, 3,000+ designers and developers, 500+ features
- Access: password protected, ask Ashley for access
- Markdown: /ai/showcase/deprecation-strategy.md
- Human: /deprecation-strategy

## Project

Defining how a design system migrates legacy libraries.

I wrote the standard for retiring components across the whole system, with a six month timeline, the warnings designers see in Figma, and the support behind each migration. Engineering carried it into code, so designers and developers read the same status and deadline.

- Before this work: The fast path, where old components are deleted and thousands of files break at once.

## Related projects

- [CityScout, from idea to enterprise](/ai/showcase/cityscout)
- [Theming at enterprise scale](/ai/showcase/theming-migration)
- [Component craft & engineering](/ai/showcase/design-system-component-builds)