October 21, 2026 · 3 min read
The Picard Problem
Jean-Luc Picard was a great captain. I'm not entirely convinced he'd make a great engineering manager.
I've been thinking about Jean-Luc Picard a lot lately.
There's a habit of his that has bothered me for years. Something goes wrong aboard the Enterprise, he asks Geordi how long it will take to fix, and then tells him he has half that time.
Apparently the warp engines run on confidence.
On a starship, I can forgive it. If the Enterprise has three hours before it explodes, then three hours is what they've got. The captain has to make decisions with whatever time remains, even if the engineering estimate says six. That's not an invented deadline. That's a problem with unpleasant physics.
But most businesses aren't starships. Most projects aren't going to explode, and most meetings with executives aren't encounters with the Borg.
Yet I've spent enough time in software to recognize the scene. An engineer estimates six weeks. Someone in charge announces that it needs to be done in three. Not because a contract expires in three weeks, or a customer will be harmed, or some external event makes the original schedule useless. It would just be better to have it sooner.
Of course it would. It would also be better if the project cost nothing and came with a roast beef sandwich.
I don't believe Star Trek invented this style of management. The notion that you can accomplish more by demanding more has probably been around as long as people have been in charge of other people. Someone once told someone else the clovis points had to be done next week, despite the fact that the mastodons weren't going to be back for three months.
But I wonder whether a generation of people who admired Picard—people who went on to lead technology companies and engineering teams—absorbed a little of that performance along with the rest of his leadership.
Because this is the part that bothers me: asking for an estimate and then announcing a different number isn't a plan. It's just editing someone else's answer.
And I'm not suggesting estimates should be treated as holy writ. They can be wrong. Assumptions can be challenged. Scope can be reduced. Perhaps there's a less elegant solution that does the job, or a risk worth taking. Those are useful conversations. They might even get you to three weeks.
But if the leader doesn't ask any of those questions, what's actually changed? The work hasn't gotten smaller. The technical uncertainty hasn't vanished. We haven't identified a shortcut. We've simply declared the same job urgent.
I used to drive along Route 20 in upstate New York to visit a friend. I'd go past a place called the Petrified Creatures Museum. I never managed to visit. I always wondered whether they'd confused “petrified” with “fossilized,” or whether it was a zoo that kept the animals terrified during business hours.
I sometimes think that's the management model we're aiming for. Nothing is actually on fire. We just want everyone to behave as though it is.
There are times when leaders need to tell people the available time is shorter than the work requires. But when there isn't a real deadline, making one up doesn't demonstrate courage or decisiveness. It mainly transfers the discomfort of wanting something sooner to the people who have to build it.
This keeps everyone in a state of perpetual urgency. Even if you're cynical enough to consider panic a management tool, you have to acknowledge that it'll stop working if you use it all the time.
A good leader can question an estimate, look for shortcuts, or decide what they're willing to sacrifice to get something done sooner.
What they can't do is make six weeks into three just by saying so.
This isn't Star Trek.