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

Marketing Management › Team and Structure

Setting Objectives for Each Marketer From the Team Plan

How to set objectives for each marketer from the team plan: outcomes they can influence, measures with baselines, shared results, development goals and reviews.
Tutorialintermediate11 min readUpdated

Why individual objectives go wrong

Most marketing teams that set individual objectives start in the right place and end up somewhere else. The team agrees a quarterly plan, the manager is asked for objectives for each person, and the quickest route is to split the team's targets by head or copy the plan's activities into each person's list. Three familiar problems follow.

The first is objectives the person cannot influence. An email specialist is handed a result about website conversion, a content writer a result about sales pipeline. Both work hard on their own channel and watch a number move, or fail to move, for reasons that sit with someone else. They learn that the objective is a lottery, and stop paying attention to it.

The second is objectives that are activities. "Publish the new nurture sequence" is a task; it says nothing about whether the sequence did anything. The north star metric and OKRs framework makes the same point about team key results, and it holds for a person: an objective is an outcome, and the tasks that might reach it belong in the work plan. When a whole team is measured on its output this way, the diagnosis for a marketing team that is busy while its objectives stand still traces how that combines with other causes to leave the key results flat.

The third is objectives that become a verdict. Google's re:Work guide to OKRs, as that framework and the comparison of OKRs and KPIs explain, treats grades as a learning tool and keeps them separate from appraisal, because people whose pay depends on a grade write safe goals. Once individual objectives are read as the whole judgement of a person, the Goodhart's law problem appears: the measure becomes the target and stops telling anyone what is happening. This tutorial sets objectives as a way to connect each person's work to the plan and to learn from the quarter. It is not a performance management process, and where those questions begin, they go to your organisation's policy and its people team.

Before you start

  • An agreed team plan. Individual objectives come from the quarter's objectives and key results, so the quarterly planning session comes first. If the team plan is still in draft, wait; objectives written against a draft are rewritten within weeks.
  • The role scopes. Each person's outcomes and ongoing responsibilities, as the team models guide describes when it links each role to a measure.
  • Each person's development plan. The guide to hiring and developing marketers builds it from a skills matrix; this tutorial uses it rather than rebuilding it.
  • Access to the data. The reports or dashboards behind every key result, so baselines can be read on the day.
  • The capacity picture. What each person already carries, from the guide to prioritising work and capacity.
  • Time in each person's one-to-one to agree the set in conversation.

