The Player-Coach Trap

A player-coach role sounds great on paper.

It’s a trap.

Or at least, it can become one very quickly.

I’ve written about this before, but it’s worth getting into the specific story because the idea is easy to understand in theory and a lot harder to recognize when you’re tired, frustrated, and standing in the middle of the problem.

The appeal of a player-coach is obvious. You’re still close enough to the work to understand what the team is facing. You can make the plan, explain the intent, and jump in when needed. You aren’t just sitting back with a clipboard, detached from the reality of the work being done.

That can be a great way to lead.

Assuming you can avoid the trap.

Because the danger is that the player side can take over and completely erase the coach side of the role. You stop leading the team through the work and start doing the work yourself.

The trap is mistaking personal execution for leadership.

A while ago I posted about learning leadership during GORUCK events. One of my failures, which eventually became one of the clearest leadership lessons I ever learned, was this exact trap.

The Cadre running the event had a standing rule.

Leaders don’t carry weight.

The reason was simple. If you’re doing too much of the physical work, you lose command and control. You stop seeing the whole group. You stop rotating people. You stop noticing who is starting to break down. You become one more person under the load instead of the person responsible for keeping the group functional.

I was leading a group of about 15 people inside a larger group of roughly 90, and we were assigned to the front of the “Pain Train,” which was a series of 4x4s linked together with sandbags bolted and clipped underneath with carabiners.

It was maniacal in the way these things tend to be.

Limited spots for people. Horrible pressure from the lumber. Swinging weight underneath it. Rucks on our backs. San Francisco at 3AM.

My job was to keep my group moving, rotate people on and off the log, watch for people who were beginning to struggle, and keep our section of the larger formation moving.

Honestly, it felt like it was going pretty well.

At the time, I was on event two of three during a 48-hour weekend. I had been awake for about 48 hours, and I was limping on what would later turn out to be a partially torn quad tendon. Toughing out dumb stuff is a topic for another time, but that’s the personal context.

My patience was thinner than it normally would have been.

My bandwidth was shot.

And that’s exactly when leadership failures tend to show up.

As the movement wore on, I noticed people from our group were missing. They were sick of carrying the weight and had started falling out, hiding toward the back of the formation. We were near the front, which meant the people who were still holding the load were getting punished even more because the bodies that were supposed to rotate in had disappeared.

The people still under the weight were really hurting.

They started yelling at each other. No amount of motivating statements were working. Eventually they started getting frustrated with the leadership too. My ATL had been trying to get people from the back to return to our group, but it wasn’t working, and the ones still carrying were getting crushed.

Then I heard someone under the log say something along the lines of, “I’d be really good if Captain Fucking America over there would get under the weight.”

He was pointing at me.

There was context there too, because 32 of us had already finished the 24-hour event before this one and come back for the 12-hour event. Somehow, that group was still doing a lot of the primary weight moving. People were smoked. People were frustrated. People wanted relief. This guy was not part of the group. And that's okay, but it's probably why my reaction was ultimately what it was.

So in that moment, all I heard was the accusation.

Immediately, I felt the rage boil over. Imagine the little Angry emotion from Inside Out blasting fire out of his head.

“Fine, fuck it,” I said audibly.

And I got underneath the Pain Train.

Being taller than almost everyone else by a lot, I immediately lifted it off a bunch of people.

Then I did what I do.

I moved weight and suffered under it without commentary.

For a minute, it felt justified.

That is probably the most dangerous part.

Because I could carry the weight. I knew I could carry the weight. I had carried plenty of weight before. I could step under the load, shut up, move forward, and let everyone see that I wasn’t avoiding the work.

But that was not my job.

What happened next is the clearest example of why leaders weren’t supposed to carry weight, and why I failed.

Because without me actively checking on people, moving them in and out of the Pain Train, and keeping track of who was suffering past the point of usefulness, nobody was getting switched.

The shouts for help grew.

