Stakeholders Involved in Building a Design System
Who builds, uses, funds, and is affected by a design system, what each group needs, and how to bring them in early.
In short
Stakeholders in a design system are the people who build, use, fund and are affected by it, and each group needs to be brought in early.
11 min readFree
What You Will Learn
A design system is never built by one person. It is built by a group of people who each have a stake in it. Some build it, some use it, some pay for it, and some are affected when it changes. In this lesson you will meet those people, learn what each one needs, and see how to bring them in early so the system actually gets used.
By the end, you should be able to name the main stakeholders, explain where their goals can clash, and describe three ways to keep them involved.
Key words
- Stakeholder
- A person or team who builds, uses, funds, or is affected by a design system.
- Design system
- A shared set of reusable parts and rules that teams use to make their products look and work the same way.
- Component
- One reusable piece of an interface, such as a button, a form field, or a menu.
- Core team
- A small group of people who look after the system day to day.
- Buy-in
- Agreement and support from people, so they are willing to take part.
- Adoption
- When teams actually use the system in their real work, not just read about it.
- Accessibility
- Making products usable by people with disabilities, for example people who cannot see well or use a mouse.
- Contrast
- How clearly text or an icon stands out from the color behind it. Low contrast is hard to read.
- Front-end developer
- A person who builds the part of a product that users see and touch.
- Stakeholder map
- A simple list of every group a system touches and how each group is involved.
Tip
Before you start any design system work, write down every group it will touch. A group you forget at the start often shows up later as a surprise, and surprises slow a project down.
Who Are the Stakeholders?
For most design systems, the people doing the work are internal. The people who use the final products are the reason the system exists, so they matter too.
Who Are the Builders?
The builders are the people who make the system itself. In most teams, three groups do most of this work.
Designers
Designers create the components, write the design guidelines, and check that each part is easy to use and accessible. Many systems have a lead designer who keeps the look and feel consistent across all the parts.
Front-end developers
Developers turn the designs into working parts that run in a product. They build and maintain the component library, and they make sure each part is fast and fits many different products and screen sizes.
Product managers
Product managers decide which features come first, based on business needs. They make sure the system supports the goals of the products that use it, and they help teams coordinate their work.
Quality, Words, and Access
Some stakeholders do not draw anything, but their work decides whether the system is good enough to ship.
QA testers
QA stands for quality assurance. QA testers check the design and the built parts against the agreed standards. They look for bugs and confirm the system works before a product is released.
Content writers
Content writers write the short words people read on a screen, such as button labels, error messages, and help text. Clear words help everyone, and they are a key part of an accessible product.
Accessibility specialists
Accessibility specialists check that parts can be used by people with disabilities. They also help other team members learn these checks.
Tip
Accessibility is cheaper to build in early. Invite the specialist to the first design talks, not the last review.
Leaders and Sponsors
Leadership includes executives and senior managers from design, engineering, and product. Some sit on an advisory group that gives strategic direction, approves big plan items, and helps clear problems that cross teams. Others act as sponsors, which means they provide money, staff time, and public support. A sponsor is the person who can say yes when the team needs resources.
What Does Each Group Need?
Each stakeholder brings something to the system and also wants something back. When you know both sides, you can ask better questions and avoid building parts nobody wants.
Developers need speed and consistency
Developers want parts that are consistent and quick to build with. They contribute feasibility checks, which tell the team early whether an idea can work in real products.
Designers need flexibility
Designers want room to adapt a pattern when a new problem appears. They contribute the look, the patterns, and the guidelines that make the product feel coherent.
Leaders need measurable value
Leaders want proof that the time and money spent on the system pay off. They contribute funding, direction, and the authority to set priorities across teams.
Leaders usually want numbers. Without a starting measurement, it is hard to prove that the system helped.
Where Do Goals Clash?
Goals clash often, and that is normal. Here are four common clashes you will likely meet.
Speed against flexibility
A developer wants to reuse one button everywhere. A designer wants a special version for one page because the page has a different job.
Consistency against new ideas
A shared rule keeps products matching. A new need may break that rule, and someone has to decide whether the rule or the need wins.
Deadlines against quality
A product manager wants a part shipped before a launch. An accessibility specialist or QA tester needs time to check it properly.
Proof against trust
Leaders ask for measurable results. Designers may say that good design takes time to show its value, which can feel like a weak answer to a budget owner.
Tip
Treat a clash as useful information. Ask what the other person is protecting, then look for a change that protects that same thing.
How Do You Engage Stakeholders?
Knowing who the stakeholders are is only the start. The next job is to bring them in, give them a clear role, and keep them involved after the first launch.
How Do You Get Early Buy-In?
Early buy-in matters because stakeholders cannot judge the value of a system that is still in progress and not yet used. Sources on design systems recommend starting the conversation early and inviting everyone who would be involved in or affected by the system.
- 1
Map the groups
List every group the system touches, from designers and developers to QA, brand, and leadership. Bring them in on purpose, one stage at a time, rather than all at once.
- 2
Listen before you pitch
Ask what is frustrating in the current work, where inconsistencies cause real problems, and what a successful system would look like to them.
- 3
Show the problem, not the tool
Point to real examples, such as several versions of the same button, duplicate files, or a page that looks different on each screen. A clear problem makes the case for a system without a long speech.
- 4
Match the picture to the question
Use simple sketches for early ideas, diagrams for big strategy talks, and a working prototype when the question is about how something behaves.
- 5
Pick your battles
Give up small points to win the main approach. A design can be strong overall even if one detail is changed to get agreement.
Tip
Adoption grows when people help shape the system. Invite teams to test early drafts and to tell you what is missing. Teams that helped build a part are more likely to use it and speak up for it.
Form a Core Team with Clear Owners
A core team is a small group that looks after the system. Some sources call it a guild. Its members are the main stewards of the system, and they should be named, not assumed. When one person or group owns each area, everyone knows who to ask, and no question falls between chairs.
Design system lead
The lead owns the vision and overall health of the system. They keep the plan in line with company goals and manage contributions from different teams.
Core team members
These are the people who build and maintain the system day to day, usually a mix of designers and developers who share the work.
Contributors and users
These are the product designers, developers, and product managers who use the system and can suggest changes. Their feedback keeps the system relevant.
Some teams use a simple chart to show who does what. A common version is called RACI. It gives each stakeholder one of four roles for each task. Responsible people do the work. Accountable people give the final yes or no and carry the result. Consulted people give their opinion before a decision. Informed people are updated as the project progresses.
Keep Communication Going
Buy-in is not a one-time event. Stakeholders change jobs, priorities shift, and new teams join. Keep the conversation going with three simple habits.
Regular check-ins
Hold short, steady meetings with each key group. Share what has been done, what is blocked, and what you need from them. Keep updates short and clear.
Feedback channels
Give teams an easy place to raise problems and ideas, such as a shared channel or a simple request form. Some teams run open reviews of proposed changes, so anyone can comment before a decision is final.
Shared updates
Send a short update when a part is added, changed, or retired. Make sure all stakeholders hear it directly and do not rely on someone else to pass it on.
Tip
Always close the loop. When you use a stakeholder's suggestion, say so. When you do not use it, explain why in a sentence or two. People keep giving feedback when they can see it matters.
Check Your Understanding
Try these two short scenarios. Each one asks you to use the ideas from this lesson, not just recall a definition.
Quick check
Your team is starting a design system. The developers say no one asked them about the new component specs, and they refuse to use them. Which stakeholder step was missed, and how would you fix it?
Quick check
Leaders want to know whether the design system is worth its budget. Which step gives them the clearest answer?
Key Takeaways
A design system depends on the people around it. Builders such as designers, developers, and product managers create and shape the parts. Quality, words, and access specialists such as QA testers, content writers, and accessibility specialists make sure the parts work for real people. Leaders provide direction and money. Each group has its own needs, and those needs will sometimes clash.
Bring stakeholders in early, name a core team with clear owners, and keep the conversation going with check-ins, feedback channels, and shared updates. When people help shape the system, they are far more likely to use it.
Sources
- Who should be the responsible person of a Design System? (Elsa Canto, Medium)
- Design System Contribution Model (UXPin Studio)
- Establishing a Clear Governance Model for Your Design System (UX Dictionary)
- Identifying Key Stakeholders - The UX Design Process (uxdt.nic.in)
- Responsibility assignment matrix (Wikipedia)
- Make the case: How to get buy-in for building a design system (Abstract)
- How to Get Non-Designers to Use and Support the Design System? (UXPin Studio)
- Creating A Design System: Organizational Buy In (UXPin)
- 15 Tips to Help Designers Gain Stakeholder Buy-In (inspireUX, Medium)
- Stakeholder Management in Design Systems: What Actually Works (Nijil David)
- How to get stakeholders to trust your design decisions (Dovetail)
- Three steps to jump-start your design system (Hike)
- Selling design system value across the org (Adobe XD Ideas)
- Play Your Part: Role-Based Advice for Agile Accessibility (Level Access)
- Foundations: accessibility roles and responsibilities (TetraLogical)
- Who Owns Accessibility When You Have a Design System? (Mantis and Co)
- Accessibility QA Workflows for Websites, Apps, and Documents (Know the ADA)
- Who is responsible for website accessibility? (Welcoming Web)
- Building an Accessibility Design Team (Accessibility.com)
Last updated on 17 November 2026
Related lessons
Learn with me
Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.