Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Marketing Management › Team and Structure

Managing Marketing Specialists Whose Work You Cannot Do

How a marketing manager leads specialists whose craft they do not share: what to judge, asking for reasoning, borrowed standards and an independent view.
Guideintermediate16 min readUpdated

Why managing a specialist differs from managing work you know

The guide to delegating marketing work gives a manager the core habits: hand over an outcome with a KPI and a Baseline, agree the level of authority for each kind of decision, and place check-ins where an error would be costly. It is written for a manager who came up through the work, and its player-coach section hands over parts of a channel the manager still runs. Such a manager can tell whether delegated work that comes back different is actually wrong.

That judgement disappears with a specialist in a discipline the manager has never practised. A head of marketing from brand or retail who takes on an analytics and tracking specialist, a technical SEO specialist, someone who builds marketing automation or a paid media buyer cannot open the work and see whether it is sound.

The marketing management pillar offers a framing that still holds. It cites the Chartered Institute of Marketing for the view that the manager's job moves from doing marketing tasks to directing them, and from skill in a channel to commercial judgement. Directing a specialist is a clear case of that move: the channel skill sits with the specialist, and the manager judges what the work is for, what it would cost to get wrong and whether it is delivering. The craft itself, how to build tracking, fix a crawl fault or structure an automated flow, belongs to each discipline's own section of the site and is not repeated here.

What you can judge without the specialism

Start by separating what a non-specialist can check from what only someone with the skill can. The tutorial for checking translated copy you cannot read yourself draws that line for one discipline: the marketer who owns the asset checks its structure, formats and links and uses a back-translation to confirm what its claims say, while sign-off on the language itself stays with a named reviewer who speaks it natively. As general practice, the same split can be tried in other specialisms.

What you look atWhat you can check yourselfWhat still needs someone with the skill
ResultsWhether the agreed outcome moved, read from the business's own recordsWhy it moved, when the cause lies inside the method
The questionWhether the work answers the decision it was meant to serveWhether a better technical route existed
ReasoningWhether each proposal states its purpose, options and risks in plain wordsWhether the technical argument holds
StandardsWhether the agreed checklist or audit was used and the review recordedWhether each line was met to the standard it describes
PredictionsWhether what the specialist expected to happen did happenHow to correct a method that keeps missing

Results come first, and they need care. Each discipline has its own counts, such as tags firing, pages crawled or conversions reported by an ad platform, and these are the discipline's own readings rather than the business's results. Agree the outcome in the business's terms, such as orders, qualified enquiries or revenue, and read it from the business's own records. The guide for the sole marketer in a business sets the same habit for anyone in that seat who buys specialist help: review the work against business results rather than against the supplier's own report. For a manager of specialists, the platform knowledge worth having is enough to follow the reasoning, not enough to do the job.

Reading those results takes some skill with numbers. Reading small numbers in marketing reports explains how to look for the count each rate is built on and how to quote a range rather than one figure, and the guide to building data literacy in a marketing team sets out the habits that let a non-analyst read a number fairly, from checking what a metric counts to asking what it is compared with.

Asking for the reasoning, not only the result

When you cannot check the method, the reasoning behind it is the closest thing to it you can see. Ask for each significant proposal to arrive with a short written note: the problem it addresses, the options considered, why this one won, what the specialist expects to happen, how the result will be read and how the change would be undone. As general practice, the rejected options say a great deal. A specialist who can say why the obvious alternative was worse has weighed the decision; one who cannot may be repeating a habit.

Tie each piece of work to the decision it serves. The guide to running an analytics request process records, at intake, the decision behind each analytics question so that the answer is shaped around it. Work framed that way is easier to judge without the craft, because the manager can ask whether the decision is now clearer.

Predictions are reasoning you can check later. Keep the expectation beside each change and compare it with what happened; over a run of changes, that record shows whose judgement to trust, however good the explanations sound.

Treat a plain explanation as part of the job. The guide to presenting your work to senior leaders prepares a specialist for exactly this: lead with the answer and the decision needed, bring evidence that holds up under challenge, and admit when the answer is not yet known. Reasoning is evidence about the thinking, not proof that the work is right: a fluent explanation can hide a fault that only someone with the skill would spot, which is why the next two sections exist.

