Your AI Rollout Is Stalling on Your Org Chart

Your best idea this quarter is probably sitting in someone's inbox, waiting for a yes. Or sitting on a "roadmap" waiting for funding and focus through an outdated delivery process. This is typically chalked up to the way things have always worked, but there is a hidden mechanism doing the quiet work. The org chart decides who you can reach, whose permission you need, and how far a good idea has to travel before it can move. You do not see it. You feel it every time the work has to climb your reporting line and cross into another team's before anything happens.

None of this is new to anyone who has worked inside a company. Approval chains have always been slow, and for years that was acceptable. The market rewarded the big, careful, multi-year bet, and a long planning cycle made sense because the technology underneath it barely moved. AI inverted that. The capability now turns over in months, so the model you wanted last quarter is already replaced, the use case has shifted, and the moment the work was built for is gone before the last sign-off lands. The org chart did not get slower. The world it sits inside got faster.

The org chart was built to keep ownership clean. Every box knows its lane, its budget, and its boss. Decisions move up to someone with authority and back down to someone with a task, and within a single department that works. But AI work moves sideways. It crosses product, engineering, operations, and risk at once, and the org chart has no fast path across. It was built for a slower, more orderly world, the same one I have written about before, when the advice most of us still lean on took shape.

The Speed Problem Lives in the Structure

If this feels familiar, you are not the only one seeing it. The research keeps landing on the same uncomfortable point, that the thing slowing AI down is rarely the technology.

Walk into almost any company right now and you will find AI everywhere and nowhere at once, pilots in every function, a chatbot bolted onto the website, a dozen experiments running, and almost none of it woven into how the work actually gets done. McKinsey's latest numbers say the same thing, with 88 percent of organizations now using AI in at least one part of the business and only 7 percent having fully scaled it. Broadening that use, the firm notes, may require redesigning the workflows around AI so the work can run at scale.

So where does the rest of that work live, the part between starting and finishing? Boston Consulting Group breaks it down. In its 10-20-70 approach to deploying AI at scale, 10 percent of the effort is the algorithm, 20 percent is the technology and the data, and a full 70 percent is the people and process around it.

The model, the part everyone obsesses over, is the smallest slice. The 70 percent is the part nobody points to when AI stalls: who decides, who hands off to whom, whose sign-off the work needs, and how a decision moves from idea to shipped. That is not a technology problem. It is an org chart problem.

If the bottleneck is structural, then buying another tool or running another training cannot touch it. A new license does not redraw a sign-off chain, and a workshop does not shorten the road a decision travels before it gets a yes. You can buy the best model on the market and watch it stall anyway, because the software was never what slowed you down. So if your last two AI initiatives stalled in roughly the same spot, that is not a coincidence, and it is not a sign your team is behind.

What We Built Instead of Waiting

Last November, my own team stopped waiting for the org chart to catch up.

We are not restructuring, nor are we changing the org chart. We are building out a new operating model on top of the structure we already have, so the work can move now. My team began merging its efforts with our engineering group and an adjacent technology team, organizing around the experiences we want to ship for customers rather than around the boxes we each report into. None of this is set in stone, and we are still iterating on the fly, reshaping the model as we learn what the work needs. But we are already operating differently than we used to, and we are blurring the traditional lines of the org chart as we go.

We have seen it most in how fast we now ship alongside our engineering partners. They can iterate on customer-facing features at a speed that would not have been possible a year ago, and our job is to keep pace. Accepting the status quo is no longer an option, because AI has changed what coding delivery looks like. So we did not wait for an org change. We worked out how to operate as one team, under a new way of thinking that puts speed and collaboration ahead of dotted lines.

All of that is the part you can measure. The shift I keep coming back to is harder to put a number on, and I describe it the same way every time. "It's amazing what can get accomplished when everyone is marching in the same direction." That alignment, more than any new box on the org chart, is where the speed comes from.

And this is only the start. The experiences our customers want do not live inside one team. They run across platforms owned by a different part of the company, a group we used to treat as someone else's problem and now treat as a partner. So we are building the connections that let both teams work in parallel instead of in silos. The question itself is shifting, from "what does my roadmap look like next year?" to "what do we need to build together to solve our customers' biggest problems?"

What You Can Build Without a Reorg

You probably cannot redraw your own org chart, and you do not need to. It can stay exactly where it is. What you can change is how fast your corner of the work moves, by building a small operating model on top of the structure you already have.

Two questions are worth your time this week. What would your ideal operating model look like, the one that lets your best AI work move at the speed it deserves? And what is the single thing standing in its way, a tool you are missing, or a mechanism you have not built?

You do not have to wait for the org chart to catch up. The fastest teams already stopped waiting, and started building.