Chapter 28: Map the Issue and the Loop Separately
Part V: Recognizing the Sequence
Keep the concern in view
“We are getting into our Loop” does not answer whether a responsibility was completed, an agreement was kept, or a boundary was respected. Recognizing an interaction gives you something to examine. It does not settle the matter you were trying to discuss.
Chapter 2, “The Issue and the Pattern,” established the distinction. Here the task is practical: describe what needs attention, then describe what starts happening while you try to address it. Keep both accounts specific enough that one cannot quietly replace the other.
In Break the Loop (BTL), the issue is what the partners are actually trying to address. Within BTL, the Loop is the proposed progression Launch → Overload → Old Story → Protection Move that a person may recognize across different disagreements; it is not simply a repeated topic, belief, or behavior. The issue and the Loop are two different things. Both can matter. These are organizing terms within Aaron Jarrels’s relationship education framework, not a diagnosis of the relationship.
The mapping guidance here is an optional educational application of that distinction. The evidence reviewed here does not establish this guidance as a validated assessment or show that it resolves disagreements. Use it to describe an ordinary, safe interaction provisionally. You do not need to produce a complete map, persuade a partner to participate, or fit every exchange into the framework.
Issue: What needs to be addressed?
Begin with the actual concern rather than a verdict about the relationship. In a fictional shared-car example, “The car was returned with too little fuel for the trip I had planned” identifies something that can be examined. “You never consider me” expresses a broader conclusion. The conclusion may reflect a serious concern, but it does not yet specify what happened or what needs attention.
Describe the relevant conduct, arrangement, and consequence. Was there an explicit agreement about refueling? Was one person relying on it? What was the practical effect? If no agreement had been made, that belongs in the account too. An expectation and a shared commitment are different things; neither should be invented afterward to make the account look clearer.
Separate what you know from what you still need to establish. You may know the fuel gauge was close to empty and that you had to stop before an appointment. You may not know whether your partner noticed it. The inconvenience does not disappear because intention is uncertain. Equally, the inconvenience alone does not establish deliberate disregard.
Next, identify what remains outstanding. In this example, that might be an agreement about returning the shared car ready for the next person’s use. If a clear commitment was missed, acknowledgment and responsibility for the consequence may also matter. These are possible concerns in a constructed example, not a rule that every couple needs the same arrangement.
An issue description need not end with compromise. A person may need information, a decision, a fulfilled responsibility, or a boundary. “I do not consent to that” is not an incomplete answer simply because it does not offer a middle position. Mapping should not convert a legitimate limit into a problem to negotiate away.
Loop: What starts happening while we address it?
Now describe the interaction without replacing the issue. Begin with the exchange you remember: what was said or done, how you experienced it, what you did next, and what followed. Keep observations and interpretations distinguishable. Where memory is incomplete, leave the uncertainty visible.
For a brief fictional illustration, imagine the car’s next user asking, “Why did you leave it almost empty?” The partner replies, “I only drove to the store.” The questioner says, “That doesn’t answer what I’m asking.” The partner responds, “You make it sound as if I did this on purpose.” The conversation shifts toward whether the opening question was an accusation.
The issue account concerns the fuel, the reliance on the car, and any relevant agreement. The interaction account concerns the question, the explanation, the repeated request, and the dispute about intention. Describing that exchange does not establish whether the explanation was evasive or the question intended as criticism. Those claims would need additional information.
From the questioner’s perspective, a provisional account might be: “When I heard an explanation without an answer about refueling, I took it to mean that the inconvenience did not matter. I repeated the question more sharply. We then argued about whether I was accusing you.” That account marks a reported meaning and the speaker’s own response. It does not fill in the partner’s inner experience.
Within BTL, the full sequence is Launch → Overload → Old Story → Protection Move. The detailed mapping chapters that follow address those parts individually. Here, a useful limit is to record only what you can identify. Do not invent narrowing capacity, a familiar meaning, or a protective function merely to complete the sequence. One described exchange also does not establish recurrence; Chapter 27 explains comparison across episodes.
Keep context and responsibility attached
The subject of a discussion should remain attached to its interaction description. Research on selected conflict discussions illustrates why. In a methods study, conclusions about observed demand-withdraw roles differed when researchers accounted for which partner was more dissatisfied with each selected topic (Crenshaw et al., 2021). Demand-withdraw concerns seeking engagement or change alongside disengagement; it is not another name for the BTL Loop.
The principal behavioral test involved 134 distressed married heterosexual couples discussing selected topics (Crenshaw et al., 2021). It does not establish that every couple switches roles, that one partner’s concern is justified, or that this chapter’s mapping guidance improves outcomes. Its narrower relevance is that an account of behavior needs its discussion context. Chapter 2 gives the fuller research treatment.
A repeated request may concern something that has repeatedly gone unanswered. An explanation may contain information necessary to understand what happened. A refusal may be a legitimate boundary. Describe the actual response before assigning a conflict label, and preserve what the request, explanation, or refusal was about.
Responsibility for the issue and responsibility for conduct during the conversation also need separate descriptions. If one person missed an agreed responsibility, the other person’s later sharpness does not retroactively cause that omission. If the questioner insults the partner, identifying the missed responsibility does not excuse the insult. Each action can be considered without assuming the contributions or consequences were equal.
The same distinction applies to your own account. You can acknowledge, “I interrupted before hearing the answer,” while retaining, “The arrangement still needs to change.” Or you can acknowledge a missed commitment while asking that the discussion proceed without insults. Neither acknowledgment settles every other question.
Put the two descriptions together without merging them
If it is safe and useful, describe one episode in two short passages. Under Issue, state the specific concern, relevant known facts or agreement, consequence, and what remains to be addressed. Mark a disputed detail as disputed rather than treating it as settled or erasing it. A partner’s disagreement does not, by itself, disprove your account.
Under Loop, describe the order of responses you can identify and your own reported experience. Include what you did next, rather than only what your partner did. A phrase such as “I understood that as dismissing the inconvenience” identifies an interpretation. It remains one person’s provisional account, not an agreed transcript or proof of intent.
Then read each passage against the other. Does the interaction description still leave the practical concern visible? Does the issue description distinguish the original conduct from what happened during the discussion? If either passage consists mainly of labels such as “selfish” or “defensive,” replace the label with the action or reported experience you can describe.
You may find that one passage is much clearer than the other. The agreement might be documented while the order of the conversation is uncertain. Or you may remember the exchange but discover that the expected arrangement had never been discussed. Keep that difference. A complete-looking account is less accurate if it fills missing information with assumptions.
These descriptions do not have to become a written record. If you choose to make notes, they remain your account and can be revised. You are not required to record episodes, obtain agreement about every detail, or share notes with a partner. Do not keep or disclose material if discovery could expose you to retaliation.
Distinguish a calmer exchange from an addressed concern
After mapping, ask separately what remains of the issue. Has a decision been made? Has a missed responsibility actually been completed? Is an arrangement still disputed? The answer may remain unfinished even if the conversation is calmer. A change in atmosphere is not evidence that an action occurred.
In the car example, the partners could speak respectfully and still leave the refueling question unanswered. They could also agree on refueling while remaining dissatisfied with how they spoke to each other. These are constructed possibilities, not findings about what mapping produces. Neither description should certify success on behalf of the other.
Avoid using recognition as a condition the other person must meet before a concern can be heard. “We need to talk about the Loop before I answer you” should not become an indefinite exemption from the original responsibility. You can identify a conversation you are unwilling or unable to continue while still being clear about what remains unresolved. This does not require staying in an unsafe interaction or promising further contact where that would be unsafe.
Mapping also does not decide which practical solution to choose. A schedule may need changing, a responsibility may need reallocating, or a boundary may need maintaining. Those decisions require the relevant facts, preferences, obligations, and consent. An interaction description does not supply them automatically.
When safety changes the task
Do not use the two descriptions to turn coercion, threats, violence, stalking, sexual coercion, or fear of retaliation into an ordinary shared Loop. Official domestic-violence guidance identifies intimidation, coercive behavior, and control as safety concerns (U.S. Department of Justice, Office on Violence Against Women, 2025). A mutual conversation map must not replace attention to the conduct and the danger.
If it is unsafe to disagree, decline, seek support, or leave the conversation, prioritize safety and individualized specialized support rather than joint mapping. You do not need a complete account or a partner’s agreement before seeking help. Do not confront a partner or disclose a map because this chapter suggests describing an interaction. Chapter 53 develops the safety and referral boundaries more fully.
Carry both questions forward
For an ordinary, safe disagreement, the result may be modest: a clearer statement of the concern and a provisional account of what happened while discussing it. Neither needs to explain the whole relationship. Leave uncertain details open, and keep the practical matter visible as you examine your own responses.
Chapter 29, “Map Your Launch,” narrows the next task to what happened and what you noticed, while distinguishing observation from inference. Carry the issue description with you. Greater detail about the sequence should not cost you sight of what still needs addressing.
Back to the Field Guide table of contents