The Armageddon Moment for Product Teams
AI is forcing product leaders to ask a question the movie industry answered in 1998: which direction is easier to train?
There is a scene in the DVD commentary for Armageddon where Ben Affleck asks Michael Bay a simple question: why is it easier to teach oil drillers to become astronauts than to teach astronauts to become oil drillers?
Bay did not have a great answer. But the question stuck.
AI is forcing product teams into the same moment right now.
The Question Nobody Wants to Ask Out Loud
As AI coding tools get better, product managers can ship working code. Not good code. Not production-ready code. But functional, demonstrable code. Vibe-coded pull requests are real. They are happening at companies you know.
At the same time, engineers have always had the option to develop product instincts. To sit closer to users. To think about outcomes instead of outputs. Some do. Most do not, because the incentive structures of most engineering organizations do not reward it.
So here is the Armageddon question for your product org: what is actually more efficient? Training a PM to ship code, or training an engineer to think like a product person?
Why This Is Not a Simple Answer
The instinct is to say both. Hire full-stack, product-minded engineers. Build a culture where everyone thinks about the user. That is the right answer in a pitch deck.
In practice, product thinking and engineering thinking are different cognitive modes. Some of the best product designers I know cannot read a stack trace. Some of the best engineers I know can rebuild your infrastructure and still miss why users are churning.
AI lowers the floor on execution. A PM with the right tools can now prototype, iterate, and ship surface-level features faster than ever. That is genuinely useful. But it does not replace the judgment required to decide what to build, how it should behave under edge cases, or whether the interaction model is actually right.
The oil drillers made it to space in the movie. But they still needed NASA.
What This Means for Product Teams Right Now
The teams getting this right are not asking which role to collapse into the other. They are asking a sharper question: where does human judgment create the most leverage?
That usually means:
- Engineers spend less time on boilerplate and more time on systems thinking
- PMs prototype earlier and validate assumptions before anything gets built
- Designers focus on the decisions AI cannot make: what should this feel like, and why
The roles are not going away. The boundaries between them are shifting. The leaders who figure out the new shape of those boundaries early will have the real advantage.