What team structure decides
Structure is a set of answers to a few practical questions. Who decides what goes live? Who owns each stage of the FunnelModel of the customer journey stages., and who owns the handover between stages? Which people share a manager, a backlog and a KPIA metric tied directly to an objective., and which have to negotiate with each other to get anything done? When a campaign underperforms, whose problem is it? An org chart is only the visible part of those answers; the rest sits in responsibility matrices, planning rituals and the informal habits that grow up around them.
The reason structure matters is that it sets the default path for work. Work flows easily inside a team and slowly across team boundaries, so wherever you draw the boundaries, you are choosing which collaboration will be cheap and which will be expensive. A channel-based team makes paid search fast and the cross-channel launch slow. A product-aligned team makes the launch fast and the shared brand standard harder to hold. No model removes the trade-off; a good structure puts the cheap collaboration where the business needs speed most.
Structure also decides where expertise accumulates. A team organised by channel builds deep specialists; one organised by product or audience builds generalists who know their customers well. Both are valuable, and the choice should follow what the business is short of. The Chartered Institute of Marketing's view of professional competence draws the same line between technical skill and the commercial judgement to direct it, and a structure needs room for both.
Models, roles, hiring, development
The four parts of team management connect: the model decides which roles exist, the roles decide whom you hire, and development decides whether the people grow into the structure or out of it.
| Area | The question it answers | Typical outputs | Where to read more |
|---|---|---|---|
| Models | How is the team grouped, and around what? | An org design, a responsibility matrix, defined interfaces | Team models and organisation design |
| Roles | What does each person own and decide? | Role scopes, decision rights, measures per role | Marketing roles from the holder's side |
| Hiring | How do we find and choose the right person? | A scoped role, an assessment task, an interview plan | Hiring and developing marketers |
| Development | How do people grow, and how do we know? | One-to-ones, a skills matrix, development plans | Hiring and developing marketers |
The core guides
Marketing team models and organisation design compares the functional, channel, product and pod models, explains hub-and-spoke for teams serving several markets, and shows how to write a responsibility matrix that makes the interfaces with sales, product and finance explicit. It also covers spans of control, choosing a model by stage and business model, and how to restructure without stalling the work.
Hiring, onboarding and developing marketers covers the manager's side of people: scoping a role before writing the advert, assessing candidates with realistic tasks, onboarding properly, running one-to-ones and feedback that help, and building skills matrices and development plans. The person applying for or holding the role has their own guidance in the marketing careers roles section, and the wider job of running marketing sits in the marketing management hub.
Further guides
Further guides cover the habits that turn a structure into a working team: handing work over, giving each person their share of the plan, reviewing how the team works together, keeping the work moving while a role is empty, passing the team itself to the next manager and managing specialists whose craft the manager does not share:
- Delegating marketing work as a manager — what to hand over, outcomes with clear authority and limits, check-ins matched to experience, and not taking work back.
- Setting objectives for each marketer from the team plan — a tutorial for outcomes each person can influence, measures with baselines, shared results, development goals and reviews.
- Running a marketing team retrospective — a tutorial for evidence from the period, what helped and what got in the way, causes, a few changes and follow-up.
- Covering an empty role in a marketing team — a tutorial for deciding what stops, pauses, is covered, is bought in or waits while a role is empty, changing the plan openly, re-scoping the role and handing the work to the new starter.
- Handing a marketing team to the next manager — a tutorial for the outgoing manager: what was agreed with each report, the plan and the promises made around it, the dates in each agency agreement, what leadership and other teams were told, who decides what from the last day and a check after the leaving date.
- Managing marketing specialists whose work you cannot do — judging outcomes and reasoning, borrowing a written standard, getting an independent view, setting authority by reversibility and hiring and developing a specialist.
Structure by company stage
Structure should change as the team grows, and the most common failure is keeping a shape that suited an earlier stage.
A single marketer or a very small team. Structure is mostly about scope: what this person owns, what goes to agencies or freelancers, and what is simply not done. The danger is a generalist being judged on every channel at once. Agree a short list of priorities and a clear line on what is out of scope.
A small team with a manager. Roles start to specialise, usually by channel or by skill (content, paid, lifecycle). The manager's job shifts from doing to arbitrating, and a weekly planning rhythm becomes necessary. The common gap at this stage is ownership of measurement and of the handover to sales.
A larger team with several leads. Leads manage sub-teams, and the choice between channel, product or pod models becomes real. Interfaces need writing down, because people no longer overhear each other. Operations and analytics usually become distinct roles here.
A multi-market or multi-business organisation. The question becomes what is central and what is local. Hub-and-spoke designs keep brand, data and shared capability central and push execution to the markets. The balance between them is covered in the organisation design guide.
At every stage, the test is the same: can each person say what they own, which measure shows whether they are succeeding, and whom they must agree with before shipping? If not, the structure needs attention before the headcount does. Linking each role to a measure that rolls up to commercial outcomes such as ROIProfit relative to cost. keeps the structure honest.
Fennick Software outgrows its channel team
Fennick Software, an invented business software company, had a marketing team of 9 organised by channel: paid, content, email and events, each with its own lead. When the company added a second product, every launch needed 4 leads to agree a plan, and the average time from brief to launch stretched from 3 weeks to 7. The head of marketing moved to 2 product pods, each with a marketer covering paid and email and a shared content specialist, while brand and analytics stayed central. Launch time returned to about 4 weeks within two quarters, and the paid lead's role became a centre-of-excellence role setting standards across both pods.
Common team problems
| Symptom | Likely cause | Where to start |
|---|---|---|
| Work stalls at handovers between channels or with sales | Interfaces never defined; nobody owns the handover | Team models and organisation design |
| Two people think they own the same decision | No responsibility matrix, or one nobody uses | Team models and organisation design |
| The manager reviews everything and is the bottleneck | Span of control too wide or decision rights unclear | Team models and organisation design, Delegating marketing work |
| The manager cannot tell whether a specialist's work is good | Work judged on a method the manager cannot check rather than on outcomes, reasoning and an outside view | Managing specialists whose work you cannot do |
| New hires take months to contribute | Role poorly scoped or onboarding left to chance | Hiring and developing marketers |
| Work slips or quietly stops after someone leaves | Nobody decided what stops, what is covered and what is bought in while the role is empty | Covering an empty role, Handing over work when someone leaves |
| A manager is leaving and what they agreed, planned and promised is only in their head | Only the leaver's own tasks were handed over; nobody recorded what the manager holds or who decides it next | Handing a marketing team to the next manager |
| Good people leave citing lack of growth | No development plans or skills conversations | Hiring and developing marketers |
| Hires look strong at interview and struggle in the job | Assessment tested talk rather than work | Hiring and developing marketers |
