Flexible Studios: Rethinking Org Design for the AI Era (Part Three)

Who Owns the Outcome?

One of the things I've enjoyed most about writing this series has been the conversations that happen after I hit publish. Every article has challenged my thinking a little more, and the comments have been just as valuable as the writing itself.

After the last post, one question kept coming up.

If teams become this fluid, who owns the outcome?

At first, I thought it was a question about accountability.

The more I sat with it, the more I realized it was really a question about leadership.

For decades we've built organizations where leadership, delivery, and organizational structure are tightly connected. The leader is responsible for the team, the work, the roadmap, and the outcome. It made sense because work itself was relatively stable. Teams stayed together, projects lasted months or years, and organizations optimized around moving work from one function to the next.

That's not the environment I see anymore.

AI is making production dramatically cheaper. Teams can move faster, explore more ideas, and solve a broader range of problems than they could even a year ago. The work is becoming increasingly fluid, which means leadership has to evolve with it.

What I've realized is that I was asking the wrong question.

Instead of asking who owns the outcome, I've started asking something different.

How do leaders create the conditions for great outcomes to happen repeatedly?

That feels like a much more interesting leadership challenge.

The experience, and opportunity, behind the model

Long before I started thinking about organizational design, I spent much of my career building startups.

In a startup, nobody has the luxury of staying inside their function. You don't ask whether something belongs to design, product, or engineering because everyone is trying to solve the same problem. The team naturally reorganizes as the business learns, priorities change, or opportunities emerge.

At the time, I assumed that was simply the reality of being small. Now I think it was something else.

Startups optimize around solving problems because they have no other choice.

Enterprises optimize around functions because that's how they've learned to scale.

For a long time, those felt like two very different worlds. AI offers an opportunity for those two models to converge.

Not because enterprises should become startups. I don't believe that. Large organizations have strengths that startups rarely do. They develop deep expertise, create stability, and build capabilities that take years to mature.

What AI changes is the cost of production, creating the space for large organizations to become much more adaptable without giving up their strengths.

Leadership creates capability

One of the biggest changes I've noticed in my own role is what occupies my attention.

On the operational side of the work, the questions shift to:

What capabilities will we need six months from now?

Where are we developing enough depth?

Where are we falling behind?

How do we help people build judgment that AI can't replace?

How do we create opportunities for someone to stretch into a new area before the business desperately needs that capability?

Those aren't project questions; they're leadership questions. That's also why I've evolved toward thinking about Stable Homes rather than project-oriented reporting structures. I think of them as places where capability is cultivated.

A great leader doesn't own people.

A great leader inspires, develops, challenges, and creates opportunities for people to grow.

Stable Homes exist to strengthen the organization's capability over time.

They're responsible for growing expertise, evolving the discipline, sharing what works across teams, and preparing people for the capabilities the business will need next.

Studios benefit from those capabilities. Stable Homes ensure continued growth.

Who owns the outcome?

That brings me back to where I started.

I don't think there's a single answer anymore. The more I've worked through this model, the less I think outcomes belong to one leader.

Great outcomes come from leadership teams working together around a shared objective. Design brings one perspective. Engineering brings another. Product, research, data, business, and domain experts contribute their own. Together, they shape the outcome.

The studio exists to bring those perspectives together around a shared set of goals and measures of success. That doesn't reduce accountability. It changes it. Instead of each function optimizing its own work, the leadership team aligns around a common outcome and measures success together.

That's a subtle difference, but I think it's an important one. The conversation shifts from:

Did my team deliver? to

Did we solve the problem?

The work doesn't become less accountable. It becomes collectively accountable.

Leadership creates the conditions

As I continue experimenting with this model, I've realized the biggest shift isn't organizational. It's philosophical.

Leadership is becoming less about directing work and more about creating the conditions where great work can happen.

That means cultivating capability instead of simply allocating resources. It means investing in people before the business needs them. It means thinking about AI not as another tool, but as another capability the organization can learn to apply.

Most importantly, it means recognizing that the best outcomes rarely come from a single function, leader, or team. They emerge when the right capabilities come together around the right problem at the right time. That's ultimately what I've been trying to describe throughout this series.

Not a new org chart. A different way of thinking about organizations.

One where Stable Homes cultivate capability. Studios apply capability. And leadership creates the conditions for both to succeed.

We're still learning, and my thinking will continue to evolve. I'm curious what you're seeing inside your own organization.

If AI continues making execution easier, what becomes the most important job of a leader?