Chapter 29: Map Your Launch
Part V: Recognizing the Sequence
Begin with one moment
A recurring disagreement may be described in a single sentence that mixes an event with a conclusion about why it happened: “You changed the plans because you do not respect my time.” Perhaps the plan changed. Perhaps that change had a real cost. The statement about respect is a further interpretation. Mapping a Launch begins by giving those elements separate places.
Chapter 12 introduced Launch as a Break the Loop (BTL) concept. Within BTL, a Launch is the event as the person experienced it when they began getting pulled into the Loop. It can be something said, done, noticed, or missing. The question is not “Who caused this entire argument?” but “What happened or what did I notice at the point where I began getting pulled in?”
That question matters because one sentence can contain several different claims. Some concern events that could be checked. Others concern an individual’s experience. Still others attribute an intention or belief to a partner. All may matter, but they are not interchangeable. A description of a Launch does not settle whether an agreement was broken, who is accountable, or what another person meant.
The following mapping process is an optional educational application of the BTL framework, not a validated assessment or a demonstrated method for reducing conflict. It can help organize an account without establishing that the account is complete or that the four-part Loop has been independently validated. You can leave any answer unfinished when the information is insufficient.
Choose a specific exchange
Start with a particular episode rather than a summary of the whole relationship. “Last night, when we were discussing the weekend schedule” gives a setting. “Whenever you disregard me” begins with a general conclusion and leaves the event unclear.
Consider a fictional example. Jordan and Taylor have discussed sharing responsibility for picking up a package before a store closes. In the evening, Jordan asks, “Did you get the package?” Taylor answers, “I had a lot going on today.” Jordan asks again. The discussion moves quickly toward whether Jordan is accusing Taylor of being irresponsible.
For Jordan, the Launch might be hearing an explanation that did not answer the question. For Taylor, it might be hearing the question repeated. These are possible points of entry into their respective experiences, not a ruling that their contributions are equal or that the exchange began there in any objective sense.
The package still matters. Was someone responsible for collecting it? Was the agreement explicit? Can it still be collected? Those questions belong to the issue. Chapter 28 explains how to map the issue and the interaction separately. A Launch description should not displace the practical question, and noticing two perspectives does not erase an unmet commitment.
Pick one moment you can describe without constructing a complete theory about the interaction. If several moments seem important, identify the one you remember first noticing and leave earlier events open for later consideration. You are describing the starting point of your account, not proving a single original cause.
What happened?
The first practical question is what you can say about the event itself. For the fictional package example, Jordan might write, “I asked whether the package had been collected. I heard Taylor say that the day had been busy, without answering yes or no.” That reports an exchange. It is more specific than “Taylor was evading responsibility,” which identifies a possible interpretation rather than the words spoken.
Sometimes the event is straightforward. A partner said, “I am not going.” A mutually agreed bill was unpaid when it was due. Someone raised their voice and used an insulting name. Such conduct does not have to be rendered neutral in order to be described accurately. The task is to identify what occurred, including conduct that may require accountability.
Other details may be uncertain. You may remember that a question was asked but not the exact wording. In that case, “You asked about the package, although I do not recall your words exactly” is better than a quotation invented for clarity. An account can be precise about its limits.
It may help to distinguish a fact supported by an agreement, message, or other record from something recalled from memory. That distinction does not mean a record is always required or that a person’s memory is unimportant. It simply prevents a recollection from being presented as a verbatim transcript when it is not.
What did I notice?
An event may contain several details. One person notices the words. Another notices the timing, silence, volume, a facial expression, or the fact that a decision has already been made. Naming what stood out can clarify the experience without claiming that the same detail had the same meaning for both partners.
Taylor might write, “I noticed that the question came again before I had explained what happened.” Jordan might write, “I noticed I still had not heard whether the package was collected.” Both descriptions can be useful. Neither establishes what the other intended by speaking or not speaking.
Perceived tone belongs here when it is clearly marked as perception. “I heard the question as sharp” reports experience. “You asked sharply because you wanted to humiliate me” adds a theory about purpose. The first statement can be sincere without making the second true.
An absence can be a Launch too, but it needs context. “I did not receive the update we agreed would be sent by noon” differs from “You deliberately ignored me.” It also differs from “I hoped for a message but we had not made an arrangement.” Missing actions, explicit commitments, and private expectations should not be merged.
What is observable, and what am I inferring?
The next distinction is between the event as you can describe it and the meaning you have attached to it. In the research literature on marital attribution, explanations for why a partner acted are distinguished from judgments about responsibility, including intention and blame (Bradbury & Fincham, 1990). This is an external conceptual distinction, not evidence that identifying a BTL Launch improves outcomes or reveals another person’s real motive.
Try placing two statements next to each other. In the package example, an event description might be: “I asked whether the package was collected and did not receive a direct answer.” An interpretation might be: “I thought Taylor was trying to avoid admitting a mistake.” The interpretation may turn out to be accurate, partly accurate, or unsupported. Nothing about separating it requires pretending that the original responsibility was unimportant.
A different interpretation is also possible: Taylor might have been preparing to explain a missed errand, attempting to defend a difficult day, or responding to an accusation they thought they heard. Those possibilities are not facts supplied by the example. Do not list alternatives merely to manufacture doubt about your own experience. Their value is to show where information remains absent.
Keep in mind
If a partner explicitly says, “I did not bother because your plans do not matter,” those words are themselves part of what happened. You need not classify clear statements as unknowable. You also need not treat every accusation or denial as conclusive proof of someone’s inner state. Describe what was said, what was done, and which further conclusions remain inferential.
Similarly, “I felt disregarded” need not be replaced with “I was probably mistaken.” A feeling is a report about your experience. Whether the partner intended disregard is a separate question. The distinction leaves room for both impact and responsibility without making subjective experience a test of intention.
Keep the context attached
A brief description should carry enough context for the reader to understand what the observed moment concerned. If a repeated question followed an unanswered request about an overdue obligation, it may matter that the obligation existed. If a partner refused a request because it crossed a boundary, that context matters too.
A short entry can distinguish the arrangement, event, effect, and uncertainty. In the package example: “We had agreed that Taylor would collect the package. I asked whether it had been collected. I did not hear an answer at first and worried the store would close. Then, I interpreted the explanation as avoiding the question, but I do not know whether that was Taylor’s intention.” The missed errand, if verified, remains open for resolution.
The purpose is not to reconstruct everything that happened or to assign a neutral score to both partners. A good description may conclude that one person missed a commitment. It may also identify an insult or threat that occurred during the discussion. Distinguishing these elements makes each visible; it does not average them into shared blame.
There may be important facts you cannot establish. You may not know whether your partner saw a message, heard a remark, knew the deadline, or intended an implication. State the uncertainty where it exists. Do not introduce an innocent explanation as though it had been confirmed. Do not introduce a hostile explanation as though the felt impact had proven it.
A compact Launch record
You may use four short prompts for one episode. These are optional writing prompts for organizing your own account, not a questionnaire with a score, a clinical measure, or an additional named BTL intervention.
First, identify the event: What happened, as best I can describe it? Include words, actions, or an important absence, and distinguish what you remember from what you can independently check.
Second, identify the noticed detail: What stood out to me at that moment? This might be a phrase, silence, change, tone as heard, or a practical consequence. The answer belongs to your experience even when the other person noticed something different.
Third, separate what is known from what is inferred: What do I know about the conduct, agreement, or consequence? What am I taking it to mean about the other person’s beliefs or intentions? If intention is genuinely uncertain, leave it open. If words or behavior clearly establish a violation or threat, name that conduct rather than treating it as an interpretive puzzle.
Fourth, keep the issue visible: What still needs to be addressed, regardless of the interpretation? The answer might be an overdue responsibility, a decision, an explanation, an acknowledgment, or a boundary. The fact that a Loop may be developing does not suspend the issue.
What to do next
An entry could be only a few sentences. “When I heard the schedule had changed, I noticed that the decision had been announced before we discussed it. I experienced that as being left out. I cannot tell from the announcement alone whether excluding me was intentional. We still need to address how shared plans are changed.” That is a provisional account, not an agreed transcript.
There is no requirement to record the exchange in writing. You may reflect privately without keeping notes. No partner must accept your map, complete a parallel map, or consent to being analyzed. If recording or sharing details could create a risk of monitoring or retaliation, do not make or share the record.
Common errors in mapping
One common error is choosing a verdict instead of an event. “You are selfish” may express anger, but it does not specify the conduct. A clearer Launch account identifies what was said, done, or missing, and may then state the hurt or anger it brought up.
A second error is moving from perceived meaning to proven intention. “The pause felt dismissive” does not by itself demonstrate that the partner paused in order to dismiss. Conversely, “You were only imagining disrespect” does not refute a report of feeling dismissed or prove that no harm occurred.
A third error is erasing the issue. “We were in our Loop” cannot stand in for answering whether the package was collected, whether money was spent without agreement, or whether a boundary was respected. The practical matter may need a response even if the conversation becomes calmer.
Another error is assuming every Launch is an obvious first event. Partners may identify different moments because they noticed different things or because their accounts begin at different places. That does not automatically establish two equivalent accounts of harm. The sequence is not a device for assigning equal responsibility.
Finally, do not force missing information into a neat four-part sequence. Launch is one part of BTL’s educational organization: Launch → Overload → Old Story → Protection Move. A person may be able to describe an event without knowing whether their attention narrowed or a familiar meaning was influential. Chapters 30–32 address those questions individually.
When mapping is not the right task
A clear threat, intimidation, stalking, sexual coercion, violence, coercive control, or fear of retaliation is not an ordinary misunderstanding to be mapped cooperatively. The U.S. Department of Justice, Office on Violence Against Women (2025) identifies controlling and abusive behavior as domestic violence concerns. In those circumstances, safety, appropriate specialized support, and accountability take priority over exploring a shared Loop.
The same applies when a partner is monitoring communication, restricting contact, or punishing disclosure. A person does not need to collect evidence, maintain notes, ask a threatening partner what they intended, or share a map to earn permission to seek help. Joint reflection can be unsafe where a person cannot disagree freely.
A legitimate refusal or boundary also need not be classified as a problematic Launch simply because the other person feels upset. A partner may experience “no” as disappointing without acquiring a claim to override it. Do not use BTL to reframe coercive acts as protective expressions that the harmed partner should accommodate.
For immediate danger, contact local emergency services where safe. In the United States, the National Domestic Violence Hotline is available at 800-799-SAFE (7233) and thehotline.org. If accessing these resources might be monitored, prioritize a safer device or private connection when available. The Field Guide’s later safety chapters address why shared-pattern methods are inappropriate in coercive circumstances.
What a Launch map can and cannot do
The intended result of this exercise is a more differentiated description of one moment. You may be able to say what you encountered, what stood out, what you inferred, and what practical issue remains. Those are parts of an account, not a finding about whether it is correct or whether a partner will agree.
This chapter does not establish that mapping improves recall, prevents escalation, reliably identifies motives, or produces better relationship outcomes. Its limited use is descriptive. Where evidence is absent, keeping uncertainty visible is more accurate than creating certainty for the sake of a complete-looking map.
If you can identify one event and the meaning you began attaching to it without losing the underlying concern, you have completed the task offered here. Chapter 30 turns to a different question: what happens to your capacity as the exchange becomes more difficult.
Back to the Field Guide table of contents