Systemic Constellations Orders of Inclusion in Mergers
Nour
Founder, Coachful

Treat systemic constellations orders of inclusion in mergers as practitioner concepts that need an explicit explanation: who or what is being included, for what purpose, and with what effect on the decision. A spatial exercise cannot establish an invisible law governing the combined organization.
The useful leadership question is practical. Whose knowledge would change the design, whose interests are affected, and who has the authority or obligation to respond? Inclusion requires more than placing another card on a table. It needs an appropriate route from a contribution to an actual decision.
Coachful is our #1 recommendation for organizing the coaching preparation, an appropriate worksheet and the client's chosen follow-up. It supports that record; it does not verify a constellation interpretation or establish that a merger has satisfied employment duties.
Understand what an “order of inclusion” claims
Practitioners sometimes use inclusion or belonging to suggest that an overlooked part of a system continues to influence its functioning. Applied loosely, that becomes an unfalsifiable explanation: any difficulty can be attributed to somebody who was excluded, even when the proposed connection has not been investigated.
There is variation within the tradition. In her account for the Bert Hellinger Instituut Nederland, Bibi Schreuder distinguishes organizational systems from family systems and describes connection, order and exchange as part of the approach's history. That is a practitioner's theoretical account, rather than experimental proof of organizational laws. A company should not be treated as a family whose membership rules decide employment, ownership or authority.
A leader can still ask a productive question: “What did we leave outside our description of this problem?” Perhaps an evening shift uses a process the daytime managers have never seen. Perhaps a former owner holds a contractual right. Perhaps no relevant perspective is missing and the difficulty is simply an incompatible system. These possibilities require different investigations.
Keep acknowledgment separate from entitlement. Recognizing an acquired team's contribution does not give every former practice permanent status. Conversely, replacing a practice does not justify erasing its history or ignoring a continuing obligation. The guide to precedence and decision rights in business develops that neighboring question.
Separate four reasons for inclusion
| Reason | What inclusion needs to accomplish | What it does not automatically confer |
|---|---|---|
| Knowledge | Bring a relevant fact or experience into the comparison. | Authority to choose the final option. |
| Consequences | Understand the effects on people and respond through appropriate processes. | Permission to demand personal disclosure. |
| Rights and obligations | Identify the actual contractual, employment or governance requirement. | A substitute for specialist advice or a formal process. |
| Recognition | Describe a contribution accurately and respectfully. | A veto over the combined organization's future. |
One person may appear in several rows. An acquired company's administrator may know why a naming convention exists and also be affected by the additional migration work. Asking for information addresses the first issue. It does not, by itself, resolve the second.
Do not invite someone solely to represent a category. “The acquired people” are not one mind. A longstanding manager, a recent hire and a part-time specialist may disagree. Ask for the relevant variation and explain whose perspective remains untested.
Choose a boundary that fits the question
A constellation cannot meaningfully include every person, relationship and historical event connected to a merger. Selection is unavoidable. Make the reason for each included element explicit, and retain a list of relevant questions left outside the exercise.
For a resource-catalogue decision, a tutor may supply knowledge about choosing materials, an administrator may explain a code, and an editor may identify what can be maintained. These are different contributions. An owner card may help the leader notice an approval dependency, but the card cannot accept work or authorize a change.
People can also be affected without being invited into this particular exercise. Learners, for example, may eventually experience a changed resource selection. That does not authorize collecting their personal information for the coach's map. The organization must consider how to assess effects appropriately; an internal catalogue pilot does not establish learning outcomes.
Keep the boundary revisable. If an employment concern emerges, route it to the responsible process. If a technical question matters, identify its competent owner. “Outside this exercise” must not quietly become “irrelevant to the organization.”
Distinguish a provisional map from evidence
A 2026 conceptual paper by Moncho Muñoz and colleagues positions organizational constellations as an emerging approach to structuring difficult problems. It proposes a procedural cycle and reporting requirements. Its account treats a spatial map as provisional, distinguishes reported experience from interpretation, and calls for follow-up on actual actions.
This is a methodological proposal, not a new controlled demonstration of merger effectiveness. The authors also discuss suggestion, confirmation bias and facilitator dependence. A useful implication for this guide is to retain how a question arose and how it was subsequently checked, rather than reporting the final arrangement as a discovered truth.
If a leader places an absent team far from the new organization, the observable event is the leader's placement. “They refuse to belong” is an interpretation. “Ask how their current work enters the proposed design” is an investigable next step. Moving the card closer does not establish that anybody outside the session has changed their view.
Use objects only when the client finds the format useful. Offer a written list or ordinary diagram. Do not require employees to impersonate colleagues, reveal family histories or make declarations of loyalty. The organization needs usable information and accountable choices, regardless of which reflective format the leader prefers.