People kept asking for swaps.

The group got worse because I stopped doing the thing I was actually supposed to be doing. 

I just walked with weight.

I’m not proud to admit this, but a certain amount of smug satisfaction showed up in my mind.

This is what they asked for. They wanted me carrying the weight instead of controlling the formation.

So fine.

Let them have it.

That’s ugly. It’s also true.

And after the tensions settled, and I had time to look back on my own actions, the feeling that filled me was regret.

I knew I could carry the weight and do my part. But my job was not to prove that. My job was to lead the section, protect the group from falling apart, and keep bodies moving through the load so that no one got buried under it.

My subordinates paid the price because I let frustration turn me into another laborer under the log.

Even if I was fine carrying a heavy load, they weren’t. And it was my job to help them by finding bodies to replace them, not to make a point.

That is why I keep coming back to this story.

It is one of the clearest examples I have of the player-coach trap.

I stopped leading and jumped into the task because I knew I could do it. I knew I could carry it. I knew I could make that part happen.

But in a team situation, that doesn’t always work. Sometimes carrying the weight is not leadership.

Sometimes it is what you do when you are tired, pissed off, and trying to prove a point instead of doing your actual job.

That transfers directly into creative work, production, management, and pretty much any team environment where the leader is also highly capable of doing the work.

Things might be going well for a while. The plan is in motion. People know what they’re supposed to do. Everyone is moving.

Then the trap starts loading itself.

The team starts struggling. The deadline gets close. The work is not ready. The details are being missed. Someone is frustrated. Someone else is hiding from the hard part. The people who are still doing the work are getting annoyed that others are not carrying their share.

And then the trap springs.

You jump into the work out of frustration.

Instead of teaching, clarifying, reviewing, redirecting, or resetting the standard, you start doing the work yourself.

Maybe you save the project once, twice, repeatedly, for a while.

But once that becomes the pattern, the team doesn’t become better or more capable. It just becomes backup for the star player.

The leader becomes the bottleneck.

The most experienced people burn out.

The younger or less experienced people become afraid of ownership.

The team learns that they don’t really have to make decisions, because when the pressure gets high enough, the strongest person in the room will step in and carry the load.

That is not leadership.

That is controlled dependency.

A lot of my thinking about leadership was shaped by time around GORUCK, endurance events, and friends who lived in the team-room and Special Forces world. I’m careful talking about that, because I didn’t serve in those units, and I don’t want to speak out of turn. But being around people who did, and listening to how they talked about teams, standards, trust, and command, influenced the way I think about this stuff.

The general idea that stuck with me is simple enough.

You can be in the fight without losing command of the team. That’s the balance.

A good player-coach still understands the work. They can still jump in when needed. They can still carry weight when the moment calls for it.

But they cannot carry so much that they lose the ability to see the whole problem.

That means the plan has to be visible. The intent has to be understood, not just the task. People need ownership of the results, not just instructions.

Failures need to be debriefed without making people afraid to try again. Content is not life or death. Most creative failures are survivable. A bad idea, a missed post, a rough edit, an angle that didn’t work, those are not reasons to make people scared of ownership.

They are reasons to teach the standard. That might be the biggest lesson for me.

Teach the standard instead of quietly fixing everything behind people.

Because quietly fixing everything feels efficient in the moment. It feels like leadership because the project gets saved. But if nobody learns why it was wrong, what good looks like, or how to make the decision next time, all you really did was prove that everything still has to run through you.

That’s how teams get weaker while the work still gets done.

And that is the dangerous part.

Because from the outside, it can look like success.

The project shipped.

The load moved.

The deadline was met.

The thing happened.

But inside the team, nothing got stronger. No one learned to carry more. No one learned to make the call. No one learned how to rotate, recover, adjust, and keep the group moving.

The best player-coaches can still do the work.

But they know the job is not to prove they can carry everything.

The job is to build a team that does not fall apart the second they stop carrying it.