Design decisions
Design decisions documents capture the context, reasoning, and consequences behind significant choices made for VA Design System components and patterns.
Design decisions documents help teams understand not just what was decided, but why — making it easier to revisit choices as requirements change and to avoid re-litigating settled questions. They create a permanent record of decisions that might otherwise be scattered across Slack threads, tickets, or meeting notes.
We use the Architecture Decision Record (ADR) format to structure these documents. Each ADR covers three things: the context that prompted the decision, the decision itself, and its consequences — including trade-offs and any open questions.
Components with design decisions
Component
Last updated
May 14, 2026
May 14, 2026
May 14, 2026
May 14, 2026
May 14, 2026
May 14, 2026
May 14, 2026
May 14, 2026
May 14, 2026
May 14, 2026
May 12, 2026
May 26, 2026
May 14, 2026
May 14, 2026
June 18, 2026
May 14, 2026
May 15, 2026
May 15, 2026
May 15, 2026
May 12, 2026
Patterns with design decisions
Pattern or template
Last updated
May 15, 2026
June 9, 2026
May 18, 2026
June 12, 2026
May 15, 2026