SPEAKER_00 0:00

I want to put you in a room. You're running an EMDR session. The client is activated, you've been doing sets, the work has been moving, and then it stops. The SUD, the number on the disturbance scale, won't budge. The same belief keeps coming back, word for word. It was my fault. It was my fault. And the room goes quiet. Here's what I notice in myself in that moment, even after all these years. A pull, a pull to do something, to talk, to reassure, to explain, to reach for the perfect sentence that's going to unlock the whole thing. That pull, that exact pull, is the most important thing to understand about cognitive interweaves, because the interweave is what we offer when processing gets stuck. And almost everything that goes wrong with interweaves goes wrong, because we use them to soothe our discomfort instead of the client's stuckness. So that's today, what a cognitive interweave actually is, when to use one, when to keep your mouth shut, and why the best ones are almost always smaller than you think. Welcome to the EMDR News Podcast. I'm Tim Vermilion. This show is the audio version of what we do all week. We track the research and the real practice questions and try to keep the signal above the noise. Clinician focused, research informed. Today's a single topic, and it's one of the most searched for questions in our whole field. What do I say when EMDR gets stuck? Fair warning. My answer is going to spend as much time on what not to say as on what to say. If that's useful, follow or subscribe wherever you're listening, so these land in your feed. Let's get into it. Let's define the thing because the name causes trouble. A cognitive interweave is a brief, targeted intervention you use when reprocessing stalls, when it loops or goes blank, or just can't reach the information it needs to move. That's it. Brief. Targeted, used at the stall. Francine Shapiro, who developed EMDR, described interweaves as proactive moves for when processing is blocked. In her 1999 paper on the anxiety disorders, she talks about introducing one when change isn't appearing after several sets. And she points to things like Socratic questioning, imagery, metaphor, eliciting information. The 2018 edition of her textbook gives the interweave its own chapter, organized around three classic domains responsibility, safety, and choice. We'll come back to those three. They're the backbone. But here's the defensible core, the part I'd want you to hold on to. An interweave introduces or draws out adaptive information, and then it hands the work back to the client's own processing. It is not the engine. The processing is the engine. The interweave is a nudge, and then you get out of the way. Now, the word cognitive misleads people, and it's worth saying why. Read literally, cognitive interweave, sounds like an intellectual correction. Like the job is to think your way out of a trauma response. But in practice, the category is so much wider than that. Interweaves can be verbal, sure, but also imaginal, relational, somatic, a gesture, a metaphor. The point was never to win an argument with the client's belief. The point is to help processing resume. Think about it this way: a client who can recite it wasn't my fault and feel absolutely nothing. That person doesn't need a better argument. They're waiting for the part of them still living in the trauma to be reached on its own terms. That's a different job than persuasion. So when do you actually reach for one? And this is where I want to slow you down, because the most common mistake isn't choosing the wrong interweave. It's intervening at all when you didn't need to. Not every pause is a block. Sometimes a client is quiet because something big is moving underneath, and the best thing you can possibly do is nothing. We get trained over and over to stay out of the way when processing is working. So before you say anything, the real question is, is this actually blocked, or am I just uncomfortable with the silence? A genuine block looks specific. The same material cycling with nothing new, disturbance staying high through repeated sets, a memory that won't generalize to anything connected to it. A client locked in a child time conviction, I'm in danger, I'm helpless, it's my fault, that the adult in the chair can't reach. And the sequence matters more than any clever word or phrase. Notice the block. Check your basics. Target, image, belief, body, dual attention, window of tolerance. Wait. If it's still moving. And then if the client genuinely lacks the information to move, offer something brief and hand it back. The interweave is for blocked processing. It is not a remedy for your discomfort. Now, the line I most want to draw in this whole episode: an interweave is not mini CBT dropped into the middle of reprocessing. I want to be careful here because I have enormous respect for cognitive behavioral therapy. But it's doing a different job. CBT often makes a belief the direct target, identify the thought, evaluate it, test it, change it. That can be a whole session, and it can be exactly right in its own lane. An interweave is narrower. It treats the stuck belief as the surface of an unprocessed memory. It offers one prompt that might let adaptive information link up. And then it gets out of the way, so processing stays the treatment. A few phrases I keep in my head. An interweave offers a doorway, not a conclusion. You don't argue a client out of guilt or fear. And the prompt should be brief enough that processing, not conversation, stays the engine. The second your interweave turns into a discussion, a lecture, a debate, it's probably stopped being an interweave. Let's talk about the themes themselves. Start with the classic three. Responsibility is often the big one for trauma-linked guilt and shame, because people process a memory from the position they were in when it happened. A child, someone overwhelmed, coerced, outranked, frozen. A responsibility interweave helps the system notice what the person actually knew at the time, what power they actually had, who else carried responsibility, and whether the thing they're condemning was a choice at all, or a reflex, or the only thing a body could do under threat. Safety is for the nervous system that's still treating the danger as present tense. It orients toward now, what's different now, what the adult can do now that the younger self couldn't. The difference between remembering danger and being in danger. Choice is for helplessness, separating the options that actually existed in that exact moment from the ones that only exist in hindsight. But stuck points don't always live in words, and the field has built interweaves that meet the block where it actually sits. Some are somatic, noticing what the body wants to do, a movement that never got to finish. Some are imaginal, an adult self stepping into the scene, a compassionate witness, a container. Some work with protective parts, some draw on the relationship itself, or on spiritual and cultural meaning the client brings. And some use music, rhythm, a lyric, a remembered voice. I'll be honest about where that one sits. It's clinically interesting, and there's been professional EMDR education exploring resonant interweaves built on sound, plus a small feasibility study on personalizing audio. But that's emerging training-based work, not an established standard. So if you use it, it has to be client-led. A song belongs to a person's history. It's a bridge to their adaptive information. It's not something you import and impose. That's the thread under all of these, actually. You make room for the client's meaning. You don't install your own. Now the territory where interweaves most often go wrong. Guilt. The reflex is it wasn't your fault. And that reflex treats all guilt as a mistake to be corrected. But some guilt is distorted, some guilt is accurate, a lot of it is mixed, and some of it is grief wearing moral language. A clinician who erases real remorse does just as much harm as one who leaves inflated blame sitting there untouched. There's a useful map here from Edward Kubani's work on trauma-related guilt. The commonplaces guilt distorts. Hindsight bias, judging a past action by what you only learned later. Inflated responsibility, ignoring everyone else who had power. Imagining ideal options that never existed, mistaking a body's survival response for a moral failing. And the slide from I did something bad to I am bad. Translated into EMDR. That becomes a few brief prompts. What did you know at that exact moment? Who else had power there? Was that a choice or what your body did to survive? Offered once, then released back into processing. It's a map for noticing. It is not a worksheet, and it should never erase accountability that's real. Moral injury asks for even more room, and this is where I want to widen the lens past the usual frame, because moral injury isn't just an individual conscience wound. It can be an act committed, an act failed, harm witnessed, or trust betrayed by leaders and institutions. The literature here is rich, Litz and colleagues on the range of transgressions, Jonathan Shea on betrayal by legitimate authority, others on the shame and grief and spiritual struggle that go well beyond a PTSD checklist. The anthropologist Ken McCleish pushes it furthest, and I find it clarifying. He argues moral injury can be embedded in a whole moral world, the training, the chain of command, the public story, the body's discipline. A veteran might not be stuck on, I did something wrong, so much as stuck inside a system that trained, required, rewarded, or concealed it. And that completely changes the interweave. The missing information isn't a tidy, you had no choice. It might live in betrayal, in grief, in a value that got violated and now needs some kind of repair. So the governing principle is restraint. You do not use an interweave to force absolution or confession or forgiveness. Accurate guilt may need repair. Inaccurate guilt may need adaptive information. Mixed guilt may need both. The task isn't to make guilt disappear, it's to help someone tell responsibility apart from omnipotence, remorse apart from self-erasure, repair apart from a life sentence. I want to end the clinical part with the quieter idea underneath all of this, because it reframes the whole technique. We teach interweaves like the hard part is finding the right sentence. I think that's backwards. The philosopher Michael Polanyi had this line that people can know more than they can tell. And trauma so often stays present precisely because the client knows something implicitly that hasn't become sayable yet. The body knows the doorway, the smell, the tone of voice, the hour of the day, the posture, the rule that kept them alive. The nervous system acts like it knows, even when the person can't say what. The memory research lines up with this in a careful way. Bruin and colleagues' dual representation theory, separating memory, you can put into words from memory tied to sensation and situation. And EMDR's own adaptive information processing model says something compatible. The memory isn't only a story that hasn't been told. It's information that hasn't linked up yet with what the person now knows. So here's where that puts the interweave. You, the clinician, bring a tacit sense of timing. When to speak, when to stay quiet. The client carries tacit knowledge held in flinch and shame and sensation. And a good interweave is just a few explicit words offered right at the seam between those two. A small bridge from what the body already understands to what the mind can finally hold. It points toward what the client carries, not toward what you want them to conclude. And that, by the way, is exactly why interweaves can't be reduced to a list you memorize. Knowing which channel is blocked, whether a prompt will help or interrupt, when to say nothing, that's judgment. A list of phrases is fine for training. It's no substitute for thinking about the actual person in front of you. One care note everything here is professional education and clinical reflection. It's not treatment guidance, and it's not a substitute for EMDR training, consultation, or individualized care. And a clinical boundary worth saying plainly, an interweave is never a tool for recovering memory content. EMDR can reduce distress and shift meaning. It does not establish what happened. No leading questions, no suggesting details. Clinical work isn't a forensic investigation. So let me bring it home. When processing stalls, the tempting question is, what should I say? And I'd love for you to trade it for a better one. What adaptive information is missing here? And what's the smallest, most respectful thing I could offer that might help this client's own processing find it? That's the whole difference between an interweave and a reframing. A reframing can tell a person what to think. A good interweave helps a client discover what they were finally ready to know. Smallest door, then step back, that's the craft. That's the episode. If it was useful, the single most helpful thing you can do is follow or subscribe wherever you're listening. It's what keeps these showing up for you. And if it landed, send it to one colleague who'd want it. That's genuinely how this grows, one clinician handing it to another. A quick word on sources because that's part of how this show works. Everything today traces back to published material. Shapiro's 1999 paper and her 2018 textbook chapter on the interweave, Kubani on Trauma-related guilt, Litz, Shea, and McCleche on moral injury, Polanyi on Tacit Knowledge, Bruin and Colleagues on Dual Representation Memory. The written version, with everything linked, is up at EMDRnews.com. And the reminders before I go. This is education and reflection, not treatment guidance or a substitute for consultation. EMDR News is independent, not affiliated with the EMDR International Association or the EMDR Institute. I'm Tim Vermilion. When the processing stalls, offer the smallest door and then trust the work. See you next time.