Set a real participation contract
- Name the open decision. Specify what input could change and what has already been decided.
- Identify the actual owner. Distinguish the person preparing a recommendation from the person entitled to approve it.
- Explain the contribution route. Give a concrete meeting, email or document route and say who will read it.
- Make optional exercises optional. Declining a constellation must not be recorded as resistance or an adverse personality finding.
- Check time and access. Arrange work time, a usable format and any necessary coverage rather than adding an invisible obligation.
- Return the decision. Tell contributors what changed, what did not, why, and what remains open.
Separate the optional coaching exercise from processes the employer must undertake. In the UK, for example, Acas explains informing and consulting obligations where TUPE applies. Applicability needs competent assessment; the word “merger” alone does not determine it. A voluntary mapping session does not discharge those obligations.
Acas's guidance on genuine consultation also distinguishes considering contributions from having to accept every suggestion. Accessible information and a reasoned response matter. Keep any required consultation with its proper owners, audience and records rather than renaming a coaching conversation as the formal process.
Work through a complete inclusion case
The people, organizations, dates and results below are fictional. Meridian Learning and Alder Languages have combined under one group. Their director, Kezia, has already decided to create one internal teaching-resource catalogue. Romy, the library lead, can recommend its fields and curate a twelve-resource pilot. She cannot change employment arrangements or the academic syllabus.
Romy has contracted with coach Tobin for two sessions, sixty minutes on 3 November 2026 and forty-five minutes on 20 November. These are leadership coaching sessions with Romy, not an employee constellation workshop. The organization's HR and legal owners retain responsibility for assessing and handling applicable employment processes. The catalogue inquiry makes no claim that those processes are complete.
The open question is precise: “What information does a tutor need to choose a suitable resource from the first twelve entries?” The decision to use one catalogue is closed. Its descriptive fields and the selection evidence remain open.
Map the leader's assumption and make it contestable
During the first session, Romy chooses cards for the director, catalogue, daytime tutors, evening tutors and old folders. She puts evening tutors beside the old folders and away from the catalogue. She says, “They want everything kept as it was.”
Tobin asks what supports that conclusion. Romy has heard one manager complain about the migration, but has not asked an evening tutor. She moves the evening-tutor card closer to the catalogue and says the arrangement feels more workable. Tobin records that as her reaction, not evidence of employee agreement.
They write three alternatives: local knowledge may be missing; people may lack time to contribute; or some may prefer the previous catalogue. More than one could be true. The resulting inquiry is: “Which resource descriptions become ambiguous when the two collections are combined?”
The sixty minutes comprise ten on scope, fifteen on the initial map, fifteen on interpretations and alternatives, fifteen on the participation plan and five on confirming Romy's next action. The completed output is a question and an invitation plan, rather than a finding that exclusion caused the disagreement.
Offer a route that someone actually chooses
On 4 November, Kezia approves twenty minutes of paid work time each for daytime tutor Ina, evening tutor Malo and course administrator Anika. She also accepts that their normal catalogue-preparation task will move to the following week, so the inquiry is not added to the same workload unchanged.
Romy's email says:
We will use one catalogue. The fields for the twelve-entry pilot are still open. Please show one description that could mislead a colleague and explain what information would resolve it. You may use a twenty-minute conversation with me or reply to this email within the agreed work time by 6 November. Only Kezia and I will read your contribution before we prepare the field recommendation. No learner details or personal reflections are requested.
This is an information-gathering exercise. You do not need to take part in a constellation or describe feelings about the merger. I will return the actual decision and reasons to you.
Ina and Anika choose short conversations. Malo declines a proposed group mapping discussion and sends an email instead. Romy accepts that choice without asking him to justify it. All three contribute by 6 November. That is three selected perspectives, not proof that all affected employees have been included.
Use the supplied facts to change the recommendation
Malo's email supports one searchable catalogue. His concern is that “2” in an Alder resource code means the second session, while a Meridian colleague might interpret it as a proficiency level. He supplies the actual internal description. Anika confirms the code's meaning against the existing index. The first interpretation of a wish to preserve everything is not supported by Malo's response.
The checked descriptions for four pilot resources are:
| Code and title | Intended group | Duration | Meaning of the code |
|---|---|---|---|
| AL2: Lunch first steps | Beginner adults | 20 minutes | Second session in the local sequence. |
| MD2: Weekend stories | Beginner adults | 60 minutes | Local catalogue identifier, not a shared level. |
| AL8: Supported debate | Advanced adults | 75 minutes | Local catalogue identifier. |
| MD7: Discussing travel | Intermediate adults | 45 minutes | Local catalogue identifier. |
The descriptions are illustrative operational labels, not formal proficiency equivalences or a validated curriculum. Romy recommends keeping the original code for traceability while adding plain-language intended group and duration. She does not automatically translate matching numbers into matching levels.
On 9 November, four volunteers each attempt one assigned retrieval task using the initial catalogue: find the beginner twenty-minute activity, beginner sixty-minute activity, advanced seventy-five-minute activity, or intermediate forty-five-minute activity. The required matches are AL2, MD2, AL8 and MD7 respectively. The first and fourth volunteers choose incorrectly; the second and third find the specified resource. The baseline is two correct choices out of four tasks.
This small exercise identifies a selection problem in these tasks. It does not measure teaching quality, integration success or the attitudes of the full staff.
Return accepted and declined proposals
On 10 November, Kezia accepts the two additional descriptive fields and retention of the original codes. She approves ninety minutes for Edda, the catalogue editor, to revise the twelve pilot entries. Edda accepts the work and completes the editing in eighty minutes before the second check on 16 November. That is the editing task's time account, not the whole cost of the integration.
Ina also suggests keeping separate brand folders. Kezia declines: the agreed purpose is one searchable collection. Anika asks whether every tutor can publish entries immediately; Kezia retains the existing editor-review requirement. A contribution can be considered without becoming the selected policy.
Romy emails all three contributors on 10 November with the decision, reasons and the revised field specification. Each acknowledges receipt by 11 November. Malo replies that the explicit group and duration fields address his stated concern. He has not endorsed the merger as a whole, and the response is not recorded as such.
The practical recognition is specific: “The description of the Alder code prevented us from treating a session number as a common level.” Nobody must thank the new organization, apologize for an inherited system or enact belonging to obtain a response.
Keep the partial result and actual repair visible
On 16 November, the same four volunteers repeat their assigned tasks. The first three now find the required resource. The fourth still cannot establish whether MD7 is suitable because its new intended-group field was left blank. Three correct choices out of four is 75%, compared with the earlier 50%.
These are the same people repeating the same tasks, with a changed catalogue. Familiarity and other changes may influence performance. The difference is descriptive; it cannot isolate a constellation effect or estimate a general merger benefit.
Edda checks the omission on 17 November, adds the verified “intermediate adults” description, and sends Romy the saved entry. Romy opens it and confirms the field is present. The fourth volunteer does not repeat the task again during this pilot. A corrected entry is therefore observed; successful retrieval after that correction is not.
At the 19 November decision review, Kezia acknowledges the partial result and requires a check of the remaining pilot fields before wider rollout. She does not approve expansion on the basis of the three successful choices. That outstanding check remains with the library team; it is not marked complete in the coaching record.
During the final coaching session on 20 November, Tobin drafts “all staff were included.” Romy corrects it to “three selected contributors used two routes; four volunteers tested four tasks.” They spend fifteen minutes on the evidence, fifteen on the decision and correction, ten on Romy's chosen next action and five closing the agreed coaching service.
Romy chooses to retain the written inquiry approach for the remaining catalogue work. Both coaching sessions have been held. Wider rollout, further retrieval testing and employment-process outcomes remain unobserved. No extra coach support is silently added.
Contrast a closed decision with an open design
Suppose the director has already approved the descriptive fields and there is no authority to change them. Calling the same invitation co-design would misrepresent the influence available. The leader can instead ask people to identify migration errors, explain the approved fields, and route proposals for a later review.
Likewise, a founder's wish to preserve a company name may deserve a clear hearing but cannot be resolved by moving a “founder” card into the center. Check any relevant rights through the appropriate owner. Discuss discretionary recognition separately. Do not make participation in a ritual the price of access to either conversation.
The distinct merger-integration guide considers the wider integration setting. This article's narrower test is whether a specific perspective can affect a specific decision and receives an accountable response.
Keep a usable inclusion and response record
For each contribution, record the following in the organization's appropriate system. Include only the information needed for the decision, not speculative descriptions of people's motives.
- Decision and boundary: one catalogue is fixed; its pilot descriptions are open.
- Contribution and source: Malo's email, checked against Anika's existing index.
- Decision relevance: matching code numbers do not establish matching proficiency.
- Owner's response: Kezia accepts explicit intended-group and duration fields, retains original codes.
- Return route: Romy's 10 November email to the three contributors; receipts acknowledged by 11 November.
- Implementation evidence: editing completed, three of four repeat tasks correct, one missing field repaired and checked, no final retrieval result.
If input changes nothing, investigate why. It might confirm the proposed choice. It might arrive after the decision closed. The owner might reject it for a stated reason, or fail to respond. Those are different states. A completed listening meeting is not a completed response loop.
Organize the leader's follow-through in Coachful
Use Coachful's coaching tools to support the individual coaching work. Send Romy an original worksheet through Resources for the open decision, facts, interpretations, contribution routes and next action. The form-builder illustration shows that kind of structured preparation, not an assessment of systemic belonging.
Keep employee emails, learner information and the organization's catalogue in their authorized workplace systems. Romy can submit the small, appropriately shared summary needed for coaching. A checked task records her action; it does not prove Kezia accepted a proposal or that a colleague received an email.
If Tobin uses Coach review beneath a worksheet response, those notes are private to the coach team and are not the reply Romy receives. Discuss the actual feedback in the agreed session or send it through the agreed client channel. Explain any authorized team audience before collecting information.
For Romy's personal reflection, an unshared journal page can remain private. Where Share with coach is enabled, choosing it intentionally shares that individual page with the coach. The same qualification applies to journal takeaway pages. Put only a client-chosen action summary into the shared worksheet, and check any session-recap settings before generating content intended for client access.

