Why operations needs a charter
Operations is the function most likely to be defined by accident. A newly appointed operations lead inherits whatever the team was struggling with on the day they started: the reporting pack, the tool nobody configured, the naming dispute, the approvals backlog, sometimes the office party. Within a few months, the role is a collection of favours, its real work is squeezed into the gaps, and nobody can say what it is for. Larger central teams have the same problem at a different scale, when two teams claim the same thing or nobody claims something important.
A charter prevents both. It sets the boundary of the function in writing, with the sponsor's agreement, so that requests outside it are redirected rather than absorbed. It names the things operations decides, so that those decisions stop being argued afresh each time. And it gives the teams operations serves a clear picture of what they can ask for, how, and what they should expect.
The marketing operations hub defines the function by its three disciplines and explains what it is not. The comparison of centralised and decentralised operations tabulates what a central hub owns and what its spokes own, and says that the model holds only when the split is written down. The charter is where it is written down, for the function itself. A whole marketing team can keep a remit in the same shape, and the guide to taking on a new responsibility tests any lasting area of work the business hands the team against that remit before it is accepted.
| Without a charter | With a charter |
|---|---|
| The role collects every orphaned task | Requests outside scope are redirected to their owner |
| Two teams claim the same area, or none does | Each area has one owner, named in writing |
| Decisions are reopened by whoever objects | Decisions operations takes are listed and agreed by the sponsor |
| Work arrives by any route | One intake route, the same as for other marketing work |
| The function is judged on impressions | It reports on a small set of operational measures |
| The scope drifts with each new manager | The charter is reviewed on a date and changed openly |
Before you start
- Read the operations pillar. Its section on what operations is and is not, and its account of the three disciplines, are the vocabulary the charter uses. Do not redraw the boundary with martech, analytics and automation from scratch.
- Know the operating model. If operations serves several teams, regions or brands, read the hub-and-spoke ownership table in the operating model comparison first; the charter's ownership list follows it.
- List the disputes. Collect the arguments of the past year about who owns what: naming, tags, tools, the asset library, approvals, reporting. Each one is a line the charter should settle.
- Find the sponsor. The person operations reports to, or who will defend the charter when it is tested. A charter without a sponsor is not worth writing.
- Know the RACI method. The RACI matrix framework explains how to assign one accountable role per decision; the decision-rights step uses it.
- Gather the current measures. Whatever the team already records about cycle time, rework and first-time pass at review, as the process hub describes them.
The steps
Write the purpose in a sentence the business would recognise
Start with one or two sentences saying why the function exists, in terms the people it serves would use. "We make it faster and safer for the marketing team to get work live, and make sure what goes out can be reported on and defended" says more than a list of activities. Avoid tool names and internal jargon. The purpose is the test every later section is checked against: if something operations is asked to own does not serve the purpose, it probably belongs elsewhere. Read the sentence to someone outside marketing; if they cannot tell what the function does, rewrite it.
List what operations owns, area by area
Write down each area operations owns, using the three disciplines as headings. Under process, that might be the design of the campaign workflow, its gates and the format of procedures. Under systems, the configuration of the work system, the asset library and the campaign taxonomy kept as the data operations guide describes, including the Naming ConventionAn agreed pattern for naming campaigns, ads, events and tracking parameters so that reports can group them reliably. and its enforcement. Under governance, the approval matrix and the access policy. Owning an area means being accountable for its design and its upkeep, not doing every task inside it. Where operations serves several teams, follow the hub's column of the ownership table in the operating model comparison.
Write down what it does not own and who does
This is the section that prevents most disputes, so give it as much care as the last. For each neighbouring area, name the owner. The design of the stack and which tools to buy sit with the martech function; the convention behind every UTMURL tags identifying traffic source. and the tracking plan sit with analytics, as naming conventions and UTMs sets out; automated workflows and their deputies sit with whoever the automation governance guide names. Then list the tasks operations is often asked to do but does not own, such as producing a particular report or running a channel, and say where those requests go. Operations still enforces the naming convention at intake; it does not own the convention.
Name the internal customers and the services each receives
List the teams and roles operations serves: channel teams, regional or brand teams, product marketing, sales, the leadership team. For each, write the services they receive in plain terms, such as intake and triage of requests, a new work type or template set up, an approval route agreed, access granted, an audit run. Keep each service to something a customer could ask for and recognise when it is delivered. This list becomes the basis of the service catalogue in the tutorial on setting service levels for marketing requests, so name services the way requesters would.
Set the decisions operations takes alone, recommends or is consulted on
List the decisions that touch operations and sort them into three groups. Some operations takes alone, such as changes to stages and fields in the work system or the format of procedures. Some it recommends and someone else decides, such as buying a new tool or changing who sits on the approval matrixA table that says which reviews each type of marketing work needs, such as legal, brand or budget, and who gives each, matched to the risk of the work.. On some it is only consulted, such as the campaign plan or the budget split. Write each decision as a row with one accountable role, following the RACI matrix. Start with the decisions from the list of past disputes; a charter that settles them has already earned its keep.
Describe how work reaches operations
Say how people ask operations for something. The route should be the same front door the rest of the team uses for marketing requests, as the campaign workflow describes, with operations requests as a work type of their own, not a separate inbox. Say how requests are triaged and who decides their order. Requests for operations to deliver campaign work go through the guide to prioritising work and capacity like any other; improvements operations chooses for itself go into its own backlog, ordered as the guide to prioritising marketing operations work describes.
Choose the measures operations reports on itself
Pick a small set of measures that show whether operations is doing its job. The process hub's cycle time by stage and rework by gate show whether work moves faster and comes back less. The governance hub's share of work passing its gates first time shows whether approvals are working. Adoption of the work system and completeness of the taxonomy show whether the systems are used. Report them as operational measures of the system, not as a KPIA metric tied directly to an objective. for individuals, and say where and to whom they are reported. Avoid vanity counts such as the number of procedures written, which reward activity rather than effect.
Agree the sponsor and the sign-off
Name the sponsor: the person who will back the charter when someone challenges it, and who resolves disputes the charter does not settle. Then take the draft to the leads of the teams operations serves, section by section, paying most attention to what operations owns and what it decides, because those limit what others may do on their own. Expect changes. Record who signed and when. A charter that only operations has agreed to will be treated as operations' opinion; one the sponsor and the customer teams have signed is an agreement.
Publish it beside the workflow and set a review date
Publish the charter where the workflow, procedures and request form live, so people find it at the moment they need it, and link it from the intake form. Tell the teams it serves what has changed in practice: which requests now go elsewhere, which decisions are now operations' to make. Set a date for the next review and name who calls it. Review it earlier when the organisation changes: a new team, a new market, a restructure, a new operations lead or a recurring dispute the charter failed to settle.
What a one-page charter contains
The charter is short by design. If it does not fit on a page or two, it is turning into a procedure manual, and the detail belongs in the procedures, the approval matrix and the service catalogue it points to.
| Section | What it says | Points to |
|---|---|---|
| Purpose | Why operations exists, in a sentence or two | The operations pillar |
| Owns | Areas operations is accountable for, by discipline | The workflow, data operations and approvals guides |
| Does not own | Neighbouring areas and their owners; tasks redirected elsewhere | Martech, analytics, automation |
| Customers and services | Who operations serves and what each can ask for | The service catalogue |
| Decision rights | Decisions taken, recommended or consulted on, one accountable role each | The RACI matrix |
| How to ask | The intake route and how requests are ordered | The campaign workflow and the prioritising guides |
| Measures | The operational measures operations reports on itself | The process and governance hubs |
| Sponsor and sign-off | Who sponsors it and who agreed it, with dates | |
| Review | When it is next reviewed and what triggers an earlier review |
A home-improvement retailer charters its operations team (illustrative)
Dornefax Home Supplies writes its operations charter
Dornefax Home Supplies, an invented home-improvement retailer with 38 stores and an online shop, appointed its first marketing operations lead from within its digital team of 12. In her first month she was asked to fix the weekly trading report, set up a new email tool, resolve a dispute about tag changes and organise the summer staff event.
She also found 2 disputes the business had been living with. The ecommerce team and the store marketing team both believed they owned the campaign taxonomy, and each had its own naming rules. Nobody believed they owned the asset library, so 3 versions of the spring brochure imagery were in circulation, one with the previous year's prices.
She drafted a one-page charter over 2 weeks. The purpose read: "We make it faster and safer to get marketing live across stores and online, and make sure what goes out can be traced and reported." Under "owns" she listed the campaign workflow, the work system, the campaign taxonomy and the asset library. Under "does not own" she listed the tag container and tracking plan (analytics), tool purchases (the digital director, with operations recommending), the weekly trading report (the trading team) and staff events (HR). She named 4 internal customers with 9 services between them, and wrote 7 decisions as a RACI, each with one accountable role.
The head of marketing sponsored it and the ecommerce, store marketing and analytics leads signed it after one round of changes, mostly to the decisions table. The first test came a fortnight later, when a store marketing manager asked operations to change a tag in the container; the charter pointed the request to analytics, and the request went there without argument. The review was set for 6 months later.
Common mistakes
- A charter that lists activities, not purpose. Without a purpose, nothing tells you whether a new request belongs to operations.
- Leaving out what operations does not own. The "does not own" section prevents more disputes than any other. Write it as carefully as the ownership list.
- Redrawing the boundary with martech, analytics and automation. Link the pillar and those roots; the charter names the owner, it does not redefine the discipline.
- Two accountable roles for one decision. That means none. One accountable role per decision, as the RACI requires.
- A separate inbox for operations requests. Use the same front door as the rest of marketing, with operations work as its own type.
- Measuring operations by its output. Counts of procedures or dashboards reward activity. Report cycle time, rework and first-time pass.
- No sponsor. A charter nobody senior will defend is ignored the first time it is inconvenient.
- Writing it once. Organisations change. Review the charter on a date and whenever a dispute it should have settled recurs; the governance hub explains how the operating model and the other components it sits beside change too.
