Build from scratch
Starting with nothing but a description of the work: the five questions YAMO asks, what each answer writes down, and what you have when they end.
On this page
If no template fits, you start from a description of the work. YAMO asks five questions, and writes your answers into a Playbook document as you go.
The five questions
They arrive one at a time, and each one shows you what it wrote before asking the next.
- What service do you already deliver? The starting description. It names the Draft Service and seeds its goal, so it opens with a real title rather than as an untitled draft.
- Who needs this Service most? The audience.
- Does this feel like the result you promise? The finished outcome, stated as a result rather than an activity.
- What do you need from someone before this Service can start? What the work needs supplied to it.
- Does this feel like the right way to deliver the Outcome? How the outcome reaches the person who wanted it.
None of this calls a model to invent your method for you. The questions are fixed, and what is written down is what you said.
What you have at the end
A Draft Service with a document: its goal, its audience, the outcome it promises, what it needs and how it delivers. That document is the Playbook, and it is readable top to bottom.
What you do not yet have is steps. The five answers describe the work; they do not write the ordered Plays that carry it out. That is the next thing to do, and until at least one step exists the Playbook cannot be deployed, which the setup checklist will tell you.
Working on the draft
The draft opens in the builder. On the left is the Playbook as it currently reads. In the middle is YAMO, which you can ask to shape a step, change a rule or set a value. On the right is what a subscriber would see.
The document is always the interface. Whether you edit a section directly or ask YAMO to, the change lands in the same file, and what you can read is what will run.
More in Build
Related
Build from a template
Copying a working Playbook into your account: what you get, what stays yours, and what the copy asks you to replace before it is really about you.Writing the steps
The ordered steps that do the work: what each one declares, how they hand work along the chain, and how instructions are written and changed.The Skill library
Reusable steps kept in your account: what a Skill is, how one is imported into a Playbook as a step, and what a Skill file has to say for itself.Deploy: making it runnable
The setup checklist and what it checks, what Deploy actually does to a Draft Service, and why nobody at all can run a Playbook before that point.Pricing
How YAMO charges: you pay for the runs you make, and nothing for the ones you do not. What a run is, what it includes, and what publishing costs.Who it's for
The six kinds of expert YAMO is built for, and what changes when the method you already follow becomes a Service that somebody else can run.
Open a Playbook that does this
Every template in the library publishes its contract and a real example output.