Change Management in Design Systems

Only 40% of design systems are still in use after 12-18 months. Not because teams forget to ship tokens. Not because of skipped documentation or picking the wrong tool. It often comes down to poor governance. 👉 When requests get buried in DMs… 👉 When blockers get solved in side chats… 👉 When decisions happen in meetings and never get logged… Adoption nosedives. Components duplicate. The system drifts. Here's the truth: A design system doesn’t live in Figma. It lives in your conversations. High-performing teams already know this and are treating governance like an open forum, not a private chat: → Slack channels dedicated to requests → GitHub discussions linked to PRs → Jira or Notion boards tracking status + owners → Decision logs anyone can revisit months later The result? Visibility, trust, and adoption. Brad Frost has been at the forefront of the design system discussion, and I love the way he frames it: Public discussion → group decision → codified pattern. And the proof is in the results: 🔹 Fortune 500 teams are cutting dupe builds just by moving requests to public Slack. 🔹 A scale-up drove a 3x increase in adoption by running governance in GitHub. 🔹 An agency reduced design debt 20–40% by keeping a weekly decision log. This isn’t theory—it’s practice. And it’s repeatable. Swipe below for a breakdown of conversation-first governance, including: → A 4-step conversation flow → A proven governance-in-action model → How to test if your governance is visible—or at risk 📌 Save this for your next sprint retro. 📌 Run the audit with your team this week. 📌 Drop your questions (and results) in the comments—I want to hear where your governance lives today. Because the truth is simple: Your design system is only as strong as the conversations around it. #designsystems #uxdesign #governance #designops ⸻ 👋🏼 Hi, I’m Dane—your source for UX and career tips. ❤️ Was this helpful? A 👍🏼 would be thuper kewl. 🔄 Share to help others (or for easy access later). ➕ Follow for more like this in your feed every day.

𝗧𝗵𝗲 𝗙𝗼𝗿𝗴𝗼𝘁𝘁𝗲𝗻 𝗦𝘁𝗲𝗽 𝗧𝗵𝗮𝘁 𝗞𝗶𝗹𝗹𝘀 𝗚𝗿𝗲𝗮𝘁 𝗣𝗿𝗼𝗷𝗲𝗰𝘁𝘀 If there's one phrase that should send shivers down every project manager's spine, it's: "We'll handle change management internally." Translation: 𝗪𝗲'𝗹𝗹 𝘄𝗶𝗻𝗴 𝗶𝘁 𝗮𝗻𝗱 𝗵𝗼𝗽𝗲 𝗽𝗲𝗼𝗽𝗹𝗲 𝗺𝗮𝗴𝗶𝗰𝗮𝗹𝗹𝘆 𝗮𝗱𝗼𝗽𝘁 𝘁𝗵𝗶𝘀 𝗻𝗲𝘄 𝘀𝘆𝘀𝘁𝗲𝗺. Here's the uncomfortable reality 👇 Many organizations treat change management like it's optional. Something fluffy. A nice-to-have. A checkbox to tick before launch. But here's what the data actually shows: 𝟳𝟬% 𝗼𝗳 𝗱𝗶𝗴𝗶𝘁𝗮𝗹 𝘁𝗿𝗮𝗻𝘀𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗮𝗶𝗹. And the culprit isn't usually bad code or flawed architecture. It's people who weren't ready, weren't trained, or weren't brought along for the ride. We pour millions into new technology. Endless hours into project design. Countless meetings into governance structures and data models. But we forget that 𝘁𝗵𝗲 𝗿𝗲𝗮𝗹 𝗰𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲 𝗶𝘀𝗻'𝘁 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝘁𝗵𝗲 𝘁𝗵𝗶𝗻𝗴 — 𝗶𝘁'𝘀 𝗴𝗲𝘁𝘁𝗶𝗻𝗴 𝗽𝗲𝗼𝗽𝗹𝗲 𝘁𝗼 𝘂𝘀𝗲 𝗶𝘁. I've watched talented teams build beautiful data platforms and AI models that check every technical box — only to see them gather dust post-launch. Not because of bad execution. Because the humans on the receiving end weren't part of the journey. 🚶♂️ They weren't consulted during design. They weren't trained effectively. They weren't given a reason to change workflows that worked (even if held together with Excel and prayer). Here's what I've learned the hard way 💡 #ChangeManagement isn't a side quest. It's the main storyline. And like any good story, it needs dedicated storytellers — specialists who understand: • Communication strategies that actually resonate • Behavioral psychology and how adults learn • Adoption metrics that go beyond "number of logins." • Resistance patterns and how to address them with empathy 𝗖𝗵𝗮𝗻𝗴𝗲 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 𝘀𝗵𝗼𝘂𝗹𝗱 𝗵𝗮𝘃𝗲 𝗮 𝗯𝘂𝗱𝗴𝗲𝘁 𝗹𝗶𝗻𝗲. It should have dedicated resources. It should start on Day 1 of the project, not three weeks before go-live, when someone panics about user adoption. If your #DataStrategy, #DigitalTransformation, or #AI projects keep stalling after launch, don't just audit your tech stack or review your backlog. 𝗟𝗼𝗼𝗸 𝗮𝘁 𝘆𝗼𝘂𝗿 𝗰𝗵𝗮𝗻𝗴𝗲 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 𝗴𝗮𝗽. Because the best tool in the world means nothing if no one changes how they work. 🎯 The fanciest dashboard is worthless if people still make decisions in spreadsheets. The most sophisticated AI model won't deliver ROI if your team doesn't trust it. Technology is the easy part. Humans are the hard part. That's why we need to stop treating change management like an afterthought. #ChangeManagement #Leadership #DigitalTransformation #AI #DataStrategy #ProjectManagement #OrganizationalChange #Teamwork #Innovation #TechLeadership

