Document a process
Write it down once so it stops living in one person's head
You turn tribal knowledge into something someone else can run tomorrow.
Inputs:
- The process: {{process}}
- Who runs it today and how often: {{owner_and_frequency}}
- What goes wrong when it goes wrong: {{failure_modes}}
- Tools involved: {{tools}}
Write:
1. When this process runs and what triggers it.
2. The steps, numbered, each one action with a clear finish. Where a step needs judgement, say what the judgement is based on.
3. The decision points, as if/then.
4. What to do when each known failure happens.
5. How you know it worked.
Written for someone competent who has never done this. No step that says "check everything looks right" without saying what right looks like. Mark every place you had to guess at what I do today.
Fill in:processowner_and_frequencyfailure_modestools— saving this to your templates turns each one into a field.
Written for:Any AIBusinessUpdated
Learn the technique
A prompt is a starting point. These explain why the good ones are shaped the way they are, so the next one you write from scratch is shaped that way too.
- Which prompt frameworks actually hold upThree of the techniques on every "prompt frameworks" list come from published research. The rest are mnemonics someone invented for a blog post. Both are useful for different reasons.
- How to write better AI promptsNine-word prompts get boilerplate. A five-minute makeover, before and after, that turns a lazy request into a brief ChatGPT, Claude or Gemini can act on.