You were taught to lead, never to follow.

Dispatch · to the desk of one working leader

You were taught to lead, never to follow.

The observation

A project manager I worked alongside once found a problem in a rollout plan two weeks before launch. The training dates fell across a public holiday in one of the regions, and half the sessions would have run to an empty room.

She did not raise it in the meeting. She moved the dates, told the two people who needed to know, and the launch went out clean.

In the review afterward, the credit went to the person who had presented the original plan. Nobody mentioned the fix, because by then there was nothing to fix.

The problem had been taken out of the world before anyone else saw it.

The pattern

Almost everyone is following almost all the time. A director answers to a vice president, a vice president to the chief.

Robert Kelley named this in Harvard Business Review back in 1988. He found that most of an organization's results come from what he called exemplary followers: people who think for themselves and stay fully engaged, trusted to work without a hand on their shoulder.

The trait is judgment, applied to someone else's plan. We never gave that a name, a course, or a title.

We built a whole industry around the hour a person leads, and almost nothing around the forty hours they follow.

The gap on your team is probably not a leadership gap. It is a followership gap.

The person who nods and does exactly what you said is your biggest risk, because they will carry a flawed instruction all the way to the wall. The person who delivers what you meant, and warns you when the instruction is wrong, is the one holding the place together.

Now the machine. AI is the perfect literal follower: it does precisely what it is told, instantly, and never pushes back. That makes pure obedience close to worthless: you can buy an endless supply for pennies.

What you cannot automate is the follower who reads the order and says, "this will get you the opposite of what you want."

The Prussian army had a word for it, worth borrowing. Auftragstaktik: you hand a subordinate your intent, not a script, and you expect them to break from the literal order the moment it stops serving it. They treated that as the highest form of following.

Hold this line

When the work comes back fast and clean, ask what they changed before you say thank you. Fast and unchanged is the answer that should worry you.

The move

This week, work both sides of it.

When someone above you hands you a direction you doubt, do not just comply and do not just resist. Deliver the intent, and name the one risk you actually believe in. Once, out loud. Then write the tripwire into the plan, so somebody has to look at it on the day.

Then ask the same of your team. Tell them you would rather hear the concern now than watch a clean plan fail in silence.

It will cost you. A team that flags freely also flags what does not matter, and some Thursdays you will sit through a risk that never arrives. You will overrule people who were right to raise it and wrong about the answer, and they will remember that you did.

The first time someone flags a problem and you wave it off, even politely, you teach the whole team that silence is safer. Reward the pushback, or you lose it, and you are left with the one thing the machine already sells for nothing: obedience.

You have been coaching your people to lead.
The harder work in front of them is to follow well.

When did you last thank someone for pushing back on your instruction? One line. I read every reply.

See you Tuesday.

Rui

P.S.  Worth your margin: Robert Kelley, "In Praise of Followers," the 1988 HBR piece that named the thing. Twenty minutes, and you will start noticing who actually holds your team together.