## Summary
The design system's governance model outlines the decisions, steps and collaborative processes involved in the creation, re-usage, modification and deprecation of system components (either core or project one-offs). It also sets clear collaboration guidelines that will enable teams to actively contribute to the system.
#### Relevant links
* [[ https://www.figma.com/file/cnbxl3nG6CKpjaTSjXTwQk/Wikimedia-Design-System-(DS)-%E2%80%93-Governance-model%2FDACI | Preliminary Governance Model diagram ]] (pictured below)
---
## Objectives
### 1. Validate the high-level paths and processes involved in the creation of components, from the appearance of the component need until its release.
Walk through the model and validate.
{F34574303 width=100%}
See [[ https://www.figma.com/file/cnbxl3nG6CKpjaTSjXTwQk/Wikimedia-Design-System-(DS)-%E2%80%93-Governance-model%2FDACI | Figma ]] for the living process model.
#### Outcomes
To be documented
### 2. Align on the initial model's guiding principles
The following guiding principles were developed and followed during the creation of the initial model:
- **Transparency**: Tasks status and progress is clearly shared and made accessible to all stakeholders. Gatekeeping, development, design and product decisions are made in the open.
- **Enablement rather than enforcement**: System consumers are considered contributors, and should be empowered by the core team to make decisions and own parts of the system. Product teams have a level of choice and impact on the system (e.g. suggesting components or variants, suggesting fixes or enhancements, or providing feedback for the governance model itself).
- **Knowledge sharing rather than knowledge silo**: Contributors should have support and access to resources that allows them to understand and influence the system's workflows, methodologies, standards and infrastructure.
#### Outcomes
To be documented
=== 3. Identify and settle on decision-making steps for DACI assignment later
Identify & define all decision-making steps to assign in close exchange with stakeholders and leadership so-called DACI (Driver, Approver, Consulted, Informed) roles and responsibilities in the aftermath of developer summit.
See [[ https://office.wikimedia.org/wiki/Product/DACI | Product Department DACI ]] & [[ https://www.atlassian.com/team-playbook/plays/daci | Atlassian documentation on the DACI model ]]
==== Outcomes
- Bring our ideas and a refined model to the dev summit next.
To be documented