What the two prompts give you
- A routine map: the work your team repeats, how much time it costs, and what an assistant could take over.
- A line you can defend: what may happen on its own, and what always waits for a person.
- An incident playbook: for each incident, how you notice it, what the team reads first, and who does what in the first minutes.
Why a reminder is not enough
A reminder hands the work back to the person who already forgot it. The team gets more messages and the task is still open. The useful question is which repeating tasks can just be done, which can be prepared for a yes, and which should stay with a person. That is what the routine map answers.
Why the playbook comes before the incident
Nobody writes good instructions at two in the morning with a site down. Whoever gets the call needs to know what to check, what to say and who decides. You write that on a quiet day, or you make it up in the dark.
Who this guide is for
Small teams that live in a chat, and whoever gets the call when the site goes down. You need no technical background for the routine map. For the playbook, sit down with whoever knows your website.
Want it set up in your company?
This guide gives you the prompts, not the build. I set this assistant up inside companies as a partner, in your own Slack. Write to me, and in a 15 minute call I'll show you what it would take over first.
