Blog

When does a company need enterprise organization design?

The signals that a company has outgrown its structure, and what changes when organization design starts to work at enterprise scale.

A lot of the CEOs and CHROs we talk with describe some version of the same moment. The company that used to run on one leader’s judgment and a handful of trusted lieutenants has grown past the point where that works, but nobody ever agreed on when, or what should replace it.

The signal is rarely the org chart itself

It shows up as symptoms: decisions that used to take one conversation now take a committee, two business units quietly building the same capability, a leadership team that agrees on strategy in the room and disagrees on it by the time it reaches the field. The structure did not break. It simply stopped matching a company that had outgrown it.

What does “enterprise” mean in organization design?

It means the organization has crossed from being one business into being a portfolio of businesses, or functions, that need to operate as one company without being run by one person. Most of the companies where we do this work sit somewhere between $500 million and $8 billion in revenue: past the size where a single leadership team can hold every decision in their heads, and short of the scale where a fully built corporate center runs the business for them.

The transition has a few reliable tells

A second business unit, product line, or geography exists for the first time, and it isn’t obvious which decisions belong to the center and which belong to the business. A founder or long-tenured leader is still, informally, the person every hard call routes through, whether or not that is written down anywhere. A board, an investor, or a first-time public filing is asking for a level of formal governance the company has never needed before. Individually, none of these is urgent. Together, they are usually the moment.

When does a company need enterprise organization design?

When the informal system that got the company to this size stops being able to carry it further: usually the moment above, where structure, governance, or decision rights have to become explicit because too much of the company is now running on unwritten understanding. Waiting rarely fixes it. The same tensions tend to resurface at the next planning cycle, the next reorg rumor, or the next good executive who leaves frustrated that nobody could tell them who owned what.

What changes with the redesign

The work is the same discipline we bring to any engagement: get the operating model right first, then treat structure, governance, and decision rights as one connected system rather than a chart redrawn in isolation. What changes at enterprise scale is the number of things that have to hold together at once: multiple business units, a corporate center that adds real value instead of overhead, and a leadership team that can make decisions without the founder in the room.

Enterprise organization design is not a bigger version of a small reorg. It is the moment a company decides, on purpose, how it will run once no single person can run all of it. Companies that make that decision early tend to make it calmly. The ones that wait usually make it during a crisis instead.

View all blogsNext postIf AI handles the code, where does the engineering actually go?