The 11 Dumbest Mistakes Picard Made in Star Trek: The Next Generation

I love Jean-Luc Picard, but here I'm counting down 11 of his dumbest mistakes in Star Trek: The Next Generation, from number 11 all the way to number one. This is a man who could talk an entire civilization out of a war, and who could also ignore the one kid who figured out his officer had been replaced by an evil twin.

The list runs from his pride and his curiosity to the Prime Directive, the Borg and a search for Data that, at number one, turns into a staffing crisis.

11. Picard lets his pride pick his heart surgeon in The Samaritan Snare

I'm starting with something I would call incredibly human. In The Samaritan Snare, Picard needs his artificial heart replaced, and Pulaski offers to perform the procedure aboard the Enterprise. His one main concern is how the crew might see him afterward. Jean-Luc, they already know you're a person. You eat lunch, you get tired, you drink Earl Grey tea. Occasionally somebody has to explain to you what the children are doing.

Still, he would rather go to a starbase than let his own medical staff handle the operation. Then complications develop, and who gets called in to save it? Pulaski, the doctor he could have used in the first place.

Going to a medical facility isn't inherently a bad decision. The mistake is letting his image become part of the medical calculation. This man regularly tells other people to put their feelings aside and make the sensible choice, and apparently that advice stops working when the captain might have to wear a hospital gown. He survives, thankfully. His dignity also survives, which makes the whole secrecy exercise feel kind of pretty unnecessary.

10. Picard gives Rasmussen too much freedom in A Matter of Time

In A Matter of Time, a man arrives claiming to be a historian from the future. He wants to observe the Enterprise during an important mission, and he conveniently can't answer certain questions because that might alter history. That's an outstanding setup if your actual goal is to steal things.

Rasmussen moves around the ship, studies the crew and starts collecting technology. Spoiler alert: he isn't the future historian he claims to be. He's a man from the past using a stolen time machine to acquire inventions he can take home. Picard eventually catches him, and I'll give him that. But the Enterprise's initial hospitality really gives this guy room to operate.

I understand the challenge. How do you verify somebody's credentials when their university supposedly hasn't been built yet? You start with an escort, limited access, something. You don't need to solve time travel to establish that a stranger shouldn't be walking away with your equipment. Picard's curiosity is usually a strength, but here it kind of makes the ship a very, very expensive gift shop for this guy. Just go grab what you want. Everything's available.

9. Picard approves shore leave in Justice before understanding the laws

In Justice, the Enterprise finds a beautiful planet filled with, let's just say, friendly people. Everybody's really, really happy. The crew gets a chance to relax, and Wesley gets to go enjoy himself with kids his age. Then he falls into a flower bed and discovers the local justice system has one setting, one rule, one law: death. That's it. That feels like information that should have been collected before scheduling recreation time.

The away team's assessment misses the most important detail about visiting the place, and Picard, as the captain, approves the visit. It's not all on him, but the final responsibility doesn't disappear because somebody else said the weather looked nice.

To his credit, he does ultimately save Wesley and talks his way out of it. But first, the episode takes us into a debate about whether the Prime Directive means they should allow a teenager to be executed over an accidental violation. There's a serious ethical dilemma underneath the story, but there's also a very preventable travel mistake sitting right on top of it. Before you send people down to play ball, maybe ask what happens when the ball goes somewhere it shouldn't.

8. Picard treats two colonies like a matching exercise in Up the Long Ladder

In Up the Long Ladder, Picard has two problems. One group needs a new home. Another colony has been reproducing through cloning, and that system is breaking down. His solution is to combine the communities and restore sexual reproduction. At the broadest level, sure, one society has space and technology and the other brings people and genetic diversity. It's a practical idea: sandwich them together.

But the discussion gets really uncomfortable when an entire community's future becomes a reproductive plan, including recommendations about women having children with different men. The mistake is how quickly this becomes a solution negotiated from above. These are people with different cultures, expectations and relationships, and putting them together doesn't automatically mean everybody wants the same future.

