Assessing the Legacy Organizations

2.1 Conducting a Rapid Current-State Organization Assessment

A rapid current-state assessment is a structured diagnostic of the organizations entering the integration. Its purpose is to establish enough evidence to support major design decisions without allowing documentation of the existing state to consume the entire project. The integration team should focus on the organizational characteristics most likely to affect value creation, business continuity, leadership choices, and the feasibility of the target model.

The assessment should begin with a clear set of questions. These usually include: How is each organization structured? Where do important accountabilities sit? Which activities are centralized or decentralized? Where are there obvious overlaps? Which capabilities differentiate the business? Where are decision rights unclear? Which leaders, teams, or processes are operationally critical? What organizational problems already existed before the transaction?

A useful diagnostic combines quantitative data with management judgment. Quantitative information typically includes headcount by function and level, reporting relationships, spans of control, management layers, employee location, compensation bands where appropriate, vacancies, contractor populations, and organizational cost. Qualitative evidence comes from leadership interviews, employee discussions, process documentation, governance materials, organizational surveys, and observation of how decisions actually move through the business.

The team should request data early, because organization datasets are rarely as clean as expected. Human-resources systems may contain outdated reporting lines, inconsistent job families, duplicate employee records, or different definitions of management levels across the two companies. Contractors may sit outside formal headcount data despite performing essential work. Employees may be administratively assigned to one function while operationally serving another. Data validation is therefore part of the assessment rather than a preliminary administrative exercise.

Leadership interviews should be structured around facts and examples rather than broad opinions. Asking whether decision making is “effective” usually produces general answers. Asking who approved the last major pricing exception, how long it took, which functions were involved, and where the process stalled produces actionable evidence. Similarly, instead of asking whether a function is appropriately staffed, ask which activities absorb the most capacity, which work is routinely delayed, and which roles the business could not operate without.

The diagnostic should explicitly distinguish three categories of findings. Integration issues arise because the transaction brings together two different organizations, such as duplicate finance teams or conflicting account ownership. Legacy issues existed independently of the transaction, such as excessive management layers or unclear decision rights within one company. Transaction-created risks emerge because integration itself may destabilize a previously workable arrangement, such as the potential loss of a key technical team.

This distinction matters because integration should not become an excuse to redesign everything. Some legacy problems should be addressed during integration because the transaction creates a rare opportunity for change. Others should be deferred if solving them would add complexity without materially improving transaction outcomes. The assessment should help leadership make that choice consciously.

Joint ventures require particular attention to organizational boundaries. The assessment should document which people, processes, technologies, contracts, licenses, facilities, and management capabilities currently reside in the parents. If the venture will receive only selected assets or employees, the team should identify the capabilities those resources currently depend on. A contributed business may appear operationally self-contained until the assessment reveals reliance on a parent treasury function, enterprise technology platform, legal team, or procurement organization.

The output should be concise: a current-state fact base, key organization metrics, major differences between the legacy organizations, critical risks, and a short list of implications for design. A rapid assessment is successful when it tells executives what they need to understand before making integration choices, not when it produces the most comprehensive description of the past.

2.2 Mapping Functions, Business Units, Reporting Lines, Spans, and Layers

Organization mapping turns raw employee and reporting data into a view of how managerial responsibility is distributed. The objective is not simply to reproduce existing organization charts. The analysis should make differences visible across functions, business units, management levels, geographies, and organizational units so that the integration team can identify structural patterns that warrant attention.

Start by establishing a common taxonomy. Two companies may use the same words to describe different work or different words to describe essentially the same activity. One organization may classify pricing specialists within finance while another places them in commercial operations. One may treat plant engineering as an operations function while another considers it part of engineering. Comparing headcount before normalizing these definitions can create misleading conclusions about duplication or efficiency.

The integration team should therefore map employees and organizational units into a common set of functions and, where useful, subfunctions. The taxonomy should be sufficiently detailed to reveal meaningful differences without becoming so granular that every unique job receives its own category. A typical corporate-function map might distinguish financial planning and analysis from accounting, or talent management from human-resources operations, because those activities may have different target-state implications.

Business-unit mapping should show the primary dimension by which each organization is managed. That dimension may be product, customer segment, geography, legal entity, channel, site, or a combination. Matrix organizations require particular care. Formal reporting may show one hierarchy while budgets, performance management, or resource allocation follow another. Understanding which axis carries real authority is more useful than merely documenting dotted-line relationships.

Reporting-line analysis should identify who reports to whom, but the team should also test whether formal reporting reflects operational reality. Senior specialists may exert substantial authority without direct reports. Functional leaders may technically report to business-unit presidents while receiving most priorities from corporate functional heads. Acquired businesses may rely heavily on founders whose influence extends far beyond their formal titles. These realities affect how easily responsibilities can be reassigned.

