Runbook / Playbook

A runbook is a step-by-step procedural guide for a specific, repeatable operation. A playbook is a strategic response guide for a class of situation. Both artifacts encode institutional knowledge and enable consistent execution without relying on the same individual each time.

Runbooks: task-level execution guides

A runbook covers one task at the level of precision needed for a competent practitioner to execute it without additional guidance. It includes the prerequisites (access, tools, data), the steps in order, decision points and their outcomes, common failure modes and how to handle them, and a verification step to confirm success. The target audience is someone who is competent in the domain but has not performed this specific task before.

Common runbook subjects in professional services: monthly billing reconciliation, client environment setup, data migration validation, go-live cutover sequence, support ticket triage.

The trigger for creating a runbook is the second time someone explains the same process. If it needed to be explained twice, it belongs in writing.

Playbooks: situation-level response guides

A playbook covers a category of event. It defines the roles involved, the decision tree, the escalation path, the communication plan, and links to the specific runbooks that apply. A single playbook may reference several runbooks.

Common playbook subjects: client onboarding (from signed SOW to kickoff), incident response (from detection to resolution to post-mortem), engagement close-out (from final delivery to archive), renewal (from early signal to signed contract).

Why services firms underinvest in both

Runbooks and playbooks take time to write and deteriorate if not maintained. The return is clearest at scale: a firm that can staff an engagement with any qualified practitioner, not only the one who has done it before, has a structural delivery advantage. Tribal knowledge is a single point of failure; runbooks and playbooks are the primary tool for converting it into shared, durable process.

Maintenance cadence

Review runbooks when the process they describe changes. Review playbooks after every major engagement where they were used. The lessons learned process should feed directly into playbook updates. Ownership of the playbook library typically sits with the practice lead or delivery operations function.