Leadership, Logic and the Occasional Kirk Moment

After writing my earlier entry on the influence of Star Trek on my thinking, I wanted to do a deeper dive into some of those aspects.

I've mentioned that over the years, Star Trek has probably influenced my thinking about leadership at least as much as many of the more conventional sources. Hopefully by now this doesn't sound odd (ok, maybe a bit), until you remember what the show was about: on the surface it was a science fiction adventure series, but underneath that, it was really a show about decision making under uncertainty. Every episode placed the crew in some unfamiliar situation: a new civilisation, a technological mystery, a diplomatic dilemma, or occasionally an alien entity with worrying godlike powers.

The interesting part was rarely the special effects, even though they were good for the era (yes, I'm looking at you Dr. Who!) It was how the characters approached the problem: the Kirk triangle. I think the most enduring element of the show is the dynamic between Kirk, Spock and McCoy. Spock represents logic and analytical reasoning, McCoy represents empathy and human intuition and Kirk sits somewhere in the middle, synthesising the two.

In modern management language we might call this balancing data-driven analysis with human context. In the show it usually involved Kirk listening to two very strong and very different perspectives before making a decision. It’s a simple model, but a surprisingly effective one: teams, not heroes!

Another thing the series gets right is something that’s occasionally forgotten in discussions of leadership: the captain doesn’t solve the problems alone. The Enterprise works because it’s a team. Kirk’s role is not to out-perform the team members in their own domains, it's to listen, integrate the information and decide on a course of action. That maps rather neatly onto the reality of running engineering organisations.

If you’ve hired capable people and ideally people who are smarter than you in their respective areas, your job isn’t to micromanage their work, it's to create an environment where their expertise can inform the decisions that matter. Large engineering projects tend to operate under similar constraints. Requirements evolve, environments change and occasionally something fails in a way no one anticipated. In those moments, leadership becomes less about having the right answer immediately and more about assembling the best available understanding and moving forward.

Kirk’s approach often involved a mixture of curiosity, consultation and occasionally a willingness to take calculated risks. It turns out that those characteristics translate reasonably well outside of television.

One other aspect of the series has stayed with me over the years. Despite all the futuristic technology, the show never pretends that technology alone solves the problem. The real decisions are always human ones. How do we treat this civilisation? What risks are acceptable? What values guide our choices?

Engineering organisations face their own versions of those questions: prioritising features, balancing delivery timelines with quality, deciding how to respond when something goes wrong. The technology matters, but the human judgement matters more.

It’s important to say that I don’t consciously think “What would Kirk do?” every time a difficult decision appears (ok, maybe sometimes!) But the underlying ideas from Star Trek have a habit of resurfacing: listen to your experts; balance logic with empathy; accept that uncertainty is unavoidable; trust the team you’ve built. And occasionally remember that even the captain of the Enterprise needed a good crew around him.

Not a bad leadership framework for a television show from the 1960s.