# UXD Systems — Design-system review worksheet

## 1. Product context

- Primary users and high-value tasks:
- Platforms and input methods:
- Accessibility, regulatory, localization, and content risks:
- Team structure, implementation stack, and maintenance capacity:
- Repeated decisions the system must support:

## 2. Evidence matrix

For each candidate system, record the primary source, access date, documented guidance, UXD Systems analysis, applicability, and unresolved questions.

| Dimension | System A | System B | System C | Product consequence |
| --- | --- | --- | --- | --- |
| Foundations and tokens | | | | |
| Component architecture | | | | |
| Patterns and content | | | | |
| Accessibility | | | | |
| Adaptivity and localization | | | | |
| Governance and releases | | | | |
| Design-to-code | | | | |

## 3. Representative workflow

- Workflow:
- Entry conditions:
- Success outcome:
- Failure and recovery:
- Keyboard and focus expectations:
- Zoom, reflow, long-content, and localization cases:
- Data, privacy, and permission considerations:

## 4. Operating model

- Accountable owners:
- Contribution criteria:
- Release and migration approach:
- Deprecation policy:
- Adoption support:
- Outcome, quality, and maintenance measures:

## 5. Recommendation

- Recommended direction and why:
- Evidence supporting the decision:
- Tradeoffs accepted:
- Unknowns requiring validation:
- First-release scope:
- Verification plan and success criteria: