Why SOLAR
Most systems start with parts and hope consistency follows. Sprawl usually follows instead. SOLAR is a simple operating model that keeps speed and consistency from fighting each other. It ties every decision to outcomes and keeps the surface area lean.
S — Set Impact Goals
What it means:
Start with outcomes, not components.
How I do it:
Define 3–5 goals with clear metrics: satisfaction (CSAT/NPS), task success, accessibility scores, performance budgets, and maintainability. Tie every system decision back to these goals.
Deliverables:
Impact brief, success metrics, KPI dashboard starter, baseline audits.
O — Optimize and Lean
What it means:
Ruthlessly reduce complexity. Keep only what drives outcomes.
How I do it:
Component rationalization, token hygiene, naming standards, and design-dev build budgets. Remove duplicates, merge variants, shrink props and options, cut asset weight.
Deliverables:
Lean library plan, token map, variant matrix, performance guardrails.
L — Lifecycle and Modularity
What it means:
Design for change. Version intentionally.
How I do it:
Clear versioning, deprecation windows, upgrade paths, dependency mapping, and atomic composition. Small parts, well-named, with contracts you can trust.
Deliverables:
Versioning policy, deprecation schedule, migration guides, module patterns.
A — Agile Governance
What it means:
Lightweight rules that speed you up, not slow you down.
How I do it:
PR/design reviews with checklists, RFCs for new patterns, scorecards, change logs, and “fast lane” approvals for low-risk updates.
Deliverables:
Governance playbook, review checklists, RFC templates, change log setup.
R — Responsible User Influence
What it means:
Patterns that guide, not manipulate.
How I do it:
Accessibility by default, inclusive content, ethical nudges, and research-backed decisions. No dark patterns.
Deliverables:
Inclusive pattern guidelines, accessibility checklist, research plan, copy standards.
