operations
how the company runs — vendors, tooling, the glue work
Holds what the company runs on: the tools, the vendors, who owns each and how a new one gets in. Take it when the work that is invisible until it fails needs an owner.
structure generate department operationsOperations — Mission
how the company runs — vendors, tooling, the glue work.
Purpose. One paragraph: what operations is accountable for, which is usually the work that is invisible until it fails. Name two or three things that must never be discovered by a customer, and say that this department owns them.
How work gets done here. Steering docs live at this root — what we run on and how something new
gets in. Repeatable how-tos in processes/; vendors, accounts and the record of what changed
accumulate in records/.
---
type: mission
standing: draft
owner: "{{owner}}"
updated: "{{date}}"
---
# Operations — Mission
_how the company runs — vendors, tooling, the glue work._
**Purpose.** _One paragraph: what operations is accountable for, which is usually the work that is
invisible until it fails. Name two or three things that must never be discovered by a customer, and
say that this department owns them._
**How work gets done here.** Steering docs live at this root — what we run on and how something new
gets in. Repeatable how-tos in `processes/`; vendors, accounts and the record of what changed
accumulate in `records/`.
type: department
name: operations
description: "how the company runs — vendors, tooling, the glue work"
about: "Holds what the company runs on: the tools, the vendors, who owns each and how a new one gets in. Take it when the work that is invisible until it fails needs an owner."
version: "0.1.0"
Also in the folder
Tooling and Vendorsdepartments/operations/tooling-and-vendors.md
Tooling and Vendors
What the company runs on, who owns each piece, and how a new one gets in. Tools arrive one afternoon at a time; this document is what stops the stack from becoming an archaeology problem.
What we run on. The tools that matter, each with an owner by name and what it is for. One line each. If nobody owns it, that is the finding — write the name of whoever will.
How a new tool gets adopted. Who decides, what has to be true before it holds company data, and whether it replaces something. A tool that is added without something being removed is a decision to carry two.
Access, and what happens when someone leaves. Where accounts live, who can grant them, and the list that gets walked on a last day. Write it now; nobody writes it on the day.
Data, and where it sits. Which vendors hold customer data, and what you would have to do to get it back or delete it. If you do not know, "we do not know" is the honest first draft.
What we deliberately do without. The category everyone expects you to have and you have chosen not to, with the reason.