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.
What are the most common reasons companies bring us in?
Six problems account for nearly all of the advisory work we do, roughly 85 percent of it; the rest is training a client’s own team to run the process themselves.
Most of the time, it starts with a new strategy or a new capability the business needs to compete. A major shift in strategy has to become real: divergent units need to operate as one global business, or a company needs to sell an integrated solution across what used to be separate product lines. Or the company needs a capability it does not have yet, building AI into how the business runs, or standing up the function and infrastructure a strategy depends on.
Sometimes the trigger is structural. A matrix already exists and is not working: the primary organizing logic is unclear, or the connections between functions and businesses are too weak for decisions to actually get made. Or the company is integrating an acquisition, standing up a business it just divested, or incubating something new inside itself for the first time.
And sometimes it is about what comes next. A leadership succession is approaching, and the organization needs to be ready for it, not just the successor: a phased transition plan and a structure that does not depend on one person’s memory. Or the company has simply accumulated layers and P&Ls that no longer earn their keep, and leadership wants to simplify the structure and free the resources for growth instead of overhead.
When does a company need enterprise organization design?
Any one of the problems above is usually enough on its own: the moment structure, governance, or decision rights have to become explicit because too much of the company is 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.