What Is the Role of a CPO? Responsibilities, Personas, and AI

“What is my role as CPO?” comes up in almost every conversation I have with product leaders. Sometimes it’s the first thing they ask. Sometimes it takes a few sessions before it surfaces. Sometimes it’s the same question but a different title: What’s my role as VP of Product? Or, what’s my role as the product leader? Either way, it’s rarely answered well. In this post, I break down the different personas CPOs commonly take on, and look at how AI is changing what the role asks of you.

Before I dive into the answer, Mathias explores the engineering side of this question in What’s my Role as the CTO? The Different CTO Personas on The Intentional Organization.

What does a chief product officer do?

A chief product officer (CPO) is responsible for connecting product strategy, the product organization, and business outcomes. The work changes with the company, but I see three enduring responsibilities:

1. The business value delivered through the product organization.
2. Setting the direction within the product organization.
3. Holding and maintaining the product culture.

These pillars stay the same wherever a CPO’s focus lies. On their own, though, they don’t tell you what to do on a Tuesday morning.

How is a CPO different from a VP of Product?

The titles CPO and VP of Product overlap, and the distinction depends on the company. As Marty Cagan notes in The VP Product Role, the head of product can carry several titles, including chief product officer. A VP of Product or even a Director of Product may already be the company’s most senior product leader.

Where both the CPO and VP roles exist, a useful way to clarify the split is by scope: a CPO may have responsibility across a broader product organization, while a VP may lead a particular product area and its teams. But the title doesn’t establish who has final authority over product strategy or investment choices, especially within a larger parent company. Both roles need strategy, judgment, and people leadership. The useful questions are: Which outcomes do you own? Which decisions are yours? And what does the leadership above you expect you to make possible?

Why the CPO role changes as a company grows

Most CPOs got here by being very good at product. They shaped roadmaps, wrote specs, ran discovery, and made the call when things were ambiguous. When the organization grows, that instinct is hard to put down. It’s the comfort zone, and the feedback loops are short. Staying close to every product decision feels like leadership, and for a while it is. Then the team grows, and the CPO becomes the bottleneck for decisions that should be made three levels down.

The alternative is rarely obvious. A CPO’s role has no single refined focus. It depends on what the business needs, what stage the company is at, and what the CPO wants to spend their energy on. All of that shifts, sometimes quarter to quarter.

I’ve experienced very different versions of product leadership myself. As founder and CEO of Reaction Commerce, I also wore the product executive hat. With a small team, my responsibilities stretched from execution and the roadmap to product vision. The Co-founder, Visionary, Strategist, Builder, and Business Owner personas were all part of the job, often in the same day. I had broad responsibility for deciding where we were going and helping us get there.

At Intuit Mailchimp, I held the CPO title and led a large organization driving hundreds of millions in revenue for millions of customers. The scale was much greater, but my scope of decision-making was narrower. We were part of Intuit, with several layers of leadership above me setting the broader product strategy. I had opinions and could advocate for a direction, but I wasn’t the person making those calls.

In that role, the People Manager, Technology Partner, and Process Designer personas took on more weight: leading a large organization, working across functions, and helping teams deliver within a direction set above me. The Strategist hat was constrained by where the decisions sat. That’s an important distinction when you’re trying to understand what a CPO actually does.

Company stage matters, but so do ownership, reporting structure, and decision rights. You can carry more responsibility for people, customers, and business results while having less authority over the product’s direction. Understanding your role means getting specific about both.

Below are the personas I’ve come across so far. Think of the list as a compass, not a prescription. It’s meant to help you orient yourself and avoid getting stuck in one persona because of outside expectations or what you think you should be doing. A CPO can carry several of these at once, but the more you pick, the less quality time each one gets. Everyone is constrained by the hours in a week.

What about the CPTO role?

It’s also worth naming the chief product and technology officer (CPTO) role. Combining product and technology leadership under one person can make decisions faster and clearer. It also concentrates a lot of authority and responsibility, which raises the need for accountability upward (to the CEO and the board) and clear expectations downward.

17 CPO personas: where to focus your time

Making these personas explicit is about choosing where to put your focus. Just as important, it clarifies where you aren’t putting it.

None of these is a permanent choice. Reassess regularly whether you’re still wearing the right hat for what the business and you need right now.

1. The Visionary

This CPO sets the long-term picture of where the product is going and why. They articulate the vision and the narrative that connects today’s roadmap to a future customers and the team can get excited about. They spend time with the question “what should we be building in three years?” so that others don’t have to guess.

2. The Product Craftsperson

Close to the work, this CPO cares deeply about the quality of the product itself. They review designs, use the product daily, give detailed feedback on specs, and hold a high bar for what ships. They shape the product at the level of detail, and they often raise the standard of the whole team.

3. The Builder

