← narwal.one/Second Brain
SecondBrain
Ask the Brain
Index/Conceptupdated Tue Oct 27 2026 08:00:00 GMT+0800 (Philippine Standard Time)

Product Management Bottleneck

product-managementbuilding-with-aiandrew-ngconstraintsfounderstask-imagination

Product Management Bottleneck

Andrew Ng's name for where the constraint moved once AI collapsed the cost of building software:

"The cost of building has plummeted and so the challenge is shifting to deciding what to build, which I've been calling the product management bottleneck."

The prescription that goes with it: "learn AI, build fast, and talk to customers." Founders, engineers and product managers can now build and iterate in hours, so the scarce input is the customer insight and judgment that decides what to build. Ng says he builds something most weekends — a wrapper, a metrics analysis, an automation — because the build cost no longer justifies waiting for a specialist.

The caveat Ng attaches

Cheap building does not make companies cheap. "Building a company is still really, really hard." What makes something meaningful still takes either real technical depth (complex software that takes months or years) or deep customer insight (talking to people, reading faces, surveys, repeated until you know what to build). Sampling widely is fine; going deep in a couple of sectors is still what builds a business.

How it sits with neighbouring vault frames

  • Task Imagination (Nate B. Jones) is the same constraint seen from the operator side: the model can run for days, so the limit is what you can imagine handing it. Ng's version is the product side: the build is cheap, so the limit is knowing what is worth building. Both locate the bottleneck in the human, not the model.
  • Disposable Software is the artefact class this produces: when build cost approaches zero, one-off tools for one occasion become rational — and selection, not construction, is the skill.
  • Context Advantage (Humans over AI) is why the bottleneck stays human: deciding what to build is a context problem.
  • Build vs Buy (Agents) inherits the consequence for enterprises: the question stops being "can we build it" and becomes "is this the thing worth our builders' attention" — the per-use-case gate already recorded there.

Sources

2026-10-27 — What the bottleneck looks like when it is skipped (per Enterprise AI Adoption and the Reshaping of Job Profiles (Research Brief 2026-10-27))

A reply inside the AI-pilled-startup thread (r/cscareerquestions, 73 upvotes) describes a company that automated the deciding, not just the building: "Requirements and product specs are generated by running an agent over transcripts of customer calls. We have no idea what we are building or if anyone asked for half the shit we built." The OP's own shop reports UI/UX that is "really, really bad," with "ten different ways to do things" and feature creep it blames partly on vibe-coding. This is Ng's bottleneck observed from the inside: transcripts are cheap input, but the inference about what is worth building is the PM's job and does not survive being delegated. The HN thread on "more code, not more software" adds the organisational version: agents will not produce more software "until the PO's and PM's of the world step back and let developers communicate directly with the stakeholders. Or the PO's and PM's could cross-train on AI coding agents." The Digital Product Management column of Agent-Delegated vs Emerging Human Work by IT Job Family is built on this section.