AI Swapped Out a Leg of the Stool. Scope is the New Bottleneck
Rethinking the Project Management Triangle in the Age of AI
About 8 months ago I did something that wasn’t possible before. I picked up a language and framework I’d never really worked in and built a working API — not by learning it and reading documentations for weeks, but by having a conversation with AI. I was shipping real, functional code in hours.
I didn’t stop there. With my team’s blessing and guidance, I started making meaningful changes in codebases I barely knew. I cleaned up years of accumulated tech debt and backfilled missing unit tests that had been on my team’s to-do list forever — work that would have taken weeks — and knocked it out in a few days while juggling my leadership duties.
If you’ve used AI coding tools seriously, you know exactly what I’m talking about. It feels like a cheat code.
But here’s the thing that’s been nagging at me: when code becomes this cheap and fast to produce, something else has to give. I think we haven’t fully reckoned with what that is yet.
The 3-Legged Stool
There’s a concept I’ve always called the 3-legged stool of project management. The three legs are Scope, Time, and Resources. The constraint is that you can only have two out of the three legs. Want to ship fast with a big scope? You’re going to need a lot of resources. Want to ship fast with a small team? You’re cutting scope. Want to do it all with limited resources? You’re going to be slow. Pick two. That’s always been the deal.
Every engineering team lives inside this constraint whether they know it or not.
AI just swapped out a leg.
Resources — specifically the cost and speed of writing code — have been fundamentally disrupted. What used to take a week can take an afternoon. What used to require deep expertise in a framework can now be done by someone willing to have a detailed conversation with an AI tool. The marginal cost of a unit of code is approaching zero.
So if Resources are no longer the binding constraint, something has to take its place. I’d argue that something is Quality. The stool still has three legs. They’re just not the same three legs anymore: Scope, Time, and Quality.
The biggest threat to that new Quality leg? Scope. Left unchecked, Scope is what will squeeze Quality out of the picture entirely.
Why Scope Creep is the New Bottleneck
Here’s what happens when code gets cheap: everyone suddenly has more ideas. The PM wants two more features. The CEO wants a dashboard. The designer has “one small tweak.” Why not? It’s so easy now, right?
This is the trap. Cheap code doesn’t mean cheaper decisions. Every feature you add still has to be reviewed, tested, integrated, maintained, and understood by your team six months from now. The thinking, the judgment, the tradeoffs — AI doesn’t do any of that for you. Scope creep has always been dangerous. With AI it becomes supercharged, because the usual forcing function — “we don’t have the bandwidth” — is suddenly a lot harder to say with a straight face.
This is exactly where Quality gets squeezed. AI-generated code can be fast, voluminous, and subtly wrong all at the same time. I believe AI will get much better in short order, but the reality now is that the more scope you allow in, the more surface area you create for things to go sideways.
So What Do You Actually Do With This?
A few things I am telling my team right now:
Be more ruthless about scope than ever before. The temptation to pile on is real and it will kill you. Define what you’re building, lock it, and defend it like your quality depends on it — because it does.
Keep your PRs as tight as they were before. Just because AI makes it easy to write or update a lot of code at once doesn’t mean you should cram it all into one PR. Keep the same discipline you had before — focused, contained, reviewable. Your teammates still have to read that code. Split up your PRs the way you always did. If your review bar is already high (raise it if not), then it doesn’t need to change much. Keep your PRs tight and your review process should stay as smooth as it always was.
Recognize where the real constraint moved. It’s not code anymore. It’s judgment — yours, your team’s, your senior engineers’. That’s the scarce resource now. Protect it accordingly.
AI swapped out a leg of the stool. Resources is out. Quality is in. Scope is the thing that will topple it if you're not watching.
How is AI changing how you think about scope and quality on your team? I’d love to hear what you’re seeing in the trenches.
As always, ship it.
Matthew