SAP Design System Essentials

Introducing the InnerSource Model

Learning Goals

• Understand what a InnerSource Model is and why we apply it to the SAP Design System

Content

In June 2024, the InnerSource Model for Web has been launched. But what exactly is the InnerSource Model? Where does the concept come from? And why is it the best organizational model for SAP Design? In this episode, Jan Rüssel answers these and other basic questions on this topic.

Play Podcast

Duration: 20 min 44 sec

Recently version 2 of the process was introduced. Jan Ruessel shared the updates with more than 250 people who joined the very first session of the 2025 SAP Design System Learning Series.

Play Video

Duration: ca. 58:56 min

Introduction to the InnerSource Process for Web

Learning Goals

• Understand the InnerSource for Web process and its key steps.
  Know how to find relevant documentation and where to look for additional information.

Content

With the introduction of the InnerSource process for Web, all requests to enhance or modify the design system must be submitted via dedicated services. Using these services ensures that the InnerSource team can involve all product design teams in relevant decisions and keep them informed about updates.

In our Experience Garage Mission, you will get to know the InnerSource Process for Web as such and the phases it consists of.

Start Mission

Duration: ca. 26 min

The Design System Services within the InnerSource Process for Web

Learning Goals

• Get to know the types of design services available
• Learn about the kinds of requests you can create
• How to choose the right request for your needs

Content

The InnerSource process is designed to enable all design teams to contribute to and benefit from the SAP Design System. While individual teams are fully responsible for certain parts of the process, other teams and stakeholders are also involved in various aspects.

These aspects primarily relate to the organization of the design system, including the creation of new elements, requests to other teams, and changes that affect stakeholders.

To address these needs, two design services have been defined to ensure that all interests are considered, and the structural integrity of the SAP Design System is maintained.

Request: Ask for a design feature or element

As a member of the product design team, follow these steps to request features or contribute new elements to the design system using the InnerSource process:

• Request a Feature: If you need a feature for a design system element owned by another team, submit a request and our InnerSource team will connect with the right team to manage it.
• Suggest a New Element: If you notice a missing component, you can propose a new design system element. We’ll check for name conflicts and add it to our inventory.
• Temporary Ownership: If you require a feature for an element that currently has no owner, you can take on temporary ownership to help bring your idea to life.

Submit a Request If You:

• Need a new feature from a design system element owned by another team.
• Want to add a new element to the design system.
• Need a feature for an unowned element and are willing to take temporary ownership.

To learn more, you can watch the video below.

Watch video

Duration: 23 min 30 sec

Contribute: Work on an element you own

As a design owner, you can apply changes and enhancements to a design system element and document these updates through the InnerSource process. This ensures clear visibility and helps gather feedback while maintaining quality assurance in a centralized location.

Steps for Design Owners:

• Receive Requests: Accept enhancement requests from other teams through the InnerSource process.
• Initiate Enhancements: Plan and implement your own enhancements to the design elements as needed.
• Document Work: Use the InnerSource process to document your changes, making them visible to other product teams.
• Gather Feedback: Collect feedback and request reviews or approvals for significant changes.
• Quality Assurance: Document quality checks and approvals centrally, ensuring transparency in your design work while keeping your planning in your local backlogs.

By following these steps, you can effectively enhance design elements while fostering collaboration and visibility across teams.

Watch video

Duration: 13 min 49 sec

The InnerSource Process from another perspective

Learning Goals

• Get to know the perspective of an Product Area on the InnerSource Process for Web
• Build empathy for the needs and challenges of different contributers

Content

What does it take to create such a complex process as the InnerSource Model? What do you need to do and be aware of when designing it?

In the first podcast episode of this learning chapter you’ll hear the answer from the perspective of a product area (Sunnya Göldner, Cloud ERP) and Core Design (Jan Rüssel). Both guests will take you through the different steps, the needs from everyone involved, the challenges that were overcome, and valuable lessons learnt. A lot still needs to be done to leave the rough waters of the early phase and enter the realms of plain sailing. But the boat is sturdy and well on its way.

Play Podcast

Duration: ca. 25 min

In the second podcast episode of this learning chapter Seiji Ike-Glenn from Concur and Maximilian Kautetzky from Signavio share their views on how SAP's InnerSource process is reshaping collaboration in their teams outside of SAP Design. They discuss real-work examples of breaking down silos, boosting innovation, and what the InnerSource process means for the future of their work.

Play Podcast

Duration: ca. 16 min

InnerSource in Action

Learning Goals

• The InnerSource Process in a nutshell
• Deeper understanding of the InnerSource for Web process by two examples

Content

