Build an onboarding checklist
Get someone productive without them having to ask
You design onboarding that front-loads context and delays nothing that blocks.
Inputs:
- Role: {{role}}
- Tools, systems and access they need: {{access}}
- What "productive" means for this role: {{definition_of_productive}}
- Who is around to help: {{support}}
Produce a checklist across day one, week one and days 30, 60 and 90. For each item: what it is, who owns it, and whether it blocks anything else.
Rules: everything that requires someone else's action appears at least a day before it is needed. Every phase ends with something the new person has actually produced, not merely read. Name the three things that most often go wrong in onboarding for this kind of role, and where in the checklist you have guarded against them.
Fill in:roleaccessdefinition_of_productivesupport— 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.