Files
boc/docs/design/COMPONENT_MATURITY.md
T
Bernt 8ee9965378 docs: Experience Audit + Component Maturity Model
- EXPERIENCE_AUDIT_QA.md (v1.0, DRAFT):
  - Audit framework: 6 questions per screen
  - Screen 1: quiXzoom Onboarding — 3s , R→D ⚠️, Decision 
    - Issue: 'kr' used instead of USD/EUR (Valutaregel violation)
    - Issue: Launch date creates hesitation
  - Screen 2: Landvex Process — 3s , R→D , Decision 
    - Issue: Technical terms in step descriptions
  - Action items: currency update, date removal, verb simplification
  - Next screens: Dashboard, Map View, Search, Mission Details, Results

- COMPONENT_MATURITY.md (v1.0, LOCKED):
  - Three levels: Foundation → Validated → Canonical
  - Foundation: RFC approved, passes 13 DoD criteria
  - Validated: used in 3 real screens, passes Experience Audit
  - Canonical: used in 5 screens, 2 sprints stable, other components inherit
  - Promotion process with verification requirements
  - Current status: all 4 components at Foundation level

Rationale: Observe first, standardize second. Components become Canonical
only after proving value in real screens. Experience Audit identifies gaps
before building components. Maturity model prevents premature standardization.
2026-07-02 11:32:25 +00:00

1.9 KiB

COMPONENT MATURITY MODEL

Maturity Levels for Design System Components

Version 1.0
Status LOCKED
Scope All Landvex & quiXzoom components

Maturity Levels

Level 1: Foundation

Criteria:

  • RFC approved
  • Follows COMPONENT_TEMPLATE.md
  • Passes all 13 Definition of Done criteria
  • Documented in Compliance Matrix

Meaning: The component is specified and stable.

Level 2: Validated

Criteria:

  • Used in at least 3 real screens
  • Passes Experience Audit
  • No critical issues found
  • Feedback from at least 2 users or user proxies

Meaning: The component works in practice.

Level 3: Canonical

Criteria:

  • Used in at least 5 real screens
  • No open issues for 2 sprints
  • Other components inherit from it
  • Documented as reference implementation

Meaning: The component is the standard for future development.


Current Status

Component Level Evidence Next Step
Button Foundation RFC-001 approved Use in 3 screens → Validated
Input Foundation RFC-002 approved Use in 3 screens → Validated
Select Foundation RFC-003 approved Use in 3 screens → Validated
Card Foundation RFC-004 approved Use in 3 screens → Validated

Promotion Process

From To Requirement Verified By
Foundation Validated 3 real screens + Experience Audit Design Review
Validated Canonical 5 screens + 2 sprints stable + inheritance Architecture Review

ÄNDRINGSHISTORIA

Version Datum Beskrivning
1.0 2026-07-02 Initial maturity model: Foundation → Validated → Canonical

STATUS

LOCKED

  • Mindre revideringar: 1.x-serien
  • Brytande ändringar: Kräver Architecture Review, ny major-version (2.0+)