What exactly is InnerSource? Who are the key players involved? And how does the process of submitting and processing a request within the SAP Design System work? In a video series of 6 parts, Jim lead you through the practical aspects of InnerSource in Action, explaining everything you need to know!

Watch Videos

Duration: ca. 16 min

Understanding the Roles within the InnerSource Process for Web

Learning Goals

• Understand the roles involved in the InnerSource Process for Web
• Be familiar with the tasks and responsibilities associated with each role

Content

The InnerSource Process for Web is carried out by several roles that play an important part at different steps in the process. In this video, you'll get an overview about the different personas and their tasks and responsibilities.

Play Video

Duration: 04 min 04 sec

In this Experience Garage mission, you will learn about these roles, their specific responsibilities, and how they contribute to the success of the process in more detail.

Start Mission

Duration: ca. 24 min

Process Owner, Design Ops Processor, Design System Expert … difficult words with responsibilities in the InnerSource process that are difficult to remember, right? Not with this entertaining podcast episode, in which Benji and Vessi explain everything you need to know about these new roles in no time at all! (Well, ok, see time stamp below…).

Play Podcast

Duration: ca. 18 min

The Role of the Requester

Learning Goals

• Understand the role of a requester within the InnerSource Process for Web
• Get to know the tasks and responsibilities of a requester

Definition

The term requester typically refers to an individual within an organization who makes a formal request for a specific product, service, or information.

In the context of the SAP Design System, everyone can be a requester. But before submission it must be reviewed and authorized by a design system expert or other nominated person who is authorized to submit an official request to the design system on their behalf.

Contribution to the InnerSource Process

Usually, the role of a requester involves initiating the request process by outlining the details of what is actually needed from the design system. He might be involved in deriving the design system requirements from product design requirements before formulating and submitting an actual design system request.

Tasks and Responsibilities

• Contributes to identify and derive the actual design system requirements from product requirements within the product area
• Formulates the design system request and provides detailed requirements for the request
• Knows the InnerSource process steps and follows the guidelines for submitting a design system request
• Acts as single point of contact and representative for this request
• Provides feedback and necessary information to support the fulfillment of the request

Request Preparation

Learning Goals

• Understand what to consider before submitting a request
• Go through each step to collect and analyze the needed information before submitting a request
• Understand the process, the types of requests available and when to use them

Use Case

As a requester you might face yourself in the situation to create the design for a new application. When you checked the available elements, you found out that there is a feature missing for the rich text editor and you want to request it. What do you need to do?

Step-by-step

Discovery & analysis phase is the first step in the InnerSource process where we make sure that what we request is the right fit for the SAP Design System.

1. Define the Design Gap
   This is the first step where you as a designer should answer few questions:

   1. What user needs the new feature/ element will fulfill?
   2. How will it enhance the user experience
      of the application you are designing?
   3. How do you imagine it will look like / behave / function?
   4. How does the new feature relate to the existing element, and how does it affect all other related elements?

2. Due Diligence
   Before you submit a request, make sure that it’s a unique and valid request

   1. Analyze the design system requirements in detail.
   2. Check if similar requests are already in place both in the internal backlog or the E-Jira.
   3. Check if another team from your area or other area has similar needs.

3. Identify the affected elements
   Outline the impact of the requested feature or element

   1. If it is a feature of an existing element, how will this feature change its current behavior?
   2. If it is a feature of an existing element, how will the change affect all the other elements that are part of their structure? Which ones will be affected by the change?
   3. If it is an element, is there a possible use of it for the existing elements? How can it enhance the behavior of the mentioned elements?

1. Document the findings

   1. Use the respective request template to document your findings.
   2. Get feedback from the Design System Expert of your area, from the design owner of the affected element(s) and development.
   3. Adjust request documentation if necessary

Understanding the Request Template

How to Submit a Request

Submitting a request to the SAP design system is very easy, but being prepared and having all the needed information at hand is the trick. Jim will give you an overview about the preparation basics in this video based on a real example.

Play Video

Duration: 01 min 52 sec

Training Material

Self-Study Courses

• InnerSource Process for the SAP Design System (Track)
• Introduction to the InnerSource Process for Web
• Understanding the Roles in the InnerSource Process for Web
• The Role of a Design System Processor in InnerSource Web Development

InnerSource in Action - A Video Series

• Video series

Design is People Podcast

• Episode 03 - Introducing the InnerSource Model
• Episode 05 - The Roles within the InnerSource Process
• Episode 09 - What it Takes to Create the InnerSource Process
• Episode 11 - Transforming Collaboration across LoBs: The InnerSource from another perspective

Additional Information

InnerSource Process for Web

• InnerSource for Web Sharepoint
• InnerSource for Web on SAP Design System Sharepoint
• InnerSource MS Team Channel
• Ownership List
• Design System Experts