How these pages work
Each page begins by measuring the symptom rather than describing it. "Our naming is a mess" becomes a count of how many variants exist for each campaign; "reporting takes forever" becomes a timed list of the steps in the last report, from first export to sending. That measurement usually shows that one or two causes carry most of the cost, which keeps the fix small.
A diagnosis table then sets out, for each cause, what you can see, the check that confirms or rules it out, the cause and the fix. Each cause has a short section with the fix, a way to verify it worked and the habit that stops it returning, and each page ends with a routine that catches the whole family of causes on a schedule. The pages route to the guides rather than repeating them: the shared taxonomy and naming enforcement live in data operations and taxonomies, the tagging convention in the UTM and naming conventions guide, and the production steps of the monthly pack in the monthly reporting pack SOP.
Which page to start from
Pick the row that matches what you can see. The problem pages beneath this introduction are listed automatically as they are published.
| What you are seeing | Start with | Background |
|---|---|---|
| Campaigns miss their launch dates again and again, and nobody can say where the days went | Campaigns keep launching late | Campaign workflow from intake to launch |
| Reports cannot group or compare campaigns because names and tags differ between teams and platforms | Campaign names and UTMs inconsistent | Data operations and taxonomies |
| The monthly marketing report takes days to assemble and is still argued over | Monthly marketing report takes days | Marketing reporting cadence |
| An error the team already fixed, such as an expired code or a wrong price, reaches customers again | Same marketing mistakes keep happening | Reviewing a marketing error |
| Legal or compliance keeps sending finished work back for its claims, prices or endorsements | Legal keeps rejecting marketing work | Building a claims library |
| Two teams find they built the same asset, bought the same tool or ran the same study | Marketing teams duplicating work | Work management and marketing calendars |
| Something wrong on a live campaign was found days after it began, by a customer or a colleague | Live campaign problems found too late | Campaign workflow from intake to launch |
Process, data or tooling: which layer is failing
Operations problems sit in one of three layers, and the cure differs for each. A process fault is a missing step, gate or owner: work enters without a brief, links are built without a check, a report has no fixed sequence. The process hub covers workflow and procedures. A data fault is inconsistency in what the systems hold: campaign values spelled several ways, metrics defined differently in each report, contact data duplicated between tools and a customer data platform (CDPUnified first-party customer profiles.). The systems hub covers work management and data operations. A tooling fault is a missing or broken connection: exports done by hand because no connector exists, or a builder that allows free text where it should offer a list.
The order of diagnosis matters. Buying a tool for what is really a process or data fault reproduces the fault in the new tool. Campaign tagging is a good example: Google's documentation on campaign URL builders describes the parameters a tagged link carries, but no builder enforces a vocabulary that nobody has agreed, which is why the UTMURL tags identifying traffic source. problem is usually solved by an owner and a list before it is solved by software. Reporting follows the same pattern: Kaushik's measurement model asks for objectives, goals and each KPIA metric tied directly to an objective. to be agreed before any report is built, and no automation shortens a report whose definitions are argued afresh every month.
When to run an operations review instead
A troubleshooting page answers one question about one symptom. When several operations symptoms appear together, such as late launches, inconsistent names and slow reporting, a broader review finds the shared cause faster; the first operations review in the marketing operations pillar takes an afternoon and produces a short, ordered list of fixes. Questions of who owns standards across teams belong to the governance hub. Problems caused by how marketing is organised and briefed, such as agency relationships or a plan that keeps changing, sit in the marketing management troubleshooting section, and analytics configuration faults in the analytics troubleshooting section.
