Chapter 28: Supervision, Consultation, and Training
You learned to witness
in the presence of a witness.
Now another clinician comes
needing that same gift.
Give what you were given.
"Good teaching is the thoughtful extension of one's own learning into the learning of another." — adapted from Parker Palmer ## Why This Framework Needs Sharing RSD treatment benefits from a shared clinical language. When supervisors, consultants, and peers share the framework, clinicians new to the work have support. Supervision sessions have common ground. Case consultations can go directly to the pattern without extensive translation. This chapter is about how to teach the model to other clinicians, use it in consultation, and support ongoing development in the work. ## Teaching the Framework Teaching this framework to clinicians who haven't worked with it before typically requires attention to several layers: The neuroscience foundation. Many clinicians have been trained to prioritize cognition over body. The polyvagal framework, social pain neuroscience, and the case for regulation-before-insight are often new to them. Ground the framework in the research. Let them read Eisenberger, Porges, the shame imaging studies. The research provides validation that the clinical approach is supported by evidence. The phenomenology. Have new clinicians observe RSD waves, either in video, in case examples, or (with consent) in live sessions. The pattern is easier to recognize when you've seen it a few times. Written descriptions only go so far; direct exposure builds the recognition skill. The stance work. This is often the hardest part to teach. Stance is internal. Clinicians can't simply read about "calm without cold" and embody it. Stance develops through practice, reflection, and one's own therapy. Support new clinicians in their own regulation work. Help them develop the practices that will make their clinical presence more reliable. The sequence. Recognize-regulate-reflect-reframe-repair. Drill the sequence until it's reflexive. In supervision, revisit it in every case consultation. "Where were you in the sequence in that moment? What did the client's state call for?" The specific interventions. Validation without colluding. The mapping framework. The six-question repair conversation. Clinicians need to practice these moves, not just know them. Role-play in supervision. Have them try phrases out loud and get feedback on how they land. ## Using the Framework in Supervision When a supervisee brings a case involving RSD features, the framework provides structure for the consultation: Start with recognition. "Walk me through the moment. What did you observe? What shifted?" Before strategy, recognition. Check regulation. "What was the client's state? What was your own state? What did the regulation look like?" These questions anchor the consultation in nervous-system reality rather than abstract case formulation. Map the sequence. "What was the cue, body, meaning, strategy, aftermath?" This slows the supervisee down and helps them see the pattern even in retrospect. Reflect on stance. "How did your stance hold in that moment? What supported it? What pressured it?" Stance work is often where the most important supervision happens. Clinicians who can maintain stance under pressure deliver better care. Identify the next move. "Given what you've just described, what do you want to try in the next session? What question do you want to sit with?" Supervision ends with an action item, not with closure. This structure doesn't replace case-specific exploration. It supplements it. Within the larger exploration of the case, these moves help keep the RSD framework alive. ## Peer Consultation Groups Peer consultation groups focused on RSD can be particularly valuable. Clinicians bring cases. The group uses shared language. Discussion moves beyond generic case consult into specific RSD-framework territory. Common themes emerge. Shared learning accelerates. Some suggestions for peer consultation structure: - Rotate presenters. Each meeting, one clinician brings a case. - Use the framework vocabulary. When someone describes a client's reaction, ask: "Where in the sequence? What was the state? What was the window?" - Reflect on stance. Not just what the clinician did, but what their stance was and where it held or slipped. - Share what worked. Success stories about specific interventions help everyone. - Acknowledge what didn't. Failures and impasses, openly discussed, teach as much as successes. Peer consultation works best when there's explicit buy-in to using the framework, a culture of openness about uncertainty, and a norm of honest feedback. ## Your Own Development RSD work, done well, asks for your ongoing development as a clinician and as a person. The framework supplies tools. You supply the instrument. The instrument needs tuning. Your own therapy. Many clinicians doing this work benefit from their own ongoing therapy, particularly work with their own rejection sensitivity patterns. If you haven't been there yourself, parts of the work will feel abstract. If you have, your empathy has ground to stand on. Consistent somatic practice. Meditation, yoga, movement, martial arts — whatever fits. A somatic practice maintained over years develops the interoceptive awareness and regulation capacity that your clinical work draws from. Reading widely. Clinical literature on trauma, attachment, somatics, neurodiversity, Appreciative Inquiry. Also literature outside clinical work: poetry, philosophy, fiction. Clinicians who only read clinical material become narrow. Clinicians who read widely have more to draw from in the room. Feedback loops. Ongoing feedback from clients, supervisors, peers. The work doesn't improve without honest assessment of what you're actually doing versus what you think you're doing. Community. Clinicians who work in isolation tend to either burn out or develop blind spots. Community provides reality-testing, support, and ongoing learning. :::ai What supports your own development as a clinician right now? What's missing? What would it take to invest more in the development of this work — your own and the field's?
Avoiding Framework Rigidity
A risk of any clinical framework is that it becomes rigid — applied without regard for the specific client, the specific moment, the specific context. The framework becomes a prescription rather than a scaffolding. The clinician performs the framework rather than working with the person.
Guard against this. The framework should make you more responsive, not less. If you find yourself executing steps rather than meeting the client, something has gone off. Step back. Reconnect with the person in front of you. The framework can wait.
Encourage this in supervisees and peers too. Celebrate when clinicians depart from the framework skillfully because the client needed something different. Discourage mechanical application. The framework is in service of the client; the client is not in service of the framework.
Closing
Transmission of good clinical work is a practice in itself. It asks you to hold the framework clearly enough to teach, and flexibly enough to model its humility. Your own development supports your teaching. Your teaching refines your own practice. The loop runs.
The final part of the book takes up ethics, measuring progress, integration, and the long arc of change — what this work looks like over years, and what it asks of clinicians who stay with it.
For clinicians sustaining this work across years, ongoing community is essential. The Perch described in Appendix B is one such community layer; your own local peer groups are another. Appendix A's baseline interventions support the sustained clinical stamina this work requires.