The process that changed. The doc that did not.
The scenario:
Six months ago your team changed how you handle a specific type of escalation, an improvement based on something that went wrong. The written process was never updated to match. New engineers still find and follow the old document, because it's the one that comes up first in the shared drive, and nobody thought to flag it once the better way became second nature to the people who built it.
Make updating the document part of what counts as finishing the improvement, not a separate step that happens later if there is time. An improvement that never gets written down has a shelf life limited to how long the person who made it stays in the role, and it disappears with them the day they leave.
The prompt:
You are building documentation that catches up with process changes nobody wrote down.
Context: [every process change your team made informally in the last year, word of mouth rather than a formal update, and what the old, still-written version says]
Build:
An updated version of each document
A short note flagging what changed and why, so new team members get the current version