Skip to main content

Pictures

Pre-flight maps for the Design System Proving Ground PRD.

Maps​

  • Outcome Map — Binary success measures: 5 outcomes, each pass/fail
  • Dependency Map — What must exist, what depends on this, kill dependencies

Map Insights​

The outcome map shows a clean chain: unified nav (O1) enables standard process discovery (O2), which enables the shipping gate (O4). CRM rewrite (O3) and meeting form (O5) prove the standard works at increasing complexity.

The dependency map reveals the key risk: only 1 organism (FormShell) exists in the lib. DS-05 (meeting agenda form) is the stress test — if it can't compose from existing atoms, the lib needs work before this PRD delivers value.

Questions​

What is the most important visual missing from the design system app picture set — and why does it matter?

  • Which relationship between elements in this diagram is most underspecified — and what would happen if it were wrong?
  • If this picture were shown to a new engineer on day one, what would they misunderstand — and how should the picture be changed?
  • What assumption does this visual make that should be made explicit in the spec?