Creating a design system is easy. Well, ok. That’s a bit click-baity. It’s not *easy.* But creating the design system is a hell of a lot easier than getting people to actually use it consistently. A lot of design systems fail, and it’s not because the components are bad. ⇢ It’s because we build them too early.  ⇢ We don’t ask what people actually need.  ⇢ We forget that adoption isn’t the goal—alignment is! --- The fact is, you’re not Kevin Costner, and just because you’ve built it doesn’t mean anyone will use it. So, what do you do when your design system isn’t getting used? Justin Crews has seen this type of thing play out multiple times inside large organizations, and he’s learned a few lessons the hard way, so you don’t have to! This week, he joins the show to discuss it and explain how we can ensure that our design system is adopted and used by the entire team. We dig into: ➡️ Why building components should come *after* documenting decisions ➡️ How design systems support standardization, not innovation ➡️ Why designers need to stop dictating and start listening ➡️ How to think about influence, trust, and the real adoption curve If your team has ever built a beautiful Figma library that no one uses… this episode is for you! --- 🎯 Here are some key takeaways from our conversation 1️⃣ Standardization starts with alignment, not consensus: First, you need clarity around tradeoffs, shared goals, and consistent outcomes. Guide documentation, don't dictate perfection. 2️⃣ Build incrementally and prove impact as you go: You don’t need a full library to start. Build the components people are already using and show how they save time or reduce confusion. Every small win earns credibility. 3️⃣ Document decisions before enforcing standards: Don’t assume your team needs a system. Show them what’s inconsistent first. Auditing what currently exists allows you to identify the actual gaps and opportunities. 4️⃣ Design systems aren’t innovation tools; they're maintenance tools. A design system can get in the way of building something new. Wait until you’ve validated patterns, then wrap them into the system. 5️⃣ Adoption follows trust and timing: Adoption happens when teams trust that the system solves real problems. Trust comes from involving people early and listening to their needs. --- This week’s episode is brought to you by Wix Studio! Web designers, let’s talk about the ‘c’ word—creative burnout. Your client site has real portfolio potential, but between resourcing, feedback, tight budgets and even tighter deadlines—it just doesn’t make the cut. Wix Studio helps close that gap. Built for agencies and enterprises, you can bring your vision to life—and keep it alive—with no-code animations, tons of AI tools, reusable design assets, and advanced layout tools. For your next project check out Wix Studio! ♻️ If you found this helpful, share it 🙏!

