Why the Omnivore Product Manager Model Is Broken

Would you let an AI operate on you with no surgeon?
Would you board a plane with no pilot?

Then why are we celebrating the death of specialists in product?

AI is creating noise: "Designers are the new engineers." "Engineers are the new designers." "PMs can now design." "PMs should ship products".

But the omnivore Product Operating Model, with the Product Manager as a centrepiece, created a precedent that AI will only amplify.

Why?

Not the fault of PMs, some are brilliant. But this model, by pushing one role to bleed into everyone else's territory, normalises conflict of interest, the kind democracies built entire systems to prevent.

It made specialists relevant only in execution, and now it is making specialty irrelevant. It erased the concept of clear ownership.

It is a model that wastes the best of everyone, including the PMs themselves, stretched far beyond what any one role should carry.

We took something simple and made it complicated. Then we are making it even more complicated.

Here's what building a product actually requires:
Designer & Research → product desirability, direction, vision
Marketing & Sales → positioning, business model, go-to-market
Engineering → building, and generating data no one else has

Above them: the Maître d'orchestre. What I call the "Playmaker", the centrepiece of a next-gen Product Operating Model. Someone who aligns the three, makes trade-offs, holds the brief, watches the clock and the budget and ensures outcome-focused KPIs are met, both at business and function level.

That's it. That's the whole model. And in that model, each specialist delegates the execution part to the AI. Humans focus on the strategy.

Yes, designers will vibe-code. For demos. To convince better.
Yes, engineers will design in Claude AI. To experiment, not to spec.
That's fine. Jobs evolve but thinking shouldn't be outsourced.

That's exactly why specialists still matter. Because you need accountability when things go wrong.