Maturity and Scale Shape EverythingEarly Systems Start As Survival ToolsGrowth Introduces Complexity and FormalizationEarly-Stage Stories: Making Do with What ExistsMaturity Unlocks Delivery and Reduces RiskAt Enterprise Scale, Systems Become InfrastructureSmall Teams Face Different PressuresThe Pattern Across All TeamsMaintenance Is Harder Than BuildingMaintenance, Not Creation, Is the Real ChallengeProduct Development Outpaces DocumentationGuardrails Become Essential for ConsistencyThe Persistent Gap Between Design and CodeWithout Documentation Rhythm, Everything Becomes a Scavenger HuntIncremental Adoption Is Often the Only Viable PathStatic Tools Cannot Capture Dynamic Interaction ComplexityTokens and Architecture Reduce Maintenance OverheadSmall Details Become Big Problems at ScaleMomentum Keeps the System AliveThe Core Pattern Across TeamsGovernance and OwnershipGovernance Is an Operating Model, Not a RulebookWhy Governance Matters More As Systems ScaleAligning Teams with Competing GoalsAvoiding the Design Police TrapWhen Governance Exists Only on PaperWhen Governance Creates More Problems Than It SolvesGovernance As Enablement, Not EnforcementWhat Mature Governance Looks LikePeople and ProcessDesign Systems Succeed or Fail Because of PeopleCulture and Buy-InHealthy Systems Reflect Healthy CulturesCollaboration Styles Shape How Systems GrowBuy-In Must Feel Tangible, Not TheoreticalChampions Create Momentum Across TeamsPositive Experiences Change Skeptics Faster Than DocumentationMeasurement Challenges Slow Buy-InEvangelism Is Continuous, Not a Launch EventThe Human LayerEmotional and Social Skills Drive Long-Term SuccessTrust with Engineering Must Be EarnedProcess Pressure Influences CollaborationOnboarding Shapes Long-Term AdoptionRelationships Make Systems WorkThe Human Layer Determines System HealthTooling, Automation, and AIFuture-Facing ExperimentsToward More Integrated ToolsInformation Where People WorkAI in Day-to-Day WorkflowsThe Philosophical Edge of ToolingSelf-Documenting SystemsFrom Themes to VoicesInterviewsMarco-Christian KrennKey TakeawaysStatic Tokens and Traditional Systems Break Under Real-World ScaleThe Future of Design Systems Is Logical and AlgorithmicContextual Awareness Is Essential for Accessibility and ScalabilitySemantics Must Replace Stylistic NamingFigma Cannot Be the Source of TruthDesigners Need to Relearn FundamentalsAI Is Useful Only When Deeply Constrained by System LogicDocumentation Must Be Self-GeneratedAccessibility Must Be Dynamic, Not StaticThe Inspiration for the Future of Design Systems Comes from Gaming EnginesLaura WacrenierKey TakeawaysProto Systems Often Emerge Long Before Formal SystemsBuy-In Came from External Pressure, Not Internal AlignmentLaura Is Deeply Skeptical of Design System HypeBureaucracy Is a Major Source of FrustrationDesigners Lose Motivation and Autonomy in Large-System EnvironmentsAI and Design System AutomationShe Does Not Regret Building the System, but Sees a Need for BalanceAccessibility Pressures Are Shaping the Direction of the DSOrganizational Scale Changes EverythingJenil GogariKey TakeawaysDesign Systems As a Natural Convergence of CS, UX, and ProductDesign System Work Often Starts As Tooling TriageBusiness Case: Not “Consistency,” but Platform Scale, Dark Mode, and AcquisitionsGovernance and Resourcing Are Hard, Especially at the BeginningInternal Marketing and Onboarding Are Ongoing, Not One-Time ActivitiesSpeaking the Same Language Between Design and EngineeringDesign Systems As an Integration Layer for Acquisitions and Hybrid ProductsAI, Design Systems, and the Source of TruthDerek HowlesKey TakeawaysGrassroots Beginnings Shape Strong SystemsEngineering Buy-In Is Non-negotiableThe Business Case Cannot Be About Consistency AloneEarly Wins Create the Permission to GrowDesigners and Engineers Think About Systems DifferentlyScale Changes What Designers NeedFigma Is Not the Source of TruthStaff Designers Can Influence CultureDesign Systems at Scale Must Evolve for New AudiencesDon LudwigKey TakeawaysThe Evolution of Design Systems Mirrors the Evolution of CollaborationThe Most Important Work Is Cultural, Not TechnicalStart with What the Product Needs MostNaming and Documentation Will Slow You Down Unless You Plan for ThemMomentum Is FragileSystems Thrive When They Become Tools for Others, Not Artifacts for DesignersReal-World Constraints Shape the SystemGood Governance Reduces FrictionAI Provides Leverage, Not ReplacementSustainable Design Requires CommunityLuke MurphyKey TakeawaysAI Is Shifting How Systems Operate, but Not How They Provide ValueDocumentation As We Know It Is DyingMulti-brand and Multi-product Systems Are at a Breaking PointMeasurement and Insights Are the Next FrontierGovernance Has Not Evolved Since 2016Code Is and Always Will Be the Source of TruthThe Future May Shift Toward Declarative or Generative InterfacesCarl NelsonKey TakeawaysYou Don’t Have to Be on the DS Team to Influence the SystemSystems Thinking Is As Important As ComponentsEngineering Partnership Is EssentialAudits Create Undeniable ClarityIncremental Adoption Works When Tied to Real Product WorkDesign Systems Improve Engineering CultureGovernance Can Help or HinderModern Tooling Speeds You Up but Can Shorten ThinkingThe Future of Design Tooling Should Mirror Film/VFX WorkflowsAI Will Speed Up Production Work, but the Real Value Is UpstreamMeli MarquezKey TakeawaysA Design System Can Fail Before It Begins If It Lacks Leadership ClarityLack of Governance Leads to ChaosSales-Driven Organizations Often Unintentionally Sabotage Design SystemsAdoption Stalls Without Cross-Functional ChampionsLarge Organizations Often Treat Design Systems As Executors, Not PartnersThe Future of Design Systems May Shift Toward Highly Customizable, AI-Generated InterfacesDespite Organizational Dysfunction, Meli Gained Deep ExperienceCole MurphyKey TakeawaysStartups vs. Scaled Orgs Produce Very Different “Systems”Design Systems Become Non-negotiable at ScaleFederated Product Systems on Top of a Strong CoreTight Constraints in Tools Protect the SystemPatterns and Flows Matter As Much As ComponentsWhen the System Is Weak, Every Designer Becomes a ScavengerAd Hoc, Fire-Drill Contributions Are Not a Governance ModelExecutive Misunderstanding of Design Systems Is a Major BlockerThe Incentive Structure Is Skewed Toward Visual Novelty, Not UX SystemsWithout Systems, Developer Tools Become Over-designed and Under-coordinatedCulture Around Sharing Patterns Affects System HealthSystem Work Is Leadership Work, Even Without the TitleTiago AlmeidaKey TakeawaysBeing a Team of One Is Still the NormCraft Is Easy. People Are Hard.Adoption Problems Come Back Years LaterPatterns and Templates Matter More Than ComponentsThe Figma-to-Code Divide Is Real but PragmaticVibe Coding and AI Are Not the Future People ThinkLeadership Skills Matter More Than Technical SkillsBurnout and Low Collaboration Are the Real BlockersJohn MurrayKey TakeawaysAdoption Depends on Advocacy, Not AssetsConsumption and Contribution Are Different ProblemsGovernance Must Balance Consistency with AutonomyDesigners Must Be Comfortable Pushing BoundariesComing into a Mature System Is Both Liberating and IntimidatingAI Is Interesting, but Not Transformative YetThe Value of a Design System Shows Up in Speed and ConfidenceMélanie WiderKey TakeawaysComing to Design Systems Through Chaos and GrowthThe Tradeoffs of a Mature System in a Large OrgFinding the Balance Between Speed and ExplorationDesign Systems As Both Enabler and HindranceThe Real Work Is People, Trust, and CollaborationGovernance vs. Guilds and the Importance of Shared SpacesAI, Recommendations, and Emerging Cross-Product PatternsNatalya ShelburneKey TakeawaysDesign Systems Are About People, Not ComponentsThe False Divide Between Art and TechnologyOwning the Polish Requires Owning the CodeDesign Systems As EcosystemsBuy-In Fatigue and the Plumbing MetaphorAI, Artists, and Technological ChangeCommunity As the Next Layer of InfrastructureCase StudiesA GitLab Case StudyBackgroundProblemOur RolesSarrah Vesselov, UX ManagerTaurie Davis, Senior UX DesignerChallengesMisconceptions and Buy-InOur ApproachOutcomeResourcingOur ApproachOutcomeToolingOur ApproachOutcomeStructure and SetupOur ApproachOutcomeComponent Redundancy: Buttons, Badges, Labels, Tags, Oh My!Our ApproachOutcomeCommunicating ValueOur ApproachOutcomeLessons LearnedNext StepsMarketingLess Reliance on Design ToolsTying It All TogetherKERN: Building a Nationwide UX Standard for the German Public SectorA National Design ChallengeInterview ContextOrigins: From Shared Frustration to Shared VisionContext and Constraints: Fragmentation, Trust, and IdentityTechnical Breakthrough: From Prescriptive Vision to InfrastructureA Prescriptive StartThe Limits of Web ComponentsThe Plain CSS and HTML PivotFrom System to InfrastructureDesign Foundations: Establishing a Shared UX LanguageDesign TokensLayoutColor and AccessibilitySpacing and DensityTypographyInteraction and MotionIconographyBranding and Theming: Preserving Local Identity While Building National RecognitionGovernance: Balancing Stability, Flexibility, and a Federated RealityA Hybrid Model Built for a Federated SystemThe Core SystemThe Extensions LayerGraduation Based on Real-World ReuseLearning from Past FailuresGovernance As DiplomacyWhy Governance MattersCommunity Infrastructure: The Engine Behind KERN’s MomentumA Collaborative Network Across Public and Private SectorsOnboarding and SupportCommunity Calls and Open ExchangeClear Contribution PathwaysTransparent Component LifecyclesWhy Community MattersGaining Consensus: Diplomacy As a Design CompetencyEarly PushbackDiplomatic FramingTurning PointsImplementation: From Early Pilots to a Scalable SystemStarting with Real ServicesIteration Through UseScaling Across Diverse EnvironmentsImplementation As MomentumImpact: Strengthening Trust, Efficiency, and Public Sector CollaborationRecognizable Government UXFaster Delivery and Reduced DuplicationAccessibility by DefaultVendor Efficiency and PredictabilityNational RecognitionCultural ShiftWhy Impact MattersChallenges Ahead: Sustaining Momentum in a Federated SystemLimited Adoption VisibilityUneven UX and Technical MaturityPolitical and Administrative ChangeMaintaining Community EnergyLong-Term Technical StewardshipIntegrating Emerging TechnologiesWhy These Challenges MatterKERN’s Transferable LessonsDesign Systems Must Reflect Organizational RealityInfrastructure Thinking Changes EverythingGovernance Is Structural EmpathyIdentity and Consistency Can CoexistCommunity Sustains What Policy CannotTrust Is Both Outcome and MechanismDiplomacy Is a Core Design Skill
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.