The steps

  1. Start from the team's objectives and key results

    Put the team's plan on a page in front of you and read each objective and key result as the thing everyone's objectives must trace back to. Separate the quarter's changes from the ongoing work. The comparison of OKRs and KPIs draws the line clearly: a KPI describes a responsibility that continues every month, and an objective is a decision to move something this quarter. A paid search specialist's account health is a KPI; growing new customers from a new audience might be an objective. Both matter, and only the second belongs in this exercise. If a team key result has no owner yet, settle that before writing anyone's objectives, or two people will write the same one.

  2. Map which results each role can move

    For each team key result, break it into the drivers that produce it, using the KPI tree: enquiries break into visits and conversion, visits into channels, conversion into pages and forms. Then mark which role's work moves each driver. Some roles connect directly to a key result, some to one driver of it, and some to none this quarter. Write the map down. It shows where a key result has no one working on it, where two people pull on the same driver, and which roles have a quarter of ongoing work rather than a change to make. The last case is normal; do not invent objectives to give everyone one.

  3. Write each person's outcome objectives

    For each person with a line to a key result, write the objective as an outcome they can influence: the driver from the map, the direction it should move and the reason it matters to the team plan. Following the re:Work guidance as the framework describes it, make objectives ambitious and concrete, keep them few and make them visible to the whole team, so everyone can see how the pieces fit. Where the team's result is lagging and will not settle until after the quarter, give the person a Leading Indicator they can move now and say which lagging result it is expected to predict. The work they will do to reach the objective goes in the work plan, not here.

  4. Give every measure a baseline and a source

    Each measure needs a definition, the report it is read from and its reading on the day the objective is written. The framework asks the same of team key results: a measure without a Baseline recorded at the time is graded by memory, and the closing conversation turns into an argument about the starting point. Use the same definition the team plan uses, or the person's number and the team's will drift apart. Where the counts are small, as they often are for one person's channel, read them as the guide to reading small numbers advises, with ranges and the counts behind every rate, so that ordinary variation is not mistaken for success or failure.

  5. Name shared results and their co-owners

    Some results cannot be moved by one person: a conversion rate that depends on the email that brings the visit and the page that takes the enquiry, or a launch result that needs content, paid media and product marketing. Write these as shared results. Name every co-owner, write what each contributes, and give each person a measure of their own part where one exists. A shared result with no named co-owners is the original problem in a different shape. If a co-owner sits in another team, agree it with their manager before the quarter starts, and check that their capacity is actually committed, as the prioritising guide describes, rather than assumed.

  6. Add one development goal from the person's plan

    Take one goal from the person's development plan, built from the skills matrix as the hiring guide describes, and put it on the same page. Where it fits, connect it to the quarter's work: someone building analysis skills might own the measurement for a shared result. The skills themselves can be described with the digital marketing skills map, and someone working towards a larger role can read the expectations in career ladders and levels. Keep the development goal separate from the results; it is judged by what the person can now do, not by a number. If the team has no plans yet, the marketing team skills matrix template builds them from rated skills and gaps.

  7. Agree the set in a one-to-one, not by email

    Draft the objectives before the conversation, and ask the person to draft theirs too. Compare the two in the one-to-one. Check three things together: that the person can influence each result, that the measures and baselines are right, and that the set fits alongside their ongoing work. If it does not fit, change the set or move work, and say which. An objective sent by email is accepted without being owned; an objective agreed in conversation is one the person can explain. Where the work needs authority the person does not yet have, settle that in the same conversation, as the guide to delegating marketing work describes. Then publish the sheets where the whole team can see them.

  8. Review progress during the quarter and change it openly

    Use the one-to-ones and the team's normal review rhythm, not a separate process. At each review, update the reading, note what is helping and what is in the way, and decide whether anything needs to change. When the team plan changes, the objectives that trace to it change too: rewrite them, note the date and the reason on the sheet, and record the new baseline if the measure changed. An objective quietly abandoned mid-quarter teaches the person that the sheet does not matter. An objective changed openly teaches them that it does. When the manager who agreed a sheet leaves or is replaced, the sheet and its change log are what the person brings to the new manager, and the guide to working through a change of manager covers that handover from the marketer's side.

  9. Close the quarter with a conversation, not a score

    At the end of the quarter, read each result against its baseline with the person and talk about what moved it, what did not, and what each of you would do differently. Grade if the team grades its key results, and treat the grade as re:Work does, as information for the next plan. No single number is the whole judgement of a person's quarter: the Goodhart's law framework explains why, and a result missed for reasons outside the person's control says nothing about their work. Pay, ratings, appraisal systems, probation and any formal performance process follow your organisation's policy and its people team, and are out of scope here. The lessons go into the next quarterly session.

What a one-page objective sheet holds

Keep each person's objectives on a single page that anyone in the team can read. The fields below are general practice; teams add or drop rows to suit.

FieldWhat it holdsWhy it matters
Team objective and key result servedThe line from the team plan this objective traces toShows the link to the plan at a glance
ObjectiveThe outcome, in a sentence, with the reason it mattersKeeps the focus on results, not tasks
Measure and definitionThe metric, defined as the team plan defines itStops the person's number and the team's drifting apart
SourceThe report or dashboard the reading comes fromMakes every reading checkable
BaselineThe reading on the day the objective was writtenTurns the closing conversation into a reading
Leading indicatorThe earlier measure the person can move now, where the result lagsGives a signal before the quarter ends
Shared withThe named co-owners and what each contributesPrevents one person carrying a result they cannot move alone
Development goalOne goal from the person's development planConnects the quarter's work to growth
Review pointsWhen the sheet will be read togetherKeeps it alive between planning sessions
Change logWhat changed during the quarter, when and whyKeeps changes open rather than quiet
Closing notesWhat moved, what did not, what was learnedFeeds the next quarterly session

