Lying to Management

Scotty preserved slack. Geordi spent it. B’Elanna rationed it. O’Brien was it.

There is a scene in Star Trek: The Next Generation where Montgomery Scott discovers the future and reacts, correctly, with alarm.

The episode is “Relics.” Scotty, having survived for decades inside a transporter buffer because apparently even death can be delayed by a sufficiently stubborn engineer, finds himself aboard the Enterprise-D. He is out of time, out of place, and surrounded by a Starfleet that looks cleaner, talks softer, and has somehow learned to make engineering seem like middle management with better lighting.

At one point, Scotty asks Geordi La Forge how long a repair will really take. Geordi gives him the actual estimate. Scotty is horrified. You told the captain the real time? What are you, new?

The scene plays as a cute generational gag. Scotty is the old hand, Geordi is the modern professional, and the joke is that the grizzled miracle worker has been padding estimates for decades while the younger engineer believes in honest reporting. It is funny because Scotty is Scotty. It is also funny because the writers accidentally documented a regime change.

This is not a scene about honesty. It is a scene about labor.

Scotty is not merely lying. Geordi is not merely telling the truth. They are operating under two different theories of what an estimate is for.

Scotty comes from a world where engineering estimates are buffers against command fantasy. Captains ask for impossible things because captains are selected, socially and institutionally, for their ability to believe impossible things should be attempted. This is sometimes leadership. It is sometimes a diagnosable condition with a chair on the bridge. The chief engineer’s job is not simply to obey that fantasy. It is to route it through material reality without letting the ship, the crew, or the laws of physics absorb the whole impact at once.

So Scotty pads.

He multiplies the estimate. He preserves uncertainty budget. He keeps a reserve of time, labor, risk, and mechanical dignity between Kirk’s heroic demand and the warp core’s indifferent response. He does not tell the truth because an accurate estimate is not a neutral fact. Once command has it, command can use it. The estimate becomes a lever. A promise. A future accusation.

If you say it takes two hours, and the mission needs it in one, someone has to absorb the difference. The captain will not. The mission will not. The schedule certainly will not. The pain moves downward until it reaches the people turning the wrenches.

Scotty’s padding is a way of pre-distributing that pain back up the chain where it belongs. It is not perfect. It is not pure. It depends on trust, ritual, and a shared understanding that the engineer’s lie protects something real. But in its healthiest form, the lie is a professional firewall. It keeps hierarchy from placing its full weight directly onto labor and calling the compression “commitment.”

Geordi inherits a different world.

The Enterprise-D is the flagship of a more procedural Starfleet. Everything is brighter. The carpets are plusher. The consoles are less likely to explode, though not unlikely enough. The ship feels less like a naval vessel bolted together by haunted geniuses and more like a floating institutional consensus. It is post-scarcity, post-sweat, post-smoking-in-the-server-room. It has counselors, children, replicators, holodecks, conference rooms, and the terrifying confidence of an organization that believes good process can civilize uncertainty.

Geordi is not less competent than Scotty. In some ways, he is probably more competent. He commands a larger department, manages more complex systems, and operates inside a ship whose technological sophistication makes the original Enterprise look like a heroic electrical fire. Geordi is excellent.

That is what makes him dangerous to himself.

He treats accurate reporting as professional virtue in an institution that still expects miracles. He gives the true estimate upward, but the social function of the deadline has not changed. The captain still needs the impossible. The ship still must be saved. The anomaly still refuses to respect the project plan. Only now the engineer has less ritualized permission to protect slack before the demand arrives.

The result is not honesty. It is exposure.

Geordi does not preserve slack. He internalizes the deadline. He becomes the kind of good employee every institution loves: truthful, capable, conscientious, and therefore exploitable. He will surface the constraint. He will explain the risk. He will make the work visible. Then, when command says the mission still requires it sooner, he will absorb the variance with his team and call the successful overextension Starfleet excellence.

