The target operating model defines how the combined business will work once the most important integration choices have been implemented. It connects the strategic logic of the transaction to practical questions about leadership, accountability, organizational structure, functional roles, shared services, decision rights, and interfaces across the enterprise. Without an explicit target model, integration teams often make local decisions independently. Finance centralizes one process, commercial teams retain regional autonomy, technology builds common platforms, and business units establish their own governance. Each choice may be reasonable in isolation while producing an incoherent organization overall.
Target-state design should not be confused with drawing an organization chart. Structure is only one component. Management must also decide where work is performed, which activities are centralized or decentralized, who owns key decisions, how functions support business units, what capabilities remain distinct, and which interfaces require formal governance. The design should be sufficiently specific to guide integration without attempting to solve every process question before the organization has learned from operating together.
7.1 Defining Target Operating Model Principles
Target operating model principles provide the rules that management will use to make organizational and operating choices. They are valuable because integration creates hundreds of decisions that cannot all be resolved by the executive committee. If leaders agree on a small number of principles early, workstreams can make detailed choices that remain consistent with the overall strategy.
The principles should be derived from the integration thesis rather than from generic organizational preferences. A transaction designed primarily to capture scale may require substantial standardization and centralization. An acquisition intended to obtain an innovative capability may require greater autonomy around product development, talent practices, or investment decisions. A geographic expansion transaction may preserve local commercial authority while centralizing finance, risk, and selected corporate functions.
Good principles are directional enough to shape decisions but specific enough to resolve trade-offs. “Put the customer first” is unlikely to determine whether account authority should sit with global product teams or country leaders. “Maintain local account ownership for regulated customers while centralizing pricing and strategic-account governance” provides substantially more guidance.
Several dimensions commonly require explicit principles. The first is centralization versus decentralization. Leadership should define which decisions benefit from scale, consistency, control, or scarce expertise and which need proximity to customers, operations, or local markets. Treasury, cybersecurity standards, financial reporting, and enterprise architecture may benefit from central control, while customer service, local commercial execution, or plant scheduling may require delegated authority.
The second is standardization versus differentiation. A combined company should not automatically force every unit onto identical processes. Standardization creates value when common methods reduce cost, improve controls, enable shared data, or make talent easier to deploy. Differentiation is justified where customer requirements, regulation, business economics, or distinctive capabilities materially differ. The principle should explain where variation is acceptable rather than allowing every existing practice to claim uniqueness.
The third dimension is functional versus business-unit authority. Strong functions can create enterprise standards and professional depth but may distance decisions from business performance. Strong business units can move quickly but may duplicate capabilities or weaken enterprise control. The target model should specify which decisions functions own, which belong to business leaders, and where joint accountability is required.
The fourth dimension is global versus local authority. Multinational integrations often fail when headquarters designs a theoretically uniform model that cannot accommodate local legal, labor, regulatory, or customer requirements. A sound principle may establish a global default with documented local exceptions rather than treating every geography as either identical or entirely autonomous.
The fifth dimension is preservation versus absorption. If the target brings superior capabilities, leadership should identify them explicitly and determine how to preserve or propagate them. The buyer should not assume that its processes automatically become the target state. Integration creates an opportunity to select the better model, design a new one, or retain deliberate differences.
Operating model principles should also address service economics. Management should decide where scale justifies shared services, where specialized capabilities should sit in centers of excellence, and which activities remain embedded in business units. This helps functions distinguish between activities requiring proximity to the business and those that can be consolidated without harming responsiveness.
A concise principle set might include six to ten statements covering customers, accountability, centralization, standardization, talent, controls, technology, and geographic flexibility. Each principle should contain enough context to explain why it matters. Principles should also be tested against real decisions before approval. If two leaders can apply the same principle to the same question and reach opposite conclusions, the wording may be too abstract.
Joint ventures require additional principles concerning parent-company roles. Management should specify whether the venture is intended to become operationally self-sufficient, rely permanently on parent services, or follow a mixed model. Principles may also address neutrality between parents, information barriers, procurement from shareholders, intellectual-property access, and circumstances under which parent-company standards apply.
Once approved, the principles should be used as design criteria throughout the integration. Organization proposals, functional models, system decisions, and governance arrangements should state how they align with the agreed principles. This creates continuity between the transaction thesis and the eventual operating organization.
7.2 Determining Leadership Roles, Decision Rights, and Organizational Interfaces
Leadership and decision rights are among the most time-sensitive organizational choices in an integration. Uncertainty at the top quickly cascades downward. Teams delay decisions because they do not know who will own the outcome, employees speculate about future roles, and workstreams design processes around reporting relationships that may change. Management should therefore resolve leadership and authority early enough to provide direction without making premature decisions unsupported by facts.
Leadership selection should begin with roles required by the target operating model, not with the existing executives available from each company. The organization should first define the accountabilities, capabilities, geographic reach, and decision scope of the future role. Candidates can then be evaluated against those requirements. Starting with individuals and designing positions around them often preserves duplication and makes future restructuring harder.
The integration team should distinguish between permanent target-state roles and interim leadership required during transition. In some situations, immediate appointment of permanent leaders is feasible and desirable. In others, critical facts about business design, regulatory requirements, or organization structure remain unresolved. Interim arrangements can provide clarity without forcing a permanent decision, provided employees understand the temporary nature of the structure and when it will be revisited.
Decision rights require equal attention. An organization chart shows who reports to whom but does not define who decides. Management should identify the recurring decisions that most influence performance and integration effectiveness: pricing, capital allocation, customer ownership, hiring, product investment, supplier selection, technology standards, risk acceptance, facility changes, and major expenditures. Decision rights should specify who recommends, who provides input, who makes the decision, and who executes it.
Ambiguous shared accountability is especially dangerous. Two executives can be jointly responsible for an outcome while neither has final authority. For example, a regional president and a global product leader may both influence pricing, customer strategy, and resource allocation. Without explicit rights, issues are either escalated unnecessarily or resolved through informal power rather than designed governance.
Decision design should follow several practical principles. Decisions that require enterprise consistency or major capital commitments often belong at higher levels. Decisions requiring rapid customer or operational response should be delegated as close to the relevant activity as prudent. Highly technical decisions may require functional authority even when business leaders own the economic outcome. Decisions that cross organizational boundaries should have a single final decision maker whenever possible.
The target model should also define organizational interfaces. Interfaces are points where one part of the organization depends on another to accomplish work. Common examples include sales and product management, finance and business units, procurement and operations, technology and functions, shared services and retained organizations, or regional teams and global functions. Many integration problems occur not within functions but at these boundaries.
Each critical interface should specify what information, services, decisions, or outputs move between the parties. Service expectations, escalation mechanisms, planning routines, and performance measures may be necessary. For example, a centralized procurement function may own sourcing strategy while plant managers own day-to-day supplier performance. The interface must establish how specifications are defined, savings opportunities are approved, supplier issues are escalated, and local requirements enter category strategies.
Governance forums should exist only where they resolve genuine cross-boundary needs. Integration can create an excessive number of committees because teams use meetings to compensate for unclear accountability. A committee should have a defined purpose, decision authority, membership, cadence, and set of issues that genuinely require collective judgment. Routine operational decisions should not need committee approval merely because the businesses have recently combined.
Leadership roles should also reflect the integration phase. An integration leader may require unusually broad coordination authority during the first year, but those responsibilities should eventually migrate into normal line management. Temporary integration governance should not become a permanent parallel organization unless the operating model truly requires it.
Joint ventures make authority design more complex because venture management operates within shareholder agreements and reserved matters. The venture chief executive may control normal operations but require board approval for capital spending, senior appointments, strategy changes, related-party contracts, or entry into new markets. These boundaries should be translated from legal documentation into practical decision rules that managers can use.
Interfaces with joint-venture parents require similar precision. If one parent supplies technology while another provides distribution, venture management should know who sets service requirements, how costs are approved, who resolves performance disputes, and which issues can be escalated to the venture board. A legal agreement is necessary but rarely sufficient for effective day-to-day operation.
The objective is an organization in which leaders understand not only their titles but also what they own, which decisions they can make, where they must collaborate, and how unresolved conflicts are resolved. That clarity becomes increasingly important as temporary integration teams give way to the permanent operating model.
7.3 Planning Functional and Shared-Service Integration
Functional integration determines how capabilities such as finance, human resources, technology, procurement, legal, marketing, and other support activities will serve the combined enterprise. Shared services are one possible component of that model, but they should not be treated as an automatic target state. The objective is to determine the configuration that best balances scale, expertise, control, responsiveness, and cost.
Planning should begin by separating activities within each function. A finance organization, for example, includes business partnering, transaction processing, controllership, treasury, tax, planning, reporting, and specialist activities. These may require different operating models. Transaction processing may be consolidated in a shared-service environment while finance partners remain embedded in business units and tax remains a centralized center of expertise.
Each activity can be evaluated against several questions. Does scale materially improve efficiency? Is standardization important for control or data quality? How much specialized expertise is required? Does the activity need frequent interaction with local managers or customers? Are local regulatory requirements material? How variable is demand? Can service quality be measured effectively? These questions help determine whether an activity should be centralized, embedded, shared, outsourced, or left unchanged.
Shared services create value when repeated transactional work can be standardized and performed efficiently for multiple organizational units. Typical candidates include accounts payable, payroll administration, employee data management, procurement operations, certain technology services, and routine financial processing. However, a business case should consider transition cost, system requirements, management overhead, language needs, time zones, service quality, and the risk of moving processes before they are stable.
Integration teams should avoid combining process redesign, system migration, organizational restructuring, and shared-service transition unnecessarily at the same moment. Each change may be justified, but implementing all simultaneously increases execution risk. A phased approach may first stabilize the process, then standardize it, and only afterward migrate the work to a shared-service model.
Centers of excellence serve a different purpose from shared services. They concentrate scarce expertise rather than high-volume transactions. Compensation design, advanced analytics, tax, cybersecurity, strategic sourcing, or specialized engineering may benefit from enterprise centers of expertise while remaining closely connected to operating units. The operating model should define how these centers set standards and support the business without becoming bottlenecks.
Functional integration should also address the retained organization. When activities move into shared services, automation, or external providers, the original function usually requires fewer operational roles but stronger capabilities in demand management, performance monitoring, policy, analytics, or business partnership. Failing to redesign the retained organization can preserve old staffing while adding a new service layer, increasing rather than reducing cost.
Service relationships should be explicit. Internal customers need to understand what the shared function provides, expected service levels, request channels, escalation routes, and responsibilities retained by the business. Formal service-level agreements may be appropriate for some activities, but even where contracts are unnecessary, service expectations should be measurable.
Technology and data architecture influence almost every functional choice. A process may be theoretically suitable for centralization but impractical while units operate incompatible systems. Conversely, common platforms can enable standardization without requiring organizational centralization. Functional and technology roadmaps should therefore be developed together rather than sequentially.
The financial model should capture both recurring savings and implementation costs. Shared-service consolidation may require systems investment, severance, facilities, migration teams, training, temporary duplication, or external support before benefits appear. Management should also account for service risks and potential loss of local knowledge when evaluating the target model.
Joint ventures frequently rely on parent-company shared services during formation. This can reduce launch cost and allow the venture to operate before it has standalone capabilities. The important design question is whether those services are temporary or permanent. If temporary, the venture needs an exit roadmap and replacement capability. If permanent, governance, service levels, pricing, investment responsibilities, data access, and dispute mechanisms become components of the enduring operating model.
The functional model should ultimately specify where each significant activity resides, who owns standards, who performs the work, how services reach the business, and what transitional steps are required. This is more useful than simply deciding that a function will be “centralized” or “integrated.”
7.4 Managing Talent-Retention and Organizational Dependencies
Organization design creates value only if the company retains the people needed to operate the business and execute the transition. Integration creates predictable talent risk because employees face uncertainty about roles, status, leadership, location, compensation, and career prospects at the same time that competitors may actively recruit them. Talent retention should therefore be integrated with organizational decision making rather than managed as a separate human-resources activity.
The first step is to identify critical talent populations. Criticality should be based on business dependency, not simply seniority. Important individuals may include customer relationship owners, engineers, regulatory specialists, plant leaders, product experts, technology architects, finance personnel, founders, or employees with unique knowledge of systems and processes. Some may be important to the long-term organization; others may be essential only through the transition.
This distinction between end-state talent and transition-critical talent is essential. A legacy-system specialist may not have a role after migration but may be indispensable until the cutover is complete. A product leader may be fundamental to the acquisition thesis and therefore require long-term retention. Different populations need different commitments, incentives, development paths, and communication.
Retention risk should be assessed at the role and individual level where legally and practically appropriate. Factors can include external marketability, uncertainty about future responsibilities, loss of autonomy, compensation differences, geographic changes, perceived cultural fit, prior relationship with key leaders, and whether competitors are likely to target the employee. The organization should avoid assuming that financial incentives alone will solve these issues.
Retention mechanisms can include leadership access, role clarity, career opportunities, meaningful integration responsibilities, compensation adjustments, retention awards, development opportunities, or accelerated organizational decisions. The correct approach depends on why the person may leave. An employee concerned about professional autonomy may respond more to clear decision authority than to a cash payment. A transition-critical employee whose long-term role will disappear may require a time-bound retention arrangement tied to specific milestones.
Communication timing should be coordinated with organization design. Excessive delay increases uncertainty, but announcing incomplete structures can create confusion and require reversals. Management should identify which decisions must be made early to protect talent and which can wait until the design is better developed. Where decisions remain unresolved, employees benefit from transparency about the process and timing even if the final answer is not yet available.
Organizational dependencies should be mapped alongside talent risk. A system migration may depend on a small group of technical employees. A facility transition may rely on experienced planners. A customer-account reassignment may require the outgoing relationship manager to support a handoff. The integration plan should make these dependencies explicit so organizational actions do not inadvertently remove capability before the related transition is complete.
Knowledge transfer should be planned rather than assumed. Critical knowledge may be documented through process maps, operating manuals, system documentation, customer plans, technical specifications, or structured handovers. For highly tacit knowledge, overlap periods and direct working relationships may be required. Documentation should complement rather than replace practical transfer where judgment and experience matter.
Leadership selection processes also affect retention across the broader organization. Employees watch whether appointments appear merit-based, politically balanced, biased toward the acquirer, or dominated by speed. A transparent selection process based on target-role requirements can improve perceived fairness even among employees who are not selected. Conversely, unexplained appointments can accelerate departures beyond the individuals directly affected.
Management should monitor leading indicators of talent risk during integration. Resignations are a lagging measure. Engagement feedback, recruiting activity, acceptance of retention offers, declined internal roles, absenteeism, changes in employee inquiries, and manager observations may provide earlier warning. Particular attention should be given to clusters: the departure of one influential employee can trigger others.
Joint ventures have additional talent dependencies because employees may transfer from parent organizations into a new entity. Individuals may worry about career prospects, benefits, seniority, mobility back to the parent, or whether the venture will have sufficient resources and prestige. The venture and parents should align on employee propositions, transfer terms, future mobility, and the treatment of scarce talent before communication begins.
The objective is not to retain everyone. Integration inevitably changes roles and may require reductions, consolidation, or reassignment. The management challenge is to differentiate deliberately: retain capabilities essential to value creation and transition, make target-state decisions promptly, and sequence departures so the organization does not remove knowledge or leadership before dependencies have been resolved.
7.5 Target Operating Model Decision Matrix
A target operating model decision matrix provides a consistent method for resolving organizational choices across functions, business units, and geographies. It is particularly useful when many teams are designing their future models simultaneously. The matrix does not replace management judgment; it makes the criteria and reasoning behind that judgment explicit.
The unit of analysis should be a meaningful activity or decision domain. Rather than asking whether “finance” should be centralized, management may separately evaluate transaction processing, business partnering, treasury, tax, planning, controllership, and reporting. Instead of asking whether “sales” should be integrated, the matrix may distinguish account ownership, pricing, sales operations, incentives, channel management, and strategic-account governance.
Decision Matrix Criteria
Each activity can be assessed using a common set of questions:
Strategic differentiation: Does the activity provide competitive advantage or require adaptation to distinct business strategies?
Scale benefit: Would consolidation materially reduce cost or improve access to scarce expertise?
Control requirement: Does the activity require consistent enterprise standards because of financial, legal, regulatory, safety, or risk considerations?
Customer proximity: Does effective performance require close connection to customers, markets, products, or local operations?
Standardization potential: Can the activity operate effectively using common processes, systems, data, and policies?
Local constraint: Do legal, labor, regulatory, language, tax, or market conditions require geographic variation?
Interdependence: Does the activity need to be colocated organizationally with other capabilities to work effectively?
Transition feasibility: Can the proposed model be implemented at acceptable cost and risk within the required timeframe?
The output should identify the proposed target model, rationale, accountable owner, important exceptions, dependencies, transition approach, and date by which the decision is required. Typical target choices include enterprise centralization, regional organization, business-unit ownership, shared services, center of excellence, outsourced delivery, coordinated autonomy, or continued standalone operation.
The matrix is especially useful for exposing inconsistent logic. One function may argue that every country requires autonomy because of local regulation while another successfully centralizes similar regulated activity. A business unit may claim that its processes are unique despite using the same customers, systems, and economics as the rest of the company. Comparison across decisions encourages management to distinguish genuine differences from organizational preference.
Executive Decision Template
Activity or capability: Define precisely what is being designed.
Current models: Summarize how the buyer, target, or parent companies operate today.
Target options: Identify realistic alternatives rather than assuming the buyer model is the default.
Evaluation: Assess the options against strategic differentiation, scale, control, customer proximity, local needs, and implementation feasibility.
Recommended model: State where the activity will reside and how authority will work.
Interfaces: Identify important relationships with other functions, businesses, geographies, or parent companies.
Transition implications: Describe organization, people, process, system, cost, and timing requirements.
Decision authority: Identify who approves the target model and any exceptions.
For joint ventures, the matrix should include an additional criterion: whether the capability should sit inside the venture or remain with a parent. The answer should reflect strategic control, neutrality between shareholders, intellectual-property protection, economic efficiency, service reliability, and the venture’s intended degree of independence. A parent-provided activity should also specify whether the arrangement is transitional or part of the permanent model.
Once major operating model decisions are approved, they should become explicit assumptions for organization design, technology planning, shared-service implementation, talent decisions, synergy tracking, and governance. Changes should be controlled because altering one design choice can create consequences across several workstreams. Used consistently, the decision matrix gives leadership a practical mechanism for building a target organization that reflects the transaction thesis rather than simply inheriting the structures of either company.