The objectives and KPIs guide in the digital marketing root covers how marketing objectives and KPIs are written at plan level; the sheet applies the same discipline one person at a time. The team structure hub maps the other people habits, from roles to development, that the sheet depends on.

An insurer's marketing team sets its quarter (illustrative)

Illustrative example — not a real result

Ostrevin Insurance turns two team objectives into individual objectives

Ostrevin Insurance, an invented specialist insurer for small landlords, had a marketing team of 6. Its quarterly plan set 2 objectives: grow online quotes from landlords new to the business, and keep more customers at renewal. The key results were online quotes rising from 1,150 to 1,400 a month and renewal rate rising from 78% to 81%.

The head of marketing mapped each key result with a KPI tree. Quotes broke into visits to the quote page and the share of visits that started a quote; renewals into renewal reminders opened, renewal pages visited and calls to the service team. On her first draft, the email specialist carried the quotes key result outright. The map showed why that was wrong: email could bring landlords to the quote page, but the quote form, its questions and its error rate sat with the web team, whose lead had just scheduled a redesign of the form.

In the one-to-one they rewrote it. Quote starts became a shared result, with the email specialist and the web lead named as co-owners and the web lead's manager agreeing it before the quarter began. The email specialist's own measure became visits to the quote page from email, with a baseline of 2,300 a month read from the analytics report on the day, as a leading indicator for quote starts. Her second objective, renewal reminders opened, had a baseline of 61% from the email platform. Her development goal, from her plan, was building the monthly reporting for the shared result herself.

At the mid-quarter review the form redesign slipped, and the change was logged with the date and the reason. By the quarter's close, visits from email had reached 2,750 a month and quote starts 1,320. The closing conversation recorded that email had done its part and that the form was now the constraint, which became the first item in the next quarterly session.

Common mistakes

  • Splitting the team's target by head. A share of a number is not an objective the person can influence. Map the drivers first.
  • Writing activities as objectives. Tasks belong in the work plan. The objective is what the tasks are meant to change.
  • Giving one person a result another team controls. Write it as a shared result and name the co-owners, including anyone outside marketing.
  • No baseline on the day. A measure without its starting reading is graded by memory, and the closing conversation becomes a dispute.
  • Inventing objectives for ongoing work. A role with no line to a key result this quarter is measured by its KPIs. That is not a gap.
  • Agreeing objectives by email. The person accepts them without owning them. Agree them in a one-to-one.
  • Changing objectives quietly. Record every change, its date and its reason on the sheet.
  • Treating the sheet as a verdict. No single number is the whole judgement of a person, and pay, ratings and formal performance processes belong to your organisation's policy and its people team.

Frequently asked questions

How many objectives should each marketer have?

As few as the person can keep in mind and actually work on alongside their ongoing responsibilities. Google's re:Work guide, as the north star and OKRs framework on this site explains, advises keeping objectives and key results few per team and visible, and the same logic applies to a person. A long list lets every task claim to serve an objective and makes the closing conversation a tour of half-finished items. If the list keeps growing, the team plan probably has too many objectives as well.

Should individual marketing objectives be linked to pay or bonuses?

The OKR guidance cited on this site treats grades as a learning tool and keeps them apart from appraisal, because people whose pay depends on a grade write key results they are sure to hit. The comparison of OKRs and KPIs notes that KPIs describing ongoing responsibilities are more often part of performance reviews. Whether and how anything feeds into pay, ratings or appraisal is set by your organisation's policy and its people team, and that question is outside the scope of this tutorial.

What if a marketer's work does not connect to any of the team's key results this quarter?

That is common and not a problem. Much marketing work is ongoing: running a channel, producing the newsletter, keeping the website accurate. Those responsibilities are described by the role and measured by KPIs, not by quarterly objectives. Do not invent an objective to give everyone one. Agree the KPIs for the ongoing work, add a development goal, and check whether the person's capacity could serve a key result next quarter instead.

Terms used on this page

Frameworks

Where this page is used

Sources

  1. Guide: Set goals with OKRs — Google re:Work

Related