The DesignOps Operating System.
A one-page canvas that turns DesignOps from a deliverable factory into an org-level operating model — workshop-ready, AI-aware, and forkable by any design org.
- Org
- Open framework
- Role
- Author
- Year
- 2025–26
- Discipline
- Operating model
Where most DesignOps shops get stuck.
Most DesignOps functions live in tickets, intake forms, and rituals — useful at the team level, invisible at the org level. When a CEO, a CFO, or a head of product asks "what is DesignOps actually for here?", the function struggles to answer in one frame.
The Operating System Canvas is that frame. Ten blocks, one page, one conversation. Each block names a decision the org has to make on purpose — or by accident.
Make the operating model legible.
v2 named the ten decisions a DesignOps function must make: who its customers are, how it intakes work, how it decides what to do, how it governs quality, how it handles risk, and how it matures. The canvas became a workshop tool — the artifact you put on the wall when a new design org is forming or an existing one is resetting.
AI as rails inside every block.
v2b added two rails to every block: an AI Design rail (how AI changes the practice inside that block) and an AI Ops rail (how AI changes the operations behind it). The point was not to bolt AI onto the side of strategy — it was to make AI a structural question every block of the operating model had to answer.
A CEO can read it. A staff designer can fill it in. A new DesignOps lead can fork it on day one.
Every block has an AI rail. The model refuses to treat AI as a sidebar.
Sized to A1, scaled for 3×3 stickies, with facilitator notes printed on the artifact itself.
What changed when teams adopted it.
Where this canvas has been used, the conversation moves out of ticket queues and into operating-model decisions inside a single workshop. Design leaders walk out with a one-pager they can present to the rest of the C-suite — and a backlog of operating-model investments, not a backlog of deliverables.
Download the full Canvas (PDF, 33 MB) · v2b AI Rails draft (PDF)
How this maps to leadership principles.
- Think Big: a one-page artifact every design org in the company can fork — strategy that travels.
- Insist on the Highest Standards: the canvas crits the operating model the way a designer crits an interface.
- Are Right, A Lot: the rails force structured choices on AI rather than allowing default-on or default-off.
- Ownership: this is the artifact you hand a new DesignOps leader on day one to own their function end-to-end.