Low diatribe

When I was a kid, I loved Voltron.

That probably isn't surprising if you grew up in the 80s. Giant robots fighting space monsters was a pretty reliable formula for grabbing a kid's attention.

But the part that stuck with me wasn't the fighting.

It was the moment before.

Five robotic lions, each powerful on its own, flying in from different directions.

They would lock together — leg, arm, torso, head — and suddenly something new existed.

Not five lions anymore.

Voltron.

At the time it just felt cool. But looking back, I think it planted something deeper in me.

It gave me one of my earliest ideas about teams.

Not groups. Not departments. Not a collection of talented individuals working in the same open-concept office.

Teams.

The kind where each part remains fully itself, but together they become capable of something none of them could do alone.

And the part I didn't fully understand then — but feel more clearly now — is that the lions mattered before they combined.

Each one could fly. Fight. Hold its own.

They weren't incomplete pieces waiting to be assembled.

They were whole.

That's what made the combination meaningful.

Not five weak parts propping each other up. Five strong parts choosing to come together.

---

I've gotten this wrong more than once.

There's a part of me that wants all five lions before I start.

All the pieces. All the clarity. All the conditions lined up.

Only then do we move.

It feels responsible. Prepared.

It's also a good way to never begin.

I remember sitting on a team initiative for the better part of a year waiting for the right moment — the right headcount, the right alignment, the right conditions. By the time everything felt ready, the window had closed. The problem we'd been preparing to solve had already been solved by someone else, messily, with half the resources, while we were still waiting to begin.

Because the story didn't start with Voltron.

The Gallactic Alliance didn't wait until they had all five lions to resist.

They started with what they had.

One ship. One pilot. One small act of defiance.

Then another.

Then another.

Voltron wasn't the beginning.

It was the result.

---

But you don't get Voltron just by assembling talented people.

Each lion has to be strong on its own. Each pilot has to trust the others. Each part has to understand its role.

And the black lion — the one that formed the head — wasn't powerful because it was "in charge."

Its job was coordination.

Not domination. Not control.

Alignment.

But even that isn't quite right.

Because the head doesn't move on its own.

It doesn't decide in isolation and then issue commands to the rest.

When Voltron moves, it's not the head leading the body.

It's the body moving as one.

The red lion doesn't wait to be told it's an arm. The green lion doesn't just "do leg stuff."

Each part is fully itself, fully capable, and somehow aware of the whole.

The head isn't controlling the system.

It's expressing what the system is already doing together.

---

That's the part we tend to miss.

We talk about leadership like it sits at the top, directing everything beneath it.

My favorite teams didn't feel like that at all.

They felt coordinated.

Like everyone understood their role, the moment, and the motion — and could act without waiting.

The "head" still mattered.

But not as a command center.

More like a point of integration.

A place where the movement becomes visible.

---

You see it in the quiet moments when everyone suddenly understands their role in the larger pattern.

The conversation shifts. The energy changes. Work that felt heavy becomes fluid.

Not because anyone became stronger individually.

Because the pieces finally fit.

---

There's a temptation, once you've seen it work, to believe that more must be better.

Rick and Morty captured this perfectly — and absurdly. Rick, never one for restraint, takes the Voltron idea and runs it straight off a cliff. Why have one combining Gotron when you can combine five Gotrons into the Gogotron? And five Gogotrons into the Gogogotron?

The name gets longer. The thing gets bigger. The original purpose gets lost somewhere around the third "go."

It's funny because it's so recognizable.

More pieces. More layers. More spectacle. No clearer purpose. Just the compulsive logic of: if combining worked once, combining again must work better.

If one strong team is good, ten must be unstoppable. If coordination creates power, maximum coordination must create maximum power.

So we stack.

Teams on teams. Layers on layers. Structure on structure.

At some point, it stops being formation and starts being accumulation.

That's the shift.

The original idea wasn't about becoming bigger.

It was about becoming something new.

The lions didn't stack.

They fit.

The best organizations I've seen don't grow by endlessly adding.

They grow by forming.

Strong individuals. Strong teams. Clear roles. Mutual trust.

And then, when needed, those teams align into something larger.

Not because they've been stacked.

Because they know how to lock together.

---

I'm still chasing it.

Not the spectacle. Not the scale.

The moment the pieces lock. The shift in the room. The work that suddenly moves like it knows where it's going.

And when it works, you don't declare victory and disband.

You do it again.

With a new problem. A new moment. A new configuration of people who are each whole on their own.

Formation isn't a destination.

It's a practice.

Something you keep doing, keep earning, keep building toward.

Every time.

Voltron form.