Organizational Design Should Create Value - not Just a New Org Chart

Most organizational design efforts start in the wrong place: the organizational chart.

Leaders begin moving boxes, changing reporting relationships, consolidating departments, and debating spans of control. The resulting structure may look cleaner, but that does not necessarily mean the organization will work better - or create more value.

At Stonehill, we believe organizational design should start with a much more fundamental question:

How does the organization need to work to deliver its strategy?

For CEOs and private equity firms, this distinction is particularly important. Organizational design should not simply clarify who reports to whom. Done correctly, it should become a powerful value-creation lever—helping accelerate revenue growth, capture acquisition synergies, improve margins, increase productivity, and create an organization capable of scaling.

That philosophy led us to develop the Stonehill MODERN™ Organizational Design

Methodology: Map, Own, Design, Enhance, Render, Navigate.

The methodology connects how work gets done with who owns it, how performance is measured, how the organization should be structured, where AI and automation can improve performance, and whether the resulting organization can actually deliver the financial and operational objectives expected of it.

M - Map How the Organization Works

Before designing the organization, we need to understand how it creates value.

Stonehill begins by mapping the operational journey—the end-to-end flow of work across the enterprise. We look at how an opportunity becomes revenue, how a customer moves through the organization, how products or services are delivered, how decisions are made, and how supporting functions enable the business.

The objective is not simply process documentation. We want to understand the architecture of the work.

Where are the handoffs? Where does ownership become unclear? Where are decisions delayed?

Where is work duplicated? Which activities create value, and which create friction?

For companies that have grown rapidly or completed acquisitions, this exercise can be particularly revealing. Different business units may be performing essentially the same work in different ways. Responsibilities may overlap. Functions may have been duplicated. Processes that worked at $100 million in revenue may no longer work at $500 million.

Mapping the operational journey creates a fact-based foundation for designing what comes next.

O - Own the Outcomes

Once we understand the work, the next question is simple:

Who owns it?

Stonehill establishes cascading roles and responsibilities from the enterprise level through functions, leadership positions, teams, and individual roles.

But responsibility alone isn't enough.

Every important responsibility should be complemented by a measurable KPI.

If a leader owns customer retention, there should be a measurable retention outcome. If someone owns sales performance, there should be measurable revenue, pipeline, conversion, or margin expectations. If a function owns integration synergies, the expected savings and timing should be visible.

This creates a direct connection between responsibility and performance.

It also helps eliminate one of the most common organizational problems: multiple people believing they are involved in an outcome without anyone clearly owning it.

For private equity-backed companies, these KPIs can cascade directly from the value-creation plan. Revenue growth, cross-selling, customer retention, gross margin, procurement savings, working capital, integration synergies, and productivity objectives become organizational accountabilities—not simply numbers in a board presentation.

D - Design the Organization

Only after we understand the work and establish accountability do we design the organizational structure.

This is where the org chart finally enters the process.

Stonehill determines how responsibilities should be grouped into roles, where those roles should reside, how functions should be organized, and how reporting relationships should work.

We evaluate management layers and spans of control, but we don't believe there is a universal "correct" number of direct reports. The appropriate span depends on the complexity of the work, the capabilities of the team, management responsibilities, geographic dispersion, decision requirements, and other operating realities.

We also address the matrix organization.

Vertical reporting relationships tell only part of the story. Modern organizations also require horizontal capabilities and standards that cross reporting lines.

We therefore consider both core competencies by organizational level and functional competencies by discipline.

A director may require a common set of leadership, financial, strategic, and people-management capabilities regardless of function. At the same time, a finance director, operations director, and technology director each require distinct functional competencies.

The result is an organizational blueprint designed around the work - not inherited reporting relationships.

E - Enhance with Process Improvement, AI and Automation

Once the initial organization has been designed, we challenge it.

This is an increasingly important part of organizational design because the organization we needed five years ago may not be the organization we need today.

Stonehill examines the work and asks a series of questions.

Can we eliminate it?

Can we simplify it?

Can we standardize it?

Can we centralize it?

Can we automate it?

Can AI augment it?

Can we completely reinvent how it gets done?

This is where organizational design intersects with process engineering, technology, AI, and automation.

The objective is not to implement AI simply because it is available. The objective is to determine where technology can meaningfully change the economics or performance of the organization.

AI might increase sales capacity without proportionally increasing headcount. Automation might eliminate repetitive administrative work. Better workflow technology might reduce handoffs and management requirements. AI-enabled analytics might dramatically increase the amount of information a manager can effectively oversee.

These changes can affect roles, staffing requirements, spans of control, capabilities, and ultimately organizational structure.

That is why we believe optimization should occur after the initial design but before the organization is finalized.

R - Render the Organization

This is where Stonehill's approach moves beyond traditional organizational design.

We don't believe a proposed organization should simply "look right."

It should be modeled.

Stonehill renders the proposed organization as a quantitative performance model using the KPIs and operating assumptions the business is expected to deliver.

Consider a growth-oriented company.

A revenue target can be translated into customers, opportunities, transactions, projects, or other units of demand. Those units can then be translated into workload, capacity requirements, roles, staffing, and management requirements.

The logic might look something like:

Revenue → Demand → Workload → Automation → Capacity → Roles → FTEs → Management Load → Cost → EBITDA

The specific modeling columns differ by company, but the principle remains the same.

We work backward from the performance the organization is expected to produce.

This allows management to pressure-test the design under different scenarios.

What happens if revenue grows 30 percent?

Where does the organization run out of capacity?

Can the sales organization support the growth plan?

Does automation allow the company to absorb additional volume without equivalent headcount growth?

Are the proposed spans of control realistic?

How much of the acquisition synergy target is actually reflected in the organization?

What happens to EBITDA?

The organizational model can then be refined before major changes are implemented. For CEOs and private equity sponsors, this creates something particularly valuable: a measurable connection between organizational design and the value-creation plan.

N - Navigate the Change

Even the best organizational design creates little value if it isn't successfully implemented.

The final stage of MODERN™ is therefore to navigate the organization from the current state to the future state.

This includes leadership alignment, talent decisions, role placement, communications, training, governance, KPI reporting, implementation of AI and automation initiatives, and ongoing change management.

The objective is not simply to announce a new organization.

It is to make the new organization operational.

Leaders need to understand their responsibilities. Employees need to know what is changing and why. New management processes need to operate. KPIs need to become visible. Decisions need to move to the appropriate level. Technology and automation need to be adopted. Management needs a mechanism for identifying problems and correcting them quickly.

For private equity sponsors, this stage also creates greater transparency into value realization. Initiatives can have owners, milestones, financial expectations, and measurable outcomes that connect directly back to the investment thesis.

From Organizational Design to Enterprise Value

The fundamental idea behind MODERN™ is straightforward:

Organizational design should create measurable business value.

On the revenue side, better design can improve sales coverage, customer experience, decision speed, cross-selling, capacity, and scalability.

On the cost side, it can eliminate duplication, capture acquisition synergies, simplify management structures, consolidate capabilities, automate work, and increase productivity.

And on the execution side, it creates something equally important: accountability.

Strategy becomes work. Work becomes responsibility. Responsibility becomes measurable performance. Those responsibilities determine the organizational structure. Technology improves the structure. Modeling proves whether it can perform. Change management makes it real.

That is the logic behind the Stonehill MODERN™ Organizational Design Methodology:

MAP → OWN → DESIGN → ENHANCE → RENDER → NAVIGATE

We don't start with the org chart. We earn the org chart.