Before you start
The session only works if the inputs are ready and the right people are in the room. Prepare the following before the day.
- The annual plan and objectives. The session translates these into a quarter, so they need to be current. If you do not have an annual plan, read the annual planning guide first; a quarterly session without annual direction becomes a wish list.
- Last quarter's results. Performance against each key result and each KPIA metric tied directly to an objective., budget spent against plan, and the list of initiatives delivered, delayed and dropped. Preparing a quarterly marketing review before the session gathers these in one document, with each result explained by its drivers.
- The backlog and intake log. Every request and idea that is waiting, already scored if your team uses the approach in prioritising work and capacity.
- Capacity. Who is available next quarter, planned leave, recurring work and agency hours.
- Inputs from other functions. Sales targets and pipeline, product launches and dates, finance constraints. Where finance's figure and the cost of the plan disagree, the comparison of top-down and bottom-up budgeting explains how to settle the gap before the session.
- A facilitator. Ideally someone other than the person who owns the decisions, so the owner can take part.
- A template. The one-page marketing plan template works well as the output format.
Book a long block of uninterrupted time, in person if possible, and send the inputs a few days ahead so that the session is spent deciding rather than reading. A session that has to decide what the brand stands for, rather than what to do next quarter, follows a different agenda, set out in the tutorial on running a brand strategy workshop.
Steps
Gather and circulate the inputs
Pull the inputs listed above into a single pre-read, short enough to be read in one sitting. Lead with results against last quarter's key results, then the annual objectives, then capacity, then the backlog. Ask each attendee to come with a view on what went well, what did not and the two or three initiatives they think matter most next quarter. Collecting views in advance stops the session being dominated by whoever speaks first, and it surfaces disagreements early enough to prepare for them. Send the pre-read with enough notice that people actually read it, and say plainly that the session will assume they have.
Review the last quarter honestly
Open the session with the review. For each key result, state where it ended, why, and what the team learned. Then look at initiatives: which delivered, which slipped and which were dropped, and what displaced them. Separate the causes the team controlled from the ones it did not. The aim is learning, not blame, so ask what the team would do differently rather than who was responsible. Capture lessons in a short list that will shape this quarter's choices, such as underestimated effort, a channel that responded better than expected, or a dependency on another team that kept slipping.
Confirm the annual objectives
Restate the annual objectives and the measures behind them, and ask whether they still hold. Most quarters the answer is yes, and the step takes minutes. Sometimes the market, the product or the business has moved, and an objective needs to change. If so, record the proposed change and who must approve it, and plan against the proposal while making clear it is pending. Use the KPI tree to show how the annual measures break down into the drivers that quarterly work can move, such as traffic, conversion stages across the FunnelModel of the customer journey stages., retention or average order value.
Draft objectives and key results for the quarter
Agree a small number of quarterly objectives, as a rule of thumb two to four, each a plain statement of what the quarter must achieve in service of the annual plan. Under each, write two to four key results that measure outcomes rather than activity: "qualified demos from new segments" rather than "launch three campaigns". The north star metric and OKRs framework explains how to write key results that are measurable, ambitious and within the team's influence. Check each key result has a baseline, a target and a named owner. If the team cannot agree a measure, the objective is probably too vague. Where a key result is a KPI pushed to a new level, the comparison of OKRs and KPIs explains how the two connect and which numbers belong in each. A growth team with an app-install target can pair install and activation key results and time its grades for maturing data, as north star and OKRs for app installs shows.
Propose initiatives against each objective
For each objective, list the initiatives that could move its key results. Start with the backlog and the attendees' pre-session views, then open the floor for new ideas. Each initiative needs a one-line description, the key result it serves, a rough effort estimate from the people who would do the work, and an owner. Resist discussing the merits at length here; the aim is a complete list to score in the next step. Initiatives that do not serve any objective are noted and parked, which is often the first time some long-standing requests are seen for what they are.
Score and prioritise the initiatives
Score each initiative on impact on its key result, confidence that it will work and effort, using the same criteria the team uses for weekly intake. Discuss the top and bottom of the ranking briefly and spend most of the time on the middle, where the real trade-offs sit. Where an initiative is high in potential but low in confidence, consider running a smaller test first. Include a rough view of expected return, especially for initiatives with significant spend, so that likely ROIProfit relative to cost. informs the ranking. End the step with a single ranked list across all objectives. A single ranking makes the opportunity cost of the team's time visible, because every initiative near the top displaces one further down.
Check the ranked list against capacity
Take the team's available capacity for the quarter, subtract recurring work and a buffer for reactive requests, and fill what is left from the top of the ranked list. Draw a line where capacity runs out. Check for skill bottlenecks as well as total hours: if three initiatives above the line all need the same designer or analyst in the same month, the plan will slip. Adjust the line, move timing or decide to buy capacity from an agency. Items below the line go on the roadmap as later work, and everyone in the room should see them there.
Name risks and dependencies
For each initiative above the line, ask what could stop it: a dependency on product, sales, legal or technology, a supplier or agency, budget approval, data access or a key person's availability. Record each risk with an owner and a mitigation, and agree who will speak to the other teams involved. Dependencies on other functions are the most common reason marketing quarters slip, so leave the session with a named person responsible for each external dependency and a date by which it must be confirmed. Note any assumptions the plan rests on, so the monthly review can test them. Carry the risks into a standing marketing risk register, where each one gains a warning sign and a prepared response that outlast the session.
Agree the plan on a page
Write the outcome on a single page: the annual objectives it serves, the quarter's objectives and key results with baselines, targets and owners, the initiatives above the line with owners and rough timing, the main risks, and what was explicitly deferred. Read it back to the room and ask whether anyone cannot commit to it. Changes are cheap now and expensive later. The one-page format matters because it is what stakeholders will actually read, and it becomes the reference point for every intake and review decision in the weeks that follow.
Set the review cadence
Before the session ends, agree how the plan will be kept alive: the weekly meeting where work and intake are reviewed against it, the monthly review of key results, and the date of the next quarterly session. Decide what evidence will trigger a change mid-quarter, such as a key result clearly off track by the monthly review or a major change in the market, and who can approve it. Put the meetings in calendars before people leave the room. A plan without a cadence decays within weeks, however good the session was.
Session agenda template
The timings below add up to a 120-minute session, the length this tutorial assumes. Adapt them to the team's size and the number of objectives; the order matters more than the minutes.
| Segment | Minutes | Purpose | Lead | Output |
|---|---|---|---|---|
| Welcome and ground rules | 5 | Set the aim, the decisions to be made and how disagreements will be settled | Facilitator | Shared understanding of the session |
| Last quarter review | 20 | Results against key results and lessons learned | Head of marketing and owners | A short list of lessons |
| Annual objectives check | 10 | Confirm or propose changes to the year's direction | Head of marketing | Confirmed objectives or a change proposal |
| Quarterly objectives and key results | 20 | Draft and agree the quarter's commitments | Whole group | Objectives with measurable key results and owners |
| Initiatives | 15 | Propose work against each objective | Whole group | A complete initiative list |
| Break | 10 | Rest and informal discussion | Everyone | A rested group for the trade-offs ahead |
| Scoring and capacity | 20 | Rank initiatives and draw the capacity line | Facilitator with owners | A ranked list and a line |
| Risks and dependencies | 10 | Name what could stop the plan | Owners | A risk list with owners |
| Plan on a page and cadence | 10 | Agree the output and the review rhythm | Head of marketing | A signed-off plan and calendar dates |
Roastember Coffee plans its autumn quarter
Roastember Coffee, an invented subscription coffee roaster, ran its quarterly session for the autumn with a team of 8 and its paid media agency. The review of the summer quarter showed that 2 of its 3 key results had been missed because a website relaunch had absorbed most of the design capacity. The team set 2 objectives for the autumn: grow new subscriptions and reduce cancellations in the first 3 months. They proposed 19 initiatives, scored them, and drew the capacity line after 7, leaving a buffer of roughly a fifth of the quarter's capacity. The main risk, a dependency on the product team for a pause-subscription feature, was given an owner and a confirmation date. By the end of the quarter, early cancellations had fallen from 14% to 11%.
After the session
Send the plan on a page to attendees and stakeholders within a day or two, while the decisions are fresh. Update the roadmap and the backlog so that items above and below the line are visible to anyone who submits a request. Brief agencies on the initiatives they own, and confirm the external dependencies by the dates agreed.
In the weeks that follow, the weekly meeting is where the plan earns its keep. New requests are scored against the quarter's objectives and placed above or below the line, and anything that displaces planned work is recorded with the reason. The monthly review checks key results and tests the assumptions noted in the risks step. At the end of the quarter, the plan on a page becomes the first input to the next session, and the planning and prioritisation hub shows how this cycle fits the wider planning rhythm.
If the plan agreed in the session is rewritten within weeks, the diagnosis of a marketing plan that keeps changing separates healthy, evidence-led change from churn and traces the churn to its cause.
Common mistakes
- Starting without the annual plan. A quarter without annual direction produces a list of good ideas with no common purpose.
- Skipping the honest review. Planning the next quarter without understanding the last repeats the same failures.
- Key results that measure activity. Counting campaigns launched says nothing about whether anything moved. Measure outcomes.
- Too many objectives. Beyond about four, everything becomes a priority and the weekly intake has no basis for saying no.
- Ignoring capacity. A ranked list without a line is a wish list. Draw the line in the room.
- Leaving dependencies unowned. Work that depends on another team needs a named person to secure it.
- No cadence. Without weekly and monthly reviews in the calendar, the plan is forgotten within weeks.
