A coworker leans over your desk at 4:40 on a Friday. Hey — any chance you could take a look at this before you head out? Just real quick.
It is not real quick. It never is. And you can feel the whole machine spin up in the half-second before you answer: the assessment of their tone, the calculation of how a no would land, the warmth you’re about to wrap around the yes so they never feel the inconvenience of having asked.
Of course! Send it over, no problem at all — typed fast, exclamation point included, maybe a little smiley so they know you really don’t mind. You didn’t decide to send that. It assembled itself.
Watch what just happened¶
There were actually two things in that reply, stacked on top of each other.
The first was the answer — whatever genuinely corresponds to the situation. Maybe that’s yes. Maybe it’s “I’m heading out, but I can look first thing Monday.” Maybe it’s a simple no. The answer is just the true response to the actual request.
The second was everything else: the exclamation point, the no problem at all, the smiley, the speed. That layer wasn’t answering the question. It was managing how the coworker felt about having asked — reassuring them, smoothing them, signaling I’m easy, I’m a delight, you never have to feel bad around me. That layer is the performance. And it runs so automatically you’ve stopped seeing it as separate from the answer at all.
Un-performing is just this: sending the answer, minus that second layer.
The whole move is subtraction¶
Picture the un-performed version of that Friday reply. I’m about to head out — I can look first thing Monday. No exclamation point. No so sorry. No warmth applied like a coat of paint to make the no go down easier. Just the true thing, said plainly, in your normal voice.
It looks almost identical from the outside. Your coworker probably won’t notice anything happened. But internally, something did. You answered the actual question and you did not perform around it. You let the reply just be a reply, instead of a small act of emotional caretaking aimed at someone who never asked you to take care of them.
That’s what un-performing means. Not being cold. Not refusing. Not making a point. Just doing the thing that corresponds to what’s happening — and leaving off the warmth-management layer you’ve been adding so long you forgot it was optional.
It’s strange how hard the simple version is. The plain reply will feel almost rude the first time, because you’re so used to the cushioning that its absence registers as a void you’re obligated to fill. That feeling — the pull to soften, to add the smiley back — is the performance showing you exactly where it lives.
Why the small version is the whole point¶
You might be waiting for the bigger instruction. The boundary to set, the conversation to have, the assertive stand to take. There isn’t one here, and that’s deliberate.
Un-performing doesn’t start with grand gestures. It starts in the most ordinary moments you have — the text reply, the desk-side ask, the throwaway exchange you’d never think twice about — because those are where the performance actually lives. Not in the big confrontations. In the thousand tiny reflexive layers you apply every single day. Subtract one of them, once, and you’ve done the real thing. Do it in moments small enough that your resistance never wakes up, and it starts to compound.
What I’m not going to do is hand you the full practice — when to drop which layer, how to stay steady when the absence of warmth makes you uncomfortable, how this fits the larger arc. That’s a real method, and it’s more than one article can hold. But you can see the shape of it now, in the most ordinary moment of your day.
If you recognized your own Friday reply in this — the exclamation point you didn’t choose, the warmth you applied on reflex — that recognition is worth sitting with. The High-Functioning People-Pleaser is built around un-performing exactly these small moments, and why subtraction, not effort, is what finally works.