When a new responsibility lands on marketing
It can arrive as a sentence in a leadership meeting, a note from the managing director or a reorganisation somewhere else in the business. Marketing should look after the website from now on, run the events, take over the staff newsletter, answer the customer reviews, produce the sales materials or run the social account the product team set up. Each sounds like a modest extension of what the team already does, and it can arrive framed as settled before anyone has asked what it involves.
The marketing management pillar describes the manager's job as looking after four things: the people, the plan, the partners and the stakeholders. A new area reaches all four at once.
The guide to prioritising work and capacity handles incoming work as requests: each one comes through Request IntakeThe single route through which every request reaches the marketing team, usually a short form, so work is triaged and checked before it starts., is weighed against the quarter's objectives and either fits the capacity or waits. The same guide adds that a type of urgent request which keeps coming back is not urgent at all: it is work that recurs without having been planned, and it belongs in the plan. A new responsibility is that case announced in advance. The prioritising guide also draws on Harvard Business Review writing to argue that organisations fail less from making poor choices than from making none, until everything counts as a priority. Taking on a new area by default, because nobody stopped to decide, is that failure, and the cost lands on the plan for as long as the work stays.
This guide covers one area joining a team that carries on; joining two complete marketing teams after a deal is the tutorial on joining two marketing programmes after a merger. Money, including any budget line moved from the team that held the work, belongs with the budget holder under the organisation's rules, and the site's marketing finance section covers budgets. Any change to someone's job is for the people team under the organisation's own policy, supplier contracts are for whoever manages them with the organisation's legal advisers, and the craft of the new area is for the site's guides on that discipline. Nothing here is legal or HR advice.
Finding out what the work really involves
The request names the visible part of the work: "the catalogue", "the website", "the reviews". The hours can sit in parts nobody mentioned. Before forming a view, build an inventory with whoever does the work today. The tutorial on taking over marketing builds one for an entire inherited programme, starting from accounts and their owners, live spending and commitments, contracts and what the calendar already promises. The tutorial on handing over a departing marketer's work builds one for a single person, from recurring tasks and work in flight to admin rights, stray files and the judgement nobody wrote down. A new responsibility needs a version of both, scaled to one area, with the advantage that the previous owner is still in the business and can be asked. The questions below are general practice.
| What to find out | Ask | Why it matters |
|---|---|---|
| Recurring tasks | What runs, when, and roughly how long each round takes | The real size of the commitment |
| Work in flight | What is half done, and what dates have already been promised | The first thing that can fail in the move |
| Accounts, tools and access | Who administers each one and whose name it is in | Control has to move with the work |
| Suppliers and contracts | Who is paid for what, and when each arrangement renews | Terms stay with the contract's manager, but the team must know of them |
| Who relies on it | Who uses the output, and what they expect | They become marketing's requesters |
| Knowledge held by one person | What they check that is written nowhere | No document carries it across |
| How it is judged | Which measure the business uses to tell whether the area is working | It sets what marketing would be held to |
| Why the move is proposed | Which problem the business wants solved | A different fix might solve it without a move |
Use the current owner's own records for time, not a figure borrowed from elsewhere, and treat any estimate as rough until the team has done the work. Ask which KPIA metric tied directly to an objective. the business will read to judge the area, and who chose it; if nobody can say, report that before anything is agreed.
The last row deserves time. A request to take over the website may really be a complaint that updates are slow. If a clearer interface or an agreed turnaround would fix the problem where the work already sits, the move is not needed, and asking is how the manager finds out.
Testing it against the team's remit and objectives
This guide applies no general rule about which areas of work belong in a marketing team. Fit is tested against what the business has already written down for this team.
The remit. A remit says what a team is for, what it owns, and what it does not own and who owns that instead. The tutorial that writes a charter for marketing operations writes one for an operations function, and the same shape works for a marketing team: a purpose sentence, a list of what the team owns and a list of neighbouring areas with their owners. Read the new area against the purpose sentence; if the work serves something else entirely, it may belong elsewhere. If the team has no written remit, writing one is the first condition of any answer.
The objectives. Ask which of the year's or the quarter's objectives the area would serve. Where it serves none, accepting it either changes the objectives, a decision for whoever set them and one to make in the open, or sets the new work in competition with everything the team has promised.
The responsibility matrix. The guide to team models and how a marketing organisation is designed writes the team's interfaces with sales, product and finance into a responsibility matrix built around decisions rather than tasks. List the decisions the new area involves, such as what goes in it, who approves it, when it goes out and who answers complaints about it, and see who holds each one today. If the content of the work depends on knowledge another team holds and will keep holding, marketing would own the output without owning what makes it right. The same guide holds back from a restructure until the problem a new shape would solve can be stated, and that test applies here: say what the move fixes, and check whether a clearer interface would fix it without moving anything.
Capability. Whether anyone can do the work now, could learn it or needs outside help feeds the cost and the conditions below, not the question of fit.
What it would cost the plan
A new area is recurring work, and recurring work is easy to under-count. The tutorial on reviewing recurring marketing work points out that routines are subtracted from capacity before new work is scored, so nobody asks whether they still earn their share, and it adds each new routine to its register when it starts, with a stated purpose and the evidence that will show whether it works. Do that before the decision rather than after it: put each recurring task from the inventory on the register with its owner, its time and its purpose.
Then count capacity the way the prioritising guide does: the people available, less holidays, less the recurring work that never stops, less a buffer for the reactive work the team's own history shows will arrive. Check each skill separately as well as the overall total, since a new area may lean on one skill, design or writing or analysis, and leave one person overloaded while the team has room overall.
What does not fit has to come from somewhere. The opportunity cost framework judges a choice against the best alternative use of the same resource, and for a new piece of recurring work its comparison table names that alternative as the planned work pushed below the capacity line. Name it: which initiative would slow or stop, and which objective it was meant to move. "Taking on the events means the spring launch content moves to next quarter" is something leadership can weigh; "it will be tight" is not.
Count the move itself as well, since learning the work and moving accounts take hours before the routine settles. Any money the area brings, for a freelancer, a tool, a supplier contract or a hire, and any transfer of budget from the team that held the work, is for the budget holder to approve under the organisation's own rules.
Accept, decline, set conditions or share
With the inventory, the fit and the cost in hand, the decision has four possible answers. The table is general practice rather than a rule.
| Answer | Suits | What to settle | Watch for |
|---|---|---|---|
| Accept | The area fits the remit and an objective, and capacity exists or agreed work stops | One owner, the measure, a review date | Accepting without naming what it displaces |
| Accept with conditions | The area fits but the plan cannot absorb it as it stands | Each condition in writing: what stops, what help arrives, the previous owner's support | Conditions agreed aloud and then forgotten |
| Share | The substance depends on another team's knowledge, the presentation on marketing's | Which side holds which decisions | Two accountable roles for one decision |
| Decline | The area fits neither the remit nor the objectives, or another team is a better owner | The reason, what would change it, and a suggested owner | A refusal that leaves the work with nobody |
Conditions work best when they are specific. A named piece of recurring work pauses or stops, with the people who receive it told. A bounded or specialist part of the area is bought in: the comparison of in-house teams and agencies makes that choice one type of work at a time, crediting agencies with specialist depth and the ability to flex, and the in-house team with business knowledge and control of data and brand. Where the answer is a new role, the tutorial on writing a marketing business case treats a hire as an investment like any other, counting costs beyond pay, such as recruitment, onboarding and management time, and staging the commitment with points to review it; recruitment approval, pay and the terms of the job stay with the people team.
Sharing suits work whose substance and expression sit with different teams. The guide to employer brand basics shares one area between the people team and marketing, with one side owning the substance and the other its expression, and the roles written down. The same pattern can fit customer emails, where the service team knows what the answer must say and marketing knows how the brand says it. Sharing holds up only while each decision keeps one owner; a row with no accountable role is the gap the RACI framework warns about.
Declining is a recommendation, not a veto, since the remit is set by whoever owns it, which may be the leadership rather than the manager. Give the reason in terms of the remit and the objectives the business has already agreed, say what would change the answer, and suggest where the work would sit better. If leadership assigns the area anyway, the prioritising guide's point applies: when a senior person chooses their work over the plan, the trade-off becomes theirs and is visible, and the displaced work leaves the plan by decision rather than by neglect.
Writing down who owns what
An answer kept only in the memory of a meeting is easy to lose in the first busy month. Write it into the documents the team already uses, so anyone can find out who decides what without asking the manager.
Start with the decisions. The RACI matrix framework gives every row exactly one accountable role, and suggests columns for roles rather than named people, so that the grid outlasts any one holder of a role. Add rows for the new area's decisions, not its tasks: what goes into it, who signs it off, when it goes out, who answers when something is wrong. For a shared area, the matrix is where the split becomes real. Keep the previous owner's role consulted on the rows where their knowledge still matters.
Then update the remit: add the new area to what the team owns, and anything declined or left with another team to what it does not own, with its owner.
If the area brings requests, add them to the team's catalogue of request types. The tutorial on service levels for the requests marketing handles sets each service levelA published promise between teams, or with a supplier, about what each type of request needs and how quickly it will be handled, agreed rather than imposed. from the time the work really takes, agrees it with the people who request it and reviews the catalogue when the work changes; the previous owner's records are the starting point until the team has its own. Requests for the new area come through the same front door as everything else. The guide for a marketer who is the whole team makes the case for a single route for requests and a written record of the work that will be left undone, and anything paused to make room belongs on that list, where it can be seen.
Finally, give each inherited routine a written procedure with an owner. The tutorial on writing a marketing SOP turns one recurring task into a procedureThe written way of doing one recurring task: who owns it, what starts it, the steps in order, checks and exceptions, so anyone qualified gets the same result. anyone qualified can follow. Write the new area into someone's objectives as well, with the measure found during the inventory, so it competes for attention on equal terms with the rest of their work.
Taking the work over from its previous owner
Agree a start date and an order of work with the previous owner and their manager, including the time the previous owner will give to the move. Their own team still has its plan, and a handover squeezed around it risks missing things.
Move control first. Add a marketing administrator to every account, tool and supplier portal in the inventory, and only then remove the access the move makes unnecessary; the leaver handover tutorial uses the same order, since records and settings tied to one person can be stranded if access goes first. Payment details and integrations set up in someone's name belong to this step.
Then run each recurring task for real with the previous owner watching. A first round done together can find gaps a conversation misses, such as the approval nobody mentioned or the check made by habit. Ask what has gone wrong before and what they would warn a newcomer about, and fold the answers into the procedures.
Tell everyone who relies on the area who their contact is now, where requests go and what turnaround to expect, and introduce suppliers to the new owner by name. Any supplier contract moves under its own terms, settled by whoever manages it. If a person moves with the work, or a colleague's job shrinks because the work leaves them, that is for the people team under the organisation's policy. Close the takeover once each routine has completed a full round in marketing's hands with no rescue from the previous owner.
Reviewing the decision
Fix the review date when the decision is made, not when someone complains. The planning and prioritisation hub treats the quarter as the unit of commitment, so a quarterly planning session after the area has completed a full cycle of its work is a sensible point; for seasonal work, that means once each of its seasons has come round.
Read the review against what was written at the start: the measure the business judges the area by, compared with where it stood before the move; the hours the work really took against the estimate; whether each condition held; and whether the work that slipped mattered more than expected, or not at all.
The review has four honest outcomes: keep the arrangement, change the conditions, change the split between marketing and the other team, or hand the area back or on, which is a decision like the original one, written down, with the same inventory and handover run the other way. Whatever the outcome, keep the area's routines on the recurring work register, so they are reviewed with everything else.
A seed company is asked to take on its catalogue and customer emails (illustrative)
Crennomax Seeds weighs a catalogue and customer emails
Crennomax Seeds, an invented mail-order seed and plant company, had a marketing team of 4: a head of marketing, a content and email marketer, a digital marketer and a designer working 3 days a week. The managing director asked for 2 things to move into marketing: the printed catalogue, mailed twice a year and produced until then by the operations manager, and the 26 email templates the customer service team used to answer questions about orders, deliveries and plants that failed to thrive.
The head of marketing spent a week with both owners. The catalogue came to about 120 hours per edition, with a printer contract that renewed each autumn. The templates took the service team about 2 hours a week to keep current, but the edits came from what only the service agents knew: which delivery problems were recurring, what the refund policy currently allowed, which plants were struggling in a hot spell.
The team's written remit said marketing owned how the company spoke to customers before and after they bought, and one of the year's 3 objectives was repeat orders, which the catalogue served directly. The templates fitted the remit only for their tone. On the recurring work register, the catalogue's hours would have pushed a planned spring growing guide below the capacity line.
The head of marketing recommended, and the managing director agreed, accepting the catalogue on 2 conditions: a freelance designer for each edition's layout, approved by the managing director as budget holder, and the monthly trade newsletter to garden centres paused for the season, releasing about 10 hours a month. The templates were shared: marketing owned tone, brand and layout, the service team owned content and sending.
Seven rows went into the responsibility matrix, with the service team leader accountable for template content and the operations manager consulted on print dates. The service catalogue gained 2 request types: a catalogue product change at 5 working days until the copy deadline, and a template tone review at 2. The spring edition ran as a shadowed production, with the content and email marketer leading each stage while the operations manager watched, and the autumn edition ran without help.
At the review, held once both editions had run, they had taken 140 and 105 hours. Garden centre buyers had asked twice for the trade newsletter, so it returned in a shorter quarterly form. The repeat-order measure covered too few seasons to settle anything, so the catalogue stayed with marketing for another year, with the freelance designer kept and the quarterly newsletter in place of the pause, and the template split stayed as it was.
Common mistakes
- Treating it as one more request. A responsibility does not finish. Count it as recurring work and decide it as a change to what the team is for.
- Deciding before the inventory. The visible part of the work may be the smaller part. List everything with the current owner before answering.
- Arguing from what marketing should own. This guide applies no general rule about it. Test the area against this business's remit, objectives and responsibility matrix.
- Accepting without naming what it displaces. "We will fit it in" leaves something to slip unannounced. Name the work that falls below the capacity line.
- Conditions nobody wrote down. Help promised in a meeting can disappear once the work arrives. Write each condition into the decision.
- Two owners for one decision. A shared area needs its decisions split. Give every row one accountable role.
- Taking the work without the access and the knowledge. Ownership of accounts in someone else's name is ownership in name only. Move control first and shadow the work.
- No review date. A decision nobody revisits becomes permanent by default. Set the date when the answer is given.
