Series ID: EDKS-BASIC-ZH-0109 · Lesson No.109 · Expert Maintenance: Operational Writing
Writing Playbooks, SOPs and Decision Guides | 编写操作手册、SOP 与决策指南
Operational writing is successful when another person can act correctly without needing the writer beside them.
Playbooks, standard operating procedures, checklists and decision guides convert knowledge into repeatable action. The language must make triggers, prerequisites, steps, ownership, exceptions, escalation and completion conditions visible.
操作型英语不是“写得正式”。真正的标准是：另一个人拿到文件以后，能不能在正确时间做正确动作，并知道什么时候不能照着普通流程继续。
Chinese Edition Hub · 中文版入口 · ← Lesson No.108 · Annual Language Audit and Personal Expert Portfolio
The operational-writing map | 操作写作地图
- document type
- trigger
- scope
- prerequisites
- steps
- decision points
- exceptions
- escalation
- verification
- version control
1. Choose the right document | 先选正确文档类型
Different documents do different jobs.
2. Policy | 政策
States rules, principles, scope and authority.
3. SOP | 标准操作程序
Describes a repeatable sequence for a defined process.
4. Work instruction | 工作指令
Gives detailed instructions for one task.
5. Checklist | 检查表
Supports reliable completion of known critical items.
6. Playbook | 操作手册
Combines options, scenarios, judgement, examples and escalation paths for variable situations.
7. Decision guide | 决策指南
Helps a user choose among actions using criteria and thresholds.
8. Do not force one document to do every job | 不要一个文档包办所有任务
A policy should not become a 40-step work instruction.
9. Start with the reader job | 先看使用者要完成什么
Ask:
- Who uses this?
- When?
- Under what pressure?
- What mistake matters most?
10. Scope | 适用范围
State where the procedure applies and where it does not.
11. Trigger | 启动条件
Use this procedure when the customer cannot complete payment after two retry attempts.
12. Exit condition | 退出条件
State when the procedure is complete or should stop.
13. Prerequisites | 前置条件
- permissions
- tools
- information
- training
- safety conditions
14. Step language | 步骤语言
Use direct verbs:
- Open
- Check
- Record
- Confirm
- Escalate
15. One step, one primary action | 一个步骤一个主动作
Long multi-action sentences make errors harder to detect.
16. Observable completion | 可观察完成标准
Weak:
Make sure everything is okay.
Better:
Confirm that the status field reads “Active” and record the timestamp.
17. Decision point | 决策点
If X, do A. If not, do B.
18. Decision criteria | 决策判据
Do not write “if serious” unless “serious” is defined.
19. Threshold | 阈值
If error rate exceeds 3%, pause the rollout and escalate.
20. Decision tree | 决策树
Useful when the process branches repeatedly.
21. Keep branches mutually clear | 分支要清楚
A user should not reasonably satisfy two contradictory branches at once unless the guide explains priority.
22. Default path | 默认路径
Show the normal route first.
23. Exception path | 例外路径
Exceptions need explicit conditions.
24. Escalation | 升级
State:
- trigger
- recipient
- information required
- deadline
25. Stop condition | 停止条件
Some procedures should stop rather than improvise.
26. Safety-critical wording | 安全关键措辞
Use clear mandatory language where authority and procedure require it.
27. Do not soften mandatory action | 不要把必须写成建议
Do not proceed is different from You may want to wait.
28. Owner | 责任人
Each handoff or action should have a clear owner.
29. Role not person where appropriate | 适合时写角色而不是姓名
Duty manager remains valid when staff rotate.
30. Inputs | 输入
Specify required data before the step begins.
31. Outputs | 输出
Specify what the process should produce.
32. Evidence of completion | 完成证据
- record
- status
- signature
- test result
- confirmation
33. Verification step | 验证步骤
Critical processes need a way to confirm the action worked.
34. Checklists | 检查表
Use checklists for important known items, not for every trivial action.
35. Checklist item style | 检查项风格
Make each item concrete and scannable.
36. Playbook scenarios | Playbook 情景
Organise by recurring situations:
- normal
- degraded
- urgent
- unknown
37. Scenario entry | 情景入口
State how the user recognises the scenario.
38. Decision guide language | 决策指南语言
- Choose A when…
- Prefer B if…
- Do not use C unless…
39. Explain rationale selectively | 选择性解释理由
Users follow procedures better when critical rules have understandable rationale, but excessive explanation can bury the action.
40. Layer detail | 分层细节
Use:
- quick path
- detailed explanation
- reference material
41. Examples | 示例
Examples reduce interpretation ambiguity.
42. Non-example | 反例
Sometimes showing what does not qualify is equally valuable.
43. Terminology | 术语
Define terms that users may interpret differently.
44. Acronyms | 缩写
Spell out the first occurrence unless the audience universally knows it.
45. Version control | 版本控制
Record:
- version
- owner
- approved date
- next review
46. Change log | 变更记录
Users need to know what changed when the change affects behaviour.
47. Review cycle | 复审周期
Operational documents decay when tools, roles or rules change.
48. Test the document | 测试文档
Give it to someone who did not write it.
49. Usability test | 可用性测试
Observe:
- where they hesitate
- where they choose wrong branch
- what they ask
50. Procedure failure may be writing failure | 流程失败可能是文档失败
Do not assume the user is careless when instructions are ambiguous.
51. Measure procedure quality | 测量流程质量
Possible signals:
- error rate
- time to complete
- escalation frequency
- clarification requests
52. Mandarin transfer: “流程”可对应 process/procedure/workflow | 功能不同
Choose based on whether you mean the system, the documented procedure or the movement of work.
53. Mandarin transfer: “操作手册”可能是 manual/playbook | 看复杂度和用途
A playbook usually contains more judgement/scenarios than a strict manual.
54. Practice A | 练习 A
Turn a paragraph of instructions into numbered steps.
55. Practice B | 练习 B
Add one decision point, one exception and one escalation trigger.
56. Practice C | 练习 C
Write a checklist with observable completion criteria.
57. Error clinic | 常见问题
| Problem | Repair |
|---|---|
| Procedure begins without trigger. | State entry condition. |
| Steps contain vague verbs. | Use observable actions. |
| Exceptions improvised. | Document branches. |
| No escalation route. | Add trigger/owner. |
| Document never reviewed. | Add version cycle. |
58. First weak link diagnosis | 第一个卡点诊断
- user starts wrong procedure → trigger/scope.
- user stalls → step clarity.
- branch wrong → criteria.
- unexpected case mishandled → exception/escalation.
- old instructions persist → version control.
59. Seven-day training cycle | 七天训练
| Day 1 | document types | 文档类型 |
| Day 2 | scope/triggers | 范围触发 |
| Day 3 | steps | 步骤 |
| Day 4 | decisions/exceptions | 决策例外 |
| Day 5 | verification | 验证 |
| Day 6 | usability test | 可用测试 |
| Day 7 | full SOP/playbook | 综合 |
60. Self-test | 自测
Write an operational document with scope, trigger, prerequisites, clear steps, decision points, exceptions, escalation, verification and version control.
61. For parents and teachers | 给家长和老师
Students can practise with revision routines, laboratory preparation, event planning or group-project procedures.
Ask another person to follow the guide without oral explanation.
62. Final real-world challenge | 最终真实任务
- Choose one repeatable process.
- Select document type.
- Define scope/trigger.
- List prerequisites.
- Write steps.
- Add two decision points.
- Add one exception.
- Add escalation.
- Add verification.
- Run a user test and revise.
Next: Lesson No.110 | 下一课
The next lesson develops data communication: explaining metrics, dashboards and trends without confusing movement with meaning or a colourful chart with a decision.
Lesson No.110 · Communicating Metrics, Dashboards and Trends · 解释指标、仪表板与趋势
Reference floor: expert-maintenance operational writing. A procedure succeeds when another user can act correctly without hidden oral instructions.
