How these pages work
Every page follows the same order. It begins by testing the symptom itself, because programme-level complaints are often partly a counting problem: enquiries that arrive by phone and never reach the report, a sales figure read over weeks for work that pays back over months, or two teams using different definitions of a lead. A diagnosis table then sets out what you can see, the check that confirms or rules out each cause, the cause, and the fix. Each cause gets a short section with the fix, a way to verify that it worked and the habit that stops it returning, followed by a routine that catches the whole family of causes before the next planning cycle.
The pages do not re-teach strategy. How to choose an audience is in the segmentation guide, how to say why a buyer should choose you is in the positioning guide, how to give each channel one job is in choosing channels, and how to connect objectives to measures is in objectives and KPIs. A troubleshooting page points to the relevant section once a cause is confirmed.
Which page to start from
Pick the row that matches what you can see, not the cause you already suspect. The problem pages beneath this introduction are listed automatically, so a new diagnosis appears here as soon as it is published; the last column names the guides that own the causes.
Platform, measurement or strategy: decide which question you are asking
Most wasted effort in diagnosing a disappointing programme comes from answering the wrong one of three questions. A platform question asks why one account, campaign or channel behaves as it does; the answer lives in that platform's settings and its own troubleshooting hub, such as the Google Ads or Meta Ads sections. A measurement question asks whether the numbers describe what happened; tags, consent, attribution and reports that disagree belong to the analytics troubleshooting section. A strategy question asks whether the work is aimed at the right people, with the right promise, through channels given the right jobs, and judged over the right period. Only the third belongs here.
A useful test is breadth. A fault confined to one channel is almost always a platform or measurement question. A fault that appears everywhere at once, or that persists however each channel is tuned, points to something the channels share: the audience, the offer, the website, the definition of success, or the market itself. Kaushik's measurement model makes the same point from the other direction: if the business objective, the goals and the KPIs were never written down together, no amount of channel optimisation can show whether the programme works.
When to plan or audit instead
A troubleshooting page answers one question about one symptom. When several symptoms arrive together, when nobody can say what the programme is for, or when the plan has not been revisited in a year, rebuilding the plan is the better tool. The tutorial on writing a digital marketing plan walks through the whole sequence, the measurement plan guide fixes what will count as success before the work starts, and the strategy section places each decision in order. Someone who has just inherited a programme can start with the takeover inventory before changing anything, and a marketing risk register records the risks that derail plans, with their warning signs, owners and prepared responses. The digital marketing pillar shows how strategy, channels and measurement fit together.