This is the poison at the heart of modern project management when it loses contact with consequence.

Work can be decomposed cleanly. Constraints can be surfaced without political consequence. Teams can commit under uncertainty. Heroics do not distort future expectations. The next impossible request will not be benchmarked against the last miracle.

Every one of these claims is false. Not metaphorically false. Operationally false. False in the way an overloaded system is false right up until it falls over and everyone starts asking why there was no warning.

There was warning. It was in the estimate. Then the estimate became a commitment.

This is why Scotty’s old trick is not merely a comic relic. It is a labor practice. A crude one, yes. A ritualized one. A practice from a world with its own pathologies and masculine little myths about genius under pressure. But it encodes a truth that later institutional culture tries very hard to forget: slack is not waste. Slack is how reality enters the plan without immediately becoming a disaster.

Once heroics are recorded as velocity, the miracle becomes planning data.

That is Geordi’s trap. He lives in a Starfleet that has mistaken transparency for control. The system wants accurate information, but not because it intends to protect the people who provide it. It wants accurate information because accurate information makes extraction more efficient. The estimate becomes legible. The constraint becomes visible. The person responsible becomes identifiable.

Congratulations. The schedule has eyes now.

This is why Captain Jellico matters.

Jellico, in “Chain of Command,” is often treated by fans as either a tyrant or a necessary hardass, depending on their tolerance for Riker’s facial expressions. But the useful thing about Jellico is that he is not stupid. He is not a cartoon bad manager. He takes command under real pressure, with the Cardassians looming and a dangerous mission in motion. He has reasons. That is what makes him dangerous.

Bad management is easy to dismiss when it is merely incompetent. Jellico is something worse: a manager with legitimate urgency and command authority who understands constraints well enough to override them.

When Geordi explains what engineering can do, Jellico does not fail to comprehend him. He converts the constraint into labor pressure. The schedule does not move. The work moves. The human cost is simply relocated downward. Engineering can work around the clock. The crew can absorb the tempo shock. The ship can be made ready because the mission requires it.

This is the Starfleet version of agile poison. Not the cute version with sticky notes and morale words. The real version.

The estimate is accepted as information and rejected as a boundary. If the team succeeds, the overrun disappears into institutional memory as capability. If the team fails, the estimate returns as evidence that they knew the risk and did not manage it.

Geordi has no rhetorical defense because he has already told the truth in a system that treats truth as obligation. Scotty’s buffer would have been unprofessional. It also might have been the only remaining protection.

This does not mean Scotty was simply right.

That would be too easy, and worse, nostalgic. Scotty’s method has limits, and The Search for Spock is where those limits become visible.

In that film, Scotty does everything the legend says he can do. He sabotages the Excelsior. He helps steal the Enterprise. He gets an undermanned, aging ship moving under conditions that would make any responsible maintenance supervisor start drinking directly from the checklist. The miracle happens. The old magic still works.

And the Enterprise dies.

That matters. Scotty’s method depends on there being slack to preserve. It depends on a captain-engineer pact, however informal, where the lie protects the mission inside a broadly legitimate structure. By The Search for Spock, that structure is broken. They are not serving under normal command conditions. They are stealing a starship from their own institution to retrieve the soul of their dead friend from a planet that should not exist. This is not operational discretion. This is grief with a warp drive.

Scotty can still coax one last act of service from the ship, but he is no longer preserving slack. He is spending principal. The reserve is gone. The miracle consumes the thing that made the miracle possible.

The cost no longer disappears into Scotty’s estimate. It has moved into the ship itself. That is the darker version of the same management problem: when labor can no longer absorb the compression, the system starts absorbing it structurally, and everyone acts surprised when the hull finally says no.

That is the anti-nostalgia clause. Scotty’s padding is not magic. It is a technique that works under specific institutional conditions. Once those conditions collapse, the same habit becomes emergency cannibalization. The lie still works, but the ship does not survive it.

Which makes Geordi less a fool than an inheritor.