This CPO is hands-on again: sketching concepts, prototyping flows, designing screens, and increasingly building working versions of ideas themselves. Instead of describing what they want in a doc and waiting for interpretation, they show it. It’s the fastest way to test an idea, align a team around something tangible, and get real feedback early. Like the Coder in the CTO world, this persona is a comfort zone with instant gratification, so it needs a boundary. The goal is to explore and clarify, not to become the person everything waits on.

4. The Portfolio Manager

With multiple products, lines of business, or major bets in play, this CPO spends their time deciding where the investment goes. They balance new bets against core improvements, decide what to fund and what to sunset, and make trade-offs visible to the rest of the executive team.

5. The Customer Advocate

This CPO spends a lot of time with customers: sitting in on calls, running interviews, visiting sites, reading support tickets. They bring the customer’s voice into the executive room and into the product org, telling the stories behind the data and keeping the team honest about who they’re building for.

6. The Business Owner

When the product is the business, the CPO often owns outcomes tied to revenue, retention, pricing, and packaging. This persona lives in the numbers and works closely with finance and go-to-market to turn product investment into business results. They’re accountable for growth, not just delivery.

7. The Data-Driven Operator

This CPO builds the instrumentation, metrics, and rituals that tell the organization whether the product is working. They define what success looks like, set up the dashboards and review cadences, and push the team toward evidence over opinion.

8. The Design Champion

Where product and design are tightly linked, this CPO makes design a first-class voice in decisions. They advocate for craft, invest in design systems and research, and make sure experience quality isn’t traded away quietly under deadline pressure.

9. The People Manager

The people manager is responsible for the product organization: hiring and developing product managers, crafting roles and career paths, running regular one-on-ones and skip-levels, giving feedback, and keeping an eye on the health of the team. In a growing org, this persona gets more important by the quarter and is often the first one neglected.

10. The Process Designer

From planning cycles to prioritization frameworks, from discovery practices to launch reviews and decision rights, the process designer brings clarity on how product work gets done. It’s essential in any growing org, but easy to overdo. The goal is clarity, not ceremony.

11. The Technology Partner

This CPO works shoulder to shoulder with the CTO, bridging product intent and technical reality. They’re deeply involved in the trade-offs between scope, quality, and speed, and in making sure product and engineering pull in the same direction instead of pulling against each other.

12. The Go-to-Market Partner

Launches, positioning, pricing, enablement, and sales support all benefit from product leadership. This CPO works with marketing, sales, and customer success to make sure the story the company tells matches the product it ships, and that the field knows how to sell it.

13. The Futurist

Eyes on the horizon, but not to see what’s visible. The futurist explores what’s beyond it: emerging technology, shifting customer behavior, adjacent markets. They prototype and experiment their way toward the next, next version of the product, supported by a team that’s capable of running the current roadmap without them.

14. The Strategist

Strategy is a fuzzy topic, often involving broad gestures that may or may not help the business grow. The strategist works to set a course through uncertainty. They talk to analysts, peers, customers, and industry experts to understand where the market might go, and use what they learn to shape where the product organization steers over the next twelve to eighteen months.

15. The Company Ambassador

Conference talks, press, podcasts, analyst briefings, customer advisory boards: this persona keeps the company and its product visible. Goals may include hiring, fundraising, partnerships, or customer interest. It means a lot of time on the road and in meetings with people whose attention or contribution matters to the business.

16. The Co-founder

If you co-founded the company, there’s a whole slew of additional responsibilities waiting for you. Close relationships with co-founders, the board, and investors are key. So is picking up whatever remains when everything else is delegated, whether that’s an urgent hire, a customer escalation, or a last-minute presentation at an industry event.

17. The Board Communicator

Being an active participant in board conversations asks for a different set of skills: presenting product progress in highly condensed form, translating roadmap and trade-offs for non-product folks, and maintaining relationships with directors. The good news is that these skills help well beyond the boardroom, especially when working with other departments in a growing company.

Choosing which CPO hats to wear

That’s quite a list, isn’t it? The sheer variety of CPO hats shows how hard it is to define this role, let alone measure its contribution to the business.

I see the list as a compass: a framework for where a CPO’s focus can lie. I use a list like this with my clients to regularly assess where their focus is and where it should be. Some quarters one hat is more prominent than another, and that’s fine. Knowing that the role will keep changing makes it easier to adapt. It’s easier to accept wearing a particular hat when you know it’s temporary, and that in a few months you’ll get to put on a different one.

Making room for the work the business needs

In a recent coaching session, a product and design leader at an early-stage software company described spending twelve hours a week reviewing designs and building prototypes. Meanwhile, two product managers need more coaching, and the team is making its next investment decision with little recent customer input or research. The Builder and Product Craftsperson hats are crowding out the People Manager and Customer Advocate. She’s regularly pulled between detailed execution work and product strategy and leadership work.

