Exhaust (Energy Erosion)
Linas JuozėnasShare
Divide Isolation & Triangulation
Divide separates you from allies, truth, and context until you stand alone and become easier to move. It often arrives quietly: “They said…”, backchannels, secret side-conversations, and messages delivered through intermediaries.
Restore the shared field.
Why Divide works.
When context is split, emotion is often asked to fill the missing pieces.
Divide thrives on asymmetric information and emotional velocity. When you only hear one side, your nervous system may rush to protect, fix, defend, or choose a side before the other perspective even appears.
By then, energy has already been spent and trust may already have been damaged. The first counter-move is the same as with every hostile pattern: name it.
“This is Divide” interrupts the relay. It reminds you not to become a courier for somebody else’s conflict and points you back toward shared ground.
+ speed
= premature allegiance. Slow the message down before it becomes a relationship fracture.
Recognition: signals & setups.
The pattern often looks ordinary until you notice where information is being kept apart.
Common signals
- “They said…” relays without names, screenshots, or context.
- Requests to “keep this secret” about a shared project.
- People avoid direct contact and prefer intermediaries.
- Two allies report different “final” versions of the same decision.
- You feel loyal to one person and suspicious of another before verifying facts.
Typical setups
- Decisions are made in private DMs rather than shared spaces.
- No written recap follows decision-bearing meetings.
- Roles and authority lines are ambiguous.
- Time pressure prevents verification before response.
Divide in the field.
Three environments. The same triangle.
Clinic triangulation
A client messages: “Your assistant was rude; don’t tell them I told you.” Emotion spikes immediately.
Instead of accepting the triangle, the healer names the pattern and replies that service concerns are handled in a shared thread so they can be resolved accurately.
Once all relevant people are present, context changes: the “rudeness” was a firm policy reminder. The client is heard, the assistant is not quietly condemned, and the policy can be explained with more care.
The silent CC
A project lead receives a forwarded screenshot of a teammate “questioning their vision.”
Instead of confronting the teammate privately, the lead posts openly: “I’m seeing questions about scope. Let’s collect them here and close with a recap today at 16:00.”
The shared thread reveals real concerns, the scope improves, and resentment falls because the process itself is visible.
The family wedge
A relative calls to complain about another: “Don’t tell them I said this, but…”
You decline the courier role: “I only discuss issues when everyone involved can hear and speak. I’ll invite them to a call.”
The wedge either dissolves or becomes visible. Either result is cleaner than carrying conflict between two people.
Collapse the triangle.
Do not choose a side before restoring the shared field.
-
Name it.
Say or write: “This is Divide.” The goal is not to accuse somebody—it is to recognize the shape of the interaction. -
Move the conversation to a shared channel.
Use a group email, project thread, shared document, or meeting containing all relevant parties. -
Confirm facts.
Ask for specifics: who, what, when, where. Attach links, documents, screenshots, timestamps, and other evidence where appropriate. -
Decide roles and authority.R · Responsible Who performs the work?A · Accountable Who owns the final result?C · Consulted Whose input is needed?I · Informed Who needs visibility?
-
Recap publicly.
Post a brief, neutral summary: what was agreed, who owns each action, and when the next step is due.
Boundary scripts.
Language that returns conflict to the people and channels where it belongs.
Short & neutral
De-triangulation acknowledgment
Thanks for raising this.
To ensure accuracy and fairness, I’m moving this into a shared thread with the relevant people.
Please reply here with any specifics—dates, links, screenshots, or other context. We’ll agree on next steps and owners in this thread.
— [Your name]
When secrecy is demanded
Five-minute Heart-Anchor reset.
Restore enough steadiness to separate fact from emotional relay.
Return to shared truth
-
Hand on heart · 30 sec
Feel the weight of your palm. Soften jaw and shoulders. -
Breath · 120 sec
Inhale 4 seconds / exhale 6. Whisper: “I return to shared truth.” -
Reality check · 60 sec
Write three facts you know for certain: names, dates, links, direct statements. -
Bridge move · 60 sec
Draft one sentence that moves the conversation into a shared channel. -
Anchor · 30 sec
Touch black tourmaline, a desk edge, or another solid object before pressing send.
messages between sides.
I return them
to the circle.
Norms. Roles. Rhythm.
Make shared reality the default rather than something you rebuild after every fracture.
Norms
- No backchannels for decisions. Private messages may clarify logistics, not silently alter scope.
- Public recaps within 24 hours of decision-bearing meetings.
- Questions live where the work lives: project board, shared doc, CRM, or agreed thread.
Roles · RACI
Rhythm
- Weekly sync: 30–45 minutes to surface misalignment early.
- Shared dashboards: status, owners, and due dates stay visible.
- End-of-week recap: what changed, what did not, and what comes next.
Templates for shared reality.
Structure the thread so nobody has to reconstruct it from memory later.
Shared Thread
Decision Recap
Mediation & escalation ladder.
Escalate structure before escalating emotion.
Shared thread. Give the relevant parties 24–48 hours to align on facts and next steps.
Keep it focused. Use a scribe or another agreed record of decisions and actions.
Bring in an appropriate mediator, manager, safeguarding professional, or other neutral person if facts remain contested.
If transparency norms are repeatedly rejected, change the engagement or leave it.
Are we drifting apart?
Use the dashboard as an operational signal—not as a diagnostic instrument.
Where transparency needs judgment.
Some matters must begin privately. Use the correct HR, safeguarding, legal, or security channel. Share only an appropriate sanitized outcome where appropriate.
Look for recurring patterns rather than treating unverified specifics as established fact. Invite accountable input where possible.
Their responsibilities may simply overlap badly. Return to scope, RACI, and the mission instead of deciding who is the villain.
Decline to become a courier of interpersonal conflict. Offer an appropriate shared conversation instead.
Connect it to the Handbook.
Use opening and closing rituals around conversations likely to carry conflict or emotional charge.
Combine shared channels with calm tone, precise language, and deliberate timing.
Shared tools, permissions, policy pages, and decision records make information drift harder.
Field questions.
What if moving to a shared thread escalates conflict?
That reaction is information. But visibility is not always the only goal: use the escalation ladder and choose an appropriate structured channel. Shared thread → live conversation → neutral third party.
Isn’t some private discussion healthy?
Yes. Emotional processing, mentoring, friendship, and many personal conversations appropriately happen in private. The distinction is that decisions affecting shared work need an accountable record.
What if a client refuses shared communication?
Offer one clear and appropriate channel such as email or a client portal. If a person repeatedly refuses the communication structure required for safe, accurate work, the engagement may not be a good fit.
Triangles fracture trust.
Circles sustain it.
When you collapse a triangle, you do not take sides— you restore the field where truth can land.
Divide weakens when conversations become visible, roles become clear, and decisions leave a record. Protect the circle—not by forcing agreement, but by giving reality a place where everyone relevant can see it.
Quick reference.
The entire response reduced to its essential moves.