Skip to content

Global Design System vs. Local Library

What’s the difference? As we scale our digital experiences across markets and teams, it’s helpful to understand how a global design system and a local library play different but complementary roles.

Global vs. Local

Global Cookbook, Local Flavors

A global design system is the world’s cookbook of core recipes and rules, while a local library is the regional kitchen shelf with adapted versions for local tastes.

Global Design System Our global design system, Builders, is the single source of truth for how we design and build scalable digital products across countries and platforms the entire organization at Gjensidige.

Think of it as the shared language that ensures coherence, quality, and speed no matter where or what we build.

Local Libraries Local libraries are created to support specific product needs and target groups. They allow for local flexibility and can also serve as testing grounds for new ideas that may later be adopted globally. When teams build and share through Local Libraries, our design system evolves in a natural, healthy way. We get a clear view of which components gain traction, which need refinement, and which ideas deserve to move into Builders. How they work together

  • The global system ensures consistency and alignment.
  • Local libraries ensure relevance and agility.
  • Together, they help us deliver better experiences faster while still respecting local needs.

If you’re unsure where to contribute or find what you need, start with the global system and build locally only where the gap is real.

How to build a local library

Sharing with others

Before you build something new, share what you’re exploring. Your challenges and solutions might be useful to others, or already solved. Use these Slack channels for alignment and discussion:

#guild-design #collab-design #guild-frontend  

Always start with Builders  Before designing something new, see if Builders already solves the problem. You can also check in with other Squads to avoid duplicating work. 

Keep your local library open and accessible Always keep your local library open and available for everyone in Figma. We also advise all squads to create their own Storybook, to keep documentation up to date. Use same setup, based on atomic design, as Builders in Figma and in Storybook. Use shared format for naming  A clear, descriptive name helps everyone quickly understand what your local library contains and who it’s for.

  • Use this format: “Descriptive name” Library.
  • Examples: Claims Library and Webshop Library

Related content

Contribute to Builders

See our step-by-step guide on how to add new or improved components to our library.

4 principles for great design

Not just for designers, these principles help us all deliver The Gjensidige Experience. Use the principles as a checklist during the design process or a tool for team discussions.

Embedded applications

To improve user journeys across editorial webpages and applications, the Builders Platform allows you to embed small applications to any page in Content Studio.