He does not create the managerialized future. He lives inside it. He is what happens after the institution keeps the demand for miracles but removes the cultural machinery that made miracles survivable. He is honest because his professional world has made honesty the visible form of accountability. He is exploitable because the same world has not made protection the visible consequence of honesty.

Then comes B’Elanna Torres, who has the good fortune to inherit neither condition cleanly and the bad fortune to inherit both as wreckage.

Voyager is engineering after institutional support has been abolished by geography. There is no spacedock. No regular supply chain. No replacement crew rotation. No sane escalation path. No adjacent Starfleet bureaucracy to blame, petition, evade, flatter, or deceive. The ship is alone. The Delta Quadrant does not care what the maintenance window says.

B’Elanna cannot fully operate like Scotty because there may be no hidden reserve to protect. She cannot fully operate like Geordi because accurate reporting into an impossible condition does not make the condition less impossible. She lives in a world where the estimate is no longer a management artifact. It is a survival negotiation.

This is why her anger matters.

Too often, B’Elanna’s temper gets treated as personality texture: half-Klingon volatility, trauma, chip on the shoulder, unresolved Maquis residue. Some of that is there. Characters are allowed to have psychologies. But structurally, her anger is also diagnostic. She is the engineer who knows the system is asking for continuity without substrate. She is expected to maintain a Starfleet standard under conditions Starfleet was never designed to survive, using whatever can be scavenged, traded, adapted, or invented before the next spatial anomaly shows up to demand plot-shaped combustion.

B’Elanna does not merely ration parts. She rations confidence. She rations risk. She rations the crew’s ability to believe that the ship will still be a ship tomorrow. That is a different relationship to slack than Scotty or Geordi had. Scotty preserved slack as craft discretion. Geordi spent it as moral obligation. B’Elanna lives after slack has become scarce enough that every decision feels like triage wearing a Starfleet badge.

Her anger is not a character flaw. It is a diagnostic signal.

Then there is Miles O’Brien.

O’Brien is the one who makes the whole analysis stop floating.

Scotty and Geordi are mythic engineers. B’Elanna, too, has a kind of tragic romance to her: the brilliant outsider keeping the lost ship alive with fury and talent. O’Brien is something else. O’Brien is maintenance.

He is not a grand theorist of warp mechanics. He is not the miracle-worker archetype in quite the same way. He is a non-commissioned officer, a working engineer, a technician with enough war behind him and enough practical knowledge in front of him to make the polished parts of Starfleet possible. He moves from the Enterprise to Deep Space Nine and spends years keeping together a Cardassian station that seems designed according to the principle that every repair should require an argument with fascist plumbing.

O’Brien does not get to be the legend of engineering. He gets to be the person who knows which conduit is lying.

This is not a demotion. It is the point.

Starfleet tells stories about exploration, command, diplomacy, and scientific wonder. But every one of those stories requires someone to keep the pressure doors working, the transporters aligned, the power grid stable, the alien station from killing everyone again, and the improvised interface between incompatible systems from turning into a religious incident. O’Brien is the human surface area of that requirement.

He is also the character who makes visible the class position usually hidden under Starfleet’s officer-romantic glow. The others manage engineering as command. O’Brien performs engineering as labor. He has authority, skill, dignity, and deep competence, but his relationship to the institution is different. He is closer to the place where consequence lands.

That is why “Hard Time” feels less like an exception than a revelation.

The episode is not about engineering. O’Brien is punished by an alien society with the memory of a twenty-year prison sentence implanted into his mind. He returns traumatized, alienated, and nearly destroyed. The plot is science fiction, but the moral accounting is familiar: the institution continues. The person who absorbed the damage is expected, eventually, to re-enter life and function. Starfleet can be compassionate. Starfleet can provide concern, care, and speeches. But the station still needs to run.

O’Brien is not just another overworked engineer. He is the proof that every elegant system eventually terminates in a person who can be spent.

