what is your documentation habit how do you write procedures

Show a REAL, repeatable habit — this is a core GPS job skill. Your habit: 1) Write for the person who has LESS context — a procedure must work for someone who wasn't in the room. 2) Structure it clearly: the goal, the steps in order, expected result at each step, and the warning signs / what to check. 3) Record the WHY, not just the what — the mechanism, so someone can reason when it goes off-script. 4) Include what was tried and FAILED (saves dead ends). 5) Keep it current and versioned — docs that are wrong are worse than none. The one-line frame: 'I write procedures the way I'd want to read them at 3 AM in a field crisis — clear steps, the why behind them, and the gotchas.' You've done this (the reference-standard calibration). Prove it with an example where your documentation let someone else get the same result.