Basic Instinct: Director's Cut

There was a period in my career when I could write a blistering email in under three minutes. Genuinely impressive turnaround time, if regrettable content. Basic instinct, in the most literal sense: no thought, no edit, straight to broadcast.

Something would land in my inbox with a tone I didn't like, an expectation I felt wasn't being met, a comment that read as dismissive, and my fingers would already be moving before I'd decided anything. I'd type fast, hit send, and feel a flash of relief. Finally, I said it. It's off my chest.

Then, almost immediately, the regret would arrive. The feeling itself was almost always fair. The timing and delivery rarely were. Nobody hands out awards for best first take.

I used to think this was decisiveness, and that was how to get things done optimally. I was capable, I was busy, and I dealt with things as they came up rather than letting them sit. It felt like communicating what good looked like and what my expectations were. It felt efficient. It felt like leadership.

It wasn't leadership.

It was a nervous system responding to a trigger and calling it a decision, wearing a very convincing decisiveness costume.

It isn't only email, either.

Email just leaves a paper trail, which is how I know how often it happened. The same instinct shows up any time something makes us properly angry - a comment in a meeting, a tone in a text from a family member, someone taking credit for something that was ours. Heat rises before thought does, and whatever comes out in that first ten seconds is rarely our best thinking.

Learning to pause there, in the actual heat of the emotion rather than just at a keyboard, is arguably the harder and more valuable version of this whole skill.

Learning to interrupt the pattern, at least the email-shaped version of it, didn't happen overnight, and it started small (after too many uncomfortable lessons). I gave myself one rule: draft, don't send. If I had the luxury of time, I'd sleep on it and come back once my head was in a different place. More often than I expected, I didn't send anything at all. I picked up the phone instead (which, if you'd told corporate-era me that the mature option was a phone call, I'd have assumed you were describing a punishment).

What I was really doing, without having language for it at the time, was refusing to release the first cut. The instinct still got to have its say (I still wrote the email, still felt everything I felt). I just stopped treating the raw footage as the final version. Somewhere between the first draft and actually pressing send, there was room to reshoot the ending.

That one shift, choosing the relationship over the reflex, changed almost everything downstream of it.

It was choosing kindness over the comeback: letting go of the need to have the last word, or to prove how clever I could be under pressure.

And it was choosing perspective over praise: the bigger picture over the small, immediate hit of feeling instantly right.

What surprised me most was how much of what I'd been reacting to had never actually been there. Tone doesn't travel well in text, and it turns out it doesn't travel especially well through a red mist either. A huge amount of what I'd read as dismissive, or careless, or deliberately unkind, evaporated the moment I heard someone's actual voice, or asked one clarifying question instead of assuming I already knew the answer.

I wasn't only responding to what had been sent to me. I was responding to my own reading of it, at a moment when I was too wound up to read anything accurately.

I see the same pattern constantly in the leaders I work with now - the instinct to jump in, to fix, to answer immediately, to prove they can handle whatever has just landed, or whoever has just annoyed them.

It rarely looks like panic. It looks like competence. It looks, from the outside, exactly like good leadership. But underneath it is often the same thing I was doing with that email: an old, automatic response mistaking speed for judgement, and calling the trailer the whole film.

A fast reaction and a good decision are not the same skill, even though they can look identical from the outside, and even though the fast one always feels far more satisfying in the moment.

Building the capacity to lead well under pressure has very little to do with becoming someone who can absorb more, respond faster, or hold more without flinching. It has everything to do with building in the space to ask, before you act, whether the action in front of you actually serves where you're trying to go.

That pause isn't passive. It isn't hesitation, or avoidance, or an excuse to never say the hard thing. It's the edit. It's the one piece of architecture that makes everything else sustainable. Without it, you're not leading - you're just releasing your first take, possibly a furious one, and calling it leadership.

Capacity, it turns out, was never about what you can survive in the moment you're triggered. It's about what you can keep doing, well, on the other side of that moment, over and over again.

These days, before I respond to almost anything that has an edge to it - an email, a comment, my own temper - I ask myself three things.

1. Does responding right now actually serve what I'm trying to achieve, or does it just relieve the pressure of the moment?

2. Is what I'm about to say kind, and does it move things forward?

3. And have I actually understood what's happening for the other person, or am I responding to a story I've built about them, based on my own history and my own triggers?

   
   

I don't always get it right. I am, on occasion, still capable of a fairly spirited internal monologue before I get there. But I no longer mistake the speed of my reaction for the quality of my judgement. And I've learned that almost everything I once called responsiveness was actually just an unexamined habit, running on autopilot, dressed up as leadership.

Basic instinct will always be the first cut.

The pause is what gets you to the director's cut instead.