I was a scout leader. A girl one, if that matters to you — it apparently mattered to the adults who kept being surprised about it.

Here’s the second thing that stuck, after the one about not leaving people behind: the best leader I ever tried to become is the one nobody in the group could point to.

The test I was taught

Not “can I get this team to the target.” Any halfway competent person can bark directions at twelve kids for an afternoon and get them there.

The actual test was: build the team strong enough that everyone can lead, and nobody wants to.

Not “nobody can.” Not “nobody’s allowed to.” Nobody wants to, because the position isn’t worth wanting. There’s no status attached to it, no visible reward, nothing to hoard. It’s just a job that needs doing right now, and whoever’s best positioned does it, and then hands it back without ceremony.

And the actual pass condition, the thing you’re aiming for: a stranger watches your group for a full day and cannot tell, at the end of it, who was in charge.

That’s not the absence of leadership. That’s leadership done so thoroughly it stopped needing a face.

Why this is harder than it sounds

It is much easier to build a team that depends on you. It happens by accident, even when you’re trying not to. You make the calls because you’re faster at making them. People start waiting for you to make them. Six weeks later you have a group that runs beautifully as long as you’re standing there, and falls apart in about ninety seconds the moment you’re not.

That’s not a strong team. That’s a single point of failure with extra steps.

Building the other kind — where roles genuinely rotate, where the person who’s tired hands off and the person who’s fresh picks up without a meeting about it — takes actively giving away the thing that makes you feel useful. You have to let someone make a call you’d have made differently. You have to stay quiet while they get it slightly wrong and learn from getting it slightly wrong, instead of stepping in to protect the outcome.

Most people who call themselves leaders can’t do that part. Protecting the outcome feels responsible. It’s actually just protecting your own positions.

What it looks like when it’s working

No one announces role changes. Whoever’s carrying the map at that moment is reading it. Whoever spots that a kid at the back is struggling handles it, without checking whether that’s “their job.” If you ask the group who’s in charge, you get a pause, then someone says “I mean, kind of everyone?” and looks a little confused that you asked.

That confusion is the whole point. It means the structure got internalized instead of imposed. Nobody’s performing hierarchy because there isn’t one to perform.

Compare that to a group where you ask the same question and get an instant, confident answer pointing at one person. That’s not necessarily a bad team. But it’s a team that has a ceiling, and the ceiling is exactly as high as that one person’s bandwidth, mood, and attention span on any given day.

Where I still use this

Not really scouting anymore, obviously. But the same test travels well into anything with more than one person in it.

Ask yourself, of any team you’re part of: if I disappeared for two weeks with no warning, does this keep running at the same quality? Not “does it survive” — does it run the same, not worse, not with everyone quietly panicking and deferring every decision until you’re back.

If the honest answer is no, that’s not a compliment to how essential you are. It’s a diagnosis. It means you built a team that needs you instead of a team that’s strong.

The version worth being proud of is the boring one: you did the job so well that from the outside, nobody could tell you’d done a job at all.

I’ve started calling it the ghost-clipboard theory of leadership: the clipboard keeps getting carried, and nobody can remember whose it was.