When Building Gets Cheap, Shaping Becomes the Job

For most of my career, the constraint was always the same: building was expensive.

Not just in dollars. It was expensive in time, in coordination, in the number of people who had to sign off before anything shipped. So organizations got built around that constraint. Most of the machinery, the estimates, the backlogs, the handoffs, existed to protect the costly act of building.

Then building got cheap.

Not free, and not effortless. But the cost of turning a clear idea into a working thing has dropped in a way most processes haven't caught up to. Shape Up always made an uncomfortable claim: the hard part was never the coding, it was deciding what was worth building and how much it was worth. Now that building is cheap, that claim is simply true. The scarce skill is shaping.

I help companies become AI-Native. And almost everywhere I look, the bottleneck has moved from the keyboard to the table where someone decides what's worth doing.

The leaky faucets that never make a cycle

Every organization is full of problems that never make it into a cycle. They keep coming back, they affect more than one person, and they have a real cost, but they're too small to shape into a project and too annoying to fix on the side of someone's desk. They're leaky faucets. Everyone walks past them. Nobody bets on them.

In most organizations, those faucets aren't inside a role. They're in the gaps between roles. The coordinator who can't update a template without a developer. The internal tool only one person understands. The report rebuilt by hand every month because automating it was never anyone's project. The workaround that's been "temporary" for two years. Each one is small. Together they're a tax the whole organization pays, quietly, forever.

The reason they don't get fixed isn't that they're hard. With AI, most of them are now genuinely easy to fix. The reason is that nobody ever shaped them. A leaky faucet never arrives as a pitch. It arrives as a sigh. So at best it lands in cool-down, patched in the scraps of time between cycles, and at worst it drips forever.

Here's what AI changes. The faucet used to be too small to be worth a bet. That math has flipped. When building is cheap, a problem that would never have justified six weeks is now easily worth a few days, which means it deserves a real place at the betting table, not the cool-down leftovers.

This is the trap I watch companies fall into when they try to "adopt AI." They buy the tools, run the training, and bolt AI onto a process still built to ration expensive engineering. The faucets keep dripping, just with a copilot watching.

Shape the outcome, not the feature

The work that makes this real starts with an executive or manager doing something specific: shaping the problem.

Shaping is not writing a spec, and it is not assigning a task. It's framing the problem at the right altitude. Concrete enough that a team knows what outcome they're chasing, loose enough that they own how to get there. A good shaped pitch says four things: here's the problem and who feels it, here's the appetite (how much time this outcome is worth), here's a rough idea of a solution, and here's what we're explicitly not doing.

Notice what's missing: an estimate. You don't ask "how long will this take." You decide "how much is this outcome worth to us," and that appetite becomes a constraint the solution has to fit inside. Fixed time, variable scope. The faucet is worth two days of someone's attention, so the solution gets shaped to fit two days, not gold-plated into two weeks.

This is the executive's real leverage in an AI-Native organization. Not approving tickets. Framing problems as outcomes worth a defined amount of time, then protecting that boundary.

Bet on it at the table

Once a problem is shaped, leadership bets on it. The betting table is where executives and managers commit a cycle's worth of attention to a small set of shaped outcomes and, just as importantly, decline the rest. There's no grooming a backlog into eternity. A pitch that doesn't get bet on doesn't get a participation trophy. It gets dropped, and if it matters it comes back better shaped.

What's new is what's now worth betting on. Because appetites have shrunk, the table can take bets it never could before. The faucets that used to be invisible are now legitimate small-batch bets. The executive who used to spend the whole session arguing over which three big projects fit the quarter can now also clear a dozen outcomes that quietly tax everyone.

Hand the bet to a team that owns the outcome

A bet goes to a small, autonomous team with one job: deliver the outcome inside the appetite. Not implement a spec. Own the result. They talk to the people who feel the problem, decide what to build, build it, and confirm the faucet actually stopped dripping. Done means shipped, not demoed.

This is the identity shift, and it's the hard part. You can hand someone an AI assistant in an afternoon. Getting a team to believe the outcome is theirs to own, and to scope their own work down to fit the appetite rather than asking for more time, takes a lot longer. No tool does it for you.

Measure outcomes, not output

If you bet on outcomes, you can't grade people on output. Story points and ticket counts quietly tell everyone the old conveyor belt is still the real job. Track the things the bet was actually about: did the outcome ship inside its appetite, did the faucet stop dripping, how many people stopped working around it. Measure the problems you closed, not the tasks you completed.

Make the bet repeatable

A single fixed faucet is an anecdote. Becoming AI-Native means making the case that this kind of bet pays off again and again, so the table keeps room for it. Put a number on the faucet before you shape it: hours per task × frequency × people affected × loaded rate, or the cost of a tool nobody can use, or the rework errors create every month. Bet, ship, show the delta. Do that a few cycles in a row and "spend a few days fixing the small things" stops being a favor and becomes an obvious return.

What you're really building

The headline insight, that the gap between a problem and a solution has collapsed, is true for one person with one tool. AI-Native is what happens when an organization rebuilds its decision-making around it: shaping over specs, appetite over estimates, bets over backlogs, outcomes over output.

An organization that bolts AI onto an unchanged process just rations cheap building with expensive ceremony. An organization that shapes its faucets into small bets and hands them to teams that own the outcome doesn't ration anything. It fixes problems as a matter of course.

That's the real transformation, and it isn't really about AI. AI made it affordable. The work is everything around it: teaching executives to shape problems as outcomes, teaching teams to own them, and changing what you bet on so the person who hears the sigh is also the person handed the time to fix it. This is the heart of an AI-native transformation, rebuilding the operating model, not bolting a model onto the org chart.

Build an organization that bets on outcomes, and you stop needing to call a plumber. The whole organization already knows how.

You cannot buy your way here

Here's the part that gets skipped, because it's the part you can't purchase.

If this is the organization you want, handing everyone AI tools is a fool's errand. Tools don't change how people work. They change how fast people do the work they already feel safe doing. Drop powerful tools into a culture that punishes a miss and you get the same cautious, handoff-heavy behavior as before, just executed quicker. The faucets still drip. Nobody risks shaping a bet that might not pan out, because in that culture a bet that doesn't pan out is a black mark.

So the real transformation isn't technical. It's a shift in how the organization treats failure.

When building was expensive, failure was expensive too, so everything got built to prevent it. Sign-offs, estimates, committees, the long chain of approval. Caution was rational when a wrong turn cost a quarter. But that same caution is exactly why the small problems never get touched: the imagined downside of a failed attempt feels larger than the very real, ongoing cost of the leak.

What makes an AI-Native organization work is the opposite instinct. Failure is a good thing when it's controlled, and controlled is the operative word. This is what shaping and betting are actually for. An appetite is a blast radius. A bet is a bounded experiment with a known, affordable cost. When a bet doesn't work it gets dropped without ceremony, and that isn't waste, it's the system functioning exactly as designed. You spent a week to learn something, for the price of a week. The teams that win are the ones that fail small, fast, and often, inside boundaries that make every failure survivable.

That instinct doesn't come from a tool. It comes from leaders who draw the boundaries, who make it genuinely safe to try inside them, and who treat a well-run failed bet as a success of the process rather than a fault of the person. Get that culture right and the tools amplify it. Get it wrong and the tools just help your organization stand still faster.

Give people permission to fail in ways that can't hurt them, and they will fix every faucet in the building. That, not the tooling, is the transformation.

If you're trying to build this, the hardest part won't be the tools. That's the work I do as an AI-native leader, and I'd like to hear how you're handling the culture. Let's talk →