What organisation design is for
A marketing organisation exists to turn a plan into results through a group of people, and its design should be judged on that alone. The org chart is the visible artefact, but the design is really a set of decisions: which people share a manager and a backlog, who holds which decision, how work passes between groups and what each group is measured on. Get those right and the chart almost draws itself.
The central insight is that boundaries have a cost. Work inside a team moves through conversation; work across a team boundary moves through requests, meetings and negotiation. Every design therefore chooses which collaboration will be cheap. Management writing in the Harvard Business Review has long made the same point about organisations in general: structure follows the work you most need to coordinate, and no structure removes the need to coordinate everything else.
Design also decides where expertise accumulates and where accountability lands. A team that groups all the paid media people together builds deep paid media skill, and when results disappoint everyone knows which lead to ask. A team that spreads them across products builds marketers who understand customers, and the accountability for paid media standards becomes shared and therefore weaker. Neither is wrong. The design question is which of those trade-offs the business can afford at its current stage.
Finally, design sets the manager's own workload. A structure with unclear decision rights pushes every disagreement upwards, and the manager becomes the team's router. A structure with clear ownership lets most decisions happen where the knowledge sits, which leaves the manager free to plan, hire and deal with stakeholders. If you are spending most of your week arbitrating, the design is the first place to look.
The models
Most marketing teams are built from five patterns, often mixed.
| Model | Grouped around | Strengths | Weaknesses | Fits best when |
|---|---|---|---|---|
| Functional | Disciplines such as brand, content, product marketing, analytics | Clear career paths; strong craft standards | Slow cross-discipline work; distance from revenue | Brand-led businesses; early specialisation |
| Channel | Acquisition channels such as paid search, social, email, SEO | Deep channel skill; clear channel measures | Channel silos; credit disputes; slow integrated campaigns | Performance-led teams with a few dominant channels |
| Product or segment | Product lines, customer segments or regions | Close to customers and commercial owners | Duplicated skills; inconsistent brand and data | Distinct products or segments with their own targets |
| Pods | Outcomes, each pod holding most skills it needs | Fast delivery; clear ownership of results | Scarce specialists stretched; standards drift | Separable outcomes and enough people to staff several pods |
| Hub-and-spoke | A central hub plus market or business-unit teams | Shared brand, data and tooling with local execution | Tension over priorities and budget between hub and spokes | Multi-market or multi-business organisations |
Functional teams group by discipline. They are common where brand and content carry the strategy and where each craft needs its own standards. Their weakness is that a single campaign needs several functions to agree, and nobody below the head of marketing owns the result.
Channel teams are the default in performance marketing. Each channel has a lead and a clear KPIA metric tied directly to an objective., which makes management simple. The cost is siloed planning, with each channel optimising for its own numbers and arguing about attribution, and customer journeys that cross channels with nobody owning the whole.
Product or segment teams sit next to commercial owners. A marketer aligned to a product line learns the product and its buyers in depth. The cost is duplication: each product team ends up with its own half-specialist in paid media, and brand and data standards diverge unless something central holds them.
Pods are small cross-functional groups that own an outcome, such as acquisition for one product, retention for a segment or a stage of the FunnelModel of the customer journey stages.. Frameworks such as RACE are a useful way to cut outcomes by stage (reach, act, convert, engage) when product lines are not the natural division. Pods move fast because most decisions sit inside them. They struggle when every pod needs the same scarce specialist, which is why they usually sit alongside a small central team.
Hub-and-spoke is the pattern for multi-market teams. The hub owns brand, positioning, data, technology and shared capability; the spokes own execution and local insight. The design question is where each decision sits, and the operations comparison of centralised and decentralised marketing operations covers the process and systems side of that choice in detail.
In practice most teams are hybrids: pods for acquisition with a central brand and analytics team, or channel teams inside a regional spoke. Hybrids are fine as long as each person can say which group they belong to and who decides their priorities.
Responsibility matrices and interfaces with sales, product and finance
Any model works better with a responsibility matrix, and none works well without one. The usual form lists the recurring decisions and deliverables down the side and the roles across the top, and marks each cell as responsible (does the work), accountable (owns the outcome and signs off), consulted (gives input before) or informed (told after). The discipline that matters is one accountable role per row. Two accountable roles means none.
Write the matrix around decisions, not tasks. "Approve campaign creative", "set the paid media budget split", "change the lead scoring rules" and "decide the launch date" are the rows that cause arguments; "write the email" rarely is. Keep it short enough to read and revisit it whenever the structure or a key person changes. The RACI matrix framework covers the matrix as a tool in its own right: writing the rows, settling disputed cells and keeping it current. Where the team has an operations function, a marketing operations charter records which of these decisions it takes alone, which it recommends and which it is only consulted on. When the business asks marketing to take on a lasting area of work another team used to run, the guide to taking on a new responsibility tests the area against the team's remit and adds its decisions to the matrix before the work moves.
The interfaces that matter most sit outside marketing.
Sales. The handover of leads, the definition of a qualified lead, follow-up expectations and feedback on lead quality all need an owner on each side and a shared measure. The guide to sales and marketing alignment covers the agreement itself; the design point is that someone in marketing must own the interface rather than everyone half-owning it.
Product. Launch timing, positioning, pricing communication and customer research cross the line between product and marketing. Decide who owns positioning and who owns launch readiness, and give product a consulted role in campaigns that make claims about the product.
Finance. Budget allocation, phasing, forecasting and the measures used to judge ROIProfit relative to cost. need a named finance partner and a named marketing owner. Without them, budget conversations happen only at year end and in crises.
Spans of control and team size
A span of control is the number of people reporting to one manager. Too wide, and one-to-ones become status updates, development stops and the manager reviews work they do not have time to understand. Too narrow, and the team grows layers that slow decisions and create managers with too little to manage.
The right span depends on the work, not on a rule. Managers of experienced specialists doing similar work can carry a wider span, because the reports need less direction. Managers of junior staff, or of people doing very different work, need a narrower one. A manager who also carries a large personal workload, such as a player-coach running a channel, should have fewer reports still, and the guide to delegating marketing work shows how such a manager hands over parts of their own channel.
Watch for the symptoms rather than counting heads. If one-to-ones are regularly cancelled, if reports wait days for decisions, or if the manager cannot describe each person's development goals, the span is too wide. If managers have so few reports that they spend most of their time doing individual work and occasionally approving someone else's, the layers are too deep.
Team size has its own limit. Small teams coordinate by conversation; beyond a modest size, conversation stops scaling and the team needs either sub-teams with leads or a written planning rhythm. Splitting a team is usually better than letting it grow until nobody knows what anybody else is doing.
Choosing a model by stage and business model
Start from what the business needs to be fast at, then choose the model that makes that work cheap. Before any team exists, a small firm's first commercial hire depends on whether the founder is short of selling time or of good conversations, as the guide to marketing when the founder sells explains.
| Situation | Usually works | Watch out for |
|---|---|---|
| Early stage, small team | Generalists with clear scopes; agencies for depth | Judging one person on every channel |
| Performance-led, few channels | Channel teams with a shared planning rhythm | Channel silos and credit disputes |
| Several products with their own targets | Product-aligned pods with central brand and analytics | Duplicated specialists; diverging data |
| Brand-led or premium business | Functional teams with a strong brand lead | Distance from commercial results |
| Long B2B sales cycle | Segment or account-aligned pods with a sales interface owner | Lead handover owned by nobody |
| Several markets or business units | Hub-and-spoke | Hub and spokes fighting over budget |
Business model matters as much as stage. A subscription business lives on retention, so a design that owns only acquisition leaves the most valuable stage of the funnel without a home. A marketplace serves two sides with different needs and may need pods for each. A business selling through partners or retailers needs someone who owns trade and channel marketing, which a channel model built around digital media will miss. Where the chosen model relies on agencies for depth, the split of work between agency and in-house team belongs in the scope section of an agency request for proposal, so every agency prices the same division of responsibilities.
Restructuring without losing momentum
Restructures cost more than they appear to. Relationships, handovers, informal knowledge and a share of the team's attention all go during the change, and some of it does not come back. Restructure when you can name the problem the new shape solves; first check whether a clearer responsibility matrix or a better planning rhythm would solve it without moving anyone.
When a restructure is justified, a few habits reduce the damage. Design around the work and the decisions first, and fit people to roles second, so the design is not a negotiation between individuals. Talk to each affected person before the announcement, not after. Publish the new responsibility matrix with the new chart, so people know who decides what from the first day. Keep in-flight work with its current owners until it ships, rather than handing half-finished campaigns across. Review the design after a quarter, with a short list of measures agreed in advance, and adjust.
Tallow and Pine moves to hub-and-spoke
Tallow and Pine, an invented homeware brand selling in 5 countries, had a central team of 14 doing everything for every market. Local managers sent requests to the centre and waited, and campaigns took around 6 weeks to localise. The new head of marketing created a hub of 8 covering brand, content production, analytics and marketing technology, and placed 2 marketers in each of the 3 largest markets with their own budgets and targets. The smaller markets kept a shared regional marketer. A responsibility matrix of 18 decisions was published with the new chart. Localisation time fell to about 2 weeks, and the main new friction, disputes over budget split, was handled by a quarterly allocation meeting chaired by the head of marketing.
The people side of the change, from re-scoping roles to hiring into the new shape, is covered in hiring and developing marketers, and the team structure hub lists the common symptoms that point to a design problem.
Common mistakes
- Copying another company's chart. A structure that works for a business with different products, channels and stage will import its trade-offs without its reasons. Design from your own work.
- Designing around people. Building roles to suit current individuals produces a structure that breaks when they leave. Design roles first, then fit people.
- Two accountable owners. Shared accountability feels collaborative and produces decisions nobody makes. One accountable role per decision.
- Ignoring the interfaces. Most failures happen at the handover to sales, product or finance. Name an owner on each side.
- Restructuring to fix a planning problem. If priorities change weekly, a new chart will not help; a planning rhythm will.
- Letting spans drift. Teams grow one hire at a time until a manager has more reports than they can develop. Check spans whenever headcount changes.
