A Different Kind of Chapter
This chapter is different from the others, and we want to be transparent about why. For most of this book, we've been writing as practitioners—PMM leaders talking to PMMs about how to do the job better. This chapter leans more heavily on the executive view, because the questions it addresses—how to structure a team, who to hire, how to manage performance—are fundamentally organizational questions.
The Org Chart Question
Here's a thought experiment that captures the organizational tension perfectly. In late 2025, we were looking at our org chart—fifty-three people across product marketing, competitive intelligence, pricing and commercialization, and research—and running a thought experiment that every CMO is quietly running:
If I were building this team from scratch today, with full access to agentic tools, would it look like this?
The honest answer was no. Not because the people were wrong—the team was strong—but because the structure was optimized for a pre-agentic operating model.
The team was organized by function: a competitive intelligence group, a content and messaging group, a technical marketing group, a pricing and commercialization group. Each function produced its own deliverables, maintained its own tools, and operated on its own cadence. The structure made sense when the bottleneck was execution.
In the agentic model, the bottleneck shifts from execution to strategy. The competitive battlecard and the pricing analysis are both produced by agents drawing from a shared knowledge base. The human work—the judgment about what the competitive landscape means for pricing, or what the pricing shift means for competitive positioning—cuts across functional boundaries.
From Role-Based to Outcome-Based
The organizational shift we're implementing at SAP—and that we think is directionally correct for most PMM teams—is from role-based teams to outcome-based teams.
📦 Role-Based Structure
Teams organized around what they produce:
- Competitive team → competitive content
- Content team → marketing content
- Enablement team → sales tools
Advantage: Clarity of scope and expertise
Problem: Strategic synthesis falls between teams
🎯 Outcome-Based Structure
Teams organized around what they achieve:
- Pipeline generation for a product line
- Competitive win rate for a segment
- Analyst perception for the portfolio
Advantage: Strategic coherence across activities
Benefit: Full spectrum of capabilities per team
In the outcome-based model, each team has the full spectrum of PMM capabilities—competitive, content, enablement, pricing—and the agent stack to execute across all of them. The team doesn't produce battlecards and positioning documents as separate deliverables; it produces a coherent go-to-market narrative that manifests as battlecards, positioning, sales enablement, and content simultaneously.
This isn't just an org design preference. It's a response to the reality that agentic tools make cross-functional execution possible for small teams in a way that it wasn't before. A team of three PMMs with a coherent agent stack can cover competitive intelligence, positioning, enablement, and content for a product line—work that previously required six to eight specialized roles.
The Full-Stack PMM
The individual contributor who thrives in the outcome-based model is what we've been calling the full-stack PMM—someone who combines strategic depth, agent orchestration capability, and execution judgment across the full scope of PMM activities.
This is a different profile from the specialist PMM who has historically been the ideal hire. The specialist—the competitive intelligence expert, the pricing analyst, the content strategist—was valuable because their deep expertise in one area produced higher-quality deliverables than a generalist could.
In the agentic era, the agent handles much of the specialized execution. The human's value comes from connecting insights across domains. The PMM who can see the thread from a competitive pricing shift to a positioning opportunity to a sales enablement need to an analyst briefing talking point—and who can direct agents to execute across all four—is more valuable than four specialists each seeing their piece of the picture.
We don't want to overclaim here. There are still roles where deep specialization matters—particularly in pricing and commercialization, where the analytical complexity requires genuine expertise, and in analyst relations, where relationship depth takes years to build. But for the majority of PMM roles—the people who own a product line's go-to-market—the full-stack profile is where the market is heading.
Hiring for the Agentic Era
If you're hiring PMMs—or if you're a PMM thinking about how to position yourself in the market—here's what the evaluation criteria look like:
Systems thinking > Deliverable experience
The question isn't "have you produced a competitive battlecard?" It's "have you designed a competitive intelligence workflow?" PMMs who think in systems—inputs, processes, outputs, feedback loops—will navigate the agentic era better.
Intellectual curiosity > Tool proficiency
The tools are going to change. What endures is the disposition to experiment, to learn new tools quickly, to build workflows iteratively, and to be honest about what's working and what isn't.
Communication range > Communication polish
The agentic era PMM needs to communicate with engineers about data architecture, sales reps about deals, analysts about evaluation, executives about performance, and agents about tasks. Code-switching across audiences is more valuable than flawless copywriting.
Adaptability > Pedigree
The best predictor of success isn't Pragmatic certification or ten years of experience. It's whether they've demonstrated the ability to adapt when the rules changed. The pattern of adaptation is what you're hiring for.
The Performance Measurement Problem
One of the hardest management challenges in the agentic era is measuring PMM performance when the traditional output metrics—number of battlecards produced, content pieces published, launches executed—become meaningless. If an agent produces the battlecard, what did the PMM contribute?
The answer is to shift from output metrics to impact metrics. Output metrics measure what was produced. Impact metrics measure what changed as a result:
- Did the competitive win rate improve?
- Did the sales cycle shorten?
- Did the analyst move us up in the evaluation?
- Did the pricing change increase deal size?
- Did the launch shift the market narrative?
Practical Impact Metrics by Role
| PMM Role | Impact Metrics |
|---|---|
| Competitive PMM | Win rate in competitive deals; time-from-signal-to-sales-response |
| Launch PMM | Pipeline generated from launch activities; analyst sentiment shift |
| Pricing PMM | Deal size growth; pricing-related win/loss trends |
These are imperfect metrics—influenced by factors beyond the PMM's control—but they point the team toward the right kind of work, which is the point of measurement. In the agentic era, where artifact production is cheap, strategic value is the only defensible basis for headcount.
Decisions That Will Shape the Next Five Years
The organizational questions this chapter raises are the ones that should keep every CMO productively restless—because the team structure decisions made in the next twelve months will determine organizational effectiveness for the next five years.
What we're seeing work: Moving from a purely functional structure to a hybrid that maintains centers of excellence for deep specialization (pricing, analyst relations) while reorganizing the rest around product-line outcomes. Each product line gets a small team of two to four PMMs who own the full go-to-market, supported by shared CoEs and the agent infrastructure the team builds.
On headcount: We are not using agentic tools to cut staff. We're using them to reallocate time from low-value execution to high-value strategy. Output quality went up. Strategic impact went up. And the ability to justify investment went up.
On hiring:
- Include a "work with AI" exercise
- Deprioritize portfolio reviews in favor of strategic decision stories
- Make customer interaction experience a hard requirement
The framing that captures it: we're hiring architects, not builders. Agents handle the building. We need people who understand the full system.
🏗️ Key Takeaways
- Hybrid team structures—centers of excellence for deep specialization plus product-line outcome teams—are emerging as the model
- Agentic tools should reallocate time from execution to strategy, not reduce headcount
- New hiring signals: "work with AI" exercises, strategic decision narratives over portfolio reviews, and mandatory customer experience
- The organizing metaphor: hire architects who understand the full system, not builders. Agents handle the building.
Test Your Knowledge
Ready to check your understanding of team structure and hiring?
Take the Chapter 13 Quiz →