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

Marketing Management › Planning and Prioritisation

Prioritising Marketing Work and Capacity

How to prioritise marketing work: request intake, scoring against objectives, capacity planning, saying no with a roadmap, and handling urgent requests.
Guideintermediate10 min readUpdated

Why prioritisation is the manager's main lever

A marketing manager has few levers that change results quickly. Hiring takes months. Restructuring takes a quarter and costs momentum. Budget is usually set for the year. What the team works on this week, and what it stops working on, can change on Monday. That makes prioritisation the most direct influence a manager has on outcomes, and also the one most easily given away.

It is given away in small steps. A sales director asks for a brochure. The chief executive wants a campaign for an event. A product manager needs launch assets earlier than planned. Each request is reasonable, each is accepted, and none is weighed against what it displaces. By the end of the quarter the team has worked hard, delivered many things and moved few of its objectives. Writing in the Harvard Business Review on strategy and execution returns to the same theme: organisations fail less from bad choices than from not making choices at all, letting everything become a priority until nothing is. When that quarter has already happened, the diagnosis for a marketing team that is busy while its objectives stand still sets a record of where the team's time went beside the key results and traces the effort to its causes.

The manager's job is to make trade-offs visible. That does not mean refusing work or guarding the team from the business. It means ensuring that whenever something new comes in, someone decides what it replaces, and that the decision is made against the objectives the team and its stakeholders agreed in the quarterly planning session.

Intake: one front door for requests

Prioritisation is impossible if requests arrive through email, chat, corridor conversations and meetings, each to a different person. The first step is a single front door: one route through which every request enters, whoever it comes from. It can be a form, a ticket queue or a shared board. The tool matters less than the rule that work not submitted through it does not exist.

A good intake captures enough to judge the request without a meeting: what is being asked for, which objective or KPI it serves, the audience, the deadline and why it is the deadline, who requested it and who will approve it. Requesters who have to state the objective often realise their request does not serve one, and that alone filters a share of low-value work.

Triage the intake on a fixed rhythm, usually weekly, as part of the team's planning meeting. Each request gets one of a few outcomes: accepted into the roadmap, added to the backlog with a reason, sent back for more information, redirected to someone better placed, or declined. Tell the requester which, and when they can expect it. A published catalogue of service levels for marketing requests sets the usual turnaround for each type of request and what the requester must provide for it to hold. The operations root covers the workflow mechanics from intake form to launch in campaign workflow from intake to launch; the manager's concern is the decision, not the plumbing. Product releases are a different flow, coming from product management rather than from requesters, and the tutorial on running launch intake tiers and schedules them before they become launch work for the team.

Scoring against objectives

Scoring turns a pile of requests into a ranked list that can be discussed. The aim is not precision; it is a shared, explicit reason why one piece of work comes before another.

CriterionQuestionHow to judge it
Objective fitWhich of the quarter's objectives does this serve?Must name one; work that serves none goes to the backlog
ImpactIf it works, how much would it move the key result?Low, medium or high, with a sentence of reasoning
ConfidenceHow sure are we that it will work?Higher with evidence from tests, research or past results
EffortHow much team time, budget and partner time does it need?Rough size from the people who will do the work
Time sensitivityDoes value fall sharply if it waits?A real external date, not a preferred one
DependenciesDoes other work or another team rely on it?Note what it unblocks or what blocks it

Rank by impact and confidence relative to effort, then apply judgement for time sensitivity and dependencies. A small set of agreed ratings is enough; elaborate weighted spreadsheets give a false sense of rigour and invite gaming. Score as a team, with the people who will do the work estimating effort, because managers routinely underestimate it. For a quick first pass over a long list, plotting requests on an impact-effort matrix separates the quick wins from the costly, low-value work before the full scoring. The comparison of the impact-effort matrix and the weighted scoring matrix explains when a sorted list should hand its hardest choices over to a weighted, evidence-backed score.

Confidence is where evidence enters. A request backed by a successful A/B Test, customer research or a past result deserves a higher score than one backed by opinion. Where confidence is low but the potential impact is high, the right answer may be a small test rather than a full commitment, in the spirit of the experimentation loop. Prioritising the tests themselves is a separate discipline covered in prioritising tests.

Expected return matters too, especially for large items. A rough view of cost against likely ROI helps separate the work that earns its effort from the work that merely fills the calendar.

Capacity planning and the roadmap

A ranked list is not a plan until it meets capacity. Start with what the team can realistically deliver in the quarter: the people available, minus holidays, recurring work that never stops (reporting, always-on campaigns, maintenance), and a buffer for the reactive work that history says will arrive. Look at last quarter's planned work against what was actually delivered; that gap is your best estimate of the buffer you need. Because recurring work is subtracted before anything is scored, it needs its own check, and the tutorial on reviewing recurring marketing work tests each routine against the evidence before it is counted again. Time for improving how the team works belongs in this count too; the guide to prioritising marketing operations work keeps those fixes in a backlog of their own and protects time for them. If AI tools are expected to free capacity, measure the change before counting on it: the guide to measuring AI's impact on team output explains why time per accepted output, review included, is a safer planning figure than hours saved as people report them.

