# First Principles Are the New Scarce Skill — Pilot to Production

> When the model can build almost anything, the bottleneck moves from how to what and why. The scarce skill is deciding what's actually worth building.

Canonical: https://thegrowthproject.com/podcast/first-principles-scarce-skill/

*Pilot to Production*, the Growth Project podcast — hosted by Sam and Maya.

- Listen: https://thegrowthproject.com/podcast/first-principles-scarce-skill/
- Read the article: https://thegrowthproject.com/blog/first-principles-scarce-skill/
- Audio: https://thegrowthproject.com/audio/podcast/first-principles-scarce-skill.m4a?v=5524b238

## Transcript

**Sam:** Last month a team shipped a feature in an afternoon. The kind of thing that used to take a small team two weeks.

**Maya:** The model wrote most of it. It was clean. It worked. They turned it off three days later.

**Sam:** Wait. It worked, and they killed it?

**Maya:** They killed it because they'd built the wrong thing. Welcome to the gap.

**Sam:** Welcome to Pilot to Production, from the Growth Project. I'm Sam.

**Maya:** And I'm Maya. Today: when the model can build almost anything, the scarce skill is deciding what's actually worth building.

**Sam:** Okay. Afternoon instead of two weeks. That's a win in my book. Where's the catch?

**Maya:** The catch is the buffer disappeared. For most of a career, the constraint was building. The months between the idea and the working thing. Hiring, coordinating, debugging.

**Sam:** The how ate the calendar.

**Maya:** Right. And because the build was slow, you could be vague about the what. Reality forced precision out of you eventually. You'd notice you were wrong before you'd gone too far.

**Sam:** And now you don't get that grace period.

**Maya:** The model builds faster than your ability to be wrong slowly. You ask for a thing, you get the thing, and you get it before you've finished thinking about whether you wanted it.

**Sam:** So the cost of the wrong answer collapsed.

**Maya:** The cost of producing the wrong answer collapsed. The cost of choosing the wrong question did not. The bottleneck moved out of execution and into framing.

**Sam:** Here's what I want to push on. When building was expensive, didn't that protect us a little?

**Maya:** That's exactly the part nobody warns you about. The friction was a filter. A half-formed idea died in the planning meeting because someone asked, who's going to build that, and the room went quiet.

**Sam:** Cost killed bad ideas before they shipped.

**Maya:** Take the friction away, and the bad ideas ship. The model doesn't push back. It doesn't ask whether the feature should exist. It takes your framing as gospel and executes it with terrifying competence.

**Sam:** So if my thinking is sharp.

**Maya:** You get leverage. If your thinking is muddy, you get a beautifully engineered version of your confusion, faster than ever. AI is an amplifier. It multiplies what you feed it.

**Sam:** Feed it clarity, it returns leverage. Feed it confusion.

**Maya:** It returns more confusion. Polished, plausible, and shipped.

**Sam:** Come back to that feature they killed. What did the post-mortem actually say?

**Maya:** It was short. The feature did exactly what they asked. The problem was upstream. They'd asked for a thing that addressed a complaint, not the cause of the complaint.

**Sam:** They optimised the surface.

**Maya:** The bedrock was untouched. And that's the trap. Most teams think they have a what problem. They actually have a why problem wearing a what costume.

**Sam:** Give me the example that lands that.

**Maya:** You don't ask, how do we build the dashboard. You ask, why does anyone need to look at a dashboard. And often the honest answer is, they don't. They need a decision made, or an alert, or for the underlying thing to stop going wrong.

**Sam:** The dashboard was a solution someone reached for before they'd decomposed the problem.

**Maya:** Decompose to bedrock. Ask why until the answer stops being inherited and starts being load-bearing. Most features die at that depth. The ones that survive are worth building.

**Sam:** So the market's repricing skills. What's getting cheap, what's getting scarce?

**Maya:** Cheap: writing the code, knowing the syntax, producing the first draft, speed of execution. Scarce: deciding the code is worth writing, knowing which problem to point it at, judging whether the draft solves the real thing, and the quality of the question.

**Sam:** The left column used to be the whole job.

**Maya:** It's what you hired for, paid for, measured. It's collapsing in value because the model does it on demand. The right column was the soft stuff you couldn't put on a Jira ticket. It's now the entire game.

**Sam:** And you've watched two kinds of operators meet this.

**Maya:** The first treats AI as a faster horse. More output, same thinking. Six months in they've built a sprawling, capable system that solves problems nobody had.

**Sam:** They confused motion for progress.

**Maya:** The second treats it as a forcing function on their own clarity. They know the model will execute whatever they ask, so they get ruthless about what they ask. They build less, and what they build is load-bearing.

**Sam:** And the second kind is pulling away.

**Maya:** Not because they have better tools. Everyone has the same tools now. Because they have better questions.

**Sam:** Okay. First thing tomorrow. Somebody's got a roadmap open. What do they do?

**Maya:** Take the roadmap and ask why five times per item. Keep asking until you hit bedrock or the item collapses. The ones that collapse were never worth building. You just couldn't see it under all the execution.

**Sam:** What else.

**Maya:** Find the last thing you shipped fast and check if it was right. Speed of build tells you nothing about correctness of choice. If you can't name the underlying problem it solved, you optimised the surface.

**Sam:** And the hard one.

**Maya:** Kill one thing you're proud of. Find the feature that works beautifully and serves no one. Turn it off. The discipline of subtraction is the muscle this moment rewards.

**Sam:** For decades the scarce skill was building. We hired for the how.

**Maya:** The model took the how. What's left is the part that was always hardest and always undervalued. Deciding what's actually worth doing, and why. The implementation was never the hard part. It was just loud enough to hide behind.

**Sam:** And it's quiet now. This has been Pilot to Production, from the Growth Project. If your model ships fast but you keep building the wrong thing, that's the gap we close, at thegrowthproject.com.

**Maya:** Thanks for listening. See you next time.