Canva Merged Its Product Org. Finish the Job: Put the Whole Loop Under the CPO.

Melanie Perkins sent a memo on Tuesday that names the real AI-era problem in a product company, and it isn't speed.

Canva is merging its product, growth, and platform teams into one Product Org, in a restructuring she says touches about 22% of the company, roughly 1,271 people. Her diagnosis, as Simon Thomsen reports it at Startup Daily: "Over time, we've divided work across more and more subspecialties and teams." That "fragmented ownership" and left "different teams responsible for many pieces of the same work." Simon Sharwood at The Register has the rest of the plan in her words: "simplifying layers, consolidating overlapping responsibilities."

That's the best one-line description I've read of what AI does to a product org. Every seat gets faster. The handoffs between them don't.

Canva fixed part of it. Product, growth, and platform now sit under one roof. Neither report says where design, product marketing, or the field land. And those are the stages where the outcome actually gets decided.

This is part 6 of The CPO Transition. Part 1 said the CPO stops owning the roadmap and starts owning the operating model, and parts 2 through 5 worked through the CEO, the CTO, the org shape, and the margin. From here the series argues the next step. The CPO owns the whole product outcome, and the org reports that way.

The short version

Canva merged product, growth, and platform into one Product Org because, in Perkins's words, fragmented ownership left different teams responsible for pieces of the same work. That's the AI-era failure mode. When a working prototype costs a day, the outcome is decided by the loop from customer signal to spec to build to story to adoption, and each handoff between reporting lines is now slower than the build itself. So finish the job: product management, design, product marketing, and forward deployed engineering report to the CPO. Brand, revenue, platform reliability, and finance stay where they are. The test is simple: for each outcome the board cares about, one executive's name should own all five stages. That's also why the CPO becomes one of the most influential seats in the company. Not because it collects headcount, but because it's the only seat that holds the whole outcome and answers for one number.

Four seats got faster this week. The loop didn't.

Look at what the other three series found in the last ten days, side by side.

The field. Scott Russell told NICE's Q3 call that the company has "fully staffed our FDE team," and described it as a shift in go-to-market. The number attached was engagements. Part 15 of The FDE Transition noticed what wasn't attached: anything the field put back into the product.

The story. Kristen Bryant Smith's survey for Appcues found 75% of marketers say their product ships faster than last year, and 7% say their launch process keeps up. The Product Marketing Transition(coming Nov 11) took that apart.

The spec. Jayesh Govindarajan, who runs Salesforce's roughly 700-person Agentforce org, told Aakash Gupta on Product Growth that he hires AI PMs for prototyping and evals. Field feedback reaches those PMs through a Slack channel with two tags, as Gupta reports it.

The quality bar. The Design Transition argued design should own the repair rate, how often users re-ask the AI, because nothing else in the stack measures whether the output landed.

Each one is a seat that sped up and a handoff that didn't. The FDE's finding goes to a sales scorecard. The ship goes out faster than the story can follow. The field's signal lands in a channel and waits for a PM to match it. The repair rate often has no reporting line at all. Four seats, four scorecards, one outcome nobody owns.

That's Perkins's sentence again, at the scale of the whole loop.

Why the CPO, and not the CEO, the CRO, or the CTO

Every step of the loop is a decision about what the product should become for every customer. Which deployment pattern turns into a feature. What the spec says good looks like. Which claim the docs and the assistants repeat. Whether the onboarding an agent runs gets the customer to the outcome.

The CEO owns all of it in theory and can't run it weekly. The CRO's scorecard is bookings, and it should stay that way; a revenue org that also owns the product loop ends up building what closed last quarter. The CTO owns the substrate the loop runs on, which part 3 argued is the first thing to get right and a different job. The CPO is the only seat whose job is deciding what gets built for everyone.

So product management, design, product marketing, and forward deployed engineering report to the CPO. The reason isn't a bigger box on the chart. It's that the decision rights and the outcome have to sit in the same place, or the outcome waits on a meeting.

Some companies are already there. In May, BILL named Michael Cieri chief product officer over product management, product marketing, product strategy, research, and design, as MarTech Edge reported from the release. SC Moatti's 2026 CPO Insights Report for Products That Count and Mighty Capital, also from May, says more than half of CPOs now carry P&L responsibility, and describes the most ambitious ones taking direct ownership of positioning, adoption, and monetization. Both are context, not this week's news. They show the direction.

What moves, and what stays

The line is easy to draw if you ask one question of each team. Does it change what the product is, or how the product is understood and adopted? Then it's in the loop.

Moves under the CPO: product management and the Product Builders, design and its quality bar, product marketing (positioning, pricing and packaging, the messaging agents read, and the adoption number), and the forward deployed engineers who sit at the customer end of the build. The case for each is its own series: The FDE Transition, The Design Transition, and The Product Marketing Transition.

Stays where it is: brand and demand generation with the CMO, quota and pipeline with the CRO, the platform, reliability, and the harness with the CTO, and the books with the CFO. Those are real jobs with their own numbers. Pulling them in would turn the CPO into a second CEO, and that's not the point.

The trade for the CPO is accountability. Taking four seats means taking one outcome number to the board, and answering for it. A CPO who takes the headcount without the number has only built a bigger org. That scorecard gets its own part later in this arc.

What I expect

These are my predictions, not facts.

My prediction: over the next 18 months, Canva's shape becomes the default AI-era reorg announcement, one product org with fewer layers, and the second wave of those announcements will name design and product marketing inside it the way BILL did.

My prediction: by 2028, growth stops being a separate org at most product-led companies. It becomes the adoption stage of the loop, owned by the same person who owns the spec.

My prediction: board searches for CPOs start asking which outcome number the candidate will own, not which roadmap they'll run. The seat grows because it holds the outcome. I don't think it merges into the CTO seat, and the last part of this arc will argue why.

Next in the series: the field reports to product, FDE and customer success inside the CPO org, and field signal into the product in hours.

One thing to try this week

Run the one-owner test. Pick the three outcomes your board cares about most. For each, write the name of the executive who owns five stages: customer signal, spec, build, story, and adoption. If a row has more than one name, the loop is split, and each extra name is a handoff the outcome waits on. Take the page to your CEO. That's the reorg conversation, and it's better to start it with a page than with a memo.

Sources: Simon Thomsen, "Mel Perkins looks to 'refound' Canva, with 22% of its workforce affected," Startup Daily, November 4, 2026, for the memo quotes as he reports them. Simon Sharwood, "Aussie Adobe assailant Canva announces layoffs in re-org affecting 22% of staff," The Register, November 4, 2026. NICE, Q3 2026 earnings call, with Scott Russell, transcript via Investing.com, November 4, 2026. Kristen Bryant Smith, "The State of Product Launches," Appcues, October 27, 2026, survey of 60 marketers with Navattic. Aakash Gupta with Jayesh Govindarajan, "What an AI-Native Product Team Actually Looks Like at Salesforce," Product Growth, November 3, 2026, as Gupta reports it. "BILL Restructures Leadership Team as AI Strategy Becomes Central to Financial Operations Platform," MarTech Edge, May 28, 2026, context only. Mighty Capital and Products That Count, "2026 CPO Insights Report," PR Newswire, May 27, 2026, context only.

Part of the running argument on Product Leadership: the product org chart was calibrated to a build cost that collapsed, and in the AI era the whole product outcome, from customer signal to adoption, belongs to one function under the CPO.

Related answer: What does Canva's one Product Org mean for who reports to the CPO?