🏫
Obvious University
Website
  • 👋Welcome to Obvious University!
  • Strategy
    • Sprints
      • 1️⃣Map
      • 2️⃣Sketch
      • 3️⃣Decide
      • 4️⃣Prototype
      • 5️⃣Test
    • Benchmarking
    • Research
      • 1️⃣Research guide
      • 2️⃣How to recruit users
      • 3️⃣How to conduct an interview well
      • 4️⃣How to take notes
      • 5️⃣How to prep for remote research
      • 6️⃣How to throw a watch party
      • 7️⃣How to create artefacts
  • Working with Features
    • Building with AI
      • 1️⃣Understand the tech
      • 2️⃣Map your product
      • 3️⃣Build a proof of concept
      • 4️⃣LLM Inputs
      • 5️⃣LLM Responses
    • Building Help and Support
      • 1️⃣How to scope a support experience
      • 2️⃣How to design discovery for support
      • 3️⃣How to design a support centre
      • 4️⃣How to write good support articles
  • Product Design
    • Microcopy
      • 1️⃣How to write well
      • 2️⃣How to write phrases
      • 3️⃣How to write messages
      • 4️⃣How to create a voice
    • Typography
      • 1️⃣How to compose type
      • 2️⃣How to create a type scale
      • 3️⃣How to pick typefaces
      • 4️⃣How to pair typefaces
    • Design System
      • 1️⃣Introduction to design systems
      • 2️⃣How to audit a design system
      • 3️⃣How to run a design system pilot
      • 4️⃣How to set up a design foundation
      • 5️⃣How to build components
      • 6️⃣How to document a design system
      • 7️⃣How to enable adoption and govern a design system
    • Mobile Engineering
      • 1️⃣Trunk based development
      • 2️⃣Agile development terminology
      • 3️⃣Git commit messages
      • 4️⃣Code review and pull requests
      • 5️⃣Readings
  • Delivery
    • Project Management
    • Collaboration
  • Hiring and Growth
    • Growth
      • 1️⃣Design growth framework
      • 2️⃣How to give ongoing feedback
      • 3️⃣How to check-in every quarter
      • 4️⃣How to address underperformance
      • 5️⃣FAQs
    • Hiring and careers
      • 1️⃣The Hiring Process
      • 2️⃣Diverse and Inclusive Hiring
  • PEOPLE EXPERIENCE
    • Benefits and Perks
      • 1️⃣Paid time off
      • 2️⃣Insurance and healthcare
      • 3️⃣Continuing education
      • 4️⃣Speaking at conferences
    • Starting at Obvious
      • 1️⃣Introducing Obvious
      • 2️⃣Set up your workspace
      • 3️⃣Onboarding
      • 4️⃣Finances
      • 5️⃣Code of Conduct
    • Employment policies
      • 1️⃣Equal opportunity employment
      • 2️⃣At-will employment
      • 3️⃣Employee records and privacy
      • 4️⃣Prevention of sexual harassment
      • 5️⃣Drugs and alcohol
      • 6️⃣Fraternisation
      • 7️⃣Non-compete and non-solicitation
      • 8️⃣Non-disclosure
Powered by GitBook
On this page
  • 👋 Introduction
  • 1️⃣ Adoption
  • Document your design system
  • Host workshops
  • Test with teams
  • Create visibility
  • Create champions
  • 2️⃣ Governance
  1. Product Design
  2. Design System

How to enable adoption and govern a design system

PreviousHow to document a design systemNextMobile Engineering

Last updated 1 year ago

👋 Introduction

After successfully running a pilot, it's important to ensure that teams can smoothly use the components and foundations for their needs. At this point, you'll also start considering the next components and updates, meanwhile teams will also reach out with their requests. This stage highlights the significance of adoption and governance in the design system's evolution.

1️⃣ Adoption

Adopting a design system involves more than just technical implementation; it's a cultural/habit shift within a team. Here are some practices that can facilitate the adoption of a design system

Document your design system

  • One fundamental way to help with adoption is to have your design system well documented. Covered here

Host workshops

  • Host interactive workshops for teams to learn and use the design system effectively. Gather feedback during these sessions to continually enhance the system.

Test with teams

  • Test WIP components to ensure the system addresses their needs, keeping in mind the guideline for a design system component.

  • This collaborative approach can help refine components and enhance their usability.

Create visibility

  • Share regular updates through newsletters or Slack messages to keep teams informed about any design system changes or additions. Share visuals and demos to make it engaging.

  • Join meetings (like design critiques) to observe and support the team whenever you identify opportunities for the design system to contribute to ongoing discussion/project.

Create champions

  • Acknowledge team members who've found the design system transformative in their workflow. Encourage them to advocate for its use and assist others in adopting it effectively.

  • Give these champions recognition—sharing their successes will inspire others to embrace the system and its benefits.

2️⃣ Governance

To scale your system in a cohesive and sustainable way, keep in mind that a design system team’s job is really to solve the common problems. The more the design system team tries to accommodate one-off problems, the less focus you can have on solving problems at scale.

An often encountered issue with design system teams is becoming a bottleneck while supporting feature teams by creating new components or additions.

To prevent this:

  • Let the team know that if this request is echoed by other teams as well, we'll escalate and prioritise it accordingly.

Focus solely on requests or components that are currently needed by at least 3 teams or features. Keep revisiting and updating the .

7️⃣
Documentation
component list