“I have some resistance about doing that. I don’t know why.” — Lou D’Alo
Session context: 2025-06-12_Mastermind — Lou surfaced this while discussing a specific action he’d been deferring, noting that the resistance didn’t have a logical explanation — it was just present.
Core Idea
When a client (or coach) reports delay on an action that they intellectually endorse — they know it would help, they’re not blocked by capability, they have time — and they can’t name why, that unnameable resistance is almost always identity-level. The delay is not laziness or disorganization. It is the nervous system doing its job: protecting an existing self-concept against the threat of change.
The specific mechanism: taking the action would require the person to become, in some small but real way, someone different. That might mean being more visible, more committed, more successful, or more exposed to failure. Any of these involves leaving behind a version of self that currently feels safe. Procrastination is the gap between the version of themselves they consciously want to become and the version of themselves their nervous system is currently protecting.
The coaching trap is treating this as a planning problem. Coaches reflexively respond to reported delay with accountability structures, systems, or encouragement. These work when the blocker is external. When the blocker is identity-level, accountability structures add guilt on top of the original resistance without touching the actual mechanism. The client now feels bad about not doing the thing and still isn’t doing it.
The right diagnostic question is not “What’s stopping you?” — which produces rational-sounding explanations that are usually rationalizations. It’s “If you actually did this, what would that make you? And is there anything about that that makes you uncomfortable?” This question locates the identity conflict directly.
Practical Application
The Identity Excavation Sequence — use when a client (or you) reports persistent delay on something they’ve already committed to:
- First, rule out external blockers: “Is there anything you literally don’t know how to do here, or any resource you’re missing?” If the answer is no, proceed.
- Ask: “If you did this — fully, no hedging — what would that make you? What word or label comes to mind?” Let them answer without prompting. Common answers: visible, committed, exposed, responsible, someone who actually does this.
- Ask: “Is there any part of you that’s uncomfortable with that identity?” The hesitation here is often the data. Don’t rush through it.
- If resistance to the new identity surfaces: “What are you protecting by staying in the current version? What would you lose if you became that?”
- Only after this excavation: discuss practical next steps. The action plan has a different quality when it’s built on top of a named identity shift rather than on top of an unnamed fear.
Related Insights
- Insight - The AI Paralysis Triad — Fear, Doubt, and Overwhelm as Compounding Blockers — the triad can mask identity resistance; what looks like overwhelm (I don’t know where to start) is sometimes identity resistance (I don’t want to become the person who has done this)
- Insight - Safe Container as Transformation Prerequisite — The Mechanism Behind Coaching Results — the identity excavation sequence only works inside a safe container; clients won’t surface an uncomfortable identity conflict with a coach they don’t fully trust
- Insight - The Guru Myth Resistance Pattern — Production Polish Hides the Messy Process — the Guru Myth can intensify identity resistance by raising the bar for what the new identity looks like; if “being a person who does this” means achieving polished expert output, the threshold for identity adoption becomes impossible
Evolution Across Sessions
This establishes the baseline for distinguishing identity-level resistance from operational delay. Future sessions should track whether the identity excavation sequence is being used by members and whether the specific identity labels that surface cluster into recognizable archetypes across clients.