AI didn’t blur product roles. It exposed what was already broken.

I have been reading the same article for six months. Different titles, different authors. But the argument is identical. AI is dissolving the boundaries between PMs, designers, engineers, and strategists. The future belongs to hybrid people: T-shaped, fluent across domains, comfortable in every part of the stack.

The advice is not wrong, exactly.

It is just answering a question that nobody asked correctly.

The hybrid framing assumes there was a clean specialist model before all this. There wasn’t. The roles that are supposedly collapsing now were never quite as clear as we acted like they were. PMs were supposed to own strategy, but in every team I have ever worked on, the actual strategic calls got made by whoever had the loudest opinion that month, sometimes in the meeting, sometimes on Slack at 11pm. Designers were supposed to own user understanding. But in practice, none of us really owned it. We had partial views and compared notes when we remembered to. Mostly we hoped the others were doing more research than we were.

Here is a test. Pick any product team you have ever been on. Ask: who would have lost their job if the wrong thing got built? Not who ran the meeting. Not who wrote the PRD. Who was actually on the hook.

For most teams, the honest answer is nobody. Or everyone, which is the same thing.

At a SaaS company I worked for a few years ago, we built a feature that nobody had asked for and everybody had agreed to. The kickoff was good. Reviews stayed clean and engineering hit the date. Three months after launch, the metrics had not moved.

The post-mortem was the first quiet meeting we had had in a while. The PM said he had assumed the designer was leading user research. The designer said she had assumed the PM was. I had assumed both of them had been talking to customers all quarter. None of us had been. We had spent four months building something based on an internal hypothesis that had never been tested with anyone outside the building.

Nobody got fired. We took the lesson, said the right things, and moved on. But the meeting stayed with me longer than the launch did. What we had run into was not a process failure. The process had worked. The thing that had failed was further upstream. None of us, including me, had owned the question of whether the feature was worth building in the first place.

This was years before the current AI conversation. The misalignment was already there. But we had enough specialists in the room that you could not see it unless you looked hard.

What changed in 2026 is not that the specialists merged. It is that the work each specialist used to do became cheap. A PM with the right tools can build a working prototype over a weekend. A designer with the right tools can write a strategy doc that holds up in front of a leadership team. An engineering lead can run user interviews and have the conversation summarised before lunch. The execution work that used to fill a sprint now fills a Wednesday afternoon.

But all three of those people are still sitting in a room having to decide whether the thing they are about to make cheaply is the thing worth making.

That part has not gotten any easier.

It might have gotten harder.

The tools made the execution portable. But they did not make the judgment portable. And judgment is the part that was never really owned by any of the roles to begin with.

This is why “hybrid skills” feels wrong as the answer. Hybrid skills are about distributing more execution work across fewer people. But the execution work is already cheap. The hard work, which has gone untouched, is deciding what to point the cheap execution at.

What is left when the rest compresses is taste.

Taste is an old, slightly embarrassing word for the thing that was always actually doing the work. Not a list of features ranked on a roadmap. Closer to the small uncomfortable instinct that one of the five proposed features matters and the other four don’t, even when you cannot fully articulate why. The same instinct that wakes you up at 11pm on a Sunday with the feeling that the thing your team is excited about will not survive contact with users, and the willingness to say so on Monday morning at the risk of being wrong in front of everyone.

Taste does not show up on a JD. It does not show up in a performance review. But it is the only product capability that gets more valuable as the rest of the work gets cheaper.

If you are thinking about where to invest your time in this environment, that is the place. Not collecting more skills. Sharpening the judgment behind the skills you already have.

Taste is built the same way it always was. You make calls. You watch them play out. Then you sit in the room when the consequences land, six months or two years later, and you are honest with yourself about whether you got it right or got lucky. There is no shortcut to that. But there never was.

I have been getting calls wrong in public for twenty years. Some have aged well. Some, looking back, were lucky timing dressed up as judgment. The only thing that has improved is being able to tell the difference faster, the next time around.

Roles will keep blurring, team sizes will keep falling, execution will keep getting cheaper. But none of that is the part that decides whether your product matters.

The part that decides has finally come out from behind the org chart. Whether that is good news depends on whether you have been doing the work all along.