Span-of-control analysis provides a useful indicator of organization structure but should not be applied mechanically. A manager with three direct reports is not necessarily inefficient, nor is a manager with twelve necessarily effective. Appropriate spans depend on task complexity, employee experience, geographic dispersion, degree of standardization, managerial workload, and the extent to which team members require coaching or coordination.

The analysis is most useful when it highlights outliers and patterns. Large populations of managers with one or two reports may indicate excessive layering, historical accommodation of individual careers, or fragmented work. Very broad spans in complex environments may indicate overloaded managers and weak supervision. Differences between comparable units may reveal opportunities for redesign or may point to legitimate operational differences that require investigation.

Layer analysis examines the number of managerial levels between the chief executive or business-unit leader and frontline employees. Excessive layers can slow information flow, increase organizational cost, blur accountability, and create roles whose primary purpose is aggregating information for the next level. Too few layers, however, can leave senior executives directly managing excessive organizational complexity.

The team should map layers consistently across both organizations rather than relying on titles. A “vice president” in one company may have responsibility comparable to a “director” in another. Leveling should therefore consider role scope, decision authority, organizational scale, reporting position, and managerial responsibility. This becomes especially important when leadership appointments and title harmonization are politically sensitive.

Location should also be integrated into the map. Knowing that two companies each have 300 finance employees reveals less than knowing where those employees sit, which activities they perform, whether they serve global or local businesses, and which locations have critical infrastructure or labor constraints. Location analysis often becomes essential when shared services, site consolidation, or regional structures are under consideration.

For joint ventures, mapping should extend beyond the proposed venture workforce. The team should show parent-company capabilities that support the contributed operations today. These dependencies may need to become venture roles, transitional services, long-term parent services, or third-party support. Without this extended map, the venture may be designed around visible headcount while overlooking essential work performed elsewhere.

The result should be a comparable structural view of both organizations that allows executives to see where they differ and why those differences matter. The map becomes a diagnostic tool for subsequent decisions about structure, duplication, management layers, role placement, and organizational scale.

2.3 Identifying Role Duplication, Capability Gaps, and Critical Dependencies

The most important current-state findings often concern three different questions: Where do the organizations perform the same work? Where is essential capability missing or insufficient? Where does the business depend on people, systems, or organizational relationships that may be disrupted by integration? These questions should be analyzed separately because each leads to different actions.

Role duplication exists when multiple positions perform substantially overlapping work that will no longer require the same level of parallel capacity in the combined organization. Duplicate chief financial officers in two companies that will become one legal and managerial entity are an obvious example. Duplication becomes less straightforward further down the organization, where apparently similar titles may represent different customers, products, technologies, geographies, or workloads.

The team should therefore assess activities, not merely titles. Two “directors of operations” may have entirely different responsibilities. Conversely, identical work may be performed under unrelated titles. A role comparison should examine purpose, principal activities, decision rights, organizational scope, required expertise, and workload. Only then can the integration team determine whether roles are duplicative, complementary, or both.

Duplication should also be separated from excess capacity. Two companies may each need payroll specialists before the transaction, but a combined organization may require fewer because the work can be consolidated. That is an integration-driven efficiency. Alternatively, one legacy organization may already be overstaffed relative to its operating requirements. Treating both situations as simple “duplicate roles” can obscure the actual source of savings and lead to weak implementation assumptions.

Capability gaps are the opposite problem. The target business may require capabilities that neither organization possesses at sufficient scale or maturity. A larger combined enterprise may need stronger investor relations, enterprise risk management, category management, cybersecurity, integration architecture, regulatory affairs, or strategic-account management. Growth into new markets may create requirements that were unnecessary in either legacy company.

A gap can also emerge because integration removes informal support that previously compensated for a weak formal capability. An acquired subsidiary may have relied on its parent for legal review or treasury expertise. A founder-led company may have made critical product decisions through a small group of experienced executives without formal processes. Once those relationships change, the new organization may need explicit roles or governance mechanisms to replace them.

The diagnostic should rate capabilities according to the future business requirement rather than according to current internal benchmarks alone. A capability that was adequate for a $300 million company may be insufficient for a $1 billion combined enterprise. Conversely, the acquiring company’s process should not automatically be considered superior simply because it belongs to the larger organization.

Critical dependencies require a different lens. These are relationships or resources on which important business outcomes depend. Dependencies may involve key individuals, systems, shared-service teams, technical centers, regulatory licenses, customer relationships, suppliers, facilities, or parent-company functions. The integration risk arises when a structural change unintentionally breaks that dependency.

