Product in 2026

The cost of turning an idea into working software has collapsed in 18 months. A PM with good judgment and a Claude subscription can ship what used to take a six-engineer team six weeks. I know because I do it.

For twenty years, I've built product by being the connective tissue — the person who translates customer insight into roadmaps, who keeps engineering and design and leadership rowing in the same direction, who ships the thing. That work still matters. But the economics of it have changed in a way that most PMs are underestimating.

Here's what actually shifted: six months ago, autonomous agents broke after three minutes. Today they run coding tasks for six hours. That's not a feature update. That's a phase change. When an agent can only run for three minutes, your job is to prompt it. When it can run for six hours, your job is to design the system it runs inside. The PM role quietly stopped being about issuing instructions and started being about architecting environments.

Which means: implementation is no longer the rate-limiter. Good ideas are. The new bottleneck is "should we build this?" — a taste problem, a judgment problem, and a customer-understanding problem.

The PMs who win in the next five years are the ones who can:

1. See the right problem before anyone else. Be pathologically curious about what people actually do, say, and avoid. Read the forums. Watch the shadow behaviors. Notice when your own behavior changes.
2. Generate quality ideas faster than their peers. Quantity is a solved problem — LLMs can produce a hundred mediocre ideas in a minute. The scarce resource is the judgment to throw out 97 of them.
3. Be the first customer of their own system. Not because PMs should replace engineers — you shouldn't. But because the loop between idea and working artifact is now tight enough that you can design, ship, and use the thing yourself. That changes what you put on the roadmap.
4. Build systems that compound from their judgment. Static skills produce static output forever. The real moat in 2026 is the learning loop — the second agent that watches your corrections, logs the deltas, and proposes how the first agent should change. After a month, it catches things it missed on day one. Your tools get better every day you use them.
5. Drive the executive alignment to ship. The thing AI cannot do: walk into a room of VPs who each own a conflicting OKR, and leave with a signed-off roadmap. Human influence is still the scarce input. Always was, actually.

Here's the part the builder-PM discourse keeps missing. Anyone can swing a hammer. Very few people can produce finished carpentry. AI can put the tools in everyone's hands — Claude Code, n8n, agent frameworks, the whole kit. What it cannot hand you is the taste to know which joint to use, where to hide the seam, when the piece is done. Craft is still rare. Craft is still the job. The tools got cheaper; the skill of producing something worth shipping got more valuable, not less.

My last three years at Google were my education in what all five of these points look like at industrial scale. I've been building the evaluation infrastructure that tells our AI systems whether they're doing their job, and the reward signal that feeds model training. Twenty-plus teams depend on it, including Gemini and Search. What I learned building it: the hardest product management problem in AI isn't the model. The model is not the bottleneck. The bottleneck is knowing — with precision — whether the model is doing what you want. Evals are product. Grounding is product. Trust infrastructure is product. Most of the people calling themselves "AI PMs" have never shipped one of those.

I'm an AI-native product manager because I had to become one. The surface area of my job stretched to include model-level decisions, eval design, non-deterministic UX, and the politics of shipping a system whose output you cannot fully predict. Now I build my own tools with AI, run my life with it, and ship prototypes in an afternoon that would have taken a sprint two years ago.

The PMs who will get hired in 2026 are not the ones with the longest resume, and they're not the ones who can rattle off the tool stack. They're the ones who can demonstrate — not claim — that they have extended how they work to meet this moment, and that they still have the judgment to know what's worth building. The cost of proving the first part is a weekend. The second part is a career.

If you're hiring, I'd love to talk.

— Adam
adam@adamlewkovitz.com