Use it when something is stuck and you must find who unblocks it.
6 rolesRead more
Skills · 124 playbooks in 12 groups
The team already knows how the job is done.
124 playbooks, among them how to ship a launch nobody has to rescue, shape a post for where it will be read, run experiments instead of opinions and read an ad account without double-counting. Each one is written around how the work usually goes wrong, and the team picks the right one for the task.
Written by people who do the job.
Each playbook captures the steps and the traps, not just the task name.
Picked for the task.
Ask Iris why signups dropped and Iris uses the analytics playbooks. You don't have to choose.
Every one is listed below.
Browse all 124, grouped by the kind of work.
All skills124Marketing22Revenue19Product & delivery15Connector literacy11Strategy10Finance9People9Execution8Grounding7Build5Legal5CEO office4
SHOWING 1–8 OF 8
Use it when deciding whether something is genuinely slipping or noise.
6 rolesRead moreUse it when tracking what somebody promised, to whom, by when.
6 rolesRead moreUse it when deciding whether to escalate, and what to put in it.
6 rolesRead moreUse it when a meeting is long, crowded or achieving nothing.
2 rolesRead moreUse it when the recurring review of what moved, stalled and needs a call.
2 rolesRead moreUse it when support volume, ticket themes, or an angry customer.
2 rolesRead moreUse it when a repeated task must survive the person who does it.
2 rolesRead moreName who unblocks it6 roles
×Reporting "blocked on legal" — a situation, not a person, so nobody is asked anything and it stays blocked for another week.
Tell slipping from noisy6 roles
×Flagging everything that moved, which trains everybody to ignore the flags. Our tracker rows and the chat about them disagree by design, so "changed" is not "slipping".
Track what was promised, by whom, by when6 roles
×Recording "we will look into the export bug" as a commitment. No owner, no date, no way to ever be late — so it is never chased and never done.
When to escalate, and what to put in it6 roles
×Escalating a status update. An escalation with no decision in it trains the recipient to stop reading escalations, which is the failure this exists to prevent.
Make a recurring meeting earn its place2 roles
×Improving a meeting by tightening its agenda. Most bad recurring meetings have no decision to make, and a better-run status meeting is a more efficient way to do something that should not be happening at all.
Run the operating review2 roles
×A recurring review that reports activity instead of exceptions, and ends with no owner and no date on anything.
Turn support volume into a decision2 roles
×Reporting ticket counts as a workload number, so the recurring cause that generates them is never named and the queue is staffed instead of fixed.
Write a procedure somebody else can run2 roles
×Writing a procedure from memory rather than from an observed run. Memory reliably omits the steps that have become automatic — the login, the filter, the one field that must be set first — and those omissions are exactly what stops the next person.
Stop launching into silence.
Start free with your website, or tell us about your product and we’ll set the team up with you.