Preserving and sharing engineering knowledge requires dedicated vocabulary. These exercises focus on the collocations SREs, tech leads, and engineering managers use when creating runbooks, postmortems, and documentation.
0 / 5 completed
1 / 5
The team uses Architecture Decision Records to ___ in a searchable format.
Document decisions is the standard knowledge management collocation. 'Document' implies creating a structured, retrievable artifact. 'Record' is close but more neutral; 'write' and 'save' are too generic and do not convey the formalised nature of ADRs.
2 / 5
Every on-call engineer is expected to ___ covering all operational procedures before their rotation.
Maintain a runbook is the operational collocation that emphasises keeping the runbook current and accurate. 'Maintain' implies ongoing ownership. 'Write' and 'create' describe initial authorship; 'build' is informal for documentation contexts.
3 / 5
Following last week's outage, the team was asked to ___ and share it with the engineering organisation.
Create a postmortem is the standard SRE collocation for producing a blameless incident review document. 'Write' is also common and emphasises the writing process; 'do' and 'make' are too informal for this critical engineering practice.
4 / 5
The tech talk series was set up to ___ from recent incidents and new technology evaluations.
Share learnings is the professional collocation for distributing insights gained from experience. 'Share' implies a collaborative, open culture. 'Present learnings' is also used in formal settings; 'give' and 'communicate learnings' are less idiomatic in engineering retrospective contexts.
5 / 5
The engineering wiki was established to ___ so that new hires could get up to speed quickly.
Build institutional knowledge is the standard collocation for accumulating organisational understanding over time. 'Build' implies a deliberate, cumulative effort. 'Create' focuses on initial production; 'store' implies only preservation; 'grow' is informal in this context.