What these playbooks are for
Most marketing work is not new. The same account gets checked every morning, the same reporting pack goes out every month, and the same planning conversation happens every quarter. Teams that do these things well rarely have better ideas than teams that do them badly; they have a rhythm, clear owners and a record of what was decided. A playbook writes that rhythm down so it survives holidays, hand-overs and new hires.
It helps to separate four kinds of operating document, because people often use the words loosely. A playbook covers a whole motion over time, with several roles and several cadences: it answers "how do we run this, week after week?". A standard operating procedure covers one task that happens on a trigger and must be done the same way each time, such as publishing a page or approving a creative: it answers "what are the exact steps?". An audit is a periodic assessment against criteria: it answers "how healthy is this right now, and what should we fix first?". A checklist is the shortest form of all, a list of things that most often go wrong, read at the moment they can still be fixed. A playbook usually calls on the other three: it schedules the audit, invokes the procedure and asks for the checklist at the right gate.
Every playbook here follows the same skeleton. It says what the motion covers and when to run it, who holds which responsibility, the cadence with its inputs and outputs, the phases of the work, one section that is specific to that motion (a decision log, a refresh queue, a set of readiness gates), how to measure whether the playbook itself is working, and the mistakes teams most often make with it.
How to adapt a playbook to your team
Read the roles first, and map them to people rather than job titles. In a small team one person may hold three roles; that is fine as long as the responsibilities are still visible, because the moment work gets busy the unowned responsibility is the one that slips. In a large team a single role may be split across an agency and an in-house owner; in that case the hand-over between them deserves its own line in the cadence table.
Then adjust the cadence to the volume and risk of the work, not to the calendar you wish you had. A small account may not need a daily check of every campaign, but it still needs someone to notice when tracking breaks. A large programme may need the weekly review split into two meetings with different audiences. The phases rarely change much; the frequency with which each one repeats is what varies.
Finally, decide where the outputs live. A playbook that produces decisions nobody can find later has not done its job. Pick one place for the decision log, one for the backlog and one for the reports, and link them from the playbook so a new team member can follow the trail. The marketing operations guides cover how to set up that shared tooling and governance, and the planning guides cover the briefs and plans that feed most playbooks.
A five-person team adopting two playbooks
A five-person marketing team at a regional software reseller runs paid search, email and a monthly report, mostly from memory. After a quarter in which two campaigns overspent and the board report arrived late twice, the head of marketing adopts the paid search and reporting cadence playbooks. She maps the playbook roles onto four people, cuts the daily paid search check down to a fifteen-minute routine for the twelve live campaigns, and moves the monthly pack deadline to the fourth working day. After three months the team has a decision log with forty entries and no overspend, and the pack has gone out on time three times running.
Which playbook when
Start from the motion that is causing the most friction, not the one that sounds most strategic. A team whose numbers nobody trusts should fix reporting before it builds an experimentation programme, because every test read-out will be argued over otherwise. The table routes common situations to the playbook to adopt first and the one that usually follows.
| Situation | Adopt first | Then |
|---|---|---|
| A search account is spending but nobody owns the weekly work | Paid search account management | Reporting cadence to give the results an audience |
| Social ads keep fatiguing and new creative arrives late | Paid social account management | Creative production to fix the supply of assets |
| Content gets published but traffic does not grow | SEO content operations | Reporting cadence for the organic numbers |
| Emails are sent campaign by campaign with no journeys | Lifecycle email programme | Experimentation programme once the journeys are live |
| A new product or major feature ships next quarter | Product launch | Quarterly planning to fold the launch into the plan |
| Every quarter starts with a scramble for budget and priorities | Quarterly marketing planning | Reporting cadence for the in-quarter checks |
| Sales complain about lead quality and slow follow-up | Inbound lead handling | Reporting cadence for closed-loop pipeline reports |
| Briefs, approvals and versions are chaotic across channels | Creative production | Paid social account management for the testing loop |
| Numbers are argued about in every meeting | Marketing reporting cadence | Quarterly planning so targets come from agreed metrics |
| Tests run ad hoc and nobody remembers what was learned | Experimentation programme | Lifecycle email programme or paid playbooks as test sources |
| Tools are bought on a card and renewals arrive unannounced | Marketing stack management | Quarterly planning so stack work competes for time and budget |
| Numbers nobody trusts after a release | Measurement governance | Reporting cadence to run the reports built on that layer |
| A release broke indexing and nobody owns the site's technical health | Technical SEO maintenance | SEO content operations for publishing and refreshing the pages on it |
| Programmatic spend nobody checks between reports | Programmatic campaign management | Reporting cadence to carry results to the business |
| Product ads run from a messy feed with no owner | Shopping and Performance Max | Peak season trading when a sales period is coming |
| The last sale overran stock or customer service | Peak season trading | Shopping and Performance Max so feed fixes are in place before the window |
| Marketing is about to enter its first new country | International market entry | Quarterly planning so the market competes for budget and time with everything else, then Multi-market marketing operations once the market passes its continue gate |
| Press coverage comes and goes with no routine behind it | PR programme | Reporting cadence so PR figures sit in the team's normal reports |
| An app is marketed release by release with no weekly routine | App marketing operations | Experimentation programme for listing, permission and message tests |
| Customer research stops after one study | Customer research programme | Quarterly planning so evidence reaches the plan when choices are made |
| Customers cannot complete a form and nobody owns accessibility across channels | Marketing accessibility programme | Creative production, where the checks join the route from brief to release |
| Consent withdrawals never reach the ad platforms | Privacy and consent operations | Lifecycle email programme, which depends on its suppression records |
| The same kind of error keeps reaching customers and each one is handled by whoever noticed | Marketing incident management | Measurement governance for tracking outages, or Peak season trading so a change freeze covers the next sale |
| AI features and tools are in use but nobody can say which, who owns them or who reviews their output | AI governance operations | Privacy and consent operations for personal data in prompts, or Marketing stack management so AI tools share the request route |
| Several markets are live but each runs its own calendar, edition and report | Multi-market marketing operations | Quarterly planning so each market is weighed against every other call on budget |
The playbooks themselves are listed automatically beneath this introduction, so a new one appears as soon as it is published.
Playbooks and the guides behind them
A playbook is deliberately thin on method. The paid search playbook tells you to review search terms every week and record what you excluded; it does not explain how negative keywords work, because the Google Ads guides already do. The reporting playbook tells you which audience sees which numbers and when; the analytics guides explain how to build a KPIA metric tied directly to an objective. tree or govern a dashboard. The governance playbooks work the same way. The measurement governance playbook runs tracking changes, release checks and the data quality check on a rhythm, while the analytics and tag management guides explain how each is done. The marketing stack management, technical SEO maintenance and privacy and consent operations playbooks do the same for tools, the site and personal data. Beside them, the marketing incident management playbook names an incident lead for every report, keeps the contact sheet current and reads the error log each month, while the procedures and tutorials it hands off to explain how each kind of error is contained and fixed. Keeping the method in one place and the rhythm in another means each can change without the other going stale.
The same division applies to measurement. Where a playbook asks you to judge a channel by ROASRevenue generated per unit of ad spend. or to read an A/B TestControlled comparison of two variants., it links the guide that defines the metric or the method rather than restating it. When a phase calls for a precise sequence of steps, such as launching a campaign or producing a reporting pack, the playbook hands off to the matching standard operating procedure; when it calls for a health check, it schedules the matching audit. Read the playbook to know what happens when and who owns it, and follow its links to learn how each piece is done.
