The Practitioner Who Held the Boundary

This is a composite story drawn from common patterns in practitioners who work with the relational conflict trigger. Details are illustrative, not specific. Take your time with this.

The scope had expanded three times in eight months.

She could see it clearly when she looked at the agreement she’d signed with her longest-standing client versus what she was actually delivering. The original scope: two strategy sessions per month and a monthly email review. What she was delivering: two strategy sessions per month, monthly email review, weekly voice message check-ins she’d “offered” after a difficult period, a quarterly report she’d started producing without it being requested, and occasional ad-hoc calls that the client scheduled informally.

None of the additions had been negotiated. Each had arrived as a reasonable accommodation to a specific situation. Each had been absorbed. Together, they had become the implicit scope — the client expected them all now, because she’d delivered them consistently.

She named the trigger before she tried to address the scope. This was important. Without naming it, she’d tried twice before to address the scope with this client: once she’d written the email and deleted it; once she’d started the conversation in a session and pivoted at the last moment when the client’s energy shifted.

The relational conflict trigger. The prediction: naming the scope issue would feel like an accusation. The client would feel criticized. The relationship would be damaged. The client would leave.

She’d been in business for four years. She hadn’t had a difficult scope conversation with a single client. Not because scope hadn’t drifted — it had, repeatedly — but because the trigger had managed the situation before the conversation could happen.

The pre-commitment was written as a script, not a principle. Not “I will hold my scope” but: “I’m going to name something at the start of our next session. Over the past several months our engagement has evolved — in a positive direction in terms of the work — and I realize I haven’t been tracking the scope clearly. I’d like to name what we’re currently doing and bring that into the formal agreement, because I want our work together to be sustainable.”

She rehearsed it. She noticed the activation as she rehearsed: tight throat, rapid heartbeat, a pull toward “or I could just let it go.” She regulated. She returned to the script.

The session arrived. She said the words. Her voice was level — she could feel the effort it took to keep it level, but it stayed level.

The client’s response was not what the trigger had predicted. There was a brief pause. And then: “Oh — yes, that makes sense. I hadn’t thought about how much had been added. Let’s look at what we’re actually doing.”

Twenty minutes later, the scope was named clearly. The client suggested an adjusted rate before she had to propose it. The conversation ended with both of them feeling the relationship was more solid, not less.

She wrote it down. What the trigger predicted: accusation felt, relationship damage, client departure. What actually happened: productive conversation, scope clarity, client-initiated rate adjustment, increased trust.

She didn’t expect the next scope conversation to be easy. The evidence record had one data point. The trigger’s record had four years of its own evidence: that avoidance maintained the relationship. The trigger’s narrative was older and more densely woven.

But the one data point was real. The client hadn’t left. The relationship hadn’t been damaged. The naming had produced relief on both sides, not rupture.

She started looking for the next scope conversation that needed to happen. There were two more with other clients — situations she’d been managing around for months. She wrote the scripts for both.

By month six she had eight scope conversations in the trigger journal. Six had gone well — the scope was named, the agreement was updated, the relationship had held or strengthened. One had been genuinely difficult — the client had pushed back, the conversation had required multiple exchanges over two weeks before resolution. One had ended the engagement, and she’d referred the client to someone better suited.

The trigger still predicted relational damage. The record showed: eight conversations, six good, one difficult-and-resolved, one appropriate ending. No catastrophic ruptures.

The data point that mattered most to her was the engagement that ended. The trigger had predicted it as a loss. Looking at the record, she saw it as a completion — a relationship that had run its course, ended with care, and freed capacity for work that was a better fit.

The trigger had been protecting against something that, in that case, was actually fine.

If you want community for this work — the Abundance GPS community on Skool offers a free trial. Come as you are.