Borrowing a standard: audits, checklists and procedures

A manager who cannot write a technical standard can adopt one that already exists, linked here rather than restated.

For analytics and tracking, the analytics implementation audit scorecard scores the whole set-up criterion by criterion, ending with whether its numbers agree with the business's own records. For technical search work, the technical SEO audit scorecard does the same for how the site is crawled and indexed. A manager cannot score either alone, but can ask the specialist to score the current state, agree which gaps to close first and treat the next scoring as a check on progress.

For changes made week to week, a checklist is the standard. The container publish checklist is the gate before a tag container change goes live, from checking the change set to noting the version to roll back to, and it includes the second review the container's rules require before anything is published. A manager can ask to see each line ticked, and can treat a change published without the checklist as a breach of the team's standard whether or not anything broke.

For recurring tasks, the standard is a procedure the specialist writes. The tutorial on writing a marketing SOP takes one task from its scope and trigger through the owner, steps, checks, exceptions and versioning to a test run by someone who has never done the task. A Standard Operating Procedure gives the manager something concrete to check: whether it exists, whether it is current and whether someone else could follow it.

Borrowed standards have limits. A checklist confirms that steps were taken, not that each was taken well, and an audit scored by the person whose work it audits is a self-assessment. That gap is what an independent view fills.

Getting an independent view

Where the method matters and you cannot judge it, bring in someone who can. The guide to buying SEO help from an agency lists an audit as one form of engagement, suited among other things to a second opinion. The comparison of in-house teams and agencies makes the point from the other side: a business that buys specialist work should keep someone on its own staff who can assess and question that work. When the specialist is that person, the manager needs the reverse: an outside view of the specialist. The sources below are general practice.

Source of the viewSuitsWatch for
An agency or freelance specialist the team already usesReviewing changes in a discipline they know, at an agreed pointReviewing work they built, or work that replaced theirs
A one-off audit by an outside specialistA second opinion on the state of a whole areaFindings with no examples and no priorities
A specialist elsewhere in the business, such as a developerChecking one change or one analysisGoodwill that runs out if the requests never stop
Whoever owns the business's own recordsReconciling results with orders, enquiries or revenueTaking a match on totals as proof that the detail is right

For analysis, the tutorial on reviewing an analysis before it is shared sets out a check by someone other than the author, who reruns the key figures from the saved queries instead of reading them off the page, and lists the commissioner acting as the only reviewer among its mistakes. A manager who commissions analysis from a specialist is that commissioner: the manager's part is to check that the analysis answers the question and the decision it was meant to serve, and to make sure somebody else reproduces the numbers.

For tracking, the container governance guide builds a second person's review into every change: someone other than the author reads the change against its request, and edit rights are kept apart from publish rights, so that not everyone who can build a change can publish it. Set up that way, the independent view is a written step in every change rather than a favour asked now and then.

Share the reviewer's findings with the specialist and ask for a response, rather than treating the outsider as the judge. Where two specialists disagree, ask each to explain, then decide by the outcome the work serves and the standard the team adopted. Check, too, what the reviewer has riding on the answer: an agency reviewing the work that replaced its own has a stake in the verdict, so hold its review to the agreed standard and read its findings with that stake in mind. Any fee for an outside review is a question for the budget holder, and its contract terms belong with whoever handles supplier contracts in the organisation.

Setting authority when you cannot check the method

The delegation guide sets authority on a scale running from acting and reporting afterwards to preparing the work while the manager decides, matches the level to the cost of getting the call wrong, and widens it as the work comes back right. With a specialist, that last signal is weaker, because the manager cannot always tell whether the work came back right. Two things take its place: how hard the change is to undo, and whether it passed through the borrowed standard and the independent review.

