Security Leadership

Star Trek: The Next Generation as Leadership Training

60 years of Star Trek. I’m a child of Star Trek: The Next Generation. The adventure, the SciFi, the imaginative stories….and now it’s considered to be a mediocre 80’s action series. The space battles are slow, the stakes reset every week, and the ship is never in danger you actually believe in.

But….It is also the best leadership curriculum on television, and for exactly the same reason. TNG spends a-lot of its time in the conference room, conversation, and collaboration.

Most leadership fiction is about the moment of decision — the founder who just knows, the general who sees the opening, the executive who walks into the boardroom with the answer. TNG is about the twenty minutes before that, when seven people with different expertise and incompatible instincts argue in front of their boss, and the boss has to pick.

That is what the job actually is. Almost nothing else on screen shows it.

Why fiction works as training at all

You cannot practice a layoff. You cannot rehearse a breach disclosure, or the meeting where you tell a customer their data was in the exposed bucket. The situations that most need judgment are exactly the ones you get to do once, live, with consequences.

This is why military academies and business schools both teach through cases. Judgment does not transfer well from principles. It transfers from worked examples — enough of them, varied enough, that you start recognizing the shape of a situation before you can articulate why.

TNG gives you 178 worked examples. Unlike a written case study, it shows you the arguments people made before they knew the outcome, which is the only condition under which you ever actually decide anything.

Six things the show gets right

1. The briefing is the work

Picard almost never decides alone. He convenes, goes around the table, asks each department head for their read, and specifically invites the objection. Then he decides, and he owns the decision as his rather than the group’s.

Notice what he does not do: he does not tell them how. “Make it so” is commander’s intent — the what and the why, with the method left to the person who knows the system. He gives Geordi an outcome and a constraint, not a procedure.

The test for your own staff meeting is simple. When did someone last change your mind in that room? If the answer is that you cannot remember, you do not have a briefing. You have a status readout with a decision announced at the end.

2. The competent leader nobody likes

“Chain of Command,” Parts I and II. Captain Jellico replaces Picard. He moves the ship to four shifts, demands readiness drills, is cold to Riker, and refuses to negotiate with the Cardassians. The crew resents him immediately and thoroughly.

The discipline of the episode is that Jellico is mostly right. He reads the threat correctly. His demands are appropriate for a ship about to face combat rather than one doing survey work. He wins the standoff. The show refuses to resolve the discomfort by making him a villain.

A leader optimized for a different threat model will look incompetent to a team optimized for the old one. If you have ever brought in a security leader after an incident, or been through an acquisition, or watched a founder-led team get its first real operator, you have met Jellico from the other side.

The useful question is not whether you like the person. It is what threat model they are solving for, and whether it is the right one now. Sometimes it is not — and Jellico is also genuinely bad at explaining himself, which is a real failure and costs him. Both things are true.

3. The investigation that turns into a hunt

“The Drumhead.” Admiral Satie comes aboard to investigate an explosion. She finds a real problem — there was genuine espionage. Then she keeps going. Worf, who wants to be useful, becomes an eager instrument. A young crewman is destroyed because he concealed a Romulan grandfather.

This is the single most useful episode for anyone running security, audit, or compliance, because those functions have an authoritarian failure mode built directly into their incentives. The investigator is rewarded for finding things. Finding nothing looks like failure. That pressure does not announce itself; it just slowly widens the scope.

The controls are boring and structural: a scope defined in writing before you start, a defined end condition, and a person with actual standing to say stop who is not the investigator. If your internal investigations have none of those three, you do not have a process. You have Satie’s process, and you are relying entirely on the investigator’s character.

4. Being ordered to argue against yourself

“The Measure of a Man.” A hearing will decide whether Data is a person or Starfleet property. Riker is compelled to argue that Data is property — if he refuses, the hearing collapses and Data loses by default.

Riker does it well. He finds the strongest version of the argument and demonstrates it by reaching behind Data and switching him off in front of the room. It is devastating, it nearly breaks him, and it is the reason the hearing means anything.

This is steelmanning as a duty rather than a debating trick. The practice version: before a decision that matters, assign someone competent to build the best case against it, and tell them to try to win. Not devil’s advocate theater, where everyone knows the objection is decorative. An actual argued case.

Then thank them in public, specifically and by name. Otherwise nobody does it a second time, and you have taught your organization that dissent is a career expense.

5. Truth before self-protection

“The First Duty.” Wesley’s flight squadron covers up the maneuver that killed a cadet. Picard, to Wesley: the first duty of every Starfleet officer is to the truth. Whether it is scientific truth, historical truth, or personal truth.

Every incident postmortem reaches a moment where a plausible, defensible, not-quite-complete story is available, and it protects someone who does not deserve to be destroyed. What happens in that moment is what your organization’s values actually are. The poster in the break room is not evidence.

If you punish disclosure, you buy silence. It is a real purchase and it works — you will hear about fewer problems immediately. You pay for it later, with interest, at a time you do not choose.

6. The advisor has a seat

Troi sits on the bridge, beside the captain, inside the command structure. Somebody whose entire job is reading the organizational and human state of the crew has standing at the table where decisions get made.

Most organizations file that function under HR and route it three levels below the room. Then they are surprised when the reorg lands badly, or when the team that shipped the migration quietly falls apart two months later.

Ask who in your organization has the job of telling you the team is exhausted — and then ask whether they have the standing to be believed when they do.

Where the show lies to you

A post that only praises the source material is not analysis, it is fandom with a business vocabulary. TNG makes leadership look more tractable than it is, in four specific ways.

  • There is no budget. Picard never chooses between the away mission and payroll. Every resource decision on that ship is a priority decision, never a scarcity one. That removes the hardest part of most real management.
  • Nobody quits. The crew cannot take a better offer. Retention is structural rather than earned, so Picard never pays the price for being difficult, and never has to weigh whether a correct decision will cost him his two best engineers.
  • Selection was done for him. Starfleet Academy filtered that crew for years. You hire from the available market, on a deadline, against a salary band you did not set.
  • The moral clarity is authorial. Picard is right unusually often because writers decided the outcome before the argument was filmed. Real deliberation frequently ends 60/40 and stays 60/40 permanently, because the counterfactual never runs.

Take TNG as a model of process, not of outcome. The way Picard runs a room is portable. The world that room sits inside is not.

How to actually use it

Watching passively teaches you nothing; you will just enjoy it, which is fine but is not training. Watch with a question in hand, and pause before each resolution to write down what you would do and why.

Three episodes to start, chosen for how directly they map onto work you probably have:

  • “Chain of Command,” Parts I and II — if you have inherited a team, or been inherited.
  • “The Drumhead” — if you run investigations, audits, or a compliance function.
  • “The Measure of a Man” — if you make decisions where the facts themselves are contested.

The lesson is not whether your answer matches Picard’s. It is whether your reasoning covered the ground his did — whether you thought of the objection that the chief engineer raised, and what it means about your blind spots that you did not.

The reason this holds up as training is that TNG dramatizes the part of leadership that is genuinely hard and almost never filmed: sitting in a room with people who each know more than you do about their piece of the problem, deciding anyway, and owning it afterward.

That is the job. The uniforms are incidental.


Where to go next


Discover more from CyberCloudAI.tech

Subscribe to get the latest posts sent to your email.

Scroll to Top