Post

What Courage Actually Looks Like in Knowledge Work

It doesn't feel like bravery. It feels like nausea.

What Courage Actually Looks Like in Knowledge Work

It doesn’t feel like bravery. It feels like nausea.


I was watching footage of Steve Jobs in 1978, getting wired up for his first television appearance. A 23-year-old Jobs told the crew: “I’m deathly ill, actually, and ready to throw up at any moment.” You can watch it here.

It reminded me of a time I felt about the same.

Back in 2004, I switched careers. I had been working as an audio, electrical, and RF engineer. I moved into IT recruitment.


1. What I believed

I believed courage was a trait. Something you either had or you didn’t. The kind of thing that made certain people comfortable on stage, in front of investors, in rooms where reputation was on the line.

I was not one of those people. Or so I told myself.

The more honest version: I had built an elaborate theory about why my particular kind of work didn’t require that kind of exposure. I was a builder, a systems thinker, an architect. The work spoke for itself. You didn’t need to be brave to be good at your craft.

That theory got stress-tested in 2004. And again last month. The result was the same both times.


2. What reality did

Different world. Different skills. Different everything. And in IT recruitment, the core activity is one that most people, given a choice, would never voluntarily do: cold calling. Picking up the phone, dialling a stranger, attempting to have a meaningful conversation with someone who did not ask to hear from you and would often prefer you hadn’t called.

Every week, two hours, mandatory cold-calling sessions. And as a trainee, I had a senior colleague sitting next to me. Watching. Listening. Correcting in real time. There was nowhere to hide and no way to delay. The structure made the action unavoidable.

The body responded the way it always responds to social evaluation threat. A pressure behind the sternum. Heart rate up. The nervous system, shaped over millions of years to respond to a saber-tooth tiger, doing its best work in an open-plan office in response to a telephone.

I needed a way to move through it. What I found, at the time, was competition. I made it about being number one in the office. Calls made, placements landed, revenue generated. If I was going to be uncomfortable, I was at least going to win.

It worked. For a while. The competitive frame gave me a reason to pick up the phone that was stronger, temporarily, than the resistance telling me not to. But motivation built on competition is borrowed fuel. It burns fast and leaves a residue. When the novelty wore off, when I was no longer the newcomer with something to prove, the motivation faded. The calls got harder again.

What didn’t fade was something else entirely. The structural fact of the colleague sitting next to me. The mandatory session. The environment that made avoidance more uncomfortable than action. That mechanism outlasted the competitive buzz by years. Not because it was pleasant. Because it was inescapable.


3. What broke

The belief that motivation is the engine.

It isn’t. Motivation is weather. It changes without warning, responds to conditions you don’t control, and is completely unreliable as a primary mechanism for doing hard things consistently.

What actually moved me, in that open-plan office in 2004, was not motivation. It was structure. Someone next to me. A timer. A room full of people all doing the same thing. An environment where not picking up the phone was more conspicuous than picking it up.

The action came first. The confidence followed. Not the other way around.

This is the part most productivity advice gets backwards. It tells you to find your why, build your motivation, get into the right mindset, then act. The sequence sounds logical. It is also, in practice, a reliable path to continued avoidance. Because the mindset rarely arrives on schedule, and waiting for it gives the resistance exactly the time it needs to consolidate.

Seneca was more precise about this two thousand years ago: “We are more often frightened than hurt; and we suffer more from imagination than from reality.”

The call was never as bad as the thirty seconds before it. The pitch was never as catastrophic as the body insisted it would be. The fear was not a reliable narrator. But I only learned that by making the call. By pitching. By doing the thing the nervous system had classified as dangerous and discovering, repeatedly, that it was survivable.


4. What this connects to

Cato the Younger used to walk barefoot in winter. Thin clothing, cold weather, sometimes rain. A Roman aristocrat who would almost certainly never be destitute, training himself anyway for a life in which he might have to experience poverty. Not because the poverty was likely. Because he did not want to fear it.

The Stoics did not try to eliminate fear. They designed deliberate exposure to it. Repeated, voluntary contact with the thing the nervous system flagged as threatening, until the threat assessment updated. Until the nervous system understood, from evidence rather than reassurance, that the thing was survivable.

This is not a motivational strategy. It is closer to physical training. You do not get stronger by thinking about lifting. You do not build courage by planning to be courageous. You build it by doing the uncomfortable thing, in a structure that makes doing it more likely than not doing it, often enough that the body stops treating it as an emergency.

The cold-calling sessions in 2004 were, without anyone naming them as such, exactly this. Structured exposure. Mandatory repetition. An environment engineered so that avoidance was harder than action.

The competitive reframe helped short-term. The structure helped permanently.


5. What this changes

Most knowledge workers are waiting for the motivation to arrive before they do the visible work. Before they send the message. Before they share the draft. Before they publish the thing that might expose them.

That wait is indefinite. The motivation does not arrive on its own because the nervous system does not update from intention. It updates from experience. And the experience only happens when you act.

The competitive frame I used in 2004 was not worthless. It got me to pick up the phone in the first week, when the resistance was highest and the habit was thinnest. That is a real function. Gamification, competition, streaks, visible progress. These work as on-ramps. They lower the activation energy at the moment it is highest, when the behaviour is new and the nervous system has not yet learned that the threat is survivable.

But they are not the destination. Motivation built on competition or novelty is borrowed fuel. It burns fast. Once the newness fades, once you are no longer the newcomer with something to prove, the leaderboard stops working. If the structure underneath it isn’t there, the behaviour collapses with the motivation.

What PEACH-Flow is built around is both. Gamification to start and to sustain momentum through the early resistance. Structure and ritual as the long-term container, for when the novelty is gone and what remains has to be the practice itself.

The colleague sitting next to me in 2004 was not a coach. He was a constraint. The competitive frame got me to sit down. The constraint made sure I picked up the phone once I was there. Both were necessary. Neither was sufficient alone.

Courage in knowledge work doesn’t feel like bravery. It feels like picking up the phone anyway, in a room where not picking it up would be more uncomfortable than making the call.

That’s the training. Not the feeling before it. The action despite it.


Building PEACH-Flow in public. If this resonates, or if you’ve lived a version of this, I want to hear about it.

peach-flow.com . basvandrongelen.com

This post is licensed under CC BY 4.0 by the author.