Why the Shomrat HaZorea Design System Was an Engineering Decision, Not a Cosmetic One

When we rebuilt Shomrat HaZorea's e-commerce platform, the design system wasn't a styling afterthought — it was the contract that let design and R&D move together. The old transactional site had drifted into one-off product rows and inconsistent spec layouts; every new page meant re-deciding the basics. So I worked with engineering to define a shared component vocabulary up front: the visual cards that power Asaf's Guided Selling, the configuration controls on the product page, the collapsible logistics blocks, the media containers for in-home video. Each existed as a single source of truth, not a screenshot to reinterpret. For a CTO, the payoff is concrete. A configurator that drills from fabric down to the foam in a pillow is genuinely complex; if every interaction were bespoke, the maintenance burden would compound. Reusable, documented components meant R&D spent its effort on the hard real-time results feed, not on rebuilding buttons. It also kept the experience coherent as we bridged physical and digital retail across many product categories. A design system, treated as infrastructure, is what makes ambitious UX shippable and survivable.