28 lines
1.5 KiB
Markdown
28 lines
1.5 KiB
Markdown
---
|
|
name: operating-guide
|
|
description: >-
|
|
The template of the operating model guide and who writes each part of it: the
|
|
packager writes the summary, and code writes every table and figure from the
|
|
data. Use when packaging a target operating model into its guide.
|
|
---
|
|
|
|
# The operating model guide
|
|
|
|
`assets/guide-template.md` is the guide's template. It has nine sections, in a fixed order.
|
|
|
|
## What you write
|
|
|
|
Only the **Summary**: one or two short paragraphs for the person who will run the solution. Say what is operated, who operates it and how the work is divided between the Parties, during which hours, and what they should look at first: a finding, a Check that waits on one, a scenario that fails, a cost over its budget.
|
|
|
|
State no number of people, no cost and no count. The key figures are set under your paragraph from the data, and a figure you wrote could differ from them.
|
|
|
|
## What is written for you
|
|
|
|
Every other section. Submit each of the template's headings with nothing under it, or a line saying it is written from the data: whatever you put there is replaced when you submit. The tables, the figures, the verdicts and the citations all come from the data files of the other Deliverables, so they cannot disagree with them.
|
|
|
|
## What you never do
|
|
|
|
- Never add a decision, a recommendation or a caveat of your own. The guide assembles what was decided.
|
|
- Never restate a figure, even in the summary.
|
|
- Never say the operating model complies with, or is certified against, a framework.
|