What is Infa
Infa Chrome Extension
How to use and install our Chrome Extension
Community
Browse community design systems
Release Notes
Featuring the latest changes to keep you up-to-date
Research Program
Participate in shaping the future of Infa
SOC 2 Type II Compliance Badge
Enterprise Ready
SOC 2 Type II certified for enterprise-level security and compliance
EventsLearnPricing
Sign up for free

Feedback

Share your feedback

Close
Anonymous submissions are auto-posted to #feedback channel. You can also share directly in Slack.

Need help?

Reach out to contact@infa.ai or see docs

Navigation
Search...
⌘ K
Focus sentinel
Close

Search Documentation

PressESCto close
Focus sentinel
Learn
  • Playbooks
    • First 90 Days
      • Phase 1: Discovery & Orientation
      • Org Structure & Stakeholder Mapping
      • Products Map
      • Success Metrics & OKRs
      • Foundations Setup
      • Phase 2: Strategy Development
      • Communication Plan
      • Adoption Roadmap
      • Feedback Synthesis Framework
      • Phase 3: Execution & Optimization
      • Value Delivery Framework
      • Optimization Systems
      • Sustainability Planning
  • Design Systems
    • Design System Stages
    • Maturity Model
    • Process Map
    • Design System Roles
  • Insights
    • Ai Ready Documentation
    • Component Tagging Strategies
    • Interactive Documentation Strategies
    • Markdown Documentation Strategy
    • Multiple Themes
    • Props Vs Slots
  • Highlights
    • Component Classification Framework
    • Documentation Evolution Stages
    • Markdown Universal Language
    • Performance Optimization Insights
Switch to Light theme
Switch to Dark theme
TermsPrivacyChat with Us
  1. Learn
  2. Playbooks
  3. First 90 Days in Design Systems

Org Structure & Stakeholder Mapping

Map the organizational landscape around your design system, identifying sponsors, team, partners, advocates, and adoption landscape.

Your first major deliverable involves mapping the organizational landscape around your design system. This comprehensive analysis answers critical questions about your ecosystem and the people within it.

info icon
Learn more about design system roles

Copy link
Core Stakeholder Identification

Map out the following stakeholder categories to understand your design system's ecosystem:

  • The executive or leadership figure who provides:

    • Budget and resources
    • Strategic direction
    • Executive air cover
    • Cross-functional authority
  • Your day-to-day collaborators:

    • Design system designers
    • Frontend engineers
    • Content strategists
    • Accessibility specialists
    • Product managers
  • Cross-functional allies who:

    • Contribute components or patterns
    • Provide domain expertise
    • Help with integration efforts
    • Offer product-specific insights
  • Champions within the organization who:

    • Promote adoption in their teams
    • Share success stories
    • Defend design system decisions
    • Bridge communication gaps
  • Future opportunities:

    • New product teams
    • Legacy products not migrated
    • Acquired companies
    • International offices
  • Teams actively integrating:

    • Migration timeline
    • Blockers and challenges
    • Support needs
    • Quick win opportunities
  • Critical learning opportunities:

    • Why they left
    • What didn't work
    • Pain points encountered
    • Potential re-engagement strategies
  • If you have multiple design systems:

    • Overlapping territories
    • Collaboration opportunities
    • Consolidation possibilities
    • Shared learnings
  • Success stories to amplify:

    • Metrics and impact
    • Best practices
    • Case studies
    • Reference implementations

Copy link
Creating Your Stakeholder Map

Document your findings in a visual format that shows:

  1. Organizational hierarchy: Where stakeholders sit in the org chart
  2. Relationship strength: Close partners vs distant stakeholders
  3. Influence level: Decision makers vs implementers
  4. Adoption status: Onboarded, in-progress, not started, churned

Copy link
Template Structure

Sponsor Layer
├── Executive Sponsor(s)
└── Department Heads

Core Team Layer
├── Design System Team
│   ├── Leadership
│   ├── Designers
│   ├── Engineers
│   └── Content/Accessibility
└── Extended Team (contractors, partners)

Product Team Layer
├── Strong Adopters
│   └── [Team names, product areas]
├── In Onboarding
│   └── [Team names, timeline]
├── Not Onboarded
│   └── [Team names, priority]
└── Detractors
    └── [Team names, reasons]

Support Network Layer
├── Advocates
├── Contributors
└── Friendly Competitors
info icon
Continue to Products Map

Content Feedback

Feedback on selected content

Close
Anonymous submissions are auto-posted to #feedback channel. You can also share directly in Slack.

Need help?

Reach out to contact@infa.ai or see docs