💡Design System Governance Models Design system governance models help organizations manage and maintain design systems across teams and products. There are three popular models—Solitary, Centralized, and Federated— each offer different approaches to how design systems are governed within an organization. 1️⃣ Solitary model (Standalone) In the solitary model, each team, project, or department creates and maintains its own design system independently. Benefits: ✔ Autonomy and flexibility: Teams can design for their unique needs without waiting for approvals or alignment. ✔ Quick iteration: Changes can be implemented without the need to coordinate with other teams. Downsides: ✔ Inconsistency: The lack of a unified system can lead to inconsistent user experiences across products. ✔ Duplication of effort: Different teams may end up solving the same problems in different ways, wasting resources. ✔ Lack of scalability: As the organization grows, maintaining multiple systems becomes inefficient and difficult to manage. Solitary model is best for early-stage startups or small organizations with highly specialized needs for products. 2️⃣ Centralized model In the centralized model, a single team (often a DesignOps) is responsible for creating, managing, and governing the design system. All teams within the organization must use this system. Benefits: ✔ Consistency: The centralized model ensures a uniform design language and experience across all products and platforms. ✔ Quality control: A central team ensures adherence to standards, best practices, and quality benchmarks. Downsides: ✔ Bottlenecks: The centralized team can become a bottleneck for requests, slowing down individual teams that need changes or new components. ✔ Limited customization: Teams with unique needs may find the centralized system too rigid or slow to adapt to their specific requirements. Centralized model is ideal for organizations seeking consistency and efficiency but may introduce bottlenecks and lack flexibility for individual teams. 3️⃣ Federated model In the federated model, multiple teams contribute to and maintain the design system. Benefits: ✔ Balanced flexibility and consistency: Teams can customize components to fit their needs while still adhering to a common design language and guidelines. ✔ Shared ownership: Teams feel more invested in the design system, increasing adoption and engagement across the organization. Downsides: ✔ Complex governance: Managing contributions from multiple teams can be challenging, especially in ensuring that changes align with the overall system’s vision and standards. ✔ Coordination overhead: Teams must coordinate their efforts to avoid duplication, miscommunication, or conflicting updates. Federated model balances flexibility and consistency, fostering collaboration, but requires robust governance and communication to avoid fragmentation. 🖼 Governance models by Nathan Curtis #design #UI #designsystem

Most change initiatives follow the same playbook: Announce the vision. Roll out the plan. Push for adoption. Then wonder why nothing sticks. Here are six rules that actually work: 1. Congruence enables empathy Before asking people to shift, understand what keeps the current system stable. What trade-offs are they making? What's working that you might break? Congruence creates the foundation for empathy. Without it, change feels like an attack. 2. Coercion: People don't resist change They resist being changed. Ask what they want to preserve before you tell them what must go. 3. Observe: Current system & situation assess what's possible Observe the system as it is—not as you wish it were. What patterns keep repeating? What forces maintain the status quo? Understanding the current state reveals what's actually possible. 4. Ascertain: Don't rely on hierarchies, weave them into your network Who is trusted? Who do people look to for advice? 5. Guide the change: Work by iterate successive approximations Balance global principles with local needs. Change isn't one-size-fits-all. Set the direction, then let teams adapt to their reality. Guide the principles. Trust teams to find their path. 6. Design experiments: Measure > Evaluate > Adjust In collaboration with people involved in change, make small changes. Change is discovery, not deployment. Design small experiments. Involve people in the design. Measure what happens. Evaluate together. Adjust based on learning. Small changes reduce risk and build confidence. The pattern is clear: These rules aren't about control. They're about understanding. Understanding the system. Understanding the people. Understanding what's possible. Most leaders try to force change. Smart leaders guide it. Subscribe at news.sarajunio.com for frameworks that help you lead change that actually lasts.