ANY answer containing a business number — load this first.
7 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–7 OF 7
Use it when you are about to guess at something only a human can decide.
7 rolesRead moreUse it when a source is not connected, or cannot answer this question.
7 rolesRead moreUse it when asked for a report, a readout, or "how are we doing".
3 rolesRead moreUse it when before trusting a source you have not checked.
1 roleRead moreUse it when two sources or two people disagree on a number.
1 roleRead moreUse it when a number moved sharply and someone wants an answer.
1 roleRead moreNever state a number without its source7 roles
×A plausible figure invented because the shape of the answer wanted one. A wrong number said confidently costs more trust than fifty "I don't have that"s.
Stop and ask instead of guessing7 roles
×Guessing to keep momentum. It is the single most trust-destroying agent behaviour and it is invisible in the output — a guess and a fact are written in the same voice.
What to do when a connector cannot answer7 roles
×Reporting 0 when the honest answer is "not connected" — two different facts that must never be reported the same way.
Produce a metrics readout3 roles
×A readout that smooths over a missing source so the report looks complete. A gap the reader does not know about is a gap they assume you covered.
Check whether the data can answer the question1 role
×Answering a question from a dataset without checking whether it is complete for the window asked about. A partially loaded table returns a number rather than an error, and the number is confidently wrong in the direction that looks like a decline.
Pin down what a metric actually means1 role
×Picking the more plausible of two conflicting numbers and reporting it. Two systems disagreeing almost never means one is broken — it means they are answering slightly different questions, and choosing between them discards the actual finding.
Work out whether a spike is real before reacting1 role
×Explaining a sudden move by finding a business reason for it. Most sharp moves are instrumentation, definition changes or partial data, and a plausible business story attached to a tracking bug survives long after the bug is fixed.
Stop launching into silence.
Start free with your website, or tell us about your product and we’ll set the team up with you.