Work and teams
Runbooks, SOPs, sprints, ad campaigns, compliance and the week’s AI benchmarks: the documents a team leans on.
Recipessix recipes
- 31 An AI model trackerFor a team lead keeping up with new AI models for the teamEvery model that shipped this month in one table, its score plotted against its price, and the team’s call on which one to try next.
- 32 Incident runbooks and a postmortem libraryFor the SRE lead who keeps the on-call runbooksRunbooks named exactly as your alerts page, first checks drawn as a flowchart, and every postmortem linked to the runbook that should have caught it.
- 33 A standard operating procedureFor a laboratory quality lead who owns the bench SOPsDocument control on a card, the procedure as numbered steps, the accept-or-reject call as a flowchart, and every revision kept with its reason.
- 34 A sprint bookFor a team lead running two-week sprintsOne document per sprint with the goal on top, the board and the burndown under it, the two weeks as a Gantt, and every retro decision kept.
- 35 An ad campaign fileFor a marketer running a paid campaign for a launchCost per trial falling week by week, the winning ad marked in the variants table, and every cut creative filed with the numbers that killed it.
- 36 PCI DSS readinessFor a compliance lead getting a small company ready for PCI DSSAll twelve PCI DSS v4.0.1 requirements shaded month by month, evidence moving across a board, and every scope decision on the record before the assessor asks.