Coop digital experience

The vision, mission, and principles that guide how CDS supports Coop's digital products.

Vision

CDS aims to set the standard for design systems in Sweden — and beyond. Not for recognition, but because the quality of our shared tooling directly shapes the quality of every product Coop ships.

A design system at this level does more than reduce duplication. It enables teams to move faster, innovate with confidence, and build digital products that genuinely earn trust. It also shapes the kind of organisation Coop becomes — one where strong designers, developers, and product thinkers choose to do their best work.

Mission

What CDS delivers looks different depending on where you sit.

For individual contributors

Designers, developers, content, and accessibility specialists succeed when they can move fast with confidence. That means components that are trustworthy, documentation that's accurate and genuinely useful, and a community that raises everyone's skill level.

We measure this through quality of output, adoption of what we ship, and whether contributors feel equipped — not just informed — to innovate.

For management

CDS contributes to delivery speed and process efficiency. Shared components reduce duplication, speed up reviews, and make on-time delivery more predictable. The value shows up in how well teams collaborate and how much time is freed up for work that matters.

For leadership

CDS is a strategic asset. The right measure of value isn't story points — it's product impact and organisational adoption. We focus on growing team capability and culture, retaining and developing the people who drive it, and making design system contribution something teams choose, not something imposed on them.

Principles

Guide, don't restrict

CDS exists to give product creators the right tools — not every possible tool. We've thought carefully about what to include, which means what's here is trustworthy and what's missing is intentional. Consistency and flexibility aren't in opposition; they're balanced by choosing well up front.

A way of working, not a deliverable

CDS isn't a Figma file, a component library, or a token set. It's a shared understanding across all platforms and disciplines that consume it. The hard deliverables — documentation, foundations, tokens built for multi-brand and theming, patterns — are expressions of that understanding. The system lives between them.

Democratised knowledge

The rules that once lived as invisible verbal glue inside the design team now belong to every product creator at Coop. No single entity owns CDS. The people who maintain it are its protectors at this point in its life — but the system itself belongs to everyone who builds with it.

Speed enables quality

Speed isn't the enemy of quality — it's how we find it faster. Moving quickly lets us validate decisions sooner, correct them earlier, and evolve the system at a pace that keeps it useful. Slow and careful sounds responsible; fast and deliberate is better.

Rigour in what we build

Adding to the component library is not a light decision. The process must be deliberate, because what we ship becomes part of the foundation others build on. When a component earns its place, it's built to provide enough freedom for product teams to create things Coop hasn't made yet.

How CDS supports the vision

Adopting CDS gives a team a package of speed: a set of tools, a kit of components, and a way of working that conforms to the Coop brand without imposing on it. Whether a team needs to follow established design principles or push beyond them, CDS is built to support both.

The bridge between design and development runs through tokens and components that exist consistently across platforms. A semantic token defined in Figma carries the same name in code. A component built for web has a counterpart in the Figma library. This shared language removes the translation cost at handoff and keeps design and implementation aligned over time.