One possible experiment would be to reduce those twelve hours to four for a month. The design lead on her team would own routine design reviews, and the PM leading each initiative would own prototype decisions within agreed goals and constraints. My client would stay involved where a decision changes the product direction or commits substantial resources. Of the eight hours freed, four could go to developing the product managers, including preparing for their annual reviews, and four to customer conversations and making sense of what they hear.

The point of this exercise is to see whether decisions move forward without waiting for her, whether the PMs get the support they need, and whether the next investment choice draws on better customer evidence. After a month, the product leader and team could review those signals and adjust. The choice is concrete: which work needs your attention now, and who needs room to own the rest?

How AI is changing the CPO role

The pillars haven’t changed, but the ground under them has. AI is moving through the CPO’s job in two different ways, and it helps to keep them apart.

The first is AI in the product: deciding where AI is core to what you offer, where it’s a feature, and where it doesn’t belong at all. The second is AI in the product organization: how your team researches, specs, prototypes, and ships, and what that does to roles, process, and pace. Most CPOs I talk to are dealing with both at once, often without having separated them.

Judgment becomes more valuable

When AI makes a product cheaper and faster to build, judgment becomes more valuable. If a working prototype takes hours instead of weeks, the question “should we build it?” deserves more of your attention. Taste, focus, and the willingness to say no matter more when there are fewer barriers to trying an idea. That puts more weight on the Visionary, Strategist, Customer Advocate, Product Craftsperson, and Builder personas.

A prototype still leaves plenty of work before a product is ready for customers: integration, security, reliability, accessibility, and ongoing maintenance. Those costs don’t disappear because the demo came together in an afternoon. The CPO and CTO still need to understand what it will take to operate and support the product, and whether the value justifies that investment.

CPOs are building again—and need clear boundaries

CPOs are building again. For years, the move into executive leadership meant stepping away from the tools. Not anymore. With AI, CPOs are designing, prototyping, and concepting themselves, often in the same afternoon an idea comes up. A rough, working prototype replaces the three-page brief, and a conversation about a clickable concept replaces a debate about abstractions. This is exciting, and I think it’s healthy: it keeps leaders close to the product and to what’s actually possible, and it makes ideas easier to share, test, and kill early.

I’ve written more about this shift in From Producer to Builder: My Journey as a Product Manager Through the Web. For a CPO, it brings a particular leadership challenge: how to contribute directly while preserving the team’s ownership.

It also changes the dynamic with the team. A prototype from the CPO carries weight. Designers, PMs, and engineers can read it as a direction, a decision, or a spec, even when it was meant as a question. So be explicit about what you’re bringing: “this is a sketch to provoke ideas” lands very differently from “this is what I want built.” Invite the team to rework it, throw it out, or take it somewhere better. Used well, hands-on concepting gives your team a richer starting point. Used carelessly, it quietly shuts down their ownership and creativity.

There’s the time question too. Building is fun and the feedback loop is immediate, which makes it easy to let the Builder hat crowd out the People Manager, Strategist, and Customer Advocate. Ask yourself regularly whether the building you’re doing is serving the product and the team, or just serving your comfort.

Product processes need shorter learning loops

Process built for slower cycles starts to creak. Quarterly planning, long spec reviews, and heavy handoffs were designed around the cost of building. As that cost drops, the Process Designer persona has real work to do: shorter learning loops, lighter-weight decisions, and clearer rules for what gets reviewed and what doesn’t. The risk is adding AI to old rituals and calling it transformation.

AI is bringing some personas back together

Product work has moved through a cycle of bundling, unbundling, and now rebundling. Early teams held many responsibilities in a few people. As companies grew, they separated those responsibilities into specialized roles. AI is making it possible to bring some of that work together again, a shift I explored in From Producer to Builder.

Think about the Customer Advocate, Builder, and Data-Driven Operator. One person might hear a customer problem, build something to test it, and examine the results. The personas are still useful, but the work can happen in one continuous learning loop, with fewer handoffs. The Visionary and Product Craftsperson can also work more closely together when a leader can make an abstract direction tangible.

This gives the CPO another organizational question to answer: which responsibilities benefit from being held together, and which need dedicated expertise or independent review? Generating a prototype doesn’t establish research rigor, sound design, or production readiness. Those disciplines still need care, even when fewer people participate in the work.

For the People Manager and Process Designer, this means reconsidering roles, development paths, and decision rights. Where could someone own more of a customer problem from discovery through learning? Where would that stretch them too far?

Rebundling can happen throughout the team. It doesn’t require the CPO to absorb every responsibility personally.

AI quality, trust, and economics become product responsibilities

