When Production Gets Cheap, Judgment Is the Bottleneck
Every major technology solves the problem it was built to solve and immediately surfaces the next one. The railroad collapsed the cost of moving goods across a continent. What it couldn't solve was where people wanted to go, which turned out to be wherever other people already were. So the railroad boom became a real estate boom became a city-building problem. Aviation solved distance and then hit airports, fuel, and the hard reality that connecting cities is easier than connecting the people inside them.
The constraint doesn't disappear. It migrates.
AI is the current move. The cost of creating things (writing, code, images, analysis, software) is collapsing. Not gradually. Collapsing. The production floor dropped for everyone at the same time, which means production stops being the differentiator not because it got easier for you, but because it got equally easy for everyone else.
What's left is the part that didn't get easier. The job isn't generating the answer anymore. It's recognizing the right answer when an agent surfaces it. Agentic AI is collapsing the doing layer further: less boilerplate, faster scaffolding, better options surfaced faster. The human job is becoming judgment under abundance. Choosing well among good options. Knowing when the elegant solution is wrong for this specific context.
The bottleneck moved from making to distributing to knowing. It's now moving toward deciding.
Coders
Coders are the clearest case because the progression is already visible in real time.
The first shift happened fast. Copilot and its successors moved the constraint from writing code to decomposing problems: knowing what to ask for, breaking work into agent-sized chunks. That was a genuine skill change and it caught a lot of people off guard.
The second shift is happening now. Even decomposition is getting automated. Agents scaffold, debug, and ship increasingly complex systems with decreasing human intervention. The bottleneck is migrating to system judgment: understanding how pieces fit together at architectural scale, knowing when the solution the agent surfaced is technically correct but wrong for this codebase, this team, this user's actual problem.
The coder who wins isn't the fastest typist or the best decomposer. It's the one who can evaluate what agents produce with enough depth to know when to accept, when to redirect, and when to throw it out. That requires understanding the problem space at a level no agent can substitute. Not because agents aren't capable, but because the context is biographical. You know this system. You know what the last three rewrites got wrong.
As agents increasingly surface two or three working implementations, the human job is recognizing which one is right, not by rewriting it, but by understanding it deeply enough to choose. Engineering taste, the capacity to evaluate architectural decisions with judgment that accumulates over years of building real things, is the skill that doesn't get commoditized. It just gets more valuable as the options multiply.
Indie developers
The production bottleneck moving means anyone can ship a working product in a weekend. The market is now flooded with working products.
Distribution is hard but solvable: SEO, niche communities, the occasional well-timed launch. The constraint that moved past distribution is positioning precision. The indie dev who owns a niche so specifically that they're the obvious answer to one exact search query has a defensible position. The one building a slightly better version of something that already exists has a much harder road.
Most indie devs are hitting the asymptote at the distribution layer and attributing it to the product. The problem usually isn't the product. "Project management for freelancers" is not a niche; it's a category. "Project management for freelance motion designers who work with agencies" starts to be a niche. The specificity that feels like it limits the market is actually what creates it.
As agents handle scaffolding and integration work, the indie dev's time increasingly goes to one question: what is the right thing to build, for whom, precisely. The developers who stay close to specific users in specific contexts will consistently out-build the ones generating products from general market observations. The insight gap is where indie dev value lives now.
Creative groups
Creative groups have a structural advantage individuals don't: curation as identity. The collective known for choosing well, for having taste its audience trusts, is building something that compounds differently than individual output.
In an environment of infinite production, the group that surfaces the right things and champions the right voices is performing a function audiences genuinely need. That's a different value proposition than "we make good things." It's "we know what good is, and you can trust us to find it."
Most creative groups are still operating in production mode, releasing work and hoping distribution follows. The ones pulling ahead are building recurring touchpoints (newsletters, communities, curated channels) where the relationship is the product and the work is evidence of taste.
Agents will generate options faster and accelerate production. The group's job becomes choosing: which direction is true to what we're building, which collaborator is right for this project, which format serves this audience right now. The groups with clear enough aesthetic identity to make those choices consistently will compound. The ones without that clarity will produce more and define themselves less.
Writers
The asymptote for writers is simpler and harsher than the others: reach is available, resonance isn't.
Anyone can generate content. The constraint that moved is voice, not just having one, but having one specific enough that an algorithm can learn who to serve it to. The mistake is optimizing for volume. The algorithm doesn't reward volume. It rewards signal: work that tells the system exactly who this is for.
Agents will draft, schedule, and optimize. What they cannot do is accumulate the specific point of view that makes the choice of what to say worth making. The judgment about which of three well-written angles is actually true to your thinking stays human. Writers who outsource that judgment will produce more and mean less.
Brands
Brands have budget and reach. What they're losing is the one thing neither can manufacture: trust.
Polished production is table stakes, and in certain contexts polish has become a liability. Audiences have learned to recognize brand voice and discount it. The constraint is now human signal: real people inside the organization with genuine opinions, and real customer relationships that create advocates rather than audiences.
Agents handle execution well. The brand's actual job is deciding what to stand for, which relationships to invest in, which hill to die on. That's precisely what can't be optimized. The brands treating AI as an execution layer while investing in trust as a strategic asset will pull away from the ones using it as a content factory.
What holds
The production collapse is real and it's not reversing. Every group above is operating in an environment where making is table stakes. The constraint moved to the same general place for all of them: the ability to choose well, consistently, in ways that accumulate into something an audience can orient around.
Agents accelerate the surfacing of options. They don't supply the judgment about which option is right.
The bottleneck always moves. Right now it's moving from making to deciding. The people and organizations investing in judgment, identity, and the trust that good decisions require are building the thing the next wave of tools won't touch.
The ones who aren't are getting faster at making things, which is now the easy part.
Thoughts? Email me at [email protected]
Back to writing