Directing @yagni · Lesson 2 of 4
How does a Team's Playbook learn your rules?
Published June 9, 2026
The Playbook is the editable, shared set of rules a Team has learned for how its work gets done. Rules are captured as a byproduct of the team working items, your edits, approvals, and declines, not configured up front. Responsibilities are what a Team is on the hook for; the Playbook is how it delivers them.
What is a Playbook rule?
A plain sentence about how the work gets done. “Renewal quotes copy finance.” “Bug reports from enterprise accounts get a same-day acknowledgment.” “Drafts to press contacts wait for a person, always.” Each rule is readable, dated, and traceable to where it came from.
Together with Responsibilities, the pair defines a Team: Responsibilities are the mandate, what the Team is on the hook for. The Playbook is the method, how it has learned to deliver. You write the first; the second accumulates.
How does a rule get learned?
By watching what the team actually does, not by being configured. The raw material is the calls you make in the Feed:
| You do this | The Team learns this |
|---|---|
| Edit the same clause in two drafts | The clause arrives right the third time |
| Approve a pattern repeatedly | The pattern is safe to handle routinely |
| Decline a proposal | The boundary it just found |
| Pull a filed item back | What should not be filed |
A captured rule renders as the Team’s: “the Sales Team learned to copy finance on renewal quotes.” It is never framed as one person’s edits, because it is not one person’s possession. The method belongs to the Team, and everyone works from it.
Who owns the rules?
The Team, workspace-wide. This matters more than it first sounds. When a rule lives in one person’s settings, the team’s quality depends on who is on duty. When the Team owns the rule, your best judgment becomes the floor for everyone, including the agent. New teammate, same Team, same method. The moat is not that the agent works; it is that your team’s judgment compounds in a place you can read.
How does autonomy grow out of the Playbook?
Gradually, visibly, and with your consent. Every Team starts draft-only: everything it wants to do lands as a proposal. As its drafts keep shipping unedited and its calls keep getting confirmed, it earns the next step, the routine and reversible work running on its own, logged with honest receipts.
Two things never change. Autonomy is earned per Team, so your Sales Team can run further ahead than your brand-new Support Team. And the floor is permanent: irreversible and high-blast actions wait for a person at every level, on every plan, with the audit trail to prove it (see security).
What should you actually do in week one?
Make calls, honestly. Edit drafts the way you actually want them. Decline what is wrong. Do not be polite to the agent; be accurate. Every call is signal, and a week of honest editing produces a Playbook you would have needed a quarter to write down. Then read it: the Playbook page is the clearest mirror of how your business actually runs that you are likely to own. When you want help interrogating it, ask @yagni.
Common questions
Do I have to write the Playbook myself?
No. Rules are learned as a byproduct of the team working items: edit a draft, approve a proposal, decline one, and the Team captures the pattern. You can edit any rule it learned, but the writing is not your job.
Who owns a Playbook rule?
The Team, on behalf of the whole workspace. A rule reads as the Sales Team learned to copy finance on renewal quotes, never as one person's setting. Everyone who reads the Team shares the same method.
Can I see and change what a Team has learned?
Yes. The Playbook is plain, readable, and editable. Every rule shows when it was learned and from what. Edit it, and the Team works the new way from then on.
How does a Team earn more autonomy?
One step at a time, with your explicit consent. Every Team starts draft-only. As you confirm its work, it graduates: first drafting, then handling the routine on its own. Irreversible and high-blast actions stay approval-gated at every level, permanently.