Design systems agreements must be documented to prevent drift¶
Insight: "Remember when we agreed that…?" is a powerful governance pattern for design systems. Agreement requires facilitation — not just deciding and announcing. Design system decisions (scope, patterns, deviations) should be explicitly documented via email confirmations, change orders, or shared meeting notes. Without documented agreements, memory fades and scope drifts. AI meeting transcription tools (Granola, Fathom, Fireflies) help remove bias from note-taking and make agreement documentation frictionless.
Detail: The pattern applies directly to design system governance: token naming conventions, component API decisions, deviation policies, and contribution guidelines all benefit from explicit documented agreement. Two common failure modes in design system programs: (1) teams don't know what's coming (no communication of roadmap/decisions), (2) teams don't remember what was already decided (no documentation trail). Both are solved by making agreements visible and revisitable. No-cost change orders can modify scope without triggering renegotiation anxiety.
Sources
- Dan Mall — "Remember When We Agreed That…" (2025-07-11)
Related: existing entry "Design systems must prove ROI in dollars" in external/design-systems.md — COMPLEMENTS