Person-dependent processes deserve special attention. Some organizations operate effectively because experienced individuals know whom to call, how to solve exceptions, or how to coordinate across poorly defined boundaries. These arrangements may not appear in process documentation. Interviews should therefore ask where the business relies on individual knowledge or relationships that cannot easily be replaced.

A practical analysis classifies findings into four actions: consolidate, preserve, build, or protect. Duplicative activities may be candidates to consolidate. Differentiating strengths may need to be preserved. Missing future-state capabilities may need to be built. Fragile dependencies may need to be protected until a durable alternative is in place.

This framework is particularly valuable for joint ventures. Parent companies may contribute similar positions that should not both transfer, yet the venture may simultaneously lack capabilities that the parents historically provided outside those teams. The assessment should clarify what work the venture needs, what it can perform itself, what capabilities must be recruited or developed, and which parent dependencies require formal service agreements.

The resulting fact base should inform organization design without predetermining individual personnel decisions. Identifying two roles as duplicative does not determine which person should remain. Similarly, identifying a capability gap does not automatically mean creating a new department. The purpose of the assessment is to define the organizational requirement first; staffing choices can then follow from the target model.

2.4 Assessing Management Processes, Interfaces, and Decision Bottlenecks

Formal structure explains only part of organizational performance. Companies with similar organization charts can operate very differently because their management processes, decision rules, and cross-functional interfaces differ. A current-state assessment must therefore examine how priorities are set, resources are allocated, performance is reviewed, issues are escalated, and decisions move across organizational boundaries.

Management processes include recurring mechanisms through which executives run the business. Examples include strategic planning, budgeting, forecasting, capital allocation, sales and operations planning, product portfolio reviews, talent reviews, performance management, risk committees, operating reviews, and investment approvals. During integration, these processes become important because the combined company cannot operate indefinitely with two competing management cadences.

The team should identify the major recurring processes in each organization and understand their purpose, participants, decision rights, frequency, required information, and outputs. The objective is not to inventory every meeting. It is to understand which forums genuinely control resources and decisions and which primarily share information.

Interfaces deserve equal attention. Many organizational failures occur not within functions but between them. Sales and operations may disagree over demand commitments. Product teams and commercial teams may have unclear launch responsibilities. Corporate functions may impose standards that business units consider impractical. Regional and global leaders may compete over staffing or customer ownership. Integration can intensify these problems by combining organizations with different expectations about who leads each interface.

A useful interface assessment follows important business decisions or workflows across functional boundaries. For example, the team might trace how a new product moves from concept approval through engineering, pricing, manufacturing, sales launch, and customer support. At each handoff, the assessment asks who owns the decision, who must provide input, what information is required, and what happens when stakeholders disagree.

Decision bottlenecks should be identified through examples rather than anecdotes about bureaucracy. The team should examine several significant recent decisions and reconstruct the path each took. How many approvals were required? Were decision rights clear? Did senior executives become involved because lower levels lacked authority? Was the same issue reviewed in several forums? Did missing data delay the choice, or was the real problem disagreement about accountability?

Common bottlenecks include decisions that require too many sequential approvals, matrices in which several leaders effectively hold veto rights, escalation of routine matters to senior management, duplicated governance forums, unclear thresholds for local versus corporate authority, and processes in which consultation is mistaken for approval. Another common problem is the absence of a defined decision owner, resulting in consensus-seeking without closure.

The assessment should also identify differences in management philosophy. One company may operate through detailed corporate standards and formal committees; another may delegate broad authority to business leaders. Neither approach is inherently superior. The question is whether the target business requires consistency, local responsiveness, speed, control, or some combination, and which legacy practices best support those needs.

Joint ventures make decision analysis especially important because management authority is deliberately constrained by shareholder rights. The team should distinguish decisions that management can take independently from matters reserved for the board or shareholders. It should also identify where parent-company input is advisory, where consent is contractually required, and how disagreements are escalated. Without this clarity, the venture may either operate too cautiously or inadvertently exceed delegated authority.

One practical output is a decision inventory covering twenty to thirty high-value recurring decisions. Each entry can show the current owner in each legacy organization, participants, approval path, cycle time, known pain points, and implications for the target model. The inventory does not need to cover every managerial choice. It should focus on decisions that materially affect customers, economics, risk, employees, or operational speed.

The goal is to understand how structure and management processes interact. Moving a team on an organization chart will not resolve a bottleneck if decision authority remains unchanged. Likewise, redesigning governance without addressing contradictory reporting relationships may not improve performance. Current-state assessment should make these interactions explicit so that later target-state design addresses the actual operating problem rather than its visible symptoms.

