Scalability in Design Systems

#Schema2025 just introduced major updates that will change how we build and scale design systems in Figma. The new features are exactly what large teams have been asking for more control, more flexibility, and less overhead. We’re especially excited about what this means for teams trying to scale design systems without slowing down their workflow. → You can now organize variables into collections Perfect for managing themes, brands, or localization without making a mess. → Components now support slots This gives teams flexibility without relying on overrides or hacks. → Figma added a native design linter So consistency is no longer a manual process—it happens by default. → Dev Mode is maturing fast Specs, handoffs, updates—all in one place, right inside Figma. They directly impact how fast teams can move while staying aligned. By combining design tokens, component logic, and Figma Make prototypes with MCP-based development workflows, we’re seeing measurable gains: → Prototypes built faster → Components reused across teams → Less design-developer back and forth → Reduced rework and decision fatigue If your team is developing or expanding a design system and you're interested in how to integrate this into your workflow or product team, feel free to leave a comment or reacht out. We're always happy to share what we've learned.

A junior reached out to me last week. One of our APIs was collapsing under 150 requests per second. Yes — only 150. He had tried everything: * Added an in-memory cache * Scaled the K8s pods * Increased CPU and memory Nothing worked. The API still couldn’t scale beyond 150 RPS. Latency? Upwards of 1 minute. 🤯 Brain = Blown. So I rolled up my sleeves and started digging; studied the code, the query patterns, and the call graphs. Turns out, the problem wasn’t hardware. It was design. It was a bulk API processing 70 requests per call. For every request: 1. Making multiple synchronous downstream calls 2. Hitting the DB repeatedly for the same data for every request 3. Using local caches (different for each of 15 pods!) So instead of adding more pods, we redesigned the flow: 1. Reduced 350 DB calls → 5 DB calls 2. Built a common context object shared across all requests 3. Shifted reads to dedicated read replicas 4. Moved from in-memory to Redis cache (shared across pods) Results: 1. 20× higher throughput — 3K QPS 2. 60× lower latency (~60s → 0.8s) 3. 50% lower infra cost (fewer pods, better design) The insight? 1. Most scalability issues aren’t infrastructure limits; they’re architectural inefficiencies disguised as capacity problems. 2. Scaling isn’t about throwing hardware at the problem. It’s about tightening data paths, minimizing redundancy, and respecting latency budgets. Before you spin up the next node, ask yourself: Is my architecture optimized enough to earn that node?

Design Systems for CRM: The Hidden Engine Behind Scalable Email & Lifecycle Operations Most teams treat “Design Systems” as something only UI or product teams need. But in CRM & Email Marketing, a well-built design system is one of the strongest multipliers of speed, quality, and consistency. Here’s why: 1. Faster Production, Less Rework When every email shares the same components: headers, footers, CTAs, spacing rules, containers. Your team spends less time reinventing layouts and more time improving performance. 2. Modular HTML = Fewer Errors Clean, tokenized, reusable modules cut QA time drastically. Instead of checking full templates repeatedly, teams validate just the variant blocks that change. 3. Consistency at Scale A design system ensures that whether 2 people are building emails or 20, the output looks aligned, intentional, and brand-safe. No random colors. No inconsistent padding. No creative drift. 4. Faster Journey Launches Pre-built journey patterns (welcome, cart abandonment, re-engagement, win-back, promo) cut launch times from weeks to days. You start optimizing earlier instead of building from scratch. 5. Easy Cross-Team Collaboration Marketing, Design, Dev, and CRM Ops all work from the same source of truth, same components, same tokens, same rules. That alone removes dozens of weekly back-and-forths. 6. Scalable Across Geos & Brands If you manage multiple brands or markets, a CRM design system becomes the backbone of multi-region automation. One core system → variations per market → zero chaos. 7. Higher Throughput Without Hiring More When production is standardized, volume goes up without increasing headcount. Same team, more output, better quality. The best CRM engines aren’t powered by bigger teams. They’re powered by better systems. Invest in a design system once, and your CRM workflow becomes faster, cleaner, and exponentially more scalable - month after month. #CRMOperations #EmailMarketing #MarketingOps #DesignSystems #Braze #SFMC #Automation #ScalableExecution

Most design systems don’t fail because they’re poorly designed. They fail because they try to change everything at once. I’ve seen this across enterprise teams again and again. A system is introduced to unify experiences overnight. Instead of accelerating teams, it slows them down. Adoption stalls. Workarounds appear. Consistency turns into friction. The problem isn’t the system. It’s the approach. At SAP, we’ve learned that design systems don’t scale through disruption. They scale through progression. That’s why our system is built as a 4-layer model, enabling phased adoption instead of a full reset. It starts with design language. Colors, typography, and iconography that build trust across every touchpoint. Then UI components. Reusable building blocks. Today, 80–90% of SAP products are already aligned here. Next, design patterns. Proven solutions with real, reusable code that reduce reinvention. And finally, floor plans. End-to-end layouts that orchestrate complete workflows. This approach recognizes the realities of enterprise complexity while ensuring  a cohesive experience across SAP's vast portfolio. The goal isn’t perfection on day one. It’s momentum that compounds over time. So before you scale your system across every product, ask yourself: Are you enforcing consistency… or designing for adoption? #SAPDesign #SAP #ArinBhowmick

Can you deliver consistent UX across thousands of enterprise products without a design system? At SAP, the answer is: definitely not! Arin Bhowmick just shared how the SAP Design System plays a key role in connecting teams, products, and experiences at scale, and it’s a solid example of what enterprise-grade systems need to support: 🔹 Shared design principles across domains 🔹 Reusable UX components and patterns 🔹 Built-in accessibility guidance 🔹 A unified visual and interaction language, from product to brand to platform When the complexity grows (teams, tech, products, timelines...), the system becomes the glue that keeps experiences aligned. The SAP DS empowers designers and devs to move fast, stay consistent, and deliver experiences that feel connected, regardless of how deep or broad the product portfolio goes. 📎 Explore: https://lnkd.in/e6UpMZ6e Design systems aren’t just about consistency; they’re about scaling clarity. What’s your take on how design systems evolve in large enterprise environments? Drop your thoughts below 👇 #DesignSystems #designsystem #UXDesign #UIDesign #uiux #uxui #ProductDesign #DesignOps #UserExperience