Use it when a number moved sharply and someone wants an answer.
1 roleRead moreThe 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.
SHOWING 121–124 OF 124
Use it when someone needs written feedback or a review cycle.
1 roleRead moreUse it when asked for a spec or PRD, or to scope a feature.
1 roleRead moreUse it when drafting an investor update or monthly summary.
1 roleRead moreExplaining 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.
Producing a review that grades a person rather than describing behaviour and its effect. A grade is arguable and forgettable; it also converts a performance conversation into a defence, which is the one thing that guarantees nothing changes.
Silence on the empty, error and permission-denied states, which the build then invents differently from what anybody wanted.
Changing which metrics get reported to fit the month. A metric that appears only in good months reads as a metric that is hiding.
Stop launching into silence.
Start free with your website, or tell us about your product and we’ll set the team up with you.