the zeal operating system · 7 documents

playbooks.

the how · the doing

seven playbooks. one per department.

Each playbook is a defined chain of roles, phases and systems — designed so projects never drift, ownership is always clear, and nothing relies on memory. Where Core OS sets direction, the playbooks are how the work actually moves.

how to read this

depth, where it’s useful.

Departments are centres of excellence. Projects are where integration happens.

Each playbook is owned by a Head of Department. They cover the standards, checklists, hand-offs and decisions that keep the wheels turning — the level of detail Core OS deliberately avoids. Read whichever is most relevant to your role first; the rest are there when you need them.

Three are project-facing (projects, creative, technical). Four are business-support (operations, people, marketing, finance). The line between them is deliberately porous.

the why

playbooks put principle into practice.
core OS says why.

If these seven documents are the how, the Core OS is the why — six documents covering mission, culture, brand, structure, decision-making and the lean stack we run on.

go to core OS