Five everyday moments in a design-system team, with and without an operating model

1. DesignerFigma

   Detaches the Button to change one colour for a campaign.

   Without an operating modelThe copy stays in the file. Nobody hears about it.

   With LoomLoom's Figma audit reports the detached copy. The fix goes to the queue for the UI engineer, due 25 Nov.

2. DeveloperSlack

   “Can I use this Card here?”

   Without an operating modelAnswered days later, in a thread nobody will find again.

   With LoomTheir agent asks Loom's MCP server and gets the Card, its rules and the exact import.

3. Product managerSlack

   Needs a raw brand colour for Friday's launch.

   Without an operating modelGranted in a direct message. No end date, so it never comes back.

   With LoomRecorded as an exception, granted by the Foundations owner, ending 19 Jan. Then it comes back to Thursday's agenda.

4. System teamOffice hours

   Twelve direct messages and a full office hour.

   Without an operating modelDecisions stay in threads. The same questions come back next week.

   With LoomThursday's triage: Loom drafts the agenda from the queue. Each decision is recorded in the repository.

5. Coding agentGitHub

   Builds a confirmation dialog for the settings page.

   Without an operating modelIt imports a modal from another library. It is merged. Now there are two.

   With LoomIt checks its draft against the system first. The off-system modal is caught before review.