Organization structures become operational only when leadership roles, accountabilities, and decision rights are explicit. A combined company can have a well-designed target operating model and a logical organization chart yet still perform poorly if executives are uncertain about who owns results, which decisions they can make independently, when they must consult colleagues, and how disagreements are resolved. These issues are especially acute after a merger or acquisition, when legacy leaders bring different assumptions about authority and management practice.
Leadership design is also one of the most consequential integration activities because it affects both operating effectiveness and employee confidence. Senior appointments signal which capabilities matter, how the combined organization will be managed, and whether the integration is progressing decisively. Delayed or ambiguous appointments can increase attrition, encourage political maneuvering, and slow lower-level organization decisions. Premature appointments, however, can lock the enterprise into roles that do not fit the target operating model.
5.1 Designing the Combined Leadership Structure
The combined leadership structure should follow the target operating model and organization architecture established in earlier stages. It should identify the executive roles required to run the future enterprise, define the scope of each position, and create a leadership team capable of making decisions across the principal dimensions of the business. The design should begin with required accountabilities rather than with the executives available from the legacy organizations.
The first question is which outcomes require enterprise-level leadership. Typical areas include overall financial performance, major business units, commercial performance, operations, finance, people, technology, risk, and other strategically important capabilities. Not every function requires a seat on the top executive team. Executive-team membership should reflect the responsibilities that need direct participation in enterprise decisions rather than status, legacy precedent, or a desire to represent every organizational constituency.
The leadership structure should also correspond to the primary operating model. If the enterprise is organized around autonomous business units, business-unit leaders should have sufficiently broad roles to exercise meaningful accountability. If global functions carry substantial authority, the corresponding functional executives may require stronger enterprise roles. In a geographic model, regional leaders may need significant operating authority. The executive structure should make the operating philosophy visible.
Integration creates several recurring leadership design choices. One is whether to retain separate leaders for previously independent businesses or immediately combine responsibility under one executive. Another is whether functional leaders should report directly to the chief executive or through a chief operating officer or similar integrator. A third concerns the number of executives required to represent geographic, product, functional, and customer dimensions without creating an unwieldy leadership team.
The design team should test each proposed executive role against five questions:
- Distinct accountability: Does the position own a material outcome or capability that is not clearly owned elsewhere?
- Decision scope: Does the role make decisions sufficiently important to justify its organizational level?
- Management scale: Is the organizational scope substantial enough to require dedicated executive leadership?
- Integration requirement: Does the role help integrate activities that would otherwise remain fragmented?
- Future relevance: Is the role part of the target organization rather than merely a temporary accommodation for the transition?
These tests are particularly useful when both legacy companies have executives with similar titles. The combined organization rarely needs two permanent chief financial officers, chief human resources officers, or heads of corporate development simply because both companies previously had those roles. At the same time, apparent duplication should not drive automatic elimination. The target business may be larger, more complex, more international, or differently organized and may therefore require leadership roles that neither company had before.
The chief executive’s span of control deserves deliberate attention. A leadership team of fifteen or twenty direct reports may allow many executives direct access to the chief executive, but it can also turn the chief executive into the primary coordination mechanism for the company. Routine trade-offs then escalate upward because no lower-level executive has sufficient cross-functional authority. Conversely, concentrating too many responsibilities under a small number of executives can create overloaded roles and weaken specialist leadership.
Where a chief operating officer, group president, or similar integrator is considered, the role should solve a specific organizational problem. Such positions can be valuable when several operating units require coordination or when the chief executive must devote substantial attention to external stakeholders, portfolio strategy, or transformation. They can be harmful when they insert an unnecessary layer between the chief executive and accountable business leaders. The role should not exist simply to accommodate a senior legacy executive.
Leadership design must also account for control and independence requirements. Internal audit, compliance, risk, quality, safety, or other oversight leaders may require direct access to the board or specific committees even when they report administratively within management. In regulated environments, senior-manager accountability rules or licensing requirements may determine who must formally hold certain responsibilities.
Temporary leadership arrangements should be identified explicitly. An integration may need a dedicated integration leader, interim functional heads, or temporary co-leadership while regulatory approvals or talent decisions are completed. Temporary structures can reduce transition risk, but they should include an intended end date or transition condition. Without one, interim roles frequently become embedded in the organization.
Joint ventures require particular discipline around the distinction between governance and management. The board represents shareholder governance; the chief executive and management team operate the venture. Shareholder executives serving as directors should not routinely bypass venture management and direct employees unless the governance model expressly permits it. Similarly, placing representatives from both parents in parallel management positions merely to preserve symmetry can create divided loyalty and unclear accountability.
The output should be a leadership architecture showing required executive positions, reporting relationships, principal accountabilities, major governance interfaces, and temporary roles. Individual names should be added only after the structure is sufficiently defined. This sequence helps ensure that leadership appointments serve the future organization rather than causing the organization to be designed around incumbents.
5.2 Defining Executive and Critical Leadership Role Charters
An organization chart identifies reporting relationships but rarely provides enough information to clarify what a senior leader is actually expected to accomplish. Role charters convert structural positions into explicit management mandates. They are especially useful during integration because responsibilities that were obvious within each legacy company may become ambiguous when functions, business units, and governance systems are combined.
A role charter should be concise enough to use in practical management discussions. It is not a conventional job description containing long lists of tasks. Instead, it should define the purpose of the role, the outcomes for which the leader is accountable, the major decisions the role owns, the resources or organizational scope controlled, and the most important interfaces with other leaders.
The role purpose should explain why the position exists in the target operating model. For example, a business-unit president might exist to deliver profitable growth for a defined product portfolio globally. A chief procurement officer might exist to leverage enterprise scale, manage strategic suppliers, and establish purchasing standards while operating units retain responsibility for local execution. Clear role purpose prevents responsibilities from becoming a collection of inherited activities.
Accountabilities should be expressed as outcomes wherever possible. “Attend operating reviews” is an activity. “Deliver business-unit revenue, margin, and cash commitments” is an accountability. “Coordinate with technology” is vague. “Ensure business technology priorities are defined and funded within the annual planning process” describes the result. Outcome-oriented language makes performance expectations easier to understand and reduces overlap among leaders.
A strong role charter typically contains six elements:
- Role purpose: The reason the role exists within the operating model.
- Principal accountabilities: The major business outcomes for which the leader is answerable.
- Decision rights: Decisions the leader can make and decisions requiring higher or shared approval.
- Organizational scope: Relevant businesses, functions, geographies, employees, budgets, or assets.
- Critical interfaces: Other leaders or governance bodies with whom the role must work closely.
- Performance measures: The small set of indicators used to evaluate whether the role is succeeding.
Role charters are most important where responsibility could plausibly fall to more than one executive. The relationship between a business-unit president and chief commercial officer may require clarification around sales resources, account ownership, pricing, channel strategy, and customer investments. The relationship between a chief information officer and business executives may require clarity over technology standards, project prioritization, digital products, cybersecurity, and application budgets.
The charter should identify boundaries as well as responsibilities. Leaders benefit from knowing what they do not own. If the chief marketing officer owns enterprise brand standards but business units own product-specific campaign execution, that distinction should be explicit. If regional executives coordinate government relationships but do not own regional profit and loss, the charter should say so.
Integration-specific accountabilities may need to be included temporarily. A functional leader may be responsible not only for running the future function but also for consolidating teams, realizing synergy commitments, harmonizing policies, or completing a systems transition. These obligations should be separated from enduring role responsibilities so that the organization understands which expectations disappear once integration is complete.
Critical roles below the executive team may also require charters. These typically include positions that own end-to-end processes, major sites, strategic customer relationships, centers of excellence, shared services, regulated activities, or cross-functional programs. Creating charters for every managerial position would be excessive. They should be used where ambiguity could materially affect business performance or integration execution.
Role charters can also support leadership selection. Candidates should be evaluated against the future role rather than compared only with one another. A leader who was highly effective in an autonomous legacy business may not be the strongest fit for a role operating within a highly integrated matrix. Conversely, a functional specialist may lack the general-management breadth required by an expanded post-transaction position.
For joint ventures, role charters should show the boundary between management authority and shareholder or board authority. A venture chief executive may be accountable for annual performance but unable to approve capital expenditures above a specified threshold without board consent. The chief financial officer may control internal financial operations while funding arrangements remain subject to shareholder agreements. These limitations are not weaknesses in the role; they are part of its operating context.
Role charters should be reviewed together rather than independently. The objective is to ensure that important outcomes have an owner, that two leaders are not inadvertently assigned final accountability for the same decision, and that gaps have not been created between roles. A leadership team is a system of complementary accountabilities, not merely a collection of individually sensible job descriptions.
5.3 Establishing Decision Rights and Accountability
Decision rights define who has authority to make specific choices. They are one of the most important connections between the operating model and day-to-day management behavior. An organization may have clear reporting lines yet remain slow if employees do not know where decisions belong or if multiple leaders believe their approval is required.
The first principle is to assign a clear decision owner wherever practical. Many people may provide input, set constraints, perform analysis, or execute the result, but one individual or governance body should normally hold final decision authority. Phrases such as “joint ownership” or “shared decision” should be used cautiously because they can conceal unresolved accountability.
This does not mean decisions should be made unilaterally. Important choices often require structured input from several functions. A commercial leader may own a customer pricing decision while finance establishes margin thresholds and legal reviews contractual terms. An operations leader may own production scheduling while sales supplies demand priorities. Distinguishing input rights from approval rights preserves collaboration without creating unnecessary vetoes.
Decision rights should be designed around the significance and reversibility of the decision. Routine, low-risk decisions should generally be made close to the work. High-value, irreversible, regulated, or enterprise-wide decisions may require more senior authority. Organizations become slow when senior leadership retains decisions that can safely be delegated, but they become uncontrolled when material commitments are made without appropriate oversight.
Financial thresholds provide one common mechanism for delegation. Capital expenditures below a defined amount may be approved by a business-unit leader, larger investments by the chief executive, and major commitments by the board. Similar thresholds can apply to contracts, hiring, pricing exceptions, litigation settlements, or acquisitions. Thresholds should reflect both economic exposure and strategic importance because some low-dollar decisions carry substantial reputational or regulatory risk.
Decision rights should also reflect the intended balance between corporate and business-unit authority. A decentralized operating model should not be undermined by requiring corporate approval for routine operating choices. Conversely, an enterprise seeking common standards should not permit operating units to opt out of essential cybersecurity, accounting, safety, or brand requirements merely because they hold profit-and-loss responsibility.
A practical decision-rights exercise begins with the decisions that most strongly influence business performance. These may include annual budgets, pricing, customer exceptions, product launches, capital investments, supplier selection, hiring of senior leaders, technology priorities, site changes, organizational appointments, and risk acceptance. For each, the design team should ask who recommends, who provides mandatory input, who decides, who executes, and who must be informed.
The team should pay particular attention to decisions that were handled differently in the legacy organizations. One company may give plant managers broad capital authority while the other centralizes approvals. One may allow sales leaders to negotiate significant price exceptions; the other may require finance approval. Unless these differences are deliberately resolved, employees will continue following legacy practices after the organization is formally combined.
Accountability should be matched to authority. A leader held accountable for revenue but unable to influence pricing, sales resources, product availability, or customer investment has incomplete authority. A functional executive expected to maintain enterprise standards without the ability to establish mandatory policies faces the same problem. Integration teams should identify these mismatches and either adjust authority or redefine accountability.
Escalation rules are also part of decision design. Escalation should occur when a decision exceeds delegated authority, when stakeholders cannot resolve a defined conflict, or when risk thresholds are triggered. It should not become the default response to ordinary disagreement. If executives routinely resolve decisions several levels below them, either delegation is insufficient or lower-level accountabilities are unclear.
Time limits can improve decision effectiveness. Some decisions become more costly when delayed than when made imperfectly. Governance mechanisms can therefore specify a required decision date or escalation point. For example, if product and sales leaders cannot resolve a launch-priority dispute within a stated period, the issue may escalate to an operating committee rather than remaining unresolved indefinitely.
Decision rights should be documented at the right level of granularity. Attempting to catalogue every management choice creates bureaucracy and quickly becomes outdated. The organization should focus on high-value decisions, recurring areas of conflict, and topics where risk requires formal authority. Other decisions can follow the general delegation philosophy of the organization.
Joint ventures require particularly precise decision rights because authority is split among management, the board, and shareholders. Governing agreements may identify reserved matters such as major capital investments, changes to strategy, financing, acquisitions, senior appointments, or related-party contracts. Management should understand both the formal thresholds and the practical process for obtaining approval. Parent-company preferences that are not contractual rights should not automatically be treated as vetoes.
Decision-rights documentation should ultimately enable people to act with confidence. Leaders should know which choices they can make without seeking permission, when consultation is required, which standards constrain their discretion, and how unresolved issues move upward. The result is not merely faster decision making; it is a more accountable organization in which authority and responsibility reinforce one another.
5.4 Building RACI and Responsibility Matrices for Critical Interfaces
Responsibility matrices are useful when important work crosses organizational boundaries and normal reporting lines do not provide enough clarity. The best-known format is RACI, which distinguishes who is Responsible, Accountable, Consulted, and Informed. Used selectively, such matrices can resolve ambiguity at difficult interfaces. Used indiscriminately, they can generate large tables that employees rarely use.
A RACI should therefore begin with a specific management problem. Appropriate applications include cross-functional processes, major recurring decisions, integration activities, regulatory responsibilities, and relationships between centralized functions and operating units. If ownership is already obvious from the organization structure and role charters, an additional matrix may add little value.
The four traditional categories have distinct meanings. Responsible identifies the person or team performing the work. Accountable identifies the individual ultimately answerable for the result or decision. Consulted identifies parties whose input must be obtained before action. Informed identifies parties who need visibility but do not participate in the decision.
The most important discipline is usually to assign one accountable owner. Several teams may be responsible for parts of a process, but multiple “A” designations frequently indicate that the underlying accountability has not been resolved. Where a board, committee, or other collective body legitimately holds approval authority, the matrix should identify that body explicitly rather than pretending one executive decides independently.
The rows of the matrix should describe decisions or outputs at a useful level of specificity. “Marketing” is too broad. “Approve annual brand strategy,” “set campaign budget,” and “approve local deviations from brand standards” are actionable. The matrix should focus on points where ambiguity can delay work or cause conflict rather than attempting to document every activity.
Responsibility matrices are particularly valuable at recurring interfaces such as:
- Business units and corporate functions.
- Global functions and regional or country teams.
- Sales, product, and operations organizations.
- Shared services and internal customers.
- Process owners and functional leaders.
- Venture management, the venture board, and shareholder organizations.
The matrix should be tested through actual scenarios. If the table says a business-unit leader is accountable for pricing, the team should test a real example involving a strategic customer, a discount outside guidelines, currency implications, and an unusual contractual term. The exercise often reveals that what appeared clear at a conceptual level still contains unresolved authority boundaries.
Consulted roles should be limited to parties whose input materially improves or constrains the decision. Organizations frequently overuse consultation because excluding a stakeholder appears politically difficult. The result is slower decisions and ambiguity over whether consultation means advice or consent. The distinction should be explicit: a consulted stakeholder can provide input but does not possess veto authority unless another rule grants it.
Likewise, the informed category should not become a justification for broad meeting attendance. Information can often be distributed through dashboards, decision logs, or routine communications. The design objective is to ensure necessary visibility without turning every decision into a committee process.
Alternative responsibility frameworks can be used when RACI terminology does not fit the organization’s needs. Some organizations distinguish recommendation, approval, input, execution, and decision. Others identify process ownership separately from decision authority. The terminology matters less than consistent definitions and disciplined use.
Joint ventures often benefit from matrices covering decisions at the boundary between management and shareholder governance. For example, venture management may develop the annual plan, the board may approve it, shareholders may provide specified input, and management may then execute it. Related-party procurement may require additional approval because of conflicts of interest. Recording these distinctions reduces the risk that parent-company representatives informally expand their authority beyond the agreed governance model.
Responsibility matrices should be living management tools rather than permanent artifacts. They should be revised when the organization changes or when experience demonstrates that a responsibility split is not working. The best matrices eventually become less visible because employees internalize the operating rules. Their value lies in accelerating that clarity during periods when organizational relationships are new.
5.5 Leadership Appointment and Role-Clarity Checklist
Leadership appointments are among the most visible milestones in organization integration. They determine who will make subsequent organization decisions, influence critical-talent retention, and give employees an early indication of how the combined enterprise will operate. Appointment processes should therefore balance speed with sufficient clarity about the target roles.
The sequence matters. Enterprise leadership positions should generally be resolved before the leaders beneath them because newly appointed executives need appropriate authority to shape their own organizations. Waiting until every detail is settled creates uncertainty, while appointing leaders before their roles are defined can constrain the design. The practical objective is to define each role sufficiently to make a sound appointment, then allow the selected leader to participate in the next level of design.
Selection criteria should be based on future requirements. Relevant considerations may include leadership record, functional or general-management expertise, ability to operate at the required scale, experience with the target business model, integration capability, talent leadership, customer credibility, and cultural adaptability. Legacy title or reporting level should not substitute for assessment against the future role.
A leadership appointment and role-clarity review should confirm the following:
- Has the role been defined from the target operating model rather than around an incumbent?
- Are the role purpose and principal accountabilities clear?
- Are major decision rights and financial authorities documented?
- Are reporting relationships and critical interfaces understood?
- Has the candidate been evaluated against future-state requirements?
- Have potential conflicts of interest or regulatory requirements been addressed?
- Are transition responsibilities distinct from permanent responsibilities?
- Have retention risks for selected and nonselected leaders been assessed?
- Is there a communication plan for the appointment and related organization changes?
- Does the appointed leader know which lower-level organization decisions remain open?
Communication should state more than the person’s name and title. Where practical, employees should understand the scope of the role, when the appointment becomes effective, which teams are affected, what remains unchanged, and when further organization decisions will be communicated. This reduces speculation and helps establish the new accountability model.
Nonselected leaders require careful management as well. Some may hold essential transition knowledge, customer relationships, or technical expertise even though they will not occupy the long-term role. Transition responsibilities, retention arrangements, handoffs, and departure timing should be deliberate. Leaving these matters unresolved can undermine both morale and operational continuity.
Role clarity should be tested after appointments rather than assumed. Within the first several weeks, leaders should review their charters and major decision rights with adjacent executives. Real decisions will often expose ambiguities that were not apparent during design. Those issues should be resolved promptly and reflected in the relevant charters or responsibility matrices.
For joint ventures, the review should additionally confirm that executives understand where their authority ends and board or shareholder approval begins. Parent-company secondees should understand whether they are acting on behalf of the venture or their employer in a given context. Board members should likewise understand that governance oversight does not automatically confer authority to manage venture employees directly.
By the end of this stage, the combined organization should have more than named leaders. It should have an explicit leadership system: roles designed around future requirements, outcomes assigned to identifiable owners, authority matched to accountability, critical interfaces clarified, and appointments sequenced so that leaders can take responsibility for the organization beneath them. That clarity provides the foundation for effective governance, management cadence, and implementation of the broader integration agenda.
