One of the people who shaped how I think about leadership never knew I existed. He commanded a starship, drank Earl Grey, and had the unmistakable voice of Sir Patrick Stewart.
The news of Stewart’s death felt strangely personal. Growing up in the 1990s, Captain Jean-Luc Picard was one of my childhood heroes. The Enterprise, the strange new worlds and the occasional encounter with the Borg certainly helped. But what stayed with me was how he treated the people on his bridge.
Picard listened. He expected people to know their jobs, gave them room to do them, and took their objections seriously. He could be demanding, distant and occasionally spectacularly stubborn. Yet Patrick Stewart gave him a combination of dignity, warmth and vulnerability that made his authority feel earned.
Decades later, I lead teams of talented Solutions Consultants, and I still recognise values I first admired on that fictional bridge. Trust your people. Listen when they disagree. Be clear about the mission. When things go wrong, stand in front of your team instead of hiding behind them.
Of course, a quarterly sales target is not a Borg invasion, however the forecast call might sound. But science fiction and fantasy give us unusually memorable ways to think about leadership. They put capable people under pressure, give them conflicting loyalties and incomplete information, and ask what they will do next. That is familiar territory for anyone working between customers, Sales, Product and delivery.
Picard: give expertise a voice
The Enterprise works because different people understand different parts of the problem. Data analyses, Geordi understands the engineering, Worf sees threats, and Troi notices things that a technical readout will never reveal. Picard’s responsibility is to hear those perspectives, weigh them and make a decision.
That is a useful model for an SC leader. An experienced manager may know the product well, but the consultant who has spent three weeks with the customer probably understands the situation better. Taking over the conversation can feel helpful while quietly teaching everyone that the manager’s answer matters most.
In a deal review, I would rather start with: What do you think is really happening? What have we actually validated? What would you recommend? The answers tell me far more than a tour through CRM fields. They also give the person closest to the work a chance to exercise judgement.
This connects with Google’s research on team effectiveness, which identified psychological safety, dependability, clarity, meaning and impact as important team dynamics. In an SC team, the practical test is whether someone can say that a proposed solution will not work, or that they need help, before the problem reaches the customer.
Inviting disagreement only counts if you respond well to it. If the first person to challenge a demo strategy gets publicly dismantled, the next meeting will be wonderfully harmonious and considerably less useful.
For individual contributors, the same principle applies in discovery. Give the customer’s experts room to explain what you have missed. Salesforce’s guidance for solution engineers emphasises active listening during discovery. That sounds obvious until you notice how easily curiosity disappears when you already have a favourite feature to demonstrate.
The Measure of a Man: protect the person behind the expertise
In The Measure of a Man, Picard defends Data’s rights when Starfleet seeks to subject him to research against his wishes. His loyalty to the institution does not prevent him from challenging it. That is part of what made the episode stay with me.
The workplace parallel is smaller, but it matters. Highly capable people can become the automatic answer to every difficult request. The integration expert gets every complicated architecture. The best presenter gets every executive demo. The reliable person gets another urgent proof of concept because everyone knows they will somehow make it work.
Eventually, being excellent becomes a workload penalty.
A leader has to interrupt that pattern. Sometimes that means negotiating scope with Sales. Sometimes it means declining an evaluation until there is a clear customer decision, agreed success criteria and someone available to run it properly. Sometimes it means admitting that the team cannot absorb another priority without dropping something else.
Standing in front of your team also means owning your contribution when things go wrong. If I accepted an impossible deadline or failed to secure the right support, that belongs in the conversation. We can still discuss preparation, judgement and performance honestly. Accountability becomes more credible when the manager participates in it.
Sisko: understand the politics, keep your boundaries
Benjamin Sisko leads in a different environment. Deep Space Nine is a place where people with different histories, loyalties and interests have to coexist. Relationships matter because he cannot simply leave every difficult situation behind at the end of an episode.
Solutions Consulting has plenty of that. Sales wants momentum. Product has a roadmap. Security needs evidence. Professional Services needs something deliverable. The customer’s sponsor wants a business outcome, while the people expected to operate the solution want to know what Monday morning will look like.
A strong SC helps those groups understand one another. When a customer asks for a feature, the useful question is often what decision or process depends on it. When Sales asks for a demo tomorrow, it helps to understand which conversation that demo is supposed to advance. Diplomacy starts with taking another person’s pressures seriously.
Sisko also gives us a warning. In In the Pale Moonlight, his effort to bring the Romulans into the war draws him into deception and devastating moral compromises. It is compelling drama precisely because the outcome does not make the methods comfortable.
Nobody should use that episode as a sales playbook. Quarter-end pressure does not turn a roadmap item into a released capability. A carefully staged demo does not establish that an integration works in production. If a prototype uses simulated data or manual steps, explain that. If a requirement remains untested, record it as untested.
The practical lesson I take from Sisko is to recognise pressure early enough to discuss it. Agree who can commit to what, bring delivery colleagues into the conversation before promises harden, and make unresolved risks visible. Customer trust has to survive the handover.
Janeway: give people direction when you cannot give them certainty
Kathryn Janeway has to get Voyager home with a crew drawn from Starfleet and the Maquis, far from the support structures they know. The destination is clear. The route, resources and next set of problems are considerably less predictable.
That distinction matters in leadership. During a reorganisation, a change in territory or a difficult product transition, people often ask questions their manager cannot yet answer. Pretending to know creates fragile reassurance. Saying nothing leaves everyone to invent their own explanation.
A useful response has three parts: here is what we know, here is what remains uncertain, and here is what we will do next. Add a time when you will return with an update, even if the update is that the answer is still pending.
For a customer evaluation, that might mean agreeing which business outcome matters, which assumptions need testing and what evidence will justify proceeding. A time-boxed proof of concept with a shared success definition gives people a route through uncertainty. An open-ended invitation to keep testing features usually gives them more uncertainty, with a larger calendar.
Janeway is also a reminder to question the romance of constant endurance. A television crew can move from crisis to crisis because another episode needs a plot. A real team needs preparation time, recovery and a sustainable workload. If every deal requires a heroic rescue, the leader should investigate qualification, staffing and scope before celebrating the next all-nighter.
The Avengers and the Fellowship: build a team with different strengths
The original idea for this article included the Avengers, and the comparison still works. A team containing Tony Stark, Steve Rogers, Natasha Romanoff and Bruce Banner has plenty of capability. It also has plenty of potential for disagreement. Bringing talented people together is only the beginning.
The same applies when hiring SCs. It is tempting to recruit versions of the person who already succeeds: confident presenter, strong product knowledge, quick with an answer. But a team also needs patient discovery, architectural depth, commercial judgement, clear writing and people who willingly help colleagues improve.
The person who spots the integration risk before the executive demo may create more value than the person delivering it. If recognition always follows stage time, we teach the team that quieter contributions matter less.
Fantasy offers another useful picture. The Fellowship in The Lord of the Rings brings very different people into a shared undertaking. Sam’s loyalty and persistence matter alongside Aragorn’s ability to lead. Carrying the story does not always mean having the most impressive title or weapon.
In an SC organisation, that means making complementary strengths visible and giving people room to grow. Pair a strong storyteller with an architectural specialist. Give the thoughtful colleague who writes excellent discovery notes a supported opportunity to lead the next workshop. Ask experienced consultants to coach, and recognise that coaching as real work.
This is also where the captain metaphor reaches its limit. Customers are collaborators, and an SC team is not a military chain of command. Many of our most important decisions happen through influence. You can lead a difficult discovery conversation, challenge an assumption or help a colleague succeed without having anyone report to you.
What this looks like on Monday morning
I have written before about moving from delivering demos to coaching the people who deliver them. These fictional leaders give me another way to think about that shift. The question becomes what I can do to help the team make better decisions when I am absent.
A few ordinary habits make that ambition concrete:
- Before the demo, agree on the mission. Which customer problem are we addressing, what outcome matters, and what decision should this meeting help them make?
- In the deal review, hear the assessment before giving yours. Ask the SC for their recommendation and the evidence behind it. Make space for the person who sees a risk.
- Before committing to a proof of concept, agree on the boundaries. Define success, scope, owners, available time and the decision that follows.
- After a difficult engagement, examine how the work was set up. Discuss individual choices alongside qualification, handovers, preparation time and the commitments leadership made.
- In the next one-to-one, talk about the person. Ask what they want to learn, what is exhausting them and which obstacle you can remove.
None of these habits requires a captain’s chair. They do require consistency. People learn what leadership means from the requests we accept, the questions we ask, the behaviour we reward and the way we react to bad news.
One last Earl Grey
I never met Sir Patrick Stewart. Yet his portrayal of Picard accompanied me from childhood into adulthood and helped shape my sense of what a good leader could look like.
The speeches were wonderful. So were the pauses before them: the moments when Picard listened, considered the consequences and allowed someone else’s expertise to change the conversation. Stewart made that kind of leadership compelling enough for a child to notice and memorable enough for an adult to revisit.
I hope the people I work with feel trusted to use their judgement, safe enough to challenge me and supported when the situation becomes difficult. That seems a worthwhile way to carry something from the bridge of the Enterprise into an ordinary working day.
Thank you, Sir Patrick, for giving us Captain Picard.
One last Earl Grey. Hot.
Make it so. 🖖