New responsibilities are landing on the CPO’s desk. Quality in AI products is harder to define and measure: evaluation, reliability, trust, safety, and data and privacy decisions all become product questions. Inference costs can reshape margins, which pulls the Business Owner persona closer to pricing, packaging, and unit economics than it may have been before. And the Data-Driven Operator’s job expands from tracking usage to defining what “good” even means for a system whose outputs vary.

The CPO and CTO relationship gets tighter

The CPO and CTO relationship gets tighter. Many of these questions can’t be answered by product or engineering alone. Model choices, build versus buy, latency and cost trade-offs, and what’s feasible next quarter all sit on the line between the two. The Technology Partner persona becomes more central, and the CPTO conversation, whether formal or informal, gets harder to avoid.

Differentiation extends beyond features

Differentiation moves. When competitors can ship similar features quickly, features alone stop being a moat. Differentiation shifts toward things like proprietary data, deep workflow understanding, distribution, brand, and trust. That’s Strategist and Customer Advocate territory, and it’s where a CPO’s time is probably best spent.

More capability still requires focus

There’s also a trap here. AI makes it feel like you can do everything yourself: draft the strategy, build the prototype, analyze the data, write the board update. It’s tempting to put on more hats because you technically can. But the caveat from earlier still applies. The more personas you carry, the less quality time each one gets, and the faster you drift back into the work that’s most comfortable instead of the work the business needs from you.

Capability isn’t the same as focus.

Likewise, the Futurist hat can quietly become an obligation. With new models and tools appearing weekly, it’s easy to spend your energy tracking every announcement. Decide on purpose how much of your attention goes to exploring, and where the rest of your team can do that exploring for you.

Lead through hands-on experience

And lead by using it. A CPO who has never worked meaningfully with these tools themselves will struggle to make good calls about where they fit, what they can’t do, and how to set expectations with the board and the team. You don’t need to become an expert, but you do need enough hands-on experience to have an informed point of view.

When the business needs a different CPO than you want to be

What happens when the business needs something from you that doesn’t line up with what you want to do? Say you’d rather stay close to the craft, but the business needs you to build an org and manage people. Or you’d rather work on vision and strategy, but the business needs hands-on delivery. One option is to hire someone for the parts you don’t want to do. A strong head of product, a head of design, or a chief of staff can take on a lot.

AI adds a new wrinkle: the pace of change can make some CPOs feel the role is moving faster than they want to, or in a direction they didn’t sign up for. That’s a legitimate reaction, and worth taking seriously instead of pushing through.

There’s still a balance to be struck, though. If what you want is so far from what the business needs, or you’re holding on to a comfort zone you don’t want to leave, it may be a chance to ask whether this is still the right role. There’s no shame in stepping into something that gives you more of what you actually want to do, without the expectations that come with the CPO title and its three pillars.

This isn’t the most pleasant part of the conversation. But as a coach, I’m not here to avoid it. Sometimes I push my clients to look at a reality they’d rather not consider, because it’s painful to leave something behind. Stepping aside takes humility and growth, and sometimes the path that feels most painful is the one worth taking.

A practical CPO self-assessment

Try the RAD framework—Reflect, Assess, Do—from our book, The Intentional Organization: A Leadership and Management Guide, to assess where your time goes and what needs to change.

Reflect

Do you recognize yourself in any of these personas? If not, what other hats are you wearing? Which of them has AI made more important, or less?

Which personas are becoming more connected in your work, and where would combining responsibilities help your team learn faster?

Assess

Look back over the last two weeks of your calendar and estimate your average weekly hours in each persona. Include the work that doesn’t make it onto your calendar, too. Then write down how you want to spend that time over the next month.

Use this worksheet for the hats you’re wearing, and add any important ones currently getting no time:

Persona	Current hours/week	Desired hours/week	Next action
Builder	___	___	___
People Manager	___	___	___
Customer Advocate	___	___	___
Strategist	___	___	___
Other: ___	___	___	___

Assign each block of time to its main purpose so you don’t count the same hour twice. Keep the total realistic: any increase needs time freed elsewhere. Which responsibilities are taking more time than they need? Which are getting less than the business needs? Also note how much of your AI work concerns the product itself and how much concerns the way your team works.

Do

Go through each persona and ask whether it really matters for the next few months. If it does and you’re still wearing too many hats, which could you delegate? Which aren’t needed right now and could be set aside, even temporarily? Pick one place where you’ll use AI hands-on yourself this month, and one process in your product org you’ll rethink instead of just augment. If you’re building or prototyping yourself, how will you make clear to your team what’s an exploration and what’s a decision?

Choose one change to make this week. Agree with the person taking on the work about their decision rights, when to escalate, and what a useful check-in looks like. Put a review on the calendar for a month from now: did your time actually shift, and did it help?

If your calendar no longer reflects what the business needs from you, that’s something we can work through in product leadership coaching.