Product marketing charter

What product marketing owns here, and what it doesn't

A working charter for the function. Fill the bracketed parts per company, then present it to leadership before anyone else sees it.

The point of this documentA charter is how you sell the function to leadership. Here's the problem, here's what this function will do about it, here's what it needs from you, and here's how you'll know it worked. If it never gets invoked to route a piece of work, it doesn't exist.

Context

[What stage this company is at. What the go-to-market motion is. What the business is betting on this year, and therefore what product marketing has to prioritise, and what it is deliberately not doing.] Today this work happens bottom-up, initiative by initiative, with each team building its own version. This function exists to make the strategy legible, consistent and measurable across every product, segment and market.

Purpose

Product marketing turns [the company strategy] into one coherent customer story: the same story from every team, so that every customer, in every market, understands what we're building, why it matters to them, and what to do next.

Ownership, in three tiers

Owning less is easier to defend.

What we own

Three to five things. Not more. These are the things that fail if we don't do them.

The narrative and messaging architecture: the single story every customer-facing team draws from, adapted per segment and market.
Positioning: who the product is for, what it replaces, and why it wins against the alternative they're actually considering.
The go-to-market framework: how launches happen: tiering, sequencing, channels, enablement and the post-launch read.
Competitive intelligence: what's true about the market, kept current, and put in the hands of the people in the room.
GTM measurement: defining what a successful launch looks like before it ships, and reading it afterwards.

What we drive with partners

We decide the approach. Another team owns execution or the final call.

Area

We own

They own

Sales enablement

The story and the materials.

Sales owns the conversation and the number.

Lifecycle and customer comms

The strategy, segmentation and message.

Lifecycle owns the sends and the infrastructure.

Pricing and packaging communication

How a change lands and how customers are brought along.

Finance and Product own the economics.

Customer research

The questions and the synthesis.

Research and Design own method and rigour.

What we input into but do not own

Name the owner for each one.

The product roadmap: Product decides what gets built. We bring customer evidence and commercial context.
Revenue execution: Sales owns selling. We own making selling easier.
Paid, brand and creative production: we set the message and the audience. Those teams own channel execution and craft.
Company strategy: leadership decides. We bring the customer's reality into the room.

First initiatives

Three to five named projects, pre-agreed with leadership, with rough horizons.

The positioning and messaging architecture, written, tested with customers, and adopted by Sales and Product. [Horizon]
A launch tiering system with written criteria, agreed jointly with Product. [Horizon]
Competitive intelligence stood up: which competitors, what's tracked, where it lives, how often it's refreshed. [Horizon]
One live launch run end-to-end on the new framework, with a published post-launch read. [Horizon]
Segmentation operationalised in customer comms: differentiated streams, not one list. [Horizon]

How we measure

Accountable for

Comprehension of what we ship: do customers and internal teams understand what changed and why.
Win rate against named competitors in contested deals.
Every launch shipping with a defined success metric and a post-launch read.

Influence, and will describe honestly

Pipeline quality and conversion through the middle of the funnel.
Activation and expansion into higher-value pathways.
Retention in the segments our story is aimed at.

Track to run the function

Content and enablement adoption, comms reach and engagement by segment, research cadence. Useful internally, never presented as success.

Attribution statementWe will not claim sole credit for revenue or retention. Too many things move those numbers. What we will do is state our contribution and show the mechanism by which we believe it moved.

When to come to us, and when not to

Come to us when

You're shipping something customers will notice, before it's built, not the week before launch.
You need to know how a change should be explained, to which customers, in what order.
You're losing deals to a competitor and can't articulate why.
You're hearing something from customers and don't know where it should go.
You're planning a customer-facing campaign or programme and want it consistent with everything else they're hearing.

Not us

You need copy written or a deck designed. That's a craft resource, and we'll help you find the right one.
You need a one-off send to a list. Lifecycle owns that. We own whether the strategy behind it is right.
You want research run on a question we've already answered. Ask us for the existing answer first.

Operating principles

Alignment is a deliverable. If teams leave a launch telling different stories, that is our failure.

Sales owns selling. Product marketing owns making selling easier. The same construction holds for Product, Support and Design: they own the craft, we own the shared story underneath it.

Customer truth beats internal opinion. Whoever has spoken to customers most recently wins the argument, and we make sure that's a documented answer.

Every team gets a story they don't have to invent. Teams can still write their own message. They never have to start from a blank page.

Nothing ships without a definition of success. Agreed before launch, read after, written down either way.

The boundary conversation

This charter will occasionally be used to decline work. When that happens it is not a statement about willingness. It's a statement about ownership. The right response to “that isn't ours” is never a shrug. It's a name. We will always tell you who does own it, and where the request should go instead. If the answer is nobody, that's a gap worth raising rather than quietly absorbing.

How to put it to work

The document is maybe forty per cent of the value. The rest is the process around it, and this is where most charters die.

Leadership first, always. Present it to your manager and the relevant execs before anyone else sees it, and treat that conversation as a pitch, including the uncomfortable parts about what isn't working today. A charter without leadership backing has no force when you use it to decline something.

Then company-wide, then departmental. The company-wide version sets the frame. The departmental sessions are where you use examples specific to that team, which is what makes it stick.

Re-present it to every new hire in an adjacent function. This is the highest-leverage reuse: new joiners form their model of what product marketing is in their first month, and if you're not in that model you'll spend a year correcting it.

Revisit roughly twice a year, or at planning. Either confirm it stands or state what's changing and why.

Actually reference it when declining work. A charter you don't invoke is a charter that doesn't exist. The first time you use it to route a request elsewhere is the moment it becomes real, and it should be a conversation about ownership, not willingness.