One-way and two-way door decisions sort choices by how easily and cheaply they can be reversed. The sort has a useful property here: the manager can make it without the craft, by asking the specialist what undoing the change would involve and what would be lost in the meantime.

  • Reversible and inside the standard. A change that has passed the agreed checklist, had its independent review and can be rolled back to a known previous version sits with the specialist, reported in the normal rhythm.
  • Reversible but outside the standard. A change the checklist does not cover comes to the manager as a recommendation with its reasoning, and the gap in the standard is noted.
  • Hard to reverse. A change to what the business counts as a result, a deletion of history, a new commitment to a supplier or anything that reaches every customer at once comes as options for the manager to decide, with the outside view attached. It stays with the manager however well the specialist understands its mechanics, because the consequences fall on the business.

Place the check-ins at those hard-to-reverse points and wherever the standard runs out. Whatever the band, a change the specialist built is reviewed by someone else before it is published; authority to act means acting once the standard and the review are satisfied, not in place of them. The manager stays accountable for the outcome, and no level of authority loosens the approvals route or the organisation's rules on who may commit spending.

Widen authority on evidence the manager can see: expectations that come true, reviews that find little, standards followed without reminders. Narrow it the same way, openly and for a stated period, rather than quietly taking decisions back.

Hiring and developing a specialist

Hiring exposes a manager without the craft, because the candidate may know more about the discipline than anyone on the panel. The guide to hiring and developing marketers still sets the shape: scope the role around outcomes and decisions before the advert, set an assessment task that mirrors the real work, and use the discussion of the task to see how the candidate reasons, copes when challenged and deals with gaps in what they knew. It also suggests a panel member from a team the role depends on; for a tracking specialist, that could be the developer who would deploy the changes.

Three further habits are general practice rather than anything the hiring guide states:

  • Build the task from the team's own past work with a known outcome, such as a tracking fault the team has since traced, so the answer can be judged without the manager's own expertise.
  • Judge it on outcome and reasoning together: did the candidate reach a sound answer, and could they explain what they would check first, what they ruled out and why?
  • Ask a specialist the team already works with to mark it, such as its agency or a freelancer in the discipline, with the candidate told in advance who will judge the work.

Keep the task proportionate, as the hiring guide asks. Recruitment approval, pay, grading and contract terms are for the people team to settle under the organisation's rules.

Development has the same problem in reverse: the manager cannot coach the craft. The hiring guide's development plans name support such as pairing, a course, or time spent with a specialist or agency, and for someone whose manager cannot coach the discipline, time with another specialist becomes the natural route for the technical side. The marketing team skills matrix template rates each skill with evidence from real work, shows where a skill rests on one person and notes for each gap whether to build it, hire for it or buy it in. The manager develops everything around the craft, from understanding the business to prioritising competing requests. Where the specialist takes on a channel they have not run before, the careers tutorial on picking up an unfamiliar channel while it runs gives them a method from their own side, with a learning log that someone else reviews; the manager's job is to find that reviewer, who may be the same outside specialist who provides the independent view.

Keeping the knowledge in the team

A specialist whose work nobody else understands fits the description of key-person risk. In the team's coverage matrix, it shows up as tasks and accounts with the specialist's as the only name against them. The operations guide on key-person risk names a tag container only one person understands among its examples of work that stops when someone is away, finds that work by listing recurring tasks and their accounts in a coverage matrix, and closes each gap through a second admin, a written procedure, cross-training or a supplier, checked with a live run. Three habits drawn from it apply here.

  • Accounts in the business's name, with more than one administrator, so that access does not depend on the specialist; the in-house comparison and the team-of-one guide both put ownership of accounts and data with the business.
  • Procedures for the tasks only the specialist can run, written by the specialist and tried by someone else in the way the SOP tutorial tests a draft with a newcomer.
  • Changes and decisions recorded where others can read them: the note behind each proposal, the expectation and what happened, and a version note on each container change.

If the specialist leaves, these are what make the gap manageable. The tutorial on covering an empty role runs the team through the period before a replacement starts, and the specialist's procedures and notes are useful material when the role is scoped again. The team structure hub routes wider people problems, such as a manager who reviews everything, to the guide that handles each one.

An umbrella maker's head of marketing manages a tracking specialist (illustrative)

Illustrative example — not a real result

Gemmolrax Umbrellas sets a standard for its tracking work

