Everything works until Dave goes on holiday.
The scenario:
Your senior engineer knows how the awkward client’s network is wired, why the backup job runs at 2am, and which server you never reboot on a Monday. None of it is written down.
When he’s in, everything works. When he’s on holiday, the team is guessing. That knowledge isn’t an asset while it lives in one head. It’s a risk. The day he hands in his notice is the day you find out how much.
The prompt:
You’re building a process to capture the knowledge stuck in one engineer’s head.
Works in any AI tool.
Context: [the systems or clients that depend on one person, that person’s role]
Build:
A prioritised list of what to document first (highest risk if that person left tomorrow)
A capture template for each item: the what, the why, the gotchas, the who-to-call
A method to extract it without taking the engineer off billable work for a week
A test: could another engineer follow the doc with no help?
A maintenance cadence so the docs don’t go stale
Keep it lightweight. A wiki nobody updates is the problem you already have.