Design systems need a go-to-market plan

A design system only delivers on its promise of consistency, efficiency, and scalability if people actually use it. Yet many teams discover that building a robust system is the easy part; getting colleagues to adopt it is the real challenge. Slack messages, presentations, and training sessions often fall flat. The missing piece is treating the design system not as an internal toolkit, but as a product that needs a marketing strategy.

By adopting a marketing mindset, design systems teams can position their work as essential infrastructure. This means crafting compelling narratives, identifying champions, and measuring impact — turning a design system from a nice-to-have into a must-have instrument for the entire organization.

Know your audience before you pitch

Before any messaging, confirm that your design system actually addresses the needs of its users. Achieving product-market fit is an ongoing loop of exploration, communication, and iteration. It requires a nuanced understanding of what drives your audience, what worries them about new tools, and how they perceive the system's value in their daily work.

Immerse yourself in the realities of designers, developers, and decision-makers. Identify not just their stated challenges, but also their unspoken frustrations and desires. Interview people across your Product Design and Engineering organization — from individual contributors to leadership — to gather diverse perspectives. Start conversations around existing processes, bottlenecks, and goals before discussing the design system itself.

Pitch to each role's priorities

Designers, developers, and project managers speak different dialects of the same language. Fine-tune your pitch for each group so the value proposition lands clearly:

  • For designers, highlight how the system enables creativity while ensuring brand consistency.
  • Developers care about reusability and efficiency gains. Emphasize how the system facilitates standardization and a frictionless design-to-code workflow.
  • Decision-makers respond to ROI: accelerated speed-to-market and reduced technical debt.

Address hesitations head-on. Understand why some may resist adoption — concerns about flexibility, technical limitations, or implementation overhead — and craft messaging that turns skepticism into enthusiasm.

Going to market: timing and channels

The rollout phase requires choosing channels and formats that suit each audience. Communicate the system's core value without overwhelming; link to deeper resources for those who want more detail.

Treat the launch as a learning opportunity. At Spotify, for example, the team prioritized collaboration and feedback loops when rethinking their design system implementation. Showing responsiveness to user feedback improves the system and builds trust.

  • Host hands-on workshops and collaborative sessions.
  • Publish concise, informative documentation.
  • Produce short videos with real-world use cases.
  • Schedule presentations at relevant team meetings.

Timing matters. Capitalize on product launches, company meetings, or quarterly planning to amplify your message. Avoid periods of low engagement like late Friday afternoons, holidays, or during company-wide events. And remember, awareness is ongoing — marketing happens continuously, not just at launch.

Build influence through advocacy

Identify internal champions who can rally others — senior designers, respected developers, or product leaders who see the system's potential. Consider formalizing advocacy through performance reviews or programs where contributors earn recognition for creating components, running training, or writing content. This fosters a culture that underscores the system's importance.

This creates a flywheel effect: empowered advocates generate momentum that attracts more users, who in turn contribute to growth and improvement. A self-sustaining community not only supports current users but welcomes newcomers, with feedback fueling continuous iteration.

Measure adoption and share wins

Establish clear success metrics for adoption, engagement, and satisfaction. Track concrete numbers:

  • Number of teams or projects using the design system
  • Contribution rates: people creating or updating components
  • Attendance at trainings, workshops, and community events
  • System usage telemetry: component inserts and detaches, library usage

Set ambitious but achievable targets, like aiming for 70% of product teams using the system within six months. Monitor progress and share wins publicly. An actively engaged community provides a feedback loop that evolves the design system into an ever more essential asset.

Adoption requires a marketing mindset

Design systems unify creative vision, streamline workflows, and help teams deliver consistent user experiences. Yet even the most carefully built system will stall if the team assumes people will find it on their own. Moving from a “build it and they will come” approach to genuine adoption requires treating the system like a product that needs promotion, not just infrastructure.

That means deliberately wearing the marketing hat: raising awareness across the organization, nurturing advocates, and demonstrating concrete value. When a design system team invests in these activities, the system becomes more than a useful library — it becomes a core part of how the organization ships digital products.

Ana Boyer, designer advocate at Figma, focuses on building community and empowering design teams. Her work centers on collaboration and iteration, and she thrives on creating structure and process where ambiguity exists.