Writing a PMM Charter That Gets Executive Buy-In

I watched a PMM director spend her entire Q3 building sales one-pagers for a product team that had its own content writer. Nobody asked her to do it formally. Nobody told her to stop. It just started with one "quick favor" in Slack and turned into a standing expectation within three weeks. By the time she realized what had happened, the product team had her name next to "sales collateral" on their internal planning doc.

She didn't have a charter. She had a job description that said things like "drive go-to-market strategy" and "collaborate cross-functionally," which in practice meant she did whatever the loudest stakeholder needed that week.

I've seen this happen at almost every company where PMM operates without a written charter. The function absorbs work from every direction because nobody, including the PMMs themselves, has defined where the boundaries are. Product wants you running launches. Sales wants you building enablement decks. Marketing wants you writing blog posts. Customer success wants you on QBRs. And because PMM touches all of those functions, saying "that's not my job" feels wrong.

It is wrong, without a charter. Because without one, your job is whatever people think it is.

Most PMM charters read like job descriptions, and that's the problem

The first mistake I see PMM leaders make is writing a charter that's really just an expanded job description. It lists responsibilities, maybe some KPIs, and calls it a day. That document goes into a Google Drive folder and never gets referenced again.

A charter is not a list of things you do. It's a political document. It establishes authority, defines boundaries, and creates a shared understanding with leadership about what PMM will and won't do. The audience for the charter is your CMO, your VP of Product, your CRO, and anyone else who might walk over with a "quick ask" that becomes a quarter-long commitment.

The best charters I've read share a few traits. They're short, usually two to three pages. They use language that executives actually respond to, meaning business outcomes rather than marketing activities. And they answer the one question that every stakeholder secretly has: "What can I expect from PMM, and what should I stop expecting?"

Defining what you own, what you influence, and what you support

This is where most charters fall apart. They list responsibilities without clarifying the level of ownership. "Go-to-market strategy" appears on the charter, but does that mean PMM owns the GTM plan, or does PMM contribute positioning to a plan that product management owns? The difference matters enormously when launch day arrives and three teams are arguing about messaging.

I recommend a three-tier framework. Write down everything PMM touches and sort it into three columns.

PMM owns means your team has decision-making authority. You set the direction, you approve the output, you're accountable for the result. Competitive positioning, buyer personas, product messaging frameworks. These should be yours.

PMM influences means you provide strategic input that shapes the outcome, but another team makes the final call. Pricing strategy is a good example. PMM should bring competitive pricing intelligence and buyer willingness-to-pay data to the table, but finance or product ultimately sets the price. Launch timing is another. PMM can advocate based on market readiness, but product leadership decides the ship date.

PMM supports means you contribute when asked, but the work belongs to someone else. Individual sales deals. Event booth design. Customer case study interviews. You show up, you help, but you don't plan it, you don't project-manage it, and you don't carry the KPI.

The power of this framework is in the conversations it forces. When you sit down with your VP of Product and say "I think PMM should own competitive positioning but only influence pricing strategy," you'll learn fast whether you have alignment. Better to have that disagreement in a planning session than in the middle of a launch.

The RACI nobody groans at

I know, everyone rolls their eyes at RACI matrices. But a charter without some version of a responsibility map is just an essay. You need something concrete that people can reference when the inevitable "who's handling this?" question comes up.

The trick is to keep it focused on the ten to fifteen activities that cause the most confusion, not every possible task your team might touch. Here's what I've seen work well as charter language:

"Product Marketing is Responsible for developing and maintaining competitive positioning, win/loss analysis, and buyer persona research. Product Marketing is Consulted on pricing changes, product roadmap prioritization, and brand campaigns. Product Marketing is Informed of customer escalations, engineering architecture decisions, and legal/compliance changes affecting messaging."

Notice what's not in there. Individual content creation. One-off sales requests. Event logistics. Product documentation. Those are the tasks that creep into PMM's plate when boundaries aren't explicit. Your charter doesn't need to list everything you won't do, but the specificity of what you will do creates implicit boundaries.

One PMM leader I worked with added a line to her charter that I've borrowed ever since: "Requests outside this scope will be evaluated quarterly and require CMO approval to add to the PMM mandate." That single sentence gave her a polite, structural way to redirect scope creep. She wasn't saying no. She was saying "let's bring this to leadership and make a deliberate decision about whether this is the right use of this team."

Navigating the political landmines

Here's what nobody tells you about writing a charter: the document itself is the easy part. The politics of getting stakeholders to agree to it will test every relationship you have.

Product leadership usually wants PMM to be a launch execution machine. They want someone who will take the feature spec, turn it into messaging, build the sales deck, coordinate the blog post, and run the launch like a project manager. A charter that says "PMM owns positioning strategy but does not project-manage launches" will get pushback. Product directors have gotten used to having a PMM who handles the messy cross-functional coordination they don't want to do.

The conversation I recommend: "I can do more valuable strategic work for your launches if I'm not buried in project management. Let me own the positioning and messaging, and let's find a PMO resource or use your existing program manager for the coordination timeline." You're not taking something away. You're offering something better.

