From Legacy Workflows to AI-Ready UX: Why Enterprise Design Needs More Than a Design System
Modernizing enterprise UX requires more than introducing a design system—such as a UI kit or component library—or adding AI. True UX modernization must begin with context engineering: explicitly encoding implicit business logic and workflow architecture.
1. Legacy Is Not Technical Debt, but Institutional Memory
- Older systems are not merely liabilities to discard. They contain implicit knowledge accumulated over years, including business rules, compliance requirements, and exception-handling cases.
- Modernization should not remove complexity indiscriminately. It should distinguish essential domain logic from unnecessary operational friction and redesign each accordingly.
2. The Limits of Design Systems: Nouns versus Verbs
- Design systems define “nouns,” such as buttons, modals, and tables, but they do not provide the “verbs”: interaction rules such as role-based navigation, recovery paths after network errors, and conditions for two-factor authentication.
- Without this system context, AI tools such as Cursor and Claude must rely on assumptions, producing inconsistent results.
3. The Solution: Encoding Design Intent through DESIGN.md
- Design intent should be maintained alongside the codebase in a machine-readable document such as DESIGN.md.
- Machine-readable tokens: Style values including spacing, color, and typography
- Behavioral heuristics: State-transition rules and layout responses to exceptions
- A component library documents what has been built, while DESIGN.md documents how the system behaves.
4. Prioritizing System Legibility over Screen-Level Design
- Producing high-quality UI without first establishing the underlying logic is one of the most common mistakes in modern software design.
- Design leadership is not limited to pixel-level execution. Its role is to translate complex domain constraints into machine-readable guidance that both human developers and AI agents can understand.
