Explore Post Merger Culture Questions With Senior Leaders

Post merger culture concerns often arrive as stories about meetings, decision speed, or whose voice receives attention. A consulting partner helps senior leaders move from broad labels toward observed situations and leadership choices. Discussion should not assign motives to either legacy organization. People describe events from their own work position, often with incomplete knowledge of pressure elsewhere. Respectful inquiry gives leaders better material than a contest over whose former practice was right.

Start by asking what leaders mean when they use the word culture. One leader might mean slow decisions. Another might mean different expectations for customer contact. A third might mean uncertainty over who speaks first during a joint meeting. Those observations lead toward different questions. A broad request to solve culture has no useful boundary. A request to examine authority during shared account decisions gives senior leaders a work situation worthy of attention.

Ask for events people saw or experienced directly. Request the setting, people involved, decision under discussion, and observed consequence. “Teams do not trust each other” leaves a large gap between claim and action. “Two account teams paused a customer proposal because neither manager knew who owned pricing approval” gives leaders a specific route to examine. Do not treat one story as proof of a widespread condition. Use several examples to identify patterns or meaningful differences.

Connect every example to an open integration choice. Leaders might need to clarify decision rights, settle meeting norms, establish communication routes, or choose operating practices needing a shared approach. Such choices belong with accountable leaders. The consulting partner helps frame questions, gather examples, and show tradeoffs. The partner does not decide employee policy or pronounce one legacy group responsible for a problem. Clear ownership keeps a culture discussion connected to work rather than personal judgment.

Choose a modest starting scope. A merger produces many stories, and an attempt to collect every concern creates delay and weak follow up. Select one work moment connected to an open leadership choice. A team might examine handoffs between account teams and service teams during a month. Defined scope helps managers collect examples in a consistent form. Leaders then discuss a real situation rather than a vague condition called culture. Scope also gives staff permission to defer important yet unrelated concerns for a later decision.

Consider a fictional conversation. Integration sponsor Helen says, “The two companies still act like rivals. Will you solve our culture problem?” Partner Dev replies, “Which work moments show this concern most clearly?” Helen describes joint account meetings where teams disagree about authority and leave follow up unclear. Dev asks which decision leadership has not made. Helen says senior leaders have not agreed who owns a shared customer plan when an account uses services from both legacy organizations.

Dev writes a decision question in plain language. Who owns a shared customer plan when both groups serve an account? He asks Helen to name recent meetings where uncertainty changed work. Helen identifies four fictional meetings during a prior three week period. In two meetings, managers left with duplicate follow up tasks. In one, a customer request waited while teams sought approval. In another, a manager chose alone because no shared route existed. Those examples supply a starting point, not a verdict about either group.

Dev meets with sales, operations, and human resources leaders. He asks every person to describe present decision routes using examples rather than character judgments. The sales leader says legacy sales managers traditionally owned a customer plan. The operations leader says service commitments now affect more of those plans. The human resources leader says managers need a clear way to raise concerns without turning every disagreement into a complaint about another group.

Ask managers for detail in a consistent form. What was a work situation? Which decision needed an owner? Which route did people use? Where did a route fail? What happened next? Such questions reduce vague statements and make examples easier to compare. They also help people discuss difficult integration issues without accusing colleagues. A manager might say, “We did not know who owned approval,” rather than claim another team sought control. Leaders then hear where a work route fails instead of trying to settle intent.

Do not confuse agreement during a meeting with a changed operating norm. A leadership choice needs a visible owner, a place where staff find the decision, and an opportunity for managers to test unclear cases. In the fictional situation, leaders choose one accountable owner for shared customer plans. They also write a route for cases where sales and service leaders disagree. The route names a decision point and expected participants. Staff know where a concern belongs when an unusual account situation arises.

Communication should answer practical questions. Tell managers which decision leadership made, which work situations fall inside a decision, and where they should bring unclear cases. Avoid broad announcements asking employees to work as one without changing a rule or practice. People need to see how a decision affects Monday morning work. A manager preparing a joint customer meeting needs to know who gathers inputs, who leads a customer discussion, and who records next actions. Plain guidance prevents every team from inventing a separate routine.

Senior leaders should review early experience after a decision. This review does not need a large culture survey. Ask managers to bring a small set of observed situations from a defined period. Look for recurring confusion, exceptions, or a route nobody uses. When staff apply a new decision differently, leaders should ask whether wording lacks clarity, whether a decision fails to fit a real work condition, or whether another owner needs involvement. Each explanation leads toward a different response, so leaders should avoid treating every exception as resistance.

Protect respect during evidence gathering. Do not ask participants to rank one legacy organization’s habits against another’s. Ask what each earlier practice sought to achieve and what present combined work requires. A former local approval route might have suited a smaller organization. A centralized route might have suited a different operating model. Leaders need not settle whose past approach was superior. They need a workable choice for present responsibilities, customers, and managers facing unclear decisions under time pressure.

Prepare a senior meeting around a few situations. Place a decision question first. Then show brief accounts of observed examples, present routes, and a choice needing leadership direction. Ask leaders to state which route applies, who owns an exception, and when they review early experience. Record uncertainty openly. A choice with a known open question is more useful than a polished statement employees cannot apply. Leaders should leave with an assigned action rather than a broad request for better collaboration.

For practice, create a fictional merger situation involving two account teams serving one customer. Write two observed moments where authority becomes unclear and state a business effect without blame. Ask a colleague to play a senior leader who says, “This proves their culture does not fit ours.” Redirect toward observed work and the open ownership choice. Then write Helen’s Friday meeting invitation, name a customer plan decision, name two managers who bring examples, and place the first case for leadership review in the final sentence.