CHAPTER SIXTEENThe Mid‐phase: Updating the System Through Evidence
PART 1: THE CONCEPT AND WHY IT MATTERS
Mid‐phase is where CMI becomes concrete. Early sessions establish fit, trust, and a shared map. Mid‐phase uses that map to generate evidence under real conditions. The client begins to test new responses in the cue contexts where old meanings, narrowed access, reinforced patterns, and identity protection have kept the loop in place. Change begins to hold when those tests are debriefed, integrated, and repeated with enough variation to travel.
Many engagements stall here for predictable reasons. Experiments get vague. Insight becomes a substitute for action. Tools become a substitute for learning. Sessions stay interesting, yet behavior does not change in the moments that matter.
Mid‐phase has one job: turning understanding into durable choice. That happens through a repeatable cycle.
- Map
- Stabilize access
- Run a micro‐experiment
- Debrief
- Integrate
- Repeat with variation
This is the engine chapter. It turns the CMI domains into a practical process for producing change outside the session, in the cue contexts where access narrows and choice becomes harder to hold (Shields et al., 2016).
WHAT MID-PHASE LOOKS LIKE WHEN IT IS WORKING
When mid‐phase is working well, several signals begin to appear:
- The client can name their loop in real time, not only in hindsight.
- The client notices state shifts early enough to protect access.
- Experiments are small, specific, and frequent. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access