You already know the advice. Take deep breaths. Observe your thoughts without judgment. Feel your feet on the ground. Notice five things you can see, four things you can hear. Meditate for ten minutes every morning.
It works — when it works. But for most people, most of the time, it doesn't. Not because the techniques are wrong, but because they're treating a symptom. They're trying to quiet the mind through the mind. And the mind has opinions about that.
Here's a different way to think about presence, one that comes from an unlikely source: improvisational theater. Improv performers have to be fully present for their work to function at all. A scene partner says something, and you must respond to exactly what they said, not what you expected them to say, not what you planned to say next. One second of internal distraction and the scene dies publicly. So improv has spent decades developing methods for presence that work reliably, under pressure, in real time. Their approach starts with a simple mechanical insight that the mindfulness tradition tends to skip.
The Bandwidth Model
Your brain has a finite processing capacity. Cognitive psychologists call it working memory; improv practitioners call it cognitive bandwidth. The label doesn't matter. What matters is the constraint: it's limited, and everything you do with your conscious mind draws from the same pool.
George Miller's landmark research (1956) established the rough number: the human mind can hold about seven items (plus or minus two) in active processing at once. More recent research by Nelson Cowan (2001) revised this downward to about four chunks of information. Either way, the number is small. Embarrassingly small, given how complicated life feels.
Here's where presence enters the picture. At any given moment, your bandwidth is allocated across two channels:
External processing: Taking in what's actually happening around you. What someone is saying. What the room looks like. What your body feels. The sensory reality of right now.
Internal processing: Running simulations, evaluations, and plans inside your head. What you're going to say next. Whether that thing you said an hour ago was stupid. What you need to do tomorrow. Whether the person across from you is judging you. How this conversation might go wrong.
Presence is what happens when the allocation tips toward external. Absence — that glazed, disconnected, "I wasn't really listening" state — is what happens when it tips toward internal.
This isn't a metaphor. It's a zero-sum resource allocation. Every cognitive cycle spent on internal simulation is a cycle unavailable for processing external reality. You cannot plan your response and listen to what someone is saying at the same time, because both tasks draw from the same limited pool. One displaces the other.
Internal Computation: The Presence Killer
Improv has a precise name for the failure mode: internal computation. It's what happens when a performer retreats into their head — planning, evaluating, judging, rehearsing — instead of responding to what's actually happening on stage.
The symptoms are instantly recognizable, on stage and off:
- Your eyes defocus slightly. You're looking at the person but not seeing them.
- Your responses come a half-beat late, because you're processing old input, not current input.
- Your contributions feel generic rather than specific, because they're coming from your mental model of the situation rather than from the situation itself.
- You miss details. Small ones first — a shift in someone's tone, a flicker of expression — then larger ones.
Internal computation isn't laziness or inattention. It's your brain doing what brains do: predicting, planning, protecting. The problem isn't that the activity is useless. Planning and evaluating are genuinely important cognitive functions. The problem is timing. When they run simultaneously with tasks that require external attention, both tasks get a fraction of the bandwidth they need, and both degrade.
Daniel Kahneman's dual-process framework (2011) maps onto this cleanly. System 2 — the slow, deliberate, analytical mode — draws heavily on working memory. When System 2 is running (planning, evaluating, worrying), it commandeers bandwidth from System 1's environmental processing. The subjective experience: you stop noticing what's happening around you. The experiential label: you're not present.
Improv's Solution: Demand-Side, Not Supply-Side
Most presence techniques are supply-side: they try to increase your capacity for attention. Meditate more. Practice mindfulness. Build your concentration muscle. These work — slowly, incrementally, and with consistent practice that most people don't sustain.
Improv takes the opposite approach. Instead of trying to expand the bandwidth supply, it makes internal computation impossible by creating demand conditions that consume all available bandwidth for external processing. You can't retreat into your head because the exercise won't let you.
This is Be Present as a structural constraint, not a spiritual aspiration.
Consider the simplest improv exercise: the word-at-a-time story. You and a partner tell a story, alternating one word each. "Once" — "there" — "was" — "a" — "lonely" — "astronaut." You cannot plan ahead because you don't control enough of the output. You cannot evaluate your word choice because the next word is already coming. Your entire bandwidth is consumed by two tasks: hearing what your partner just said, and producing a word that fits.
The result: total presence. Not because you decided to be present. Because the exercise architecture left no bandwidth for anything else.
This is the insight that most presence advice misses. Presence isn't a state you achieve through willpower. It's a state that emerges automatically when the demand for external processing exceeds the supply available for internal processing. Fill the bandwidth with external tasks and the internal chatter has nowhere to live.
The Exercises That Force Presence
These are structured bandwidth consumers. They work not by teaching you to be present but by creating conditions where presence is the only option.
The Repetition Exercise
Sit across from someone. One person says a simple observation: "You're wearing a blue shirt." The other person repeats it back: "I'm wearing a blue shirt." Back and forth. The observation changes only when something genuinely changes — a shift in expression, posture, energy.
Why it works: Your entire job is to see what's in front of you and report it. There's nothing to plan, nothing to evaluate, nothing to be clever about. The bandwidth is fully consumed by observation and response. Internal computation has no foothold.
The Mirror Exercise
Two people stand facing each other. One moves slowly; the other mirrors. After a few minutes, try to dissolve the leader-follower distinction. Both people move, both people follow.
Why it works: Mirroring someone's physical movement in real time requires continuous external attention. The moment you start thinking about what to do next, you fall behind. The exercise trains your attention to stay locked on external input — your partner's body — rather than drifting to internal simulation.
Applying the Bandwidth Model Off Stage
You don't need to join an improv class to use this model, though it helps. The principle transfers: presence increases when external processing demand increases relative to internal processing.
In conversation: Stop composing your response while the other person is talking. Instead, try to notice one specific thing about how they're saying what they're saying — their pace, their energy, their word choice. This consumes bandwidth that would otherwise go to internal rehearsal. You'll find your responses become more relevant, not less, because they're based on what actually happened rather than what you predicted would happen.
In work: Before starting a task, remove the inputs that feed internal computation. Close the tabs. Silence the phone. Each open input is a bandwidth claim that pushes your processing toward internal management and away from the task in front of you.
In daily life: When you catch yourself not-present, don't try to force presence through willpower. Instead, increase the external demand. Engage a sense you weren't using. Touch something and notice its texture. Listen to the ambient sound and identify three distinct sources. Give your bandwidth something external to process, and the internal chatter loses its foothold.
The Reframe That Changes Everything
Presence isn't a spiritual achievement. It's not a personality trait. It's not something some people have and others don't. It's a bandwidth allocation state that shifts based on demand conditions.
You've been fully present thousands of times — during an intense conversation, a close game, a moment of danger, a first kiss. In each case, the external demand was high enough to consume your full bandwidth. The internal narrator went quiet not because you told it to, but because there was no room for it.
The practical question isn't "how do I become a more present person." It's "how do I create conditions where presence is the natural outcome." Structure the demand, and the presence follows.
This article draws on the improv knowledge graph at The Physics of Connection. For the full system behind presence, bandwidth, and internal computation, explore the Systems of Improv path, or start with Be Present and Cognitive Bandwidth.
Sources cited: Miller (1956), Psychological Review. Cowan (2001), Behavioral and Brain Sciences. Kahneman (2011), Thinking, Fast and Slow. Hines, Improv Nonsense Substack.