A repeatable way of working.
The trigger, the source of record, the steps, the file name, the delivery rule, the fallbacks and the limits for a job she will be asked to run again. Change the method here and every future run changes with it.
Teammate substrate / Playbooks
A playbook is an internal SOP for a job that comes back: where the work starts, the steps in order, what the file is called, where it gets filed, how it is returned, and where the teammate has to stop. Roan wrote the two below himself, after a user asked him for flood maps often enough that doing it from scratch each time stopped making sense. The tenth request now comes back the same as the first.
Playbooks and memory
The trigger, the source of record, the steps, the file name, the delivery rule, the fallbacks and the limits for a job she will be asked to run again. Change the method here and every future run changes with it.
The atomic things she has learned: which folder this client wants documents in, who signs off on what, what the last decision was and why. Facts about your company, held separately from any one procedure.
Playbooks come with the teammate. They are part of how she learns a role and repeats it, so there is nothing extra for your team to buy, run or maintain.
On demand
A short list of what she knows how to do stays in front of her at all times. When a request matches one of those triggers, the full procedure loads for that job — so a teammate can hold a hundred playbooks without carrying a hundred playbooks into every conversation.
Anatomy of a playbook
Steps alone leave the expensive parts open. A playbook that works also fixes where the work starts, what the finished file is called, where it lands, who gets it back and on which channel, and the point where the teammate has to hand the question to a person.
The request or condition that should pull these instructions in. Get it right and she reaches for the playbook without being told to.
Where the work has to begin, and which sources are authoritative enough to put your name on the result.
The actions in order, the fallback when a source is down, and the point where she stops and hands it to a person.
One stable file name, so anyone can tell what a document is from the folder listing without opening it.
Where the finished file gets filed, and every channel the person who asked expects to see it come back on.
What this work cannot settle, which record actually controls, and when a specialist has to take it from here.
In practice / Roan
Roan works construction for a real-estate developer. Site diligence kept asking for the same two documents, so he wrote the procedure for both, including the part everyone forgets: produce the artifact, file it in the project folder, and return it on every channel it was asked for.
FEMA FIRMette - [Street Address, City ST].pdfZoning Map - [Street Address, City ST].pdfThe compounding effect
When the source moves, the ordinance changes or you want the file somewhere else, she edits the playbook and the next run picks it up. The work you spent teaching her stays taught, and nobody has to remember to re-teach it.