- **Epistemic status:** #seedlings A [[Design Language System]] needs to adapt to the needs of the user when you have an established team that [[Develop and maintain a library for your Design Language System]]. If the [[Design Language System]] is understood as an unchangeable source, the users will perceive it as an unhelpful tool and start looking for better alternatives. Having a clear governance plan can allow the [[Design Language System]] to thrive as time goes on. Answering the following questions can help you get started: - What happens when an existing pattern doesn’t quite work for a specific application? Does the pattern get modified? Do you recommend using a different pattern? Does a new pattern need creating? - How are new pattern requests handled? - How are old patterns retired? - What happens when [[Software Bug]]s are found? - Who approves changes to the [[Design Language System]]? - Who is responsible for keeping documentation up to date? - Who makes changes to the UI patterns? - How are changes in the [[Design Language System]] deployed to live applications? - How will the users find out about new changes? Ensure to make communication between the maintainers and the users as easily as possible, having resources for submitting a [[Software Bug Report]] or getting ad hoc support. Schedule regular meetings to review the [[Design Language System]] to get more official feedback and keep the [[Stakeholders]] up-to-speed on the roadmap to make sure the needs of the business are addressed. --- ## References - “Atomic Design by Brad Frost” Accessed Jun 15, 2022. <https://bradfrost.com/blog/post/atomic-web-design/>