He does not preserve slack. He is slack. The institution spends him whenever the polished parts of Starfleet encounter something that still has bolts.

That line is cruel. It is also hard to avoid.

Because O’Brien is what happens when engineering is not mythology. It is maintenance. Not the glamorous rescue, not the famous miracle, not the beautiful diagnostic display where the chief engineer reroutes power through a paragraph of invented physics. Maintenance is the repeated encounter with a system’s refusal to stay fixed. Maintenance is knowing that success often looks like nothing happening. Maintenance is preventing disaster so effectively that the institution forgets disaster was ever possible.

That is why maintenance cultures are so vulnerable to extraction. Their best work disappears. Their failures become visible. Their slack gets treated as inefficiency because, when they are doing their jobs well, the thing they protect against does not happen.

Scotty’s padding made that invisible work slightly more visible inside command ritual. Geordi’s transparency made it legible but less protected. B’Elanna’s scarcity made it existential. O’Brien’s life shows what happens when the institution simply assumes someone will be there to absorb the incompatibility.

This is the labor history hiding inside Starfleet engineering.

It is tempting to frame the whole thing as a decline narrative. Scotty had craft knowledge. Geordi had process. B’Elanna had crisis. O’Brien had trauma. That is not wrong, exactly, but it is too tidy. Star Trek is rarely clean enough to support a straight line, and real labor history is worse.

The better reading is that each engineer reveals a different relationship between truth, slack, and authority.

Scotty lies because truth without protection is dangerous. Geordi tells the truth because his institution has made transparency the visible form of professionalism. B’Elanna distrusts both lie and truth because scarcity has made the distinction secondary to survival. O’Brien shows that behind every theory of engineering management is someone whose body, time, memory, and family become the final buffer.

The argument is not that engineers should lie. The argument is that institutions should ask why experienced people feel the need to.

Padding estimates is often treated as a moral failure: laziness, dishonesty, sandbagging, lack of accountability. Sometimes it is. People can abuse slack. Teams can hide incompetence behind complexity. Craft discretion can curdle into guild protection. Scotty’s method depends on a cultural pact, and cultural pacts can rot.

But the managerial alternative is not automatically honesty. It is often just forced exposure. Demand accurate estimates from people who lack the power to make those estimates binding, and you have not created accountability. You have created a better instrument for assigning blame.

Truth needs standing. It needs consequence. It needs some mechanism by which saying “this will take six hours” actually protects the six hours, or at least forces the person demanding two to own the risk of compression. Without that, transparency is not integrity. It is surveillance with nicer stationery.

This is where the “Relics” joke stops being a joke.

Scotty hears that Geordi gave the captain the real estimate and recognizes the danger immediately. Not because Geordi is foolish, and not because Scotty is morally superior, but because Scotty comes from a working culture where the estimate is part of a negotiation with power. Geordi comes from one where the estimate has become an input to management.

One treats uncertainty as something to be governed.

The other treats uncertainty as something to be reported and then overcome by sufficiently excellent people.

Anyone who has worked inside a modern technical organization knows which one wins on paper. The visible board. The sprint commitment. The cheerful fiction that if everyone tells the truth into the machine, the machine will respond with wisdom instead of appetite.

Sometimes it does. More often, it eats the slack and congratulates itself on improved throughput.

That is the part Star Trek gets right by accident. The future did not eliminate labor politics. It changed the vocabulary. It replaced the smoky engine room with a carpeted conference room and called the result maturity.

But matter still resists. Ships still break. Deadlines still compress. Captains still ask for miracles. And somewhere, under the utopian lighting, an engineer still has to decide whether the truth will protect the work or feed it to command.

Scotty’s lie worked because everyone understood what the lie protected. Geordi’s truth failed because the institution treated truth as commitment. B’Elanna survived after commitment became absurd. O’Brien reminds us that every clean system diagram ends somewhere inside a wall, where a tired person is holding two incompatible pieces together and being told the schedule is still real.