How to Choose an Organizational Design Consultant: A Practical Guide for CEOs, CFOs, and PE Sponsors
Why Operator Experience Matters
Most organizational redesigns begin when a leader can feel the business becoming harder to run.
Decisions take longer. Customer issues move between departments without a clear owner. Revenue grows, but the organization adds people faster than it adds capacity. An acquisition creates duplicate teams and competing ways of working. Managers spend more time resolving internal friction than serving customers or improving performance.
At that point, someone suggests changing the org chart. It may be necessary. But moving boxes before understanding the business can preserve the problems under new reporting lines.
If you are a CEO, CFO, COO, or private equity sponsor choosing an organizational design consultant, the most important question is whether that person understands how to operate a business. A strong consultant can connect objectives to work, work to accountability, and accountability to a structure that delivers measurable results.
Organizational design is an operating decision
An organization exists to perform work and produce outcomes. Its design determines whether it can do so efficiently and consistently.
Consider a company that wants to double revenue over three years. The design questions extend well beyond who reports to whom:
Can sales identify, pursue, and close the required volume of opportunities?
Can operations fulfill the additional demand without sacrificing quality?
Where does work pass between commercial, operational, and support teams?
Who makes pricing, staffing, service, and investment decisions?
What work should be standardized, centralized, automated, or kept close to the customer?
How many people and managers will the future workload require?
Will the resulting cost structure support the company’s financial goals?
Those are operating questions. The org chart should reflect the answers.
The same principle applies to a cost reduction program or post-merger integration. Eliminating a role on paper does not eliminate the work that role performed. Combining two departments does not automatically combine their processes, systems, or customer responsibilities. A consultant must understand where the work will go and what will happen to performance.
The first test: Has the consultant operated a business?
An organizational design consultant does not need to have held every executive title. But the person leading the work should understand the consequences of decisions in a functioning operation.
Operators know that a clean model can break when an important customer needs an exception, a key manager leaves, a system cannot produce the required data, or demand rises faster than planned. They have dealt with the friction between functions, made tradeoffs under financial constraints, and been accountable when a plan did not work.
Ask prospective consultants about their direct experience:
What functions or operating programs have they led?
Have they owned a budget, a P&L, a transformation, or an integration?
What organizational decisions have they implemented personally?
What changed after their proposed structure went live?
Where did a design fail, and how did they correct it?
Look for specific answers about processes, decisions, capacity, customers, costs, and outcomes. A polished framework is useful. Evidence that the consultant understands what happens on Monday morning is more useful.
Why an HR-only lens can miss the core problem
Human resources is an essential partner in organizational design. HR leaders contribute critical knowledge about talent, compensation, employee relations, leadership development, employment requirements, and the human impact of change.
But those capabilities alone do not define the operating model.
Many companies assign organizational design to someone whose career has centered on benefits administration, employee relations, or HR policy. Those are important disciplines, but they do not necessarily prepare someone to redesign how a business creates value, calculate the capacity required to meet demand, or determine where process ownership should sit.
The concern is about the skill set leading the work, not the department in which the person works. An HR leader with deep operating model, process, and analytical experience can be an excellent organizational designer. A consultant from any background who lacks those abilities will struggle.
The strongest engagements combine perspectives. Operations explains how work is performed. Finance tests the economics. HR addresses talent and transition. Technology identifies constraints and opportunities. Leadership decides the strategic tradeoffs. The organizational design consultant must be able to bring those perspectives together.
Start with objectives, not reporting lines
Before reviewing the current org chart, ask what the business is trying to accomplish.
The objective might be to integrate seven acquisitions, improve margin, enter a new market, reduce decision time, scale a service model, or improve customer retention. Each objective has different implications for capabilities, processes, staffing, and leadership.
A consultant should translate broad ambitions into design requirements. For example, “improve customer experience” might require one owner for the full customer journey, faster resolution of service issues, better data at the point of contact, and a consistent handoff between sales and delivery.
Those requirements can guide structural decisions. Without them, leaders tend to negotiate reporting relationships based on current personalities and historical territory. The result may be politically acceptable while leaving the underlying operating problem untouched.
Ask: “What business outcomes will determine whether this organizational design succeeds?”
Map the process before assigning the people
The next step is understanding how the company actually works.
Follow a few important journeys from beginning to end: lead to order, order to delivery, issue to resolution, acquisition to integration, or demand to staffing. Examine the decisions, handoffs, systems, delays, and exceptions along the way. Compare the documented process with what employees and customers experience.
This work exposes organizational design problems that an org chart cannot show. Two functions may each believe the other owns a step. A senior executive may approve routine decisions because no one has delegated authority. Several teams may collect the same information because their systems do not connect. One role may quietly hold the entire process together.
A consultant who skips process analysis may create new departments around broken workflows. A consultant who understands the process can decide what should be simplified first and then design roles around the work that remains.
Ask: “Which end-to-end processes will you map, and how will what you find change the proposed structure?”
Make accountability explicit
People often describe an organizational problem by saying, “No one owns it.” Sometimes several people own pieces of it, but no one owns the result.
Effective organizational design identifies the outcomes the business needs, assigns clear ownership, and gives owners the authority and information required to perform. That includes decisions made within a function and decisions that cross functions.
A useful design should answer questions such as:
Who owns the customer outcome from sale through delivery?
Who decides when service levels conflict with cost targets?
Who is accountable for an integration synergy?
Who can change a process used by several departments?
What gets escalated, to whom, and when?
Accountability cannot be solved merely by adding a responsibility to a job description. The work, decision rights, measures, and management routines must support it.
Ask: “How will you resolve shared ownership and define decision rights across departments?”
Use analytics to test the design
An organizational model is a set of assumptions about work and capacity. Those assumptions should be examined before the company changes roles or makes staffing decisions.
The consultant should be comfortable working with data on revenue, demand, transaction volume, service levels, productivity, headcount, management layers, costs, and performance. Where the data is incomplete, the team should state its assumptions and show how the answer changes under different scenarios.
For a growth plan, the question may be whether sales and operations can support the target volume. For a merger, it may be which capabilities are genuinely duplicated and which are already at capacity. For a margin program, it may be whether work can be eliminated or automated before positions are removed.
A benchmark such as “one manager for every eight employees” may prompt a useful question. It cannot decide the right structure on its own. The nature and complexity of the work matter.
Ask: “What data will you use to model workload, capacity, headcount, and cost? What assumptions will leadership be able to challenge?”
Evaluate the proposed team, not just the firm
The partner who presents the proposal may not conduct the interviews, map the processes, build the model, or guide the implementation. Meet the people who will do those things.
Ask who has operating experience, who will lead the analysis, who will facilitate difficult leadership decisions, and who will be present when the new model goes live. Review a sample of the firm’s work, with client information removed if necessary. Useful artifacts might include an operational journey map, accountability framework, scenario model, role architecture, or transition plan.
The proposal should make the scope and responsibilities clear. A company making sensitive decisions about leadership, staffing, and performance needs experienced judgment throughout the engagement.
Ask what happens after the design is approved
A future-state chart does not implement itself.
Managers need to understand new responsibilities. Employees need to know how work and decisions will change. Performance measures may need to be established. Systems and processes may require updates. Leaders must identify problems as the new model begins operating and correct them quickly.
Ask whether the consultant will support leadership alignment, communication, role transitions, new management routines, and performance tracking. If those activities will be handled internally, identify the executive who owns them and the capacity available to do the work.
Ask: “What will be different in the first 30, 60, and 90 days after implementation, and how will we know whether the design is working?”
Warning signs when evaluating a consultant
Be cautious if a prospective partner:
Proposes a structure before understanding the objectives and workflows.
Treats the org chart as the main deliverable.
Relies on generic span-of-control benchmarks without studying the work.
Cannot explain how responsibilities and decision rights will change.
Promises savings without identifying where the work will go.
Has no method for testing capacity and financial assumptions.
Focuses exclusively on talent or HR administration while leaving operations out of the analysis.
Provides no plan for implementation, adoption, or performance measurement.
Cannot identify the experienced people who will do the work.
No method removes the judgment required in organizational design. A good consultant gives leaders the operating facts and financial implications needed to make those judgments well.
A better sequence for organizational design
The order of the work matters. Begin with the results the business needs. Understand the processes that produce those results. Establish ownership and decision rights. Then design roles, teams, reporting relationships, and management layers.
Next, examine where better processes, technology, AI, or automation can improve the model. Test the proposed organization against workload, capacity, headcount, cost, and financial goals. Finally, implement the change and measure whether it delivers the intended outcomes.
That is the logic behind Stonehill’s MODERN™ Organizational Design Methodology:
MAP how work, decisions, and value move through the business.
OWN the outcomes through clear responsibilities, decision rights, and KPIs.
DESIGN the roles, capabilities, structure, spans, and layers required.
ENHANCE the model through process improvement, technology, AI, and automation.
RENDER a quantitative view of workload, capacity, headcount, cost, and expected performance.
NAVIGATE implementation through leadership alignment, communications, governance, and change management.
The method begins with the business and ends with a functioning organization. The chart is a product of that work.
If your company is growing, integrating acquisitions, restructuring, or struggling with unclear ownership, Stonehill can help you assess how the business operates and design an organization equipped to deliver its objectives.