Then fill the remaining capacity from the top of the ranked list until it is full, and stop. Everything below the line goes on the roadmap as later work or stays in the backlog. The roadmap should show what is being worked on now, what comes next and what is under consideration, without promising dates for the later items. A simple board or a one-page roadmap shared with stakeholders is enough. Where the whole team is one person, the guide to working as a marketing team of one scales the intake, the ranking and the "not doing" list down to a single marketer's week.

Check capacity by skill as well as in total. A team can have spare hours overall and still be overloaded in design or analytics, which then become the bottleneck for everything. Where a specialist is the constraint, either prioritise around them or buy capacity from an agency or freelancer for the peak. The comparison of the Pareto principle and the theory of constraints explains how to tell a step that limits the team's output from work that is simply worth more. Keep the north star metric and OKRs framework in view: capacity should flow to the work that moves the key results, not to the work that is easiest to start.

Saying no and negotiating scope

Most requests should not get a flat no. They should get a choice. Show the requester where their request ranks and what it would displace if it jumped the queue, and ask what they would prefer. Often the answer is that the request can wait, or that a smaller version would do. When the requester is senior and chooses their request over planned work, the trade-off is now their decision and is visible to everyone, which is exactly how it should be.

Negotiating scope is the other tool. A request for a full campaign may be served by an email and a landing page. A request for new assets in many formats may be served by adapting existing ones. Ask what the requester needs to achieve, not what they asked for, and offer the smallest version that achieves it.

When you do decline, give the reason in terms of the agreed objectives, say what would change the answer, and point to where the request now sits. A visible roadmap makes declining much easier, because the requester can see that the team is not idle and that their request was weighed rather than ignored. The planning and prioritisation hub explains how the roadmap connects to the quarterly and annual plan.

Urgent requests and escalation

Some requests will be genuinely urgent: a competitor move, a press issue, a broken page, a sales opportunity with a real deadline. The plan should expect them. Define what counts as urgent in advance (an external deadline or a material risk, not a senior requester) and keep the capacity buffer for it.

Give urgent work its own route. The requester flags urgency at intake with a reason; the manager or a named deputy decides quickly whether it qualifies; if it does, it goes straight into the work, and the team agrees what pauses. Record each urgent request, and review the list monthly. If the same kind of urgent request keeps arriving, it is not urgent; it is unplanned recurring work that belongs in the plan. When what arrives is not a request but a whole area of lasting work the business wants marketing to own, the guide to taking on a new responsibility weighs it against the team's remit and shows what it would push below the capacity line.

Agree an escalation path for disputes. When two stakeholders both insist their request comes first and the scoring does not settle it, the decision goes to the person who set the objectives, usually the head of marketing or a leadership sponsor. Escalating is not a failure; it is the system working, and it stops the team being pulled between competing bosses.

Illustrative example — not a real result

Larkspur Health takes control of intake

Larkspur Health, an invented private clinic group, had a marketing team of 5 receiving requests from 11 clinic managers by email and phone. In one quarter the team delivered 64 pieces of work and moved neither of its 2 objectives. The manager introduced a single request form, a weekly triage meeting and a scoring sheet with 4 criteria, and reserved about a quarter of capacity for urgent work. In the next quarter the team accepted 27 requests, declined or deferred 30 with a reason, and delivered a patient-acquisition campaign that had been postponed twice. New patient enquiries rose 15% on the previous quarter, and complaints from clinic managers fell once they could see the roadmap.

Common mistakes

  • Many front doors. If requests can reach the team by any route, prioritisation happens by accident. Close the side doors.
  • Scoring that nobody believes. Complex weighted models invite gaming. Keep the criteria few and the reasoning written.
  • Planning to full capacity. Without a buffer, the first urgent request breaks the plan. Use last quarter's history to size it.
  • Ignoring skill bottlenecks. Total hours can look fine while one specialist blocks everything. Plan by skill.
  • Flat refusals. A bare no damages relationships. Offer a trade-off or a smaller scope instead.
  • Treating seniority as urgency. A senior requester is not a deadline. Define urgency by external dates and real risk.
  • Never reviewing the urgent list. Recurring urgent work is unplanned work. Move it into the plan.

Frequently asked questions

What is the best scoring model for marketing requests?

The best one is simple enough that the team actually uses it. Score each request on its contribution to the quarter's objectives, its expected impact, the confidence behind that estimate and the effort it needs, then rank by impact and confidence relative to effort. The numbers matter less than the conversation they force about why one piece of work beats another.

How much capacity should a marketing team leave unplanned?

Enough to absorb the urgent requests, fixes and reactive work your history says will arrive, which for most teams is a meaningful share of the quarter. Look at what the team actually did last quarter against what it planned and use that gap as the buffer. Planning to full capacity guarantees that the plan will slip.

How do I say no to a senior stakeholder's request?

Do not say no; show the trade-off. Put the request through the same scoring as everything else, then show the stakeholder what it would displace on the roadmap and ask which they prefer. Most senior people accept a clear trade-off, and when they choose their request over planned work, the decision and its cost are now theirs and visible.

Terms used on this page

Frameworks

Where this page is used

Part of these learning paths

Also related

Sources

  1. Harvard Business Review — Harvard Business Review

Related