Slide 30
Slide 30 text
HIAMF®
Every design system is different and unique to every organization.
• Interviews and surveying a broader (potential) contributors,
influencers and leaders to assess perspective, attitudes,
culture, and existing practices.
• Requirements gathering via task analysis, tech planning,
and convention setting.
• Product tours to immerse in as-is products and in-flight
designs to which the system will apply, taking screenshots
and notes.
• System(s) reviews assessing as-is design assets, code
libraries, standards documentation depth and quality, and
governance models.
Month
Planning and Strategy
Discovery Concepts
1
1.0 Release Circle
• Defining what a design system is and why it’s important.
• Proposed scope, timing, products and processes included
in 1.0 release, subsequent product adoption and support,
and system development and maintenance that follows
(the how and when).
• Recommended multi-disciplinary system
team composition and how they’ll engage contributors and
decision-makers (the who).
S1
2
S2 S3 S4 S5 S6
3 4
0.1
Alpha
0.3
Beta
Simpler libraries can take 2–3 months while robust component catalogs —
flexible theming, sophisticated tooling, robust documentation — may take a
couple months longer. By the cycle’s end, the 1.0 represents the “big launch”
you publicise is generally available to product squads at the ready.
0.1
General
availability
“Big launch”
5