← All case studies

Figma × Loblaw Digital

Figma x Loblaw Digital, one design system for 14 brands

Homepage build time from three months to two weeks

Fragmented and duplicating work to building on a shared, federated system

Members read free

Unlock the full breakdown

Enter your email to open every case study in the library: the full screenshot, why it works, and the one thing worth stealing. One email unlocks all of them.

Free. No spam. Unsubscribe anytime.

Why it works

The story leads with something Loblaw could not do before: run a single, federated design system across 14 distinct brand identities without forking or rebuilding components for each. That is a genuine New Capability claim, not just a speed improvement, though efficiency gains (the three-month to two-week homepage build) are the clearest proof point. The piece is honest about what is still in progress, citing MCP Server and Code Connect as early-stage explorations, which adds credibility.

Steal this

Anchor the scale of the problem in concrete numbers before introducing the solution. Loblaw's opening context, 14 brands, 40+ websites, 4 apps, 3,000 locations, 80% of Canadians, makes every subsequent efficiency claim feel earned rather than generic.

Full screenshot of Figma x Loblaw Digital, one design system for 14 brands Click to enlarge ↗
View the original on figma.com ↗

This is editorial commentary and curation. The case study, screenshot, and all metrics are Figma's published work; we link to the source and lead with our analysis.

  • Vendor Figma
  • Customer Loblaw Digital
  • Industry Enterprise Software
  • Trigger Legacy tool stack could not support scale of 14 brands and 40+ digital properties
  • Format Written narrative
  • Structure Challenge-Solution-Results
  • Medium Web page