An acquisition creates a new ownership structure immediately. Everyday decision-making takes more conversation. A functional leader may continue using a familiar approval route while a colleague assumes the new structure is already in place. Both can be acting responsibly according to their understanding. The practical task is to make that understanding shared before uncertainty travels into customer commitments and team priorities.
Start with the decisions that affect the work
Choose a small set of consequential decisions to examine first. These could concern a customer promise, a shared resource, a product priority or an exception to a working practice. The right choices depend on the integration. Ask where repeated clarification, competing approvals or delayed responses are affecting progress. This gives the leadership discussion a concrete starting point and keeps it connected to the operating reality.
Trace one recent decision from the initial question to the final action. Who supplied information? Who believed they could approve it? Who needed to be consulted? Who learned about the outcome later than they expected? Include both legacy organizations in this account. The exercise can reveal a missing connection between capable people without turning the discussion into a comparison of which organization worked better.
Separate contribution from final accountability
Important decisions often benefit from several perspectives, while final accountability still needs to be clear. Identify the person who can make the decision, the people whose knowledge should shape it and those who need to act afterwards. Explain what each contribution is for. A colleague supplying specialist input should understand whether they are advising, approving a defined requirement or taking responsibility for implementation.
Give the accountable person sufficient context and appropriate authority. Naming an owner while leaving every practical choice subject to another approval creates a gap between the title and the work. Where authority is temporarily limited during integration, say so openly. An interim arrangement with an explicit review point is more workable than an ambiguous promise of autonomy that people interpret differently across functions.
Agree how consultation will happen
Consultation needs a question and a timeframe. Ask the people involved to comment on the trade-off they are qualified to assess, and explain when the decision is needed. Allow a reasonable response window across locations. A general request for thoughts can create a long discussion in which everyone contributes, yet the person accountable remains unsure which concerns require a decision and which are useful context.
Make disagreement usable. A leader may express concern directly in a meeting, through a private conversation or in a carefully worded follow-up. Ask what the concern means for the choice at hand. Invite alternative options and the reasoning behind them. Culture can influence how a view is expressed, while hierarchy, relationships and past experience also matter. Work with the specific interaction rather than assuming a national pattern explains it.
For decisions involving customers, include the person responsible for communicating externally. They need to understand what can be confirmed and what remains conditional. An internal agreement can create a new problem if a customer hears a stronger promise than the teams intended. Clarify that communication responsibility before closing the decision.
Make temporary agreements explicit
Integration teams often need to operate while the permanent structure is still being designed. A temporary decision agreement can identify the owner, limits, information required and review date for a defined area of work. Keep it short enough for people to use. Explain who can change the arrangement and how colleagues will learn about the change, so an interim practice does not become an accidental long-term rule.
Consider an illustrative resource decision between two functions. Both need a specialist for time-sensitive work. An interim agreement might identify the leader who sets the priority, the information each function provides and the route for an urgent exception. The value lies in resolving the actual dependency. A complex chart is unnecessary if a clear conversation and a visible record give everyone a workable understanding.
Tell people what was decided and why
A decision is incomplete as a coordination act until the people carrying it out understand it. Share the choice, the reason, the next owner and any condition that could prompt a review. Acknowledge the perspectives considered, including those that led to a different preference. Colleagues can support an outcome more effectively when they understand how their input was considered and what the decision now requires of them.
Use the communication to distinguish settled questions from open ones. An integration announcement can create uncertainty when it combines a confirmed change with several possibilities. Label each clearly. When an answer is still being developed, identify who owns it and when the next update is expected. People then have a reliable reference for planning their work and responding to questions from their teams.
Review the arrangement against real decisions
After a few working cycles, revisit the decisions chosen at the start. Ask whether ownership was clear, the right knowledge arrived in time and the receiving team could act. Notice where the arrangement added unnecessary waiting or left someone outside an important conversation. These observations make it possible to refine the process around the work instead of defending a design because leaders already announced it.
M&A Cultural Integration can support the leadership alignment and working relationships involved in these choices. Begin with one decision that repeatedly travels between leaders. Bring the people responsible together and agree how that decision will work next time. A practical agreement that survives its first real use can become a useful foundation for the wider integration effort.