Something quiet happened while the industry was busy marveling at what AI agents could build. The question of what to build — never the glamorous question, never the one that trends — became the only question that matters.
We are living through a rare and disorienting inversion. For most of software's history, execution was the hard constraint. Ideas were plentiful; the ability to translate them into working products was the bottleneck. That bottleneck is dissolving. AI coding assistants, autonomous agents, and LLM-powered pipelines have compressed the cost of building to a degree that would have seemed impossible five years ago. A competent engineer with the right tools can now produce in a weekend what once took a team a quarter.
Which means the engineering problem is increasingly solved. The product problem is not. When anyone can build anything, what you choose to build — and why — becomes the entire game.
Speed without direction is just faster failure
Velocity feels like progress. Shipping feels like winning. But there is a version of the AI-accelerated future that is quietly catastrophic for the companies living it: teams building faster than they are thinking, accumulating features the way previous generations accumulated technical debt.
The problem was never engineering capacity. Most failed products were not failed because they could not be built. They failed because they solved the wrong problem, misread the customer, or built the right thing for a market that did not yet exist — or had already moved on. AI does not change any of that. If anything, it amplifies it. Higher velocity in the wrong direction gets you to the wrong place faster
This is why the most valuable person in the room right now is not the engineer who knows how to wield the best AI tools — though that matters — but the person who can look at a customer, understand something true about them, and translate that understanding into the exact right thing to make. The person who can feel the gap between what a user says they want and what they actually need. The person who knows, before a line of code is written, that this idea is worth building and that one is not.
Human taste as competitive advantage
There is a term that gets used somewhat loosely in product circles: taste. It sounds soft, subjective, hard to hire for. But in practice it is quite specific. Taste is the ability to hold a customer's experience in your mind with enough fidelity that you can make decisions on their behalf — decisions about what to include, what to cut, what to say and how to say it, what friction is acceptable and what is not.
LLMs, for all their extraordinary capability, do not have this. They can generate plausible surfaces — copy that sounds right, flows that look reasonable, features that seem coherent. But they have no stake in the outcome. They cannot be embarrassed by a bad product. They do not know that your particular customer is the kind of person who will forgive a rough edge but will never forgive being made to feel stupid. That kind of understanding — granular, human, earned from observation and conversation and failure — is not something you can prompt your way to.