Gaming leadership is real leadership

The claim, stated plainly

I believe relevant leadership experience comes from wherever people actually lead. Since 2009 I have run organizations in parallel: engineering teams and enterprise accounts at work, and gaming organizations after hours — starting with Crystal Legends Online from 2009 to 2012, an alliance in Last War that I led as its R5 through 2023 and 2024, and most seriously in EVE Online, where I have served as a corporation CEO of a 50+ member corporation and as alliance director for operations spanning more than a hundred people.

The polite assumption is that one of these is a job and the other is a hobby. My experience is that they are the same discipline practiced under different constraints — and that the gaming side, in specific ways, is the harder classroom. This is the serious version of that argument, from the gaming record on my About page.

What a large gaming organization actually is

Strip the spaceships away and an EVE alliance is this: a volunteer organization of 50–300 people that must recruit continuously, train newcomers, fund itself through internal industry and logistics, defend territory against motivated rivals, negotiate treaties, and mobilize dozens of people on twenty minutes’ notice — indefinitely, with 100% at-will membership and zero payroll.

That is not like an organization. It is one. EVE in particular is famous for this because the game’s economy and politics are player-driven: supply chains, banking, espionage, and coalition warfare all exist because players built institutions to run them.

The skills that transfer

Leading without positional power

A workplace manager’s requests carry implicit force: performance reviews, compensation, employment itself. An alliance director has none of that. If an operation is badly planned, people don’t file a grievance — they don’t show up. You learn very quickly that attendance is a real-time referendum on your leadership, and the levers that remain are the fundamental ones: clear purpose, competent planning, visible fairness, and making people feel their time was respected.

Managers who learn in that environment arrive at the workplace insight most take a decade to reach: the paycheck buys attendance, not effort. Effort is volunteered — always — and it is earned the same way in a standup as in a fleet briefing. This is servant leadership learned under conditions where nothing else works at all.

Real-time incident command

A contested fleet engagement is an incident bridge with better graphics: incomplete information, a hostile clock, a hundred people waiting on your next call, and a comms channel that will dissolve into noise unless you impose structure. The disciplines are identical — designate a single voice, separate reporting from deciding, give orders with intent attached so subordinates can improvise correctly, and run the retrospective afterward without shaming the scout who called it wrong.

I have run both kinds of bridge. The transfer is direct enough that it works in both directions: my incident-command habits at work got noticeably better in the years I was flying fleets.

Logistics and operations at scale

Keeping a hundred-member organization supplied — doctrine ships fitted, fuel stocked, staging systems provisioned ahead of a deployment — is supply chain management with unforgiving feedback. Forecast wrong and the failure is public, immediate, and measured in members who drift to better-run rivals. The same instincts (buffer inventory against volatility, shorten the pipeline, make status visible to everyone) map straight onto running delivery organizations.

Diplomacy between organizations you don’t control

Alliance leadership is continuous negotiation: treaties, non-invasion pacts, market access, intelligence sharing — with counterparties who have their own internal politics and no contract law to appeal to. Reputation is the only enforcement mechanism, so you learn to make agreements that are self-enforcing because both sides keep winning. That is exactly the skill a client technology leader uses across the table from partner vendors, and the reason I treat vendor management as a diplomatic function rather than a procurement one.

Succession and turnover as a constant

Volunteer organizations churn. Twenty to thirty percent annual turnover is a good year, so every role must have a trained second, every process must survive its author leaving, and knowledge hoarding is an existential threat rather than an annoyance. The math held in every game I’ve led in — the Last War alliance I ran through 2023 and 2024 had completely different mechanics from EVE and exactly the same turnover problem. I now apply the same test to my professional teams that I apply to alliance departments: if this person logged off permanently tonight, what breaks tomorrow? Whatever the answer is, that’s the next delegation project.

What doesn’t transfer

Honesty about the limits keeps the argument credible:

• Consequence weight. A lost fleet is a bad evening; a failed hospital system is not. Gaming builds decision mechanics, but calibration to real-world stakes has to come from real-world practice.
• The personnel floor. You can remove a toxic member from an alliance in minutes. Workplace performance management is slower, more humane, and legally constrained — rightly so — and gaming teaches you little about doing it well.
• Selection effects. Everyone in the fleet chose to be there. Workplace teams include people at every level of engagement, and leading the reluctant is its own skill.

Using it credibly

If you lead seriously in games and want the experience to count: describe the function, quantify the scope, and hold it to resume standards of truth (“led logistics for a 100-member volunteer organization; coordinated operations across 12 time zones”). Expect a skeptical first reaction and welcome the follow-up questions — the conversation that starts with a raised eyebrow usually ends with the interviewer telling you about their own guild.

And if you hire engineers: the candidate who has kept a volunteer organization alive for five years has demonstrated retention, delegation, and operational discipline under the hardest incentive conditions there are. That signal is real. I would know — it’s on my resume, in both columns.

The control group

Here is the engineering way to look at it. If you want to know which parts of leadership are load-bearing, you need an environment where the confounding variables are removed — and a volunteer gaming organization is that environment. No salary, no title gravity, no HR process, no career consequences for walking away. Every mechanism that keeps a workplace team together for reasons other than leadership quality has been stripped out. What survives the stripping is the actual discipline: clear purpose, competent operations, fair dealing, visible respect for people’s time, and succession planning that assumes everyone eventually leaves.

Run leadership in that environment for a few years and you stop being able to fool yourself. A workplace gives a mediocre manager a dozen ways to misread retention as loyalty and compliance as buy-in. An alliance gives you one metric, updated nightly: who logged in, and who quietly didn’t.

That is why I keep both practices running and why each one audits the other. Work taught me consequence weight, formal accountability, and the patience that real personnel management requires. Games taught me — faster and more brutally — what people actually follow when nothing compels them to. Titles, incentives, and org charts vary between the two worlds. The system underneath doesn’t: people volunteer their best effort to leaders who are worth it, and no compensation structure has ever changed that.