Gemmolrax Umbrellas, an invented maker of umbrellas selling online, has a marketing team of 6. Its head of marketing came from brand and retail work and had never built tracking when the business hired its first analytics and tracking specialist, after 3 years in which an agency had maintained the tag container.

She agreed his first outcome in the business's terms. In the month before he started, the order system recorded 1,240 online orders and analytics recorded 930 purchases, 75% of them. The outcome was for tracked purchases to reach at least 95% of the order system's count by the end of his second quarter, read monthly from the order system rather than from tags firing. Each proposed change came with a note of no more than a page; his note on purchase tracking rejected 2 alternatives, rebuilding the whole container at once and asking the web developers to change the checkout code, and said why. She could not judge the mechanics, but she could see a choice had been made.

The team adopted the analytics implementation audit and the container publish checklist as its standard. The specialist's first scoring came out amber, and they agreed the 4 gaps to close first. The agency that built the original tracking stayed on a small advisory arrangement, approved by the finance director: it reviewed each workspace before publishing, as the checklist's second review, and looked over the quarter's changes at the quarter's end. Because the agency had built the tracking he was now changing, she shared each of its reviews with him for a response rather than treating it as the verdict. Any change that had passed the checklist, had the agency's review recorded and could be rolled back went live without waiting for her. A proposal to change which actions counted as conversions waited for her decision, with the agency's view attached, and she approved it a month later, once the 3 reports that relied on the old definition had been listed and their owners told.

She also asked for procedures for the 2 exports only the specialist could run, and a member of the email team ran each one from its procedure while he watched. By the end of the second quarter, analytics recorded 1,160 purchases against 1,210 orders in its last month, 96%, the audit's second scoring, which the agency checked at its quarter-end review, came out green, and 14 changes had been published, 1 of them rolled back the same day when the live check showed a tag firing twice.

Common mistakes

  • Waving the work through. Not understanding the method is no reason to stop judging. Judge the outcome, the reasoning and whether the standard was followed.
  • Asking to be taught the discipline. It turns the specialist into a tutor. Ask for the reasoning and the options rejected, scaled to the decision.
  • Judging by the specialism's own counts. Tags firing and pages crawled describe activity. Read the outcome from the business's own records.
  • Letting the specialist mark their own work. A self-scored audit and a self-reviewed change are not checks. Build an independent review into the routine.
  • Setting authority by confidence. Sounding sure is not evidence that a change can be undone. Set the level by how hard the change is to reverse.
  • Hiring on vocabulary. Fluency in the discipline's terms is not sound reasoning. Set a task from past work with a known outcome.
  • Leaving the knowledge in one head. Ask for procedures, keep accounts in the business's name and record each change.

Frequently asked questions

Do I need to learn the specialism to manage a specialist?

Not to the point of doing the work. Learn enough of the vocabulary and the main moving parts to follow the specialist's reasoning, ask useful questions and read the results against the business's own records. Beyond that, the manager's time goes further on what only the manager can do: agreeing outcomes, deciding the changes that are hard to undo, arranging an independent review and developing the specialist. Asking for the basics to be explained once, in plain words, is fair; asking the specialist to teach you the discipline is not.

What if the specialist is more experienced than I am?

It does not change what the manager is there to do. The manager does not need to know more about the craft; the manager owns the outcome, the priorities and the decisions that cannot easily be undone. Say that openly, agree how the work will be judged, and draw on the specialist's experience to choose the written standard the team adopts and the outside reviewer it uses. Experience in the discipline can earn wider authority over reversible changes as the evidence builds, but never an exemption from review.

What should I do if I suspect the specialist's work is poor?

Test the suspicion before acting on it. Compare the results with the business's own records, check whether the agreed standard was followed and ask someone with the skill for an independent view of the specific work. If that view confirms a problem, give specific feedback, agree what changes and narrow the specialist's authority for that kind of change for a while, saying why. If problems persist despite clear outcomes, standards and support, raise them in one-to-ones; a formal process, if one is needed, is for the people team to run under the organisation's policy.

Terms used on this page

Frameworks

Sources

  1. Chartered Institute of Marketing — CIM

Related