2.5 Current-State Assessment Checklist and Diagnostic Templates

A disciplined current-state assessment should produce a common fact base quickly enough to inform integration decisions. Standard templates help create consistency across functions and business units, particularly when several teams are conducting assessments in parallel. The templates should be lightweight: their purpose is to structure judgment and make comparisons possible, not to create documentation for its own sake.

The first tool is a current-state assessment checklist. For each major function, business unit, geography, or contributed joint-venture operation, the team should confirm that it has examined the following:

• Organizational purpose, scope, and principal responsibilities.
• Headcount and organizational cost by activity, level, and location.
• Formal reporting structure, management spans, and organizational layers.
• Major leadership roles and practical decision authority.
• Critical capabilities, specialist skills, and institutional knowledge.
• Potentially duplicative roles or activities.
• Known capability gaps or capacity constraints.
• Critical customer, operational, regulatory, technology, and people dependencies.
• Major recurring management processes and governance forums.
• Important cross-functional interfaces and known decision bottlenecks.
• Current organizational pain points and previously planned changes.
• Implications for Day 1, interim-state, and target-state design.

The checklist should be supported by a function diagnostic template. A one- or two-page profile for each function can summarize its mandate, organization structure, headcount, locations, leadership, major activities, management processes, dependencies, and key findings. Using the same format for both legacy organizations makes differences immediately visible.

A second tool is the organization metrics dashboard. Useful measures can include total headcount, managers as a percentage of employees, average and median spans of control, number of organizational layers, proportion of managers with very narrow spans, headcount by location, vacant positions, contractor population, and management cost. Metrics should be segmented where necessary because enterprise averages can conceal important variation.

These measures are diagnostic signals, not automatic targets. A narrow span may be appropriate for highly complex technical work. A broad span may be reasonable in a standardized service center. Benchmarking can help identify questions, but organization design should not become an exercise in forcing every unit toward a generic span or layer standard.

A third tool is the role and capability matrix. Rows represent major roles or capabilities; columns capture the legacy organizations, future requirement, duplication assessment, criticality, talent risk, and preliminary implication. This template is particularly helpful in situations where titles differ or where leadership needs to distinguish between overlapping positions and complementary expertise.

A fourth tool is the dependency map. The team lists critical business activities and identifies the people, functions, systems, facilities, licenses, suppliers, or parent-company services required to perform them. Dependencies should be rated according to impact and replaceability. A dependency with high business impact and no near-term substitute becomes an explicit integration risk and should have an owner and mitigation plan.

A fifth tool is the decision and interface diagnostic. For each selected decision, document the current decision owner, contributors, required approvals, typical cycle time, escalation path, and pain points. Comparing the same decision across both organizations often reveals major differences in management philosophy. It also creates concrete evidence for later target-state decision-rights design.

The assessment team should synthesize these materials into a short executive diagnostic rather than forwarding raw templates to senior leadership. The synthesis should highlight the handful of findings that matter most for integration. A useful structure includes major structural differences, likely duplication, differentiating capabilities, important gaps, critical dependencies, decision bottlenecks, and immediate risks requiring action before target-state design is complete.

Each finding should be written as an implication rather than a description. “Company A has five layers while Company B has seven” is descriptive. “The acquired commercial organization contains two additional management layers that appear to slow account-level decisions and should be tested during target organization design” is actionable. Similarly, “the venture depends on Parent A for treasury” becomes more useful when expressed as “the venture requires either a formal treasury service agreement or an independent treasury capability before parent support can be withdrawn.”

The team should also maintain a clear distinction between validated facts, working hypotheses, and decisions. A current-state diagnostic may suggest that two roles are duplicative, but that conclusion remains a hypothesis until their responsibilities and future requirements are understood. Likewise, identifying a weak management process does not mean the target company must adopt the other organization’s process. Labeling evidence appropriately prevents preliminary observations from becoming accidental commitments.

Before closing the assessment phase, the integration leader should test whether the fact base is sufficient for the next set of decisions. The key question is not whether every organizational detail has been documented. It is whether leadership can now compare the legacy organizations on a consistent basis, understand the most consequential differences and dependencies, and make informed choices about the target operating model.

A strong current-state assessment creates disciplined selectivity. It reveals which parts of the legacy organizations can be consolidated, which capabilities should be protected, where new capabilities must be built, and which dependencies constrain the timing of change. It also exposes the difference between the formal organization and the way work actually gets done. That understanding is essential before leaders begin drawing the combined structure, assigning accountability, or selecting the practices that will define the future organization.