— Donella Meadows, systems researcher / Source (Google Books)

— Donella Meadows, systems researcher / Source (Google Books)

The documentation is not just for designers and developers. It's also for content strategists, marketing teams, product managers, ….

— Bethany Sonefeld, IBM / Source (YouTube)

https://twitter.com/runemadsen/status/1027592311792971776

What do document

Every decision

This helps future teams to challenge these decisions and it offers a base for discussion.

Versioning

Context

Contributions

Celebrate contributions and gives teams the feeling of being part of the design system.

Contribution

Meeting notes

Share meetings notes to enable quiet people, remote workers and people on vacation to participate.

Meetings

Processes

Make processes clear: Document everything, even if the processes seam obvious for you. Set the expectations very clear.

— Inayaili de León, Microsoft Azure / Source (YouTube)

Overviews

Provide a master table where you can show, which component is located where.

Screenshot from Atlassian
– Sarah Federman, Adobe / Source (YouTube)

Screenshot from Atlassian – Sarah Federman, Adobe / Source (YouTube)

Further readings

All design projects should start in a Google Doc