Brenna is the one who points out the practical problem in front of everybody's face: the men can sit around solving civilization, but the women are expected to make the plan happen. Picard isn't ordering a forced breeding program, but he is getting remarkably comfortable presenting an enormous social arrangement like he found the missing piece of a puzzle. Sometimes the diplomatic solution needs a few more conversations with the people who are expected to live inside it.

7. Picard tells Q the crew is ready for anything in Q Who

In Q Who, there is confidence, and then there is announcing your confidence to somebody who can move your starship across the galaxy because he is bored. Picard tells Q they're prepared for whatever awaits them, so Q decides to test that statement literally and introduces the Enterprise to the Borg.

They were absolutely not prepared. Their weapons can do damage, but the Borg adapt and repair, and the Enterprise can't simply outrun them. Eighteen crew members die, and Picard finally has to ask Q for help. Q is responsible for putting them there, and I'm not handing him a free pass because he calls it a lesson. Picard's confidence did not force Q to endanger innocent people.

But Picard still makes a bad assessment. He takes the Federation's considerable experience and treats it like proof that they can handle threats they've never imagined. The impressive part is that he eventually admits he needs help. The mistake comes before that, when he mistakes being capable for being ready for everything. Space is enormous, Jean-Luc. You have explored a tiny portion of it. Maybe leave yourself a little room for surprises.

6. Picard avoids Hugh because he might complicate the plan in I Borg

This entry about I Borg is specifically about Picard's initial treatment of Hugh, because the decision he eventually makes is one of the reasons I love this character. The Enterprise rescues the injured Borg drone, Hugh, and the crew develops a plan to send him back with an invasive program intended to destroy the Collective. Picard is ready to proceed.

He initially resists treating the drone as an individual, and given what the Borg did to him, that reaction makes sense. But understandable doesn't always mean good. The really revealing moment is Picard acknowledging that he avoided speaking to Hugh because he didn't want anything interfering with the plan. That's a dangerous place for a leader to land: deliberately keeping your distance from information because it might make your preferred decision harder, and maybe make you a little uncomfortable.

Once he actually talks to Hugh, he encounters someone capable of independent thought and loyalty, someone who refuses to help assimilate his friends. So Picard changes course, and that's good. But the mistake was needing that much persuasion to look at the person whose life he was about to use as a delivery system.

5. Picard prepares to remove the colonists by force in Journey's End

In Journey's End, Starfleet orders Picard to relocate a community of Native American descendants because their planet is being transferred to Cardassian control under a treaty. The colonists refuse to leave. Picard faces a real problem. The treaty matters, another conflict would cost lives, and he can't simply pretend the political situation doesn't exist.

But he starts moving toward forcibly transporting these people out of their homes, and that's where I want the captain who gives all those wonderful speeches to stop and listen to himself. These colonists have a history of displacement, and their home matters to them. Yet the practical answer becomes removing them because the governments have finished negotiating.

Wesley challenges the process and warns the colonists about what is planned. Eventually another arrangement allows them to remain while giving up Federation citizenship. That ending doesn't make their future safe, but it did prove the choice was more complicated than leave voluntarily or we will transport you. I think Picard's mistake is letting the assignment narrow his thinking before the alternatives were exhausted. He felt conflicted, absolutely, but feeling terrible about a decision doesn't automatically make the decision right.

4. Picard is prepared to let the Boraalans die in Homeward

In Homeward, an inhabited planet is losing its atmosphere, and the Boraalans don't have the technology to escape. Worf's foster brother Nikolai wants to save at least a few of them. Picard refuses because of the Prime Directive, and this is one of those moments where I understand the rule and still can't get comfortable with how he applies it. The people aren't asking Starfleet to choose their government or give them weapons. Their world is becoming uninhabitable. They're going to die.

