The reading version
Risk logs fall behind because of friction, not laziness. The format is rigid, the vocabulary is formal, and nobody wants to spend 40 minutes re-scoring yesterday's vendor delay when they could be fixing it.
The log isn't a document. It's a decision tool. The moment you treat it like paperwork, it rots. Running the update loop weekly — notes in, formatted risks out, you reviewing for sanity — keeps the decision tool alive with twenty minutes of your time, not ninety.
What AI handles, what you handle
The model can write a one-sentence risk, score it, and name an owner role. It can't tell you which risk actually keeps you up at night. That's the line you don't cross: the scoring is automated; the judgment on what to escalate is still yours.
- Shape raw updates into sections
- Group wins by theme
- Enforce word count
- Draft the headline
- Decide what the single headline is
- Rank the blockers
- Name the risk you're worried about
- Sign your name to it
