Systemic Constellations in M&A: Evidence and Practice
Nour
Founder, Coachful
Systemic constellations in M&A use a spatial representation of roles and relationships to prompt reflection about integration. A responsible coaching adaptation treats the arrangement as someone's perspective, not hidden organizational truth. It can help people explain different understandings, but it cannot replace financial, legal, operational or cultural due diligence.
An acquisition changes authority, job prospects, customer commitments and valued ways of working. People may disagree for good reasons. This guide develops a bounded mapping conversation, a filled evidence worksheet and a complete fictional follow-through in which a technical lead declines a meeting and a customer exception remains unresolved. The aim is useful inquiry followed by actual decisions, not loyalty diagnosis.
Match the integration question to the right evidence
| Integration task | Needed evidence or process | Possible mapping contribution |
|---|---|---|
| Clarify authority | Governance, role descriptions and decision records. | Compare perceived overlaps without granting new authority. |
| Understand employee concerns | Appropriate interviews, consultation and employee representation. | Identify voices that have not been heard. |
| Maintain customer continuity | Actual commitments, handoff records and customer feedback. | Generate questions about potentially vulnerable handoffs. |
| Assess acquisition value | Defined objectives and financial and operational analysis. | Identify perspectives relevant to interpreting the results. |
A map cannot establish what absent employees believe, predict retention or prove acquisition success. If the problem is a missing decision rule, a decision-rights table may answer it directly. If employee accounts are missing, consult the people concerned rather than asking executives to embody them. Use the method that fits the question.
Keep the research limits in view
Scholtens and colleagues' 2021 systematic review of organizational constellations identified seven prospective effectiveness studies, only two with controls. It reported potentially useful organizational findings, including perceived improvements, while describing generally low study quality, heterogeneous outcomes and small samples. It was too early for firm effectiveness conclusions. Fidelity had not been assessed, and differing methods complicated interpretation.
That is neither proof the method has no possible use nor validation of hidden fields or an M&A diagnosis. The review does not establish that a particular card exercise prevents integration failure. Treat mechanisms as hypotheses and evaluate the actual work rather than attributing a business result to one workshop. The exercise below is an original coaching adaptation, not a reproduction of the review's supplementary procedure or a clinical protocol.
Use belonging, contribution and authority as questions
If a practitioner uses terms such as belonging, order or exchange, turn the labels into discussable questions rather than immutable laws. A group's reaction does not establish that an invisible rule has been broken. Prior seniority, organizational history and emotional attachment do not automatically determine current managerial or legal authority.
Belonging: who is affected and whose account is missing? Include acquired staff, established teams, customers, suppliers and people leaving, where relevant. Recognizing someone does not promise that every role or legacy process will remain.
Contribution: which knowledge and commitments should be understood before changing the process? Document customer relationships, useful work and specialist capability. Give people an actual opportunity to contribute rather than substituting a ceremonial thank-you.
Authority: who can decide what now, within which documented boundary? Mark uncertain exceptions. A budget owner may not be the product approver; a product approver may not be entitled to vary a customer promise.
These questions leave room for workload, incentives, job insecurity and an unclear integration plan. For related ideas, see the guide to organizational loyalties. Keep a proposed explanation attached to its source rather than declaring that concern or disagreement proves unconscious loyalty.
Offer a bounded format with genuine alternatives
Agree one question, such as “Where are roadmap changes becoming unclear?” Use labeled cards, objects, paper or a suitable shared board. A person can choose a plain role list or private written input instead. Nobody needs to stand for a colleague, report bodily sensations as evidence or disclose personal history to participate.
Ask the map's author what a position means. Distance might represent communication, formal separation or the available space on the page. Do not supply the interpretation. Separate a source document, first-person experience, inference and question. “I do not know the approval route” is an account; “Engineering distrusts us” needs evidence and the affected people's views.
- Define the question and decision owner: state what the exercise can inform and who ultimately decides.
- Agree participation and records: explain alternatives, audiences and relevant confidentiality limits.
- Label roles and missing voices: distinguish participants' accounts from absent people's unknown views.
- Ask descriptive questions: let each person explain their arrangement and disagreement.
- List claims to check: retain sources, uncertainty and a suitable inquiry route.
- Agree feasible actions: obtain real receiving capacity and return to integration governance.
Pause or change format if it becomes coercive, exposing or detached from the question. A coach's preferred method should not make declining seem disloyal. The ICF Code of Ethics offers a professional reference for role and information-exchange agreements and competent practice; it is not a substitute for applicable legal requirements.
Case: two understandings of product authority
In this original fictional case, Ari coaches integration lead Iris. Noel leads the acquired product team, Cleo represents the parent company's product leadership, Vik is an engineering manager and Sana is an account lead. The target is a complete decision route for two example roadmap cases by 2 February 2029. Earlier integration work, company records and customer commitments are outside the bounded account, not free inputs.
Ari spends twenty minutes on Monday 15 January preparing and sending Iris the purpose and finite plan. It includes a private written return by 22 January at 17:00, a twenty-minute review on 1 February and a closing read on 2 February. Iris spends ten minutes on 16 January reading, accepting and preparing and sending Noel and Cleo an invitation about the business question. Ari reads the acceptance and prepares for ten minutes on 17 January. Noel and Cleo each use ten minutes to read their invitations and prepare.
All four take part in a forty-minute conversation on 17 January. Noel declines standing in for anyone; they use seated role cards instead. They agree that the coach's private written reflection will go only to Iris, while any company inquiry will use selected business questions. This original ten-turn exchange occurs within the session:
Ari: What question should these role cards help us examine?
Iris: Why roadmap changes keep returning for approval.
Noel: I place product away from the executive group because I do not know who can approve the change.
Cleo: I thought your team owned the roadmap within budget.
Ari: Those are different understandings. What record establishes the boundary?
Iris: The budget owner is named, but the exception route is not clear.
Ari: Whose relevant knowledge is missing?
Noel: Vik knows technical delegation. Sana knows customer commitments. We cannot speak for them.
Ari: What inquiry could follow without deciding the answer here?
Iris: Ask them about the two cases and agree a workable return, with the uncertain exception kept open.
Noel's card expresses his uncertainty. It does not prove what all acquired staff feel. Cleo's expectation is not a new delegation, and Iris cannot turn an unresolved customer issue into permission by drawing a closer connection.
A private interpretation is corrected before business inquiry
Ari spends fifteen minutes on 18 January preparing and sending V1 only to Iris. It wrongly describes acquired-team distrust as established and says authority is settled. Iris spends ten minutes on 19 January reading and rejecting those assertions. The conversation established neither claim.
Ari spends twenty minutes on 22 January reading the correction, removing the assertions, amending the four-claim worksheet and preparing and sending this repair only to Iris at 16:00, one hour before the promised return:
I treated a participant's uncertainty as acquired-team distrust and described authority as settled. Neither conclusion was established. I have removed both from V1. Noel described his own understanding, Cleo offered a different expectation and the customer exception remains open. The revised worksheet distinguishes those accounts from documents and questions. It is private to you under our arrangement, not an assessment of absent colleagues. Please use a separate business-only inquiry if you choose to ask Vik and Sana for relevant information.
| Claim or observation | Status | Check | Possible action |
|---|---|---|---|
| Noel and Cleo describe different approval expectations. | Different first-person accounts. | Inspect relevant delegation and the two example changes. | Describe the ordinary route and retain exceptions. |
| Acquired staff distrust the parent company. | Unsupported interpretation removed from V1. | Use appropriate employee inquiry if this becomes an agreed question. | No psychological team label or inferred consensus. |
| A customer promise constrains a roadmap change. | Question requiring account information. | Ask Sana about the relevant existing commitments. | Keep the change held where authority remains unclear. |
| A founder is blocking integration. | No verified instance in this case. | Seek actual events and hear the person's account through the right route if raised. | Do not turn a hypothetical claim into a finding. |
The blank worksheet uses these four columns. A striking arrangement must not become an employee assessment or official explanation of resistance. None of the absent people's feelings has been measured, and no founder has been contacted or assessed.
A declined meeting leads to actual written returns
Iris spends fifteen minutes on 23 January reading the correction and preparing and sending a business-only request to Vik and Sana. It contains neither the private map nor an account of coaching perceptions:
Please identify the existing decision boundaries for the two roadmap cases: an internal change within budget, and a change that may affect a customer delivery promise. I need the relevant source, what it establishes and what it leaves open. This is not an instruction to approve either change or contact a customer. A joint discussion is one option. Please offer that or a realistic written return, including time to read the selected status afterward. You do not need to participate in a constellation exercise to answer.
Vik spends ten minutes on 24 January reading and replying. He declines a proposed joint meeting and offers fifteen minutes on 26 January to check the existing technical delegation and return an answer, plus five minutes on 30 January to read a status. Sana spends ten minutes that day reading and offering a twenty-minute written return on 26 January and a five-minute status read on 30 January.
Iris spends ten minutes on 25 January reading both offers and sending acceptance. Vik and Sana each spend five minutes reading it that day. The written route is accepted; their absence from another workshop is not evidence of resistance.
Vik uses his fifteen-minute block on 26 January to read the existing delegation and prepare and send this return:
The existing technical delegation names Noel for ordinary product changes within the documented budget boundary. That helps explain the internal case, subject to the delegation's conditions. It does not settle an exception involving a customer delivery promise. I have not approved either proposed change or created a new authority. Please preserve that distinction in the status. I can provide the technical record through our ordinary business route, but cannot represent absent engineers' feelings or join the proposed group exercise.
Sana uses twenty minutes that day to read the relevant existing customer commitments and prepare and send her return:
The internal example is described in our current record as not changing a customer commitment. The second example may affect a delivery promise, and the authorized exception owner is not established in the material I checked. Please keep that change held for the appropriate company review. This is a real customer constraint, not evidence that an acquired team rejects integration. I have not contacted a customer, varied a contract or approved release. The company still needs an authoritative answer.
These are scoped role-holder returns, not legal conclusions supplied by the coach. They clarify the documented ordinary route for one case while leaving the other held. They do not establish a complete agreed protocol or approve either actual product change.
On 29 January Iris spends fifteen minutes reading both returns and preparing and sending a selected business status to Noel, Cleo, Vik and Sana. It records the ordinary delegation as described, the open exception and the absence of release approval. Each spends five minutes reading on 30 January without replying. Receiving a status is not agreement to an undisclosed new responsibility.
Review the real outcome, including the unresolved case
Iris spends fifteen minutes on 30 January preparing her selected learning and sending it privately to Ari. Ari spends fifteen minutes on 31 January reading and preparing and sending a reply. Iris spends ten minutes on 1 February reading it and preparing before their actual twenty-minute review.
They retain three conclusions: the initial expectations differed; relevant role holders actually returned information through accepted written windows; the complete two-case route is still not achieved. The ordinary route is described for one case, while the customer exception has no confirmed owner. One of two cases is clarified in that limited sense, not two approved changes or a successful integration.
Ari spends ten minutes on 2 February preparing and sending the finite close below to Iris. She spends five minutes reading it that day without replying.
Keep the documented ordinary route separate from the unresolved customer exception and from approval of either product change. The two-case target is not met. My withdrawn distrust interpretation must not reappear in a company report. Vik's written alternative and Sana's customer concern were legitimate contributions, not resistance. Any next company review needs its own authorized owner, scope and accepted capacity. This coaching exchange does not book that review or require another mapping exercise.
Include every participant's handling
| Person | Measured activities, minutes | Used / allocated |
|---|---|---|
| Ari | 15 January purpose and finite plan prepared/sent 20; 17 acceptance read and preparation 10; mapping conversation 40; 18 V1 prepared/sent only to Iris 15; 22 correction read, worksheet amended and repair sent 20; 31 learning read and reply prepared/sent 15; 1 February review 20; 2 close prepared/sent 10 | 150 / 180 |
| Iris | 16 plan read, accepted and invitations prepared/sent 10; 17 mapping conversation 40; 19 V1 read and correction sent 10; 23 amendment read and business request prepared/sent 15; 25 two offers read and acceptance sent 10; 29 two returns read and status prepared/sent 15; 30 selected learning prepared/sent 15; 1 February reply read and preparation 10; review 20; 2 close read 5 | 150 / 195 |
| Noel | 17 invitation read and preparation 10; mapping conversation 40; 30 status read 5 | 55 / 70 |
| Cleo | 17 invitation read and preparation 10; mapping conversation 40; 30 status read 5 | 55 / 70 |
| Vik | 24 request read and written alternative offered 10; 25 acceptance read 5; 26 delegation read and return prepared/sent 15; 30 status read 5 | 35 / 50 |
| Sana | 24 request read and written windows offered 10; 25 acceptance read 5; 26 commitments read and return prepared/sent 20; 30 status read 5 | 40 / 55 |
The known total is 485 person-minutes against 620 allocated, a difference of 135: thirty, forty-five and four lots of fifteen. The four-person forty-minute conversation and two-person twenty-minute review contribute 200 already included live minutes; other measured work is 285. Earlier records, integration operations, customer work and future company review are outside this account, not free. The difference is not proven company-wide headroom or a saving.
Recognize history without demanding reconciliation
Ask which capabilities, customer relationships and useful practices should be understood before change. Recognition needs follow-through. If leaders say a support team built an important escalation process, create an actual opportunity for that team to contribute to redesign, with time and decision scope agreed.
Optional personal expressions are not mechanisms that repair an organization. Do not require gratitude to a founder, an apology, acceptance of a hierarchy or a declaration of belonging as evidence of readiness. Recognition also does not preserve every legacy process. Explain fixed decisions, open proposals, reasons and constraints honestly.
HSE's Change standard emphasizes timely information, consultation, opportunities to influence proposals, timetables and support. Relevant legal, HR, employee-representation and integration obligations still need the appropriate expertise. A workshop cannot substitute for consultation, merger approval or employment advice.
Protect people during an unequal transition
A senior leader may experience open exploration while an employee fears a loyalty assessment. Explain records and audiences, allow disagreement and declining, and provide written or private alternatives. Do not infer safety merely because nobody objects publicly.
Move serious allegations, threats or concerns about employment rights into the suitable process rather than treating them symbolically in the group. Stay within competence and obtain relevant support. A map should not decide whether a dismissal is lawful or what a customer contract permits.
Judge follow-up by the original question: whether an authorized owner can be identified, what remains open, whether actual handoffs improve and whose account is missing. If collecting response times or rework, define the source, denominator and period. Ask whether participants could decline or disagree, but do not turn an emotional moment into proof of organizational benefit. Correct wrong interpretations and stop using the map when a conventional table would serve better.
Keep coaching reflection separate from governance records
Coachful is our #1 recommendation for organizing an appropriate client worksheet and agreed follow-up, not for certifying an acquisition or diagnosing teams. Forms and worksheets can hold the original claims-and-evidence prompts. Coach review is private to the coaching team; saving it does not deliver Ari's correction to Iris or issue a company decision.
Use the separate agreed sending route and verify audiences. Keep the client's private reflection distinct from the selected business status and official governance record. Linking the coach's own task to a client does not assign that task to the company or notify its employees.
Demonstration screens illustrate tools, not this company or an actual customer configuration. The family-business dynamics guide considers overlapping roles in another context. Compare relevant Coachful features with the agreed information and work requirements.
Frequently asked questions
Do most mergers fail because of hidden loyalties?
No sound universal claim follows. Define success and examine strategic, financial, operational and human factors. Do not use an unsupported failure percentage to sell this exercise.
Can a constellation diagnose integration resistance?
It can generate perspectives and questions, not establish a hidden cause. Check facts and hear affected people's accounts through appropriate routes.
Must people represent absent employees?
No. Use role cards, ordinary discussion or another chosen format. No participant needs to embody a colleague, report sensations as evidence or disclose personal history.
Can executives map without other employees present?
They can describe their own perspectives while marking the missing voices. They cannot establish employee views by representation. Obtain appropriate consultation instead.
What makes the exercise useful?
A clear question, genuine choice, checked interpretations and feasible follow-through. The useful outcome may be a simpler process table, an unresolved question honestly retained or a decision not to use the method again.
