A practitioner can know the right modality for a presenting concern, have the technical skills, follow the protocol — and still produce stalled work, because the underlying stance toward the client’s unconscious processes is adversarial rather than collaborative.
This is one of the most under-discussed variables in clinical training. It is also one of the most determinative.
Two stances
The adversarial stance treats the client’s unconscious as something to be overridden. The patterns are problems. The defenses are obstacles. The resistance is something to push through. The therapist’s job is to deliver insight, technique, or pressure that will produce change despite the unconscious’s reluctance. The implicit model: the conscious mind is the agent of change, and the unconscious is the obstacle to it.
The collaborative stance treats the client’s unconscious as the senior system that knows things the conscious mind does not. The patterns are signals. The defenses are protective structures the system built for reasons. The resistance is data — the system is registering that an intervention does not yet match the layer the problem is on, or that the conditions are not yet safe enough for the deeper work, or that the proposed change would cost something the conscious mind has not yet acknowledged. The therapist’s job is to create conditions under which the client’s deeper layers can do the reorganization the system needs.
The two stances produce visibly different sessions. They produce visibly different therapeutic relationships. And they produce visibly different outcomes — particularly on problems that sit at the IL or runtime layer.
The architectural truth
The framework’s claim is that the collaborative stance is not a stylistic preference. It is the stance that matches the actual hierarchy of the client’s cognitive system.
The unconscious runtime processes approximately 11 million bits per second of input. The conscious mind processes roughly 50 bits per second of deliberate thought. The runtime was operating before the conscious mind came online developmentally and processes each moment 300 to 500 milliseconds before conscious awareness. The runtime is the senior system. The conscious mind is the junior interface.
This means a few things in practice.
The client’s unconscious almost certainly knows something about the situation that the conscious mind has not yet articulated. The somatic responses, the dreams, the recurring imagery, the relational pattern — these are the runtime’s output. They are signals. Treating them as obstacles to be defeated is treating the senior system as the enemy of the work.
The client’s defenses — the patterns the conscious mind has organized to manage difficult material — are structures the system built when it had reason to. Tearing them down before alternative structures are in place produces destabilization rather than change. The collaborative stance respects the defenses as the system’s protective infrastructure and works with the system to identify when and how the protection can be reorganized.
The change the work is aimed at, when it arrives, will not arrive from the conscious mind issuing commands to the deeper layers. It will arrive from the deeper layers reorganizing themselves under conditions the practitioner and client have created together. The therapist’s job is to help create those conditions.
What working-with looks like in session
Several practical dimensions:
Listen for signals first; interpretations second. Before offering frameworks for understanding what the client is reporting, attend to what the body, the affect, the imagery, the silences are saying. The runtime’s signal is rarely in the verbal content. It is in the channel underneath.
Treat resistance as information. When a client cannot do the homework, cannot stay with the affect, cannot enter the material the practitioner has identified — the collaborative move is not to push through. It is to ask what the resistance is protecting. The system has a reason for its current configuration. The reason is data.
Slow down at threshold. When the work approaches material that the runtime has been protecting, the system signals the approach: somatic activation, dissociation, sudden topic change, fatigue, narrative disorganization. These are titration signals. The practitioner who pushes through them is overriding the system’s pacing. The practitioner who slows down — often dramatically — is trusting the system to indicate when it is ready.
Translate, do not override. When the unconscious produces material the conscious mind dismisses (just a dream, not important, weird), the practitioner’s role is often to translate the material into a form the conscious mind can take seriously, without forcing premature meaning onto it. I notice your body shifted when you said that. What did your body say? is a translation move. Your body is wrong, focus on the cognition is an override move.
Hold material the client cannot yet hold. Some content arrives in session before the client’s conscious mind can integrate it. The practitioner who can hold the content — registering it, taking it seriously, returning to it later — gives the client time to develop the capacity to hold it themselves. The conscious mind learns from watching the practitioner refuse to dismiss what the runtime is reporting.
Set conditions; do not deliver outcomes. Effective therapy shapes the conditions under which the client’s system can reorganize. Safe relationship. Predictable rhythm. Reliable attention. Appropriate pacing. Permission for difficult material. These are environmental adjustments. The reorganization itself happens at a layer the practitioner does not directly access.
What the client experiences
A client working with a collaborative practitioner often reports a particular phenomenon: the work feels different than they expected. They do not feel pushed. They do not feel argued with. They feel received. The patterns they were ashamed of get treated as protective structures rather than personal failures. The dreams they would have dismissed get taken seriously. The somatic signals they had learned to override get attended to.
Under those conditions, change tends to arrive. Not on the schedule the conscious mind would have demanded. Not in the form the conscious mind would have specified. But change arrives, often more durably than change produced by override-style work, because the change is happening at the layer where the encoding actually lives.
A diagnostic question for the practitioner
When the work is stalled, the practitioner can ask: am I in adversarial stance or collaborative stance with this client’s unconscious right now?
If adversarial — pushing for change, frustrated with resistance, treating defenses as obstacles, racing the conscious mind ahead of the runtime — the move is not to push harder. It is to step back into the collaborative stance and let the system reveal what it has been signaling all along.
The practitioner is not the agent of change. The client’s runtime is the agent of change. The practitioner’s job is to be the conditions under which the runtime can do its work.
Trust the senior system. Create the conditions. Watch for the signals.
The change will come from below.