Jump to content
Toggle menu
Join us to design better enterprises

Enterprise Design System

Enable your teams across the enterprise to self-organize and make better design decisions faster, through a system of established practices and readymade building blocks. Deliver a coherent, integrated set of solutions across the experience of your customers, and achieve transformation at scale involving all key stakeholders.

Navigate the Enterprise Design Framework
Enterprise Design System

What is it?

The System is a tool made for teams involved in redesigning and transforming parts of the enterprise, such as new products or services, processes or organizations. Designed as a collection of reusable and interconnected building blocks, it regroups the elements needed to co-design and deliver better solutions, faster and more coherently than in isolation: guiding principles for a common purpose, data and insight, reusable pattern libraries, tools for automation and algorithms, and collaboration platforms for cross-team learning to run experiments at scale. The System provides the ingredients and guidance needed to implement solutions that deliver positive impact on the enterprise, itself represented as system landscape. It enables enterprise stakeholders and teams build the right thing the right way.

Beyond individual solutions for singular problems, your challenge involves change at scale in order to deliver across the board. Introduce the System to make the leap from innovation to transformation: work in parallel on a portfolio of connected projects and products, increase coherence between outcomes, align various teams on a common purpose, and reduce the effort of later integration (design debt). Designing a System enables transformation across areas, products and domains of the enterprise. It provides multiple teams with a single tool to design and deliver their part both coherently and autonomously, and doing so faster by working with a shared set of integrated and automated components.

When to use it?

The System is designed to be made available as a digital product, a shared resource across all teams designing parts of the enterprise, connecting various initiatives, products and areas. Start to develop parts of the system that had been triggered by Sprints, a “minimum viable system” out of building blocks that makes it easier running similar workshops. Identify priority Stack aspects across all 5 layers where a System will be the most effective. Make available Scan insights and data relevant beyond individual projects or solutions and measure continuously. Create generic, repeatable Scenarios describing your system landscape making them available for reuse, such as platforms, tools, capabilities, teams that feature again and again in your designs.

How to use it?

The System tool provides guidance and structures to build and adapt a system for transformation. Start to develop parts of the system that had been triggered by design sprints. What would have made the sprints easier to run? A good starting point is to think about a minimum viable System that cuts through the 5 layers of the System rather than focusing only on one layer.

Building Blocks

What are the toughest decisions when designing critical parts of your enterprise? What makes or breaks the user experience, where does coherence matter the most? The generative part of the System, Building Blocks, provides designers with readymade solutions. For each priority Stack aspect identified, it contains tools to guide and accelerate decisions, design patterns for recurring challenges, and a set of reusable assets.

Playbook of Design Principles

A playbook of Principles provides guidance to crucial design decisions and explains universal values behind different products and areas of the enterprise. This creates a shared understanding of what matters most across teams.

Design Pattern Library

A Pattern library contains solution designs and reference models for common challenges encountered by different teams. Patterns save time by providing reusable templates for applied designs, and help achieve enterprise-wide coherence.

Design Asset Repository

A repository regroups recurring design Assets featuring across different designs, such as products or platforms. It describes their nature to design teams reusing them, and makes interdependencies and relationships visible.

System Landscape

Any enterprise it relies on a multitude of interconnected systems to work.The System Landscape captures this is a system of systems using the Stack to navigate different types of systems, such as: your management system and organization design, IT systems and digital platforms, operations and delivery systems. Together they shape the enterprise as a whole.

Systems of Engagement

Systems for engaging and connecting your community of enterprise stakeholders such as staff, clients and partners. Enabling exchange, collective thinking and self-organization around Big Picture challenges and ideas.

Systems of Intelligence

Systems for tracing and managing the interplay of Anatomy elements, the various moving parts of the enterprise. Making well-informed decisions based on live observation through data and metrics.

Systems of Reference

Systems representing the shared knowledge of the enterprise about itself and its environment. Using Frames to establish base models that capture people, transactions, records and rules.

Systems of Design

Systems that enable reinventing and redesigning parts of the enterprise translating insight and knowledge into action. Collaboratively making conceptual decisions in a Design Space of challenges and opportunities.

Systems of Delivery

Systems that accelerate and automate the Rendering of enterprise elements to its various audiences. Bringing the enterprise design to live in tangible, usable artefacts.

Designing with Systems

By introducing the System, you enable your teams to effectively combine Systems Thinking with Design Thinking. Depending on your particular transformation challenge and objectives, designing the System to fit involves determining a set of focus parameters:

  • Pace: focusing on the resilient and stable core, or enabling agile and lean detailed solution design?
  • Time: focusing on future development or current operations?
  • Scale: focusing on high-level models for a shared understanding, or detailed templates and code for fast delivery?
  • Automation: focusing on manual and lightweight documentation, or generative tools for automated delivery?
  • Stream: focusing on a intentful transformation portfolio and specification, or inspiring bottom-up emergence?
  • Perspective: focusing on inside-out delivery and adoption, or outside-in learning and adapting?
  • Governance: focusing on central control of the System or going for distributed ownership?