One quarter of a design system
A tool records a request. An operating model gives it a name and a date. Move week by week through one quarter of Harbor UI, a system we made for testing. Send the Foundations owner on holiday, or let a launch deadline meet the colour rule, and see who acts. The agenda, the queue, the due dates and the expiries are the real output of Loom's governance code, worked out when the page is built. Working Working
ops quarter
| Week | With an operating model | With tools only |
|---|---|---|
| Week 0 · Thursday 5 November | Week 0. Nothing has been asked yet. Thursday's agenda says there is nothing to discuss. | Week 0. Nothing has been asked yet. |
| Week 7 · Thursday 24 December | Week 7. The Foundations owner is away. 2 reviews moved to the delegate and are on Thursday's agenda. | Week 7. 8 requests are recorded with no owner and no due date. The Foundations owner is away, and nothing in the record says who covers. |
| Week 11 · Thursday 21 January | Week 11. The checkout exception expired. The finding is back with the Foundations owner, who must decide again. | Week 11. 9 requests are recorded with no owner and no due date. The checkout exception has no expiry, so it is still in place and nobody is asked to decide again. |
| Week 13 · Thursday 4 February | Week 13. The checkout exception expired. The finding is back with the Foundations owner, who must decide again. | Week 13. 10 requests are recorded with no owner and no due date. The checkout exception has no expiry, so it is still in place and nobody is asked to decide again. |
The live version could not load. The table shows weeks 0, 7, 11 and 13.
Sample data from Harbor UI, a made-up system whose roles are not real people. The queue, agenda, due dates and expiries are the real output of Loom's governance code; the tools-only side shows the same events with no owners, service levels or expiry recorded.
Data: sample records, real governance code.
Start with a conversation about your system.
We read your system, show you what we found, and agree with your team what to fix first.