First, set where the team's time went beside the key results
Start with a record, not an impression. Two sources are enough. The first is the work board: list every item the team finished in a recent stretch and, beside each, the key result it was meant to move, or nothing if it named none. The second is a brief time log: over a short, typical stretch of work, each person notes roughly how many hours went to each kind of work, such as objective work, requests from other teams, recurring routines, rework, and waiting for an answer or a sign-off. The tutorial on reviewing recurring marketing work holds that a rough figure from the people doing the work will do, because the point is the relative size of each kind of work, not timing anyone.
Then put both beside the key results. For each key result, ask how much of the finished work and the logged time traces to it, and whether it moved. Three readings usually appear. Some key results had almost nothing worked against them, because the hours went to work that names no objective. Some key results moved, but they count the team's own output, such as campaigns launched or posts published. And some work traced to a key result but sat waiting, for a decision from the manager or for another team at a handover.
Two frameworks help read the gap. The north star metric and OKRs framework separates the outcome the business cares about from the activity meant to produce it, and expects key results to measure the first. Goodhart's law explains why a count of campaigns launched climbs while nothing else does: once a measure becomes a target, effort drifts to the cheapest way of moving it, and whatever is measured draws work away from whatever is not.
Check, too, that this is the right page. If the plan itself keeps being redrawn mid-quarter, the diagnosis for a marketing plan that keeps changing comes first; this page starts from a plan that holds. If the work is aimed at the objectives but arrives late, the diagnosis for campaigns that keep launching late traces where the days go. And if an agency's figures rise while sales do not, the diagnosis for agency reports that look good while sales are flat is the better start.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| Much of the finished work names no key result | Whether each accepted request stated the objective it serves | Requests accepted without being scored against the objectives | Every request names its objective or goes to the backlog; score as a team |
| Routine work takes a large share of the time log | Each routine's purpose, receivers and evidence of use | Recurring work taken off capacity and never questioned | Keep, shrink, change or stop each routine, trying stops as pauses |
| Key results show progress while the business outcome is flat | Whether each key result measures an outcome or counts the team's output | Key results written as activity | Rewrite key results as outcomes with a baseline, a target and an owner |
| People can say what they did, not which result they own | Whether individual objectives trace to a team key result each person can move | Team objectives never turned into each marketer's own | Outcome objectives per person, with shared results and named co-owners |
| Items queue for the manager's sign-off or return to the manager's desk | How long delegated items wait for an answer, and who decides | Decisions kept with the manager | Delegate outcomes with a stated level of authority and planned check-ins |
| Work stops where one channel or team hands to another | Who owns each handover, and what passes across it | Handovers between channels or with sales never defined | One accountable owner per interface, written into a responsibility matrix |
| The same blockers come up quarter after quarter | Whether the team holds a retrospective and checks its changes | No retrospective | A retrospective each cycle that picks one or two changes, each owned, tested and dated |
Fix, verify and prevent each cause
Requests accepted without being scored
The guide to prioritising work and capacity shows how capacity leaks away a little at a time: a sales director wants a brochure, an executive wants an event campaign; every request looks sensible, every one is accepted, and nobody asks what it pushes out. The guide cites writing in the Harvard Business Review for the theme that organisations come to grief less through poor choices than through never choosing at all.
Fix: route every request through one intakeThe single route through which every request reaches the marketing team, usually a short form, so work is triaged and checked before it starts., whoever it comes from, and require it to name the objective it serves; work that serves none is parked in the backlog with a reason. Score the rest together, with effort estimated by whoever will carry the work out, and show a requester what their request would displace.
Verify: over the next few weeks, every accepted item on the board names a key result, and the next time log shows less time on work that names none.
Prevent: triage on a fixed weekly rhythm, and when a senior requester chooses their request over planned work, record the trade-off so it is visible rather than silent.
Routine work nobody questions
Recurring work comes off capacity before anything new is planned, which is right for planning and means, as the recurring work tutorial explains, that no one checks whether each routine still earns its slice of the hours. A report outlives the director it was built for; a newsletter carries on after its product is retired.
Fix: list every routine with its owner and a rough time cost, note its purpose and who receives it, and look in the team's own records for signs that it is worth keeping. Put each into keep, shrink, change or stop, treat a stop as a pause where possible, and tell the people who receive the work before anything pauses. Then agree in the open what the freed hours are for; the tutorial warns that, left alone, they are soaked up by whatever requests come in next.
Verify: the paused routines are not missed by their receivers, and the released hours appear on the board as objective work.
Prevent: review routines at a fixed point in each planning cycle, before capacity is counted again.
Key results that count activity
The tutorial on running a quarterly planning session asks that key results track outcomes, not activity, and is blunt about the alternative: a tally of campaigns launched cannot show whether any outcome changed. A plan built on such counts reports steady progress while the outcome stands still, which is Goodhart's law at work.
Fix: rewrite each key result as an outcome with a baselineAn estimate of what a metric would have done without a given change, campaign or promotion, against which the effect is measured., a target and one named owner, and move the counts of output into the work plan where they belong. Where the outcome is slow to show, pair it with a leading indicatorA measure that moves before the business outcome it is expected to predict, paired with a lagging measure that confirms the outcome later. the team can move inside the quarter, and say which result it is expected to predict. The comparison of OKRs and KPIs separates the ongoing measures of a role from the changes a quarter commits to.
Verify: at the next monthly review, the discussion opens with outcome readings against their baselines, and a key result can no longer be met while the business outcome stays flat.
Prevent: at each planning session, test every draft key result by asking whether it could be hit without anything changing for customers or the business.
Objectives nobody owns personally
The tutorial on setting objectives for each marketer names three ways individual objectives go wrong: the person cannot influence them, they are activities, or they become a verdict. The quickest route, copying the plan's activities into each person's list, produces the second, and people end up measured on output while no one owns a result.
Fix: start from the team's key results, map which role's work moves each driver, and write each person's objective as an outcome they can influence, with a measure, the source of its figure and a baseline read on the day. Name co-owners for results nobody can move alone. The tutorial follows Google's re:Work guide to OKRs as the framework describes it: keep objectives few, and treat grades as learning, separate from appraisal.
Verify: each person can name the team key result their objective traces to and read its current figure against the baseline.
Prevent: review individual objectives openly during the quarter, and when the team plan changes, change the individual ones with it.
Decisions that stay with the manager
The guide to delegating marketing work lists the symptoms: decisions pile up with the manager, people hold changes they could have made alone, and the interesting work never leaves the manager. The team looks busy because much of its work is waiting.
Fix: delegate outcomes rather than tasks, each with a measure, a baseline and the parts that are fixed, and state the level of authority that comes with it, so the person knows whether to act or to ask. Routine, reversible decisions that stay inside an agreed budget and the brand guidelines suit acting and reporting afterwards. Agree check-ins when you delegate, matched to the person's experience and to the points where an error would cost the most.
Verify: fewer items on the board wait for the manager's answer, and work that comes back differently is not taken back.
Prevent: thin the check-ins out deliberately as work comes back right, and say when the level of authority changes.
Handovers nobody owns
The guide to team models and organisation design puts it plainly: most things go wrong where marketing hands work to sales, product or finance, and someone in marketing must own each interface rather than everyone half-owning it. Channel teams bring deep skill and the matching cost of channel silos, so integrated work slows at the joins between them.
Fix: write a short responsibility matrix around the decisions and handovers that cause arguments, with one accountable role per row, and name an owner for each interface. For sales, that covers lead handover, what counts as a qualified lead, what follow-up sales commits to and how lead quality is reported back.
Verify: items that used to wait at a join now move on within the team's normal rhythm, and nobody has to ask who decides.
Prevent: revisit the matrix whenever the structure shifts or a key person moves on.
No retrospective
Without a regular look at how the team works, the same blockers come back each quarter: incomplete briefs, handovers that lose information, meetings that do not earn their time. The tutorial on running a marketing team retrospective looks at how the team worked over a period, whatever the results.
Fix: hold a retrospectiveA planned look at how a team worked over a period, separate from what its campaigns achieved, ending in one or two owned changes with a date. at the end of each planning cycle, draw evidence from the calendar and the work system, trace each large theme to how the team works, whether a process, a rule or a habit, never to a person, and pick a single change, or two at most, within the team's control, giving each an owner, a way to test it and a date.
Verify: the next retrospective opens by checking whether each change held, and says whether to keep, adjust or drop it.
Prevent: feed the retrospective's changes into the next plan, and send themes the team does not control to the manager to raise.
Prevention: scored intake, an outcome check each fortnight and a quarterly look at routine work
The causes above share one signature: hours that do not reach a key result, or a key result that moves while the outcome does not. The cheapest prevention is to look for it often enough to act on it, through three habits.
The first is scored intake. Every request enters through one route, names the objective it serves and is weighed against what it would displace before anyone starts it. Work that serves no objective goes to the backlog openly, with a reason the requester can see. Where too much accepted work is in flight together, the guide to limiting work in progress holds it back until there is room to finish it, so the team finishes objective work instead of starting more of everything.
The second is an outcome check each fortnight, or at whatever regular point the team already meets. Read each key result and its leading indicator against the baseline, then read the board's finished items beside them and ask which work moved which result. Read the outcome first and the activity second. When a result has had little work against it, say so and decide whether to move effort towards it or accept the gap; when the activity is climbing and the outcome is not, treat the key result as suspect before blaming the people. Keep each KPIA metric tied directly to an objective. that describes ongoing work in the same view, so the routine responsibilities stay visible without being mistaken for the quarter's changes.
The third is a quarterly look at routine work, held before capacity is counted for the next plan. Repeat the recurring work review, record what was paused and what was released, and put the released time where the plan needs it. Keep a short time log from the people doing the work at the same point each quarter; the share of time going to objective work, compared with the last reading, is the most direct sign of whether the three habits are holding.
Around those habits, keep the quarter's own rhythm. Individual objectives are reviewed openly in one-to-ones, the authority levels set for delegated work are widened as the work comes back right, the responsibility matrix is revisited when the structure changes, and the retrospective at the end of the cycle checks whether the changes it chose last time held. If other management problems show up alongside this one, start from the marketing management troubleshooting hub to choose the page to read first.
A language school chain finds where its marketing effort went (illustrative)
Gorquint Language Schools
Gorquint Language Schools, an invented chain of 5 adult language schools with a marketing team of 6, delivered all 31 campaigns on its list for a quarter while enrolments from new learners, the quarter's main objective, stayed flat against a baseline of about 420.
A two-week time log beside the board showed where the hours went. About 35% went to a weekly newsletter, branch posters and 4 reports set up years earlier, 2 of which nobody had opened in months. About 25% went to brochures branch managers had requested directly, none scored against the objective. Roughly 10% was waiting for the head of marketing to approve sends. Objective work had about a fifth of the team's time.
The key results counted campaigns launched and posts published. Each marketer's objectives copied the team's activities, so the social lead's objective was a number of posts rather than trial lessons booked.
Gorquint scored every new request against the enrolment objective, paused the 2 unused reports and moved the newsletter to fortnightly, and rewrote the key results as new-learner enrolments with trial lessons booked as the leading indicator. Each marketer took an outcome objective they could move, with a baseline read on the day. Routine sends within the brand guidelines no longer waited for the head of marketing, and the team held a retrospective at the end of the quarter.
The next quarter's time log put just over half of the team's hours on objective work. New-learner enrolments rose to about 470, and no branch asked for the paused reports back.
Common mistakes
- Asking the team to work harder. The hours are already there; they are going to the wrong work.
- Accepting reasonable requests one at a time. None is weighed against what it displaces.
- Counting routines as fixed. Subtracting them before planning is right; never questioning them is not.
- Measuring campaigns launched. The count rises while the outcome stands still.
- Copying the plan's tasks into each person's objectives. People are then judged on output, and nobody owns a result.
- Delegating tasks but keeping the decisions. The work waits at the manager's desk.
- Leaving handovers to goodwill. An interface everyone half-owns is one nobody owns.
- Holding a retrospective with a long list of changes. A couple of changes that actually happen are worth more than many that never do.