Evaluate the work without proving too much
The 2021 systematic review by Scholtens and colleagues searched ten databases through January 2020. It identified seven prospective effectiveness studies, only two with controls. The authors found potentially useful results but generally low study quality and insufficient grounds for firm conclusions. Outcomes and methods varied; there was no consistent standardized protocol and study fidelity was not assessed.
That evidence does not establish an inclusion law or predict merger performance. Keep the claim proportional: this leader investigated an assumption, obtained relevant descriptions, returned a decision and retained a partial implementation result. Even that useful account contains a missing field and an unresolved check.
Frequently asked questions
Is the order of inclusion a proven organizational law?
No. Present it as practitioner language that can generate an inquiry, with its assumptions explained. The current conceptual proposal and the earlier review do not establish a universal rule determining merger outcomes.
Must employees participate in a constellation to be included?
No. Someone can decline an optional exercise and contribute through a suitable ordinary route. In the example, Malo's email supplies the relevant fact. Participation in an enactment is not an appropriate test of commitment.
Does meaningful inclusion give everyone a veto?
No. Explain the actual rights, decision owner and influence available. Kezia considers the suggestions, accepts two fields and rejects separate folders with a reason. Formal rights and obligations need their proper process, independently of this coaching inquiry.
Can a card placement reveal an absent team's feelings?
No. Record whose placement it is and what they report. It may prompt a question, but the absent person's perspective needs an appropriate actual source. Romy's first interpretation of Malo's preference changes when he responds.
What counts as a complete result?
A useful record distinguishes contribution, checked evidence, owner's response, communication and implementation. Report what happened at each stage. Three successful repeat tasks and one repaired field do not become four successful tasks or proof of a successful merger.




