Consider an illustrative integration review. Each function reports progress, the plan has named owners and the next milestone appears achievable. Then a familiar issue returns: two teams are waiting for a decision that each believes belongs elsewhere. The meeting ends with another request to accelerate. What the teams need is more specific: a shared understanding of how the decision will be made and what each person can do next.
Follow a stalled outcome back to its dependency
Integration plans organize a large amount of work, yet a milestone can depend on arrangements that are harder to capture in a schedule. A customer commitment may require two leaders to agree a trade-off. A combined team may need clarity about whose approval applies. A new operating process may depend on knowledge held by someone whose role is changing. These are practical dependencies that deserve attention alongside the formal workstreams.
Choose one outcome that is moving more slowly than expected and trace it backwards. What needs to happen immediately before it can progress? Which information, permission or agreement is missing? Continue until the team can name a decision or interaction it can actually address. This approach narrows a general conversation about integration pace into a specific question with people, context and a possible next step.
Keep the inquiry factual. Ask for the most recent example, the sequence of actions and the points where understanding differed. A delayed response may reflect competing priorities, uncertainty about authority or a concern that has yet to be discussed. Several explanations can fit the same behavior. Starting with the sequence allows the people involved to contribute their understanding before a leadership team settles on an interpretation.
Include the cost of waiting in the discussion, expressed in terms the team can substantiate. A customer answer may remain open, a colleague may be unable to schedule work or two functions may be maintaining competing plans. Naming that consequence helps the decision owner judge the priority without inventing an estimate of the acquisition value at risk.
Make the business reason usable in everyday decisions
The rationale for an acquisition is usually expressed at a level broader than a team's daily work. People may understand the ambition while remaining uncertain about what it means for a customer exception, a product choice or a local practice. Translate the business rationale into the trade-offs leaders expect teams to make. Explain where consistency matters, where local judgment is valuable and which questions are still open.
Invite the acquired organization to explain the capabilities and relationships that support its value. A familiar process may look inefficient from outside while serving an important customer need. Equally, a practice may have outgrown its usefulness. Examine both possibilities with the people closest to the work. Preserving value requires an understanding of what creates it, including knowledge and working relationships that may be difficult to see in a formal review.
Connect the integration message with a small set of concrete examples. If a shared customer experience is a priority, explain which decisions should be coordinated. If a specialist capability needs room to develop, clarify the boundaries around that autonomy. These examples give managers a useful reference for answering questions and help teams understand how the strategy should influence their next choice.
Bring leadership differences into a working conversation
Leaders from the two organizations may carry different assumptions about consultation, speed, accountability and how concerns should be raised. Each approach may have served a previous context well. During integration, those assumptions meet in shared decisions. A leadership discussion can explore the differences through actual situations, allowing each person to explain what they are trying to protect and what information they need to decide responsibly.
For example, one leader may want a recommendation early enough to shape it, while another expects the team to resolve the detail before involving them. When those expectations remain implicit, the same update can appear premature to one person and late to another. Agree what an early conversation is for, what preparation it requires and when a final recommendation should arrive. This creates a practical rhythm without demanding identical leadership styles.
Give particular attention to relationships that now carry shared responsibility. Two leaders whose teams previously operated separately may need time to understand each other's commitments, constraints and preferred ways of working. Their alignment affects the instructions teams receive. A short, direct conversation between those leaders can sometimes resolve a dependency that several layers of project reporting have simply continued to describe.
Clarify decisions while the structure is evolving
An integration often needs to function before its permanent arrangements are complete. Make temporary decision rights explicit in the areas where uncertainty affects delivery. Name the accountable person, the perspectives needed, the limits on the decision and the route for an exception. An interim agreement should include a review point, so people understand that it is a considered working arrangement that can develop as the integration progresses.
Distinguish consultation from approval. A specialist may need to review a particular requirement without becoming the owner of the whole decision. A leader may need visibility because of a related commitment, while the team remains responsible for implementation. Explaining those distinctions helps people contribute effectively and reduces the tendency to seek additional permission simply because several stakeholders are involved.
Publish the outcome where the people carrying out the work will see it. State the decision, the reason and the next action. Where a question remains open, give it an owner and an expected update. People can plan around a known uncertainty more effectively than around an assumption that an answer exists somewhere else. Clear communication also helps managers explain changes consistently across locations and working schedules.
Treat employee questions as useful operating information
Questions about roles, reporting lines and future expectations are part of how people make sense of a changing organization. Provide routes through which those questions can reach someone able to respond. Listen for recurring themes, while preserving the privacy and context of individual conversations. A repeated question may indicate that the published message leaves an important practical implication unexplained.
Managers can ask what their teams need in order to carry out the next period of work. Which responsibilities are clear? Where are people receiving different instructions? What customer or delivery knowledge should the integration team understand? This keeps the conversation connected to agency and contribution. It also gives managers an opportunity to recognize the effort involved in delivering everyday commitments while learning new working arrangements.
Be precise about what can be answered. If a decision is still under consideration, explain the process and the next communication point within the information the organization can responsibly share. Follow through on that communication promise even when the answer remains open. Reliability in small updates can help create a more dependable relationship between leaders and teams during a period when many other things are changing.
Choose interventions that fit the source of friction
Different integration difficulties call for different responses. A missing approval route needs an operating clarification. A leadership relationship affected by competing expectations may benefit from facilitated alignment. A team learning to work across cultural contexts may need opportunities to practise communication and collaboration. Selecting support begins with an honest account of the situation, including what the organization itself needs to decide or change.
M&A Cultural Integration can help leaders examine culture, relationships and ways of working as part of the wider integration effort. Keep the engagement linked to a meaningful business question. What should people be able to understand, discuss or coordinate more effectively afterwards? This creates a useful connection between development activity and the work that sponsors want to strengthen.
Avoid giving a workshop responsibility for an unresolved management decision. Participants can learn to communicate more clearly while still receiving incompatible priorities from senior leaders. Address those priorities with the appropriate owners. Then use development or coaching to support the conversations and behaviors needed to make the agreement work. Each part of the response should carry a responsibility it can realistically influence.
Review progress through the decisions that now move
Return to the stalled outcome chosen at the beginning. Has the missing decision been made? Do the teams understand the agreement? Can they carry out the next action without recreating the same uncertainty? These questions provide evidence about the specific intervention. Broader integration outcomes also depend on systems, resources, customers and market conditions, so describe contribution with appropriate care.
Build the review into existing integration conversations. Ask leaders to bring an example of a dependency resolved, an agreement that needs adjustment and a question requiring sponsor attention. Keep the discussion short enough to remain useful. The purpose is to help the organization learn how its combined ways of working are taking shape, while maintaining attention on the commitments it has already made.
Momentum becomes more meaningful when people can see what enabled it. A clarified decision, a dependable update or a stronger relationship between two leaders may look modest beside the scale of a transaction. Yet those are tangible conditions through which teams carry out the integration. Start where one of those conditions is missing, involve the people responsible and agree the next practical change together.