
Organizational design
What Organizational Design Looks Like When It’s Done Right
One company outsourced, one flattened the layers and one moved people into new jobs. Each answer came from assessing the problem underneath.
The minute people hear “organizational design,” the layer below the C-suite asks one question: Is my job at risk?
Sometimes the honest answer is yes. After an acquisition, finance, human resources and marketing usually end up with two people in the same role. Trimming duplicate roles leads to a leaner, more efficient organization. The organizational design work we do often starts somewhere else, and the best results look different at every company. Take three companies: one had its experts stuck on the wrong work, one had a structure too deep to see through and one needed a new structure in a labor market too thin to rehire from.
A midsize company with experts focused on noncore activities
In early 2021, we worked with a midsize healthcare technology firm. Its scientists use big data analytics to turn real-world patient health data into regulatory-grade evidence.
To sustain its growth, the company needed more of its workforce’s time on its core service. Leadership didn’t want to cut anyone, and with reason: few people had the statistical, technical, scientific and healthcare industry skills it needed, and recruitment was limited to the U.S., where that talent was most expensive.
Leadership assumed nobody outside the U.S. could do any of the specialized work. So the question became which work counted as core processes that needed specialists and which noncore work could move to lower-cost providers. Value stream mapping answered it. Through an RFP, we found providers in India, the Philippines and Eastern Europe who could take on about 80% of the ancillary work. They charged roughly a third of the in-house cost. The company kept its core processes in-house, started small and grew the outsourcing once it worked.
The result: Senior staff refocused on the highest-value work, with lower management overhead and faster turnaround, and the company could scale up and publish more research at minimal cost to its workforce.
A 7,000-person company where utilization hid the problem
An engineering services firm had more than 7,000 people, nearly all billable and tracked at 75% utilization or higher. Leadership saw an efficient workforce and had good reason to resist cuts: eliminate a billable person and you lose revenue. That took the usual utilization review off the table.
A review of spans and layers turned up the problem: depth. The organization ran 10 layers deep, and some leaders oversaw 600 or 700 people. By layer 3 or 4, communication thinned. So we looked at profitability by account and by subdepartment. Utilization ran high overall, yet some accounts still lost money, often on legacy contracts nobody had revisited.
Utilization can hide a lot. An employee can log 40 hours against a fixed-fee project and do 10 hours of real work. That person looks busy, and the company gets a fraction of what they know how to do. The same held for managers stacked 10 layers deep. We recommended moving toward six layers and shifting excess managers into billable client roles, where their experience earns revenue again. My colleague Brian Twomey tells the story of this project from his side in “Organizational Design Projects Have an Image Problem.”
The result: With fewer layers between leadership and front-line teams, the new design reduced management costs, improved communication and sped up decisions.
A small company that moved people to new roles
Leadership at a medical-legal services company already knew its structure no longer worked. It wanted to reorganize its invoicing, collections and servicing functions while keeping as many people as possible. The local labor market was too thin to hire from, and recruiting new people to the area was a hard sell.
That ruled out the usual organizational design playbook of cutting roles in some departments and hiring in others.
We matched people to the new roles by tenure and skill set. About four dozen people moved into other departments, mostly laterally, with some moving into a higher salary band. That took HR policy work, a benefits review and a training program. Cutting and rehiring would have been easier, but it would have cost the company its culture.
The result: The company kept people who knew the business and went into its growth plans with a stronger workforce.
What good organizational design takes
Each company needed a different organizational design, and the same four things made each recommendation hold. Two depend on leadership, while two depend on how the work gets done.
Buy-in, test early.
Many leaders agree with the plan until the data points to their team members—the people who have grown with the company (and with them). The most common objection we hear: “We expect growth next year.” Sometimes we hear it after 24 months of flat revenue.
One decision, made once.
Cuts that come every few months leave everyone wondering whether today is their last day, and that confidence takes a long time to win back. When companies run it themselves, one round at a time, the disruption over the next year and a half can cost millions and wear on the culture in ways nobody can put a number on.
No surprises at the end.
An organizational design project with us runs 12 to 14 weeks. By week six, we have a hypothesis for the future organization, and we spend the rest of the time testing it with the top three or four management layers. By the final readout, leadership has weighed in and knows what’s coming, so the change itself goes more smoothly.
Depth.
We typically work down to layer 4 or 5, map processes end to end, from order entry to billing, and run day-in-the-life studies. Published benchmarks give us an anchor; the work in each department sets the real span target. Our modeling tools, built over years and faster now with AI, get us to a starting point quickly. Then the final recommendation comes from looking people in the eye and asking hard questions.
Our modeling tools get us to a starting point quickly. The final recommendation comes from looking people in the eye and asking hard questions.
Done right, organizational design leaves leaders knowing their company and the people who run it. CEOs tell us they didn’t know a span should have been six or eight, that a department was that lean or that one region was spread so thin. If you’re a new CEO, or an operating partner with a fresh add-on acquisition, I can’t think of a better place to start.
Start with one portfolio company. Prove it. Scale on your timeline.
Tell us which one is behind plan and what the model assumed. You’ll talk to someone who has done the work.
Talk to an advisor