Sales leadership wants PMM to be an enablement factory. Battlecards, objection handling guides, competitive cheat sheets, one-pagers for every deal. And honestly, some of that is legitimately PMM work. The problem is volume and customization. When sales wants a custom deck for every enterprise prospect, that's not enablement. That's sales support, and it should be staffed and budgeted as sales support.

Charter language that works here: "PMM delivers enablement assets at the segment and persona level. Account-specific customization is the responsibility of sales, with PMM templates and frameworks available as starting points." This protects your team while still giving sales what they need to self-serve.

Marketing leadership wants PMM to fill content gaps. When the content team is behind on blog posts, guess who gets asked to write? When demand gen needs landing page copy, guess who becomes the "messaging expert" they pull in? A strong charter makes clear that PMM creates messaging frameworks and positioning documents that content and demand gen teams use as source material. PMM is not the backup copywriter.

Getting your executive sponsor

A charter without executive sponsorship is a wish list. You need someone at the VP level or above who will back this document when stakeholders push back. And they will push back.

The best sponsor is usually your CMO, but only if your CMO understands what PMM actually does. I've worked with CMOs who think product marketing is just "the marketing team that works with product." If that's your CMO's mental model, you'll need to educate before you can get sponsorship.

The pitch I've seen land consistently goes like this: "Right now, PMM is spread across fifteen different activities with no clear prioritization. That means we're doing a mediocre job at everything instead of an excellent job at the three things that move revenue. I want to write a charter that focuses this team on the highest-impact work and creates clear expectations with our stakeholders. I need your support to make it stick."

That framing works because it speaks in outcomes, not org chart politics. You're not asking for territory. You're asking for focus. Executives love focus because they associate it with efficiency, which they associate with results.

Bring data if you have it. Track two weeks of your team's time and categorize it by the own/influence/support framework. When you can show that 40% of your team's time goes to "support" work that doesn't ladder up to PMM KPIs, the case for a charter writes itself.

Using the charter to say no without burning bridges

The charter is a shield, but only if you wield it carefully. Pulling it out like a weapon every time someone makes a request will make you the person nobody wants to work with. The goal is to reference it as a shared agreement, not a personal boundary.

When a product manager asks you to project-manage a launch, the wrong response is "that's not in my charter." The right response is "I'd love to help make this launch successful. Based on the charter we agreed to with [executive sponsor], my team will own the positioning and messaging. Can you loop in your program manager for the cross-functional timeline? I'll make sure they have everything they need from the PMM side."

You're still being helpful. You're still being collaborative. You're just doing it within the boundaries everyone already agreed to.

The charter also gives you a framework for annual planning conversations. When leadership wants to add a new responsibility to PMM, you can point to the existing charter and say "happy to take this on. What should we deprioritize to make room, or are we adding headcount?" That forces a resource conversation instead of a silent scope expansion.

I've seen PMM teams that review their charter every six months with their executive sponsor. That rhythm keeps the document alive and gives you a natural moment to renegotiate if the business has changed. Maybe you launched a PLG motion and self-serve onboarding messaging is now critical. Maybe you lost a headcount and need to drop competitive coverage on a secondary market. The charter makes those conversations structured instead of reactive.

What good charter language looks like

I'll leave you with a few lines from charters that I've seen work in practice. These aren't templates to copy verbatim, but they show the tone and specificity that makes a charter useful instead of decorative.

"Product Marketing is accountable for maintaining competitive positioning across all products in the portfolio. This includes quarterly competitive landscape reviews, win/loss analysis with a minimum sample of 20 deals per quarter, and battlecard updates within 5 business days of significant competitive changes."

Specific. Measurable. No room for interpretation about what "competitive intelligence" means.

"Product Marketing participates in launch planning as the messaging and positioning authority. Launch project management, including cross-functional coordination, timeline ownership, and asset tracking, is owned by the PMO or product operations."

Clear delineation. PMM shows up with the strategic work. Someone else runs the Gantt chart.

"Requests for PMM resources outside the scope of this charter will be logged and reviewed in monthly leadership syncs. Approved additions will include corresponding scope reductions or headcount justification."

This is the line that saves you. It doesn't say no. It says "yes, through a process," which is the corporate equivalent of a polite boundary.

The charter is the floor, not the ceiling

One last thought. I've had PMMs tell me they worry that a charter will make them seem inflexible or territorial. That's a reasonable fear, but it misunderstands what a charter does.

A charter establishes the minimum scope of your function. It tells the organization "this is what you can always count on from PMM." It doesn't prevent you from going above and beyond when it matters. You can still help a rep prep for a critical deal. You can still jump in on a blog post when the team is slammed. You can still volunteer for a project that excites you.

The difference is that those become choices, not obligations. And when you choose to help, people appreciate it more because they know it comes from deliberate investment of your time, not a standing expectation.

PMM teams without charters end up exhausted, undervalued, and invisible. They do enormous amounts of work that gets attributed to other teams. They burn out trying to be everything to everyone. And when budget season comes, they can't articulate their value because their value is scattered across thirty different activities that no single stakeholder fully sees.

Write the charter. Get it signed. Use it. Your team deserves to do the work that only PMM can do, and your stakeholders deserve to know exactly what that work is.