The shadow of Be Present. Internal computation is the act of retreating into your own head — planning, rehearsing, evaluating — while the scene continues without you.
The classic tell: your partner says something and your eyes glaze over. You aren't looking at them — you're looking at the script in your head. You're scrolling through your mental Rolodex of responses, trying to find the clever one, the right one, the funny one. Meanwhile, time advances irreversibly. Your partner has already moved on. When you finally deliver the line you rehearsed, it lands on a scene that no longer exists.
This is the deer in headlights failure mode. The brain is maxed out trying to simultaneously listen, remember, plan, and perform. Something has to give, and what gives is reception — you stop observing external reality because all your bandwidth is consumed by internal processing.
Why it happens: Multiple roots. Distrust — you don't trust you'll have something to say if you don't prepare it. Perfectionism — you need the line to be good before you'll release it. Self-judgment — you're auditioning your ideas before an internal critic, and the critic keeps rejecting. (Internal computation often IS judgment running in real-time — the voice in your head is a terrible scene partner.) Trained habit — school and work reward planning; the computation reflex is deeply grooved. Spolin named this the "approval/disapproval syndrome." And underneath all of these: ego — "I need to be good" triggers the retreat into the head.
The result is latency: your response addresses a point made thirty seconds ago, not the one your partner just made.
The physical signature: The body announces computation before the mind admits it. Eyes go up or defocus. Breathing shallows. Weight shifts backward. Mouth opens but nothing comes out. Hands freeze or fidget. Your scene partner reads this instantly — they can see you leave before you know you've gone.
Susan Messing nails the felt experience from the other side: "If you're in your head, you're not here with me." It's weirdly lonely — being on stage with someone who is physically present but cognitively absent. The audience feels it too. The scene stutters. The energy drops.
The paradox: The more you try to prepare, the worse you perform. The preparation itself consumes the bandwidth you need to actually respond.
Recovery — when you catch yourself computing: The fix is physical, not cognitive. You can't think your way out of thinking.
- Breathe out. A deliberate exhalation activates the parasympathetic system and interrupts the freeze.
- Touch something. An object in the scene, your partner's shoulder, the floor. Physical contact re-anchors you in the shared space.
- Say the first word in your mouth — even if it's wrong. A bad line delivered now is better than a good line delivered after the moment has passed.
- For the full recovery protocol, see Recovery: Latency.