So Nikolai secretly transports a group aboard the Enterprise and hides them in a holodeck recreation of their surroundings. That creates serious problems. His deception is risky, and the story shows that cultural shock can have devastating consequences. But he also demonstrates that some lives can be saved.

Picard eventually helps complete the relocation, but before Nikolai forces the issue, his position is to let the disaster run its course. For me, that's the failure. He treats noninterference as the end of the discussion when it should be the beginning of a much harder conversation. I want the captain who searches for another option here. Somebody else had to make him search.

3. Picard ignores Wesley while Lore impersonates Data in Datalore

We've reached the famous shut up, Wesley moment in Datalore, and the problem is that Wesley has noticed something genuinely important. Data has an identical brother, and that brother is really, really dangerous. The person presenting himself as Data is behaving suspiciously, Wesley is trying to explain it, and Picard shuts him down.

There are situations where Wesley does need to stop talking. I think we can all agree this is an exceptionally bad candidate for one of them. The Enterprise has brought aboard an android who looks exactly like a trusted officer, so identity verification should be a priority. Instead, the kid who spots the impersonation gets treated like he's interrupting a staff meeting to ask what's for lunch, while Lore is working with the Crystalline Entity that could get everybody killed.

Yes, Wesley can be irritating in early TNG. I get it. That doesn't make his evidence less useful here, and this is why the scene belongs so high on the list. Picard's irritation affects his judgment during an actual security threat. You don't have to enjoy the warning, but you do need to listen to it.

2. Picard has no effective answer when Data takes the ship in Brothers

In Brothers, Data receives a signal from Dr. Soong and suddenly the Enterprise belongs to him. He changes course, forces the bridge crew to evacuate, imitates Picard's voice and locks the ship's controls behind an access code the crew can't get through. Meanwhile, they were transporting a child who needed urgent medical treatment.

Data isn't casually choosing to betray everybody. He's responding to a summons built into him. The problem is what that reveals about the ship: one compromised officer can take control so completely that the captain and the senior staff have no effective way to get it back. I'm not saying Picard should have predicted this signal, but command security should account for officers being compromised. In Star Trek, this happens before breakfast.

A voice imitation should not be enough to make the computer accept that the captain is giving an order. They work with an android who can imitate voices and think way faster than everybody else. That's a known capability. Some of that failure belongs to Starfleet's designers, but Picard commands the ship. He's the boss, and the episode exposes a massive weakness in the system he relies on. The flagship needs a better emergency plan than asking Data to please stop.

1. Picard sends nearly everybody down to find Data in Descent

At number one, I'm going with Descent. Data disappears with the Borg and Picard wants him back, which is completely understandable. They're friends. Data is his officer and a member of his family. Then Picard orders all available personnel into search teams and leaves Beverly commanding a skeleton crew aboard the Enterprise in a situation involving the Borg. That's the part where my confidence is shattered.

Beverly is capable, and she proves it. This isn't about whether she deserves the chair. It's about giving her a dangerously reduced crew while sending most of your people onto a planet where you don't fully understand the threat. Then Picard goes down too, along with key officers. His team ends up captured by Lore and the Borg, while Beverly has to handle the danger in orbit with the resources he left her.

Picard does give her an escape instruction: if the ship is threatened, she is to leave without waiting for the people below. That's sensible contingency planning, I get it. But it doesn't fix the original decision to spread the crew across the surface and weaken the ship supporting the mission. The Enterprise is your transport, your medical facility, your firepower, your way home. It is your home, and protecting it protects the search teams. Instead, Picard turns a rescue mission into two emergencies that other people have to solve. His loyalty to Data is admirable. His deployment plan was a hot mess.

I still want Picard in the chair, of course, but loving a captain doesn't mean every decision gets a standing ovation. If your answer is that you would have listened to Wesley, you've already improved one Enterprise security briefing.

Which of these decisions would you have challenged if you were on the bridge?