Empowered Product Teams Were a ZIRP Feature

The short version

The empowered product team was a luxury of the zero interest rate era, not a timeless truth, and now that capital is expensive and AI changed the constraint, the empowered-team orthodoxy is breaking. The model assumes a company can afford to hand cross-functional teams broad autonomy and patient time to discover the right outcome. That patience was cheap when capital was cheap. It is not cheap now. Worse, the whole empowered apparatus existed to make good decisions about scarce, expensive engineering capacity, and AI collapsed that cost, so the machinery is aimed at a constraint that no longer binds. Marty Cagan was not wrong for his era. He was wrong to teach an era-specific configuration as a permanent law of product. What replaces it is a smaller team of product builders carrying more of the loop with agents. Here is the uncomfortable case.

I taught the empowered team gospel. I installed it. At three different companies I stood in front of a product org and made the case for autonomous cross-functional teams owning outcomes, and I believed it. I still think it was right, for the world it was built for. That world had near-zero interest rates and is gone.

The model was an economic feature, not a law

Here is the thing the empowered team literature almost never says out loud. The model is expensive.

You take a group of senior people, you give them broad autonomy, you tell them not to rush to solutions, you fund a discovery cadence, and you accept that they will spend weeks learning their way to the right outcome before they commit to a build. That is a beautiful way to work. It is also a luxury good. It assumes your company can afford the patience.

That patience was affordable in the zero interest rate era because capital was cheap and the market rewarded growth over efficiency. You could carry a large product org running deliberate discovery because money was nearly free and nobody was asking hard questions about cost per outcome. The empowered product team was not a timeless truth. It was a feature of a specific cost of capital, the way free snacks and ten-person platform teams were features of the same era.

“

The empowered product team was not a law of product management. It was a luxury good of cheap capital, taught to a generation as a permanent truth.

”

When the rate environment flipped, the tolerance for slow, autonomous discovery shrank with it. Boards started asking why a product outcome took a fully loaded cross-functional squad three months to get to. The honest answer, that the model was tuned for a world where that was fine, did not survive contact with expensive capital.

AI removed the constraint the model existed for

The cost of capital is half the story. The other half is worse for the orthodoxy.

Walk back to why empowered teams existed in the first place. Engineering capacity was scarce and expensive. The most important decision in product was how to spend that scarce capacity, and getting it wrong was a six-month, seven-figure mistake. The entire empowered apparatus, the cross-functional trio, the dual-track discovery, the opportunity solution trees, existed to make that expensive bet well. It was a sophisticated system for rationing a scarce resource.

AI collapsed the resource. When an agent produces a working prototype in an afternoon, the bet is no longer six months and seven figures. It is an afternoon. The elaborate machinery for rationing scarce build capacity is solving a constraint that mostly stopped binding. You do not need three weeks of discovery to de-risk a build you can just do and test the same day. I make the fuller version of this case in why Cagan built the church and we may not need one, and the empowered team is the church's central ritual.

So the model got hit from both sides at once. Capital got expensive, which killed the patience it required. And AI got cheap, which killed the constraint it was built to manage. A model can survive losing one of its load-bearing assumptions. This one lost both in the same eighteen months.

What is actually breaking

I want to be precise, because the lazy version of this take says empowered teams are dead and that is not what is happening.

The autonomy is not breaking. Teams should still own outcomes. The thing breaking is the size, the ceremony, and the assumption that you need a full cross-functional squad running a discovery cadence to make good product decisions. That apparatus was the expensive part, and it was expensive specifically to manage a scarce build resource that is no longer scarce.

The companies clinging hardest to the full empowered model are the ones who learned it as scripture during the cheap-money decade and never updated the assumption underneath it. They are running a luxury process in an economy that no longer subsidizes luxury, to manage a build cost that no longer exists. The discovery hygiene is impeccable. The configuration is from a dead era.

I was wrong about how permanent it was

I will own my part. When I installed empowered teams, I taught them as the right way to do product, full stop. Not as the right way to do product given cheap capital and expensive build. I stripped the conditions off the conclusion and handed people the conclusion as a law.

That is the same error I now think the whole canon made. The empowered team thesis correctly described how the best companies worked in a specific cost structure. The mistake, mine and the field's, was teaching a configuration as a constant. When the cost structure flips, every orthodoxy built on it has to flip too, and most people who learned the orthodoxy as truth cannot see the assumption they are standing on. The resistance I write about in why empowered teams fight the change is mostly people defending a configuration as if it were a principle.

“

The error was never the empowered team. It was teaching a configuration tuned to cheap capital and expensive build as a permanent law. Flip both, and the law was always a lease.

”

What replaces it

Smaller teams of product builders who carry more of the loop themselves, with agents compressing what used to take a full squad. The autonomy stays. The outcome ownership stays. The patient multi-week discovery cadence and the headcount it required do not.

In my current work at Falkster.AI, the empowered trio is a single builder plus a fleet of agents. A customer outcome comes in, a listening agent extracts it, agents dispatch to build a prototype the same day, and the builder judges the result against the real outcome. That is not the empowered team made faster. It is a different shape entirely, tuned to a world where build is cheap and judgment is the scarce thing.

Pick one thing to try this week

Look at your team's discovery cadence and ask one question about it. Was this designed to manage scarce, expensive build, or to learn about the customer. If the honest answer is the first one, it is solving a problem AI mostly erased, and you are paying ZIRP-era process costs in an expensive-capital world. Try killing one ceremony this sprint and replacing it with a same-day prototype tested against a real customer outcome. If the team learns more from the prototype than they would have from the ceremony, you just felt the orthodoxy break.

Sources: Silicon Valley Product Group, on empowered product teams · a16z, on the changing cost structure of software · Lenny Rachitsky, on product org design