The org chart is a lie.

An orchestra needs a conductor. It needs first violins sitting in front of second violins. It needs the woodwinds to the left and the brass to the right. Everyone has sheet music. Everyone plays their part. Nobody improvises. And if the oboist suddenly picks up a trumpet mid-performance, the whole thing falls apart.

A jazz band works differently. There's a loose structure, sure. Someone counts off the tempo. But after that, the bassist can solo. The pianist can comp. The drummer can lead. The sax player reads the room and decides, in real time, whether this moment needs melody or space. Nobody asks permission. The music is better because the roles are fluid.

Most product teams in 2026 are orchestras. Rigid seating. Fixed parts. A conductor who controls the tempo.

But the work has become jazz.

Here's what I mean. For the last two decades, the product team org chart has looked roughly the same. A PM writes the spec. A designer makes the screens. An engineer builds what's been specced. QA tests it. They all meet on Tuesdays to politely disagree about scope, then ship something three weeks late that nobody's fully happy with.

This structure made sense when each of these skills took years to develop and couldn't be faked. The PM couldn't prototype because prototyping required code or advanced Figma skills. The designer couldn't query a database. The engineer couldn't run a user interview without accidentally leading every question.

But AI just handed everyone a second instrument.

The PM can now prototype a working concept in an afternoon. The designer can ship a functional front-end without waiting for engineering. The engineer can synthesize user research, generate test scripts, and explore design alternatives before the designer has even opened their laptop.

The boundaries that justified the org chart are dissolving. And most companies are pretending they aren't.

The org chart protects roles, not outcomes.

I worked with a product team a few years ago where the designer and the PM were in a cold war over who "owned" the product vision. The designer felt it was a design-led question. The PM felt it was a strategy-led question. They each made decks. They each presented to leadership. They each lobbied allies in Slack channels they thought the other didn't know about. (They both knew.)

The product, meanwhile, sat in a backlog gathering dust while two smart people argued about whose name went on the thing.

That team didn't have a skills problem. It had a territory problem. The org chart had drawn lines, and those lines had become fences, and those fences had become identities. The PM was protecting "PM-ness." The designer was protecting "designer-ness." Neither was protecting the user.

This is what org charts actually do in most companies. They don't organize work. They organize ego. They tell people what's theirs and, more importantly, what isn't. And the moment someone crosses a line, even to help, the immune response kicks in. "That's not your lane." "Let's keep the roles clean." "I think we should respect the process."

The process. The process is a polite word for "the way we've always done it, and I'd prefer not to think about whether it still makes sense."

AI didn't create the problem. It just made it impossible to ignore.

The truth is, rigid role boundaries were always a bit of a fiction. The best PMs I've ever worked with could sketch interfaces on a whiteboard that were better than half the wireframes I'd seen from junior designers. The best designers I've known understood business models well enough to challenge the PM's assumptions in ways that made the product sharper. The best engineers I've worked alongside had more user empathy than some researchers I've met.

Great product people have always been jazz musicians. They just had to pretend they were in an orchestra because the org chart demanded it.

What AI has done is make the pretending harder. When a PM can go from idea to clickable prototype in two hours using AI tools, the old argument of "well, the PM doesn't have the design skills to do that" evaporates. When a designer can write and deploy a simple feature without filing a Jira ticket and waiting three sprints, the old argument of "well, the designer can't build" evaporates too.

The walls are coming down. And the people most threatened aren't the ones without skills. They're the ones whose entire identity was built on being the only person in the room who could do a specific thing.

That's a hard sentence to sit with. But I think it's the truest one in this piece.

The question nobody in leadership is asking.

If your PM can prototype, your designer can ship, and your engineer can research, what exactly is the org chart protecting?

It's not protecting quality. Quality comes from taste, judgment, and experience, not from job titles.

It's not protecting speed. Speed comes from fewer handoffs, not more.

It's not protecting the user. The user doesn't care if the person who fixed their problem was a PM, a designer, or an engineer who got curious on a Friday afternoon.

What the org chart is protecting is comfort. The comfort of knowing your lane, your title, your territory. The comfort of a Jira board that assigns work to roles instead of to problems. The comfort of never having to say "I don't know how to do that yet, but I could probably learn it by Thursday."

I get the appeal. I do. Clarity is comforting. Knowing your job description is comforting.

But comfort and speed rarely live in the same room. And right now, the companies that are shipping fastest are the ones where people pick up whatever instrument the song needs, not the one their job title says they play.

The org chart isn't going to disappear. I'm not naive enough to believe that. Companies need structure. People need roles. Somebody has to know who approves the budget and who talks to the customer when things go sideways.

But the org chart should describe how decisions flow, not how skills are fenced off. It should be a routing system, not a caste system.

The jazz band still has a bandleader. Someone still counts off the tempo.

They just don't tell the bassist she's not allowed to solo.