The Scotty Factor: Practice the workplace you want to lead
Starting with the one you’re in
Scotty understands that keeping the Enterprise running is only part of his job. He also has to manage the expectations of the man in the captain’s chair.
In Star Trek III: The Search for Spock (1984), Kirk asks his chief engineer how long the refit will take. “Eight weeks, sir,” Scotty says, and then, before Kirk can open his mouth, “but ya don’t have eight weeks, so I’ll do it for ya in two.” Kirk pauses. “Mr. Scott, have you always multiplied your repair estimates by a factor of four?” And Scotty, without a flicker of shame: “Certainly, sir. How else can I keep my reputation as a miracle worker?”
It’s a wonderfully humorous exchange, but it tells us quite a bit about working aboard the Enterprise. Kirk expects the impossible. Scotty has learned to leave himself room to deliver it. Somewhere along the way, the miracle became part of the job description. Scotty's padding is not vanity. It is a structural buffer, built by hand, because the organization won't build one.
Eight years later, The Next Generation put a fine point on it. In the episode "Relics," a rescued and disoriented Scotty watches Geordi La Forge tell Captain Picard that an analysis will take an hour. Scotty pulls him aside. "Do you mind a little advice? Starfleet captains are like children. They want everything right away and they want it their way. But the secret is to give them only what they need, not what they want." How long will it really take? An hour, Geordi says. Scotty is scandalized. "Oh, laddie, you have a lot to learn if you want people to think of you as a miracle worker."
Two engineers, two operating systems. Geordi can give honest estimates because Picard treats an honest estimate as information rather than an opening bid. The difference between Kirk and Picard was never the engineer. It was the captain, and the culture the captain built.
Which leaves a question the show never asks: what happens to the engineer who gives the honest estimate in Kirk's engine room?
Taking my questions about workplace expectations directly to Engineering. AI-generated illustration depicting me with Star Trek’s Scotty and Geordi La Forge, accompanying commentary on their approaches to work. Created with ChatGPT; concept and art direction by Susan Marie / Scenescape Media. Unofficial; not endorsed by the rights holders.
The third engineer
I admire a good engineering miracle. I’m less enthusiastic about building a workplace that requires one every Tuesday. This dynamic requires a third engineer, the one who isn't on screen. They give the honest estimate. They get overruled. And then They quietly make it work anyway, at night, on the weekend, in the hours the organization never asked about and never paid for. They perform the miracle without the padding that protected Scotty, and get the same reward he did: the deadline is met, the metrics turn green, and next time the ask is a little bigger.
I know this engineer well, because I have spent much of my working life being her. If someday I were to lead a workplace, I’d like to think strategic priorities, systems, and processes would allow competent people to finish their work inside the allotted number of hours. I have, however, noticed that I don’t consistently practicing that in the workplace. That contradiction bothers me, and I suspect I am not the only one living inside it.
Here is the uncomfortable part. The habits that make you the person everyone relies on are also the habits that keep a broken system from ever being fixed. Your conscientiousness is a shock absorber. It keeps leadership from feeling the impact of its own capacity planning.
The forty-hour test
Forty hours is an odd number to treat as sacred. It is a hundred-year-old industrial compromise. Ford Motor Company moved its factory workers to a five-day, forty-hour week in 1926 because Henry Ford believed shorter hours were good business. The Fair Labor Standards Act began phasing in a national standard in 1938, starting at forty-four hours and reaching forty by 1940. Nobody arrived at forty by studying knowledge workers with laptops.
And yet the number has held up better than the people who ignore it. The Stanford economist John Pencavel went back to the wage sheets of British munitions workers in the First World War, most of them women. They had been studied obsessively because the government needed shells and wanted to know how hard it could push. Below about 49 hours a week, output rose roughly in proportion to hours. Above that, the returns shrank, and by 70 hours the workers produced about what they had at 56. The extra fourteen hours bought nothing except exhaustion and accidents. This was assembly-line work with a physical product you could count. There is no reason to think writing, analysis, teaching, or management holds up better under the same strain, and every reason to think it makes things worse.
So consider forty hours not as an aspiration you abandon the moment things get hard, but as a design constraint. A budget. If the work does not fit inside it, something has to be postponed, simplified, delegated, automated, or stopped. That forces a set of questions most of us avoid: What work matters, and what am I doing merely because I am conscientious? Which expectations are real, and which have I imposed on myself? And the one that matters most for anyone who hopes to lead: what would I stop asking of a team if I had to justify every hour it consumed?
Call it the forty-hour leadership test. If competent people routinely need nights and weekends to succeed, the system is borrowing from their private lives to conceal a capacity problem. The test applies to organizations. It also applies, uncomfortably, to the way you run your own desk.
How conscientious people stabilize broken systems
This is not just a personal quirk. Researchers, naturally, have a more respectable name for part of it: “individual initiative”, a form of organizational citizenship behavior. In 2005, the management researchers Mark Bolino and William Turnley surveyed 98 working couples and asked each partner to rate the other's initiative: arriving early, taking on extra work, volunteering for the thing nobody else wants. The people whose partners rated them highest reported more role overload, more job stress, and more conflict between work and family. The link between initiative and work-family conflict was stronger for women. Later research gave us another useful phrase, “citizenship pressure”: the felt obligation to go the extra mile because everyone around you is going it too — until the extra mile becomes the baseline and a new extra mile appears beyond it.
Anyone who has worked in an office can fill in the mechanics, and the condition is easy to dissect into three moving parts:
The first is the compassion trap. You absorb extra work to protect a supervisor, a colleague, a student, a client. The work gets done. Leadership, seeing only the result, concludes that current staffing and process are perfectly adequate. Your kindness has just become evidence against the people you were trying to help.
The second is the subsidy. Every unpaid hour, every piece of emotional labor spent smoothing over a gap in the process, is free capacity donated to the organization. The true cost of the work never appears on any ledger, so no one ever budgets for it.
The third is delayed failure. Systems often get fixed only when the strain becomes visible. By preventing a dozen small, survivable failures this year, you may be arranging a larger one later. A resignation, a collapse, a burnout that takes one of your colleagues with it. A system can look healthy right up until the day its shock absorber walks out the door.
So the sharper question is not "Can I get all of this done?" It is "What organizational truth would my overfunctioning conceal?"
Rehearsing the workplace you don't have yet
It would be convenient to file all of this under Future Susan's Problems: something to fix when I have a team, a title, and perhaps an office with a door, possibly a window. Unfortunately, Future Susan will arrive carrying the habits Present Susan practices now. The way I manage my own work is already a rehearsal for the workplace I may someday be creating for others. If my current habits became the culture of an entire team, would I want to work there?
That is why I have stopped thinking of boundaries only as self-care. They are also operational discipline. Nobody hands you a team and says, "Now be humane." You arrive with whatever habits you have been practicing, and those habits become the standard, whether or not you ever announce them. These are some of the rehearsals I am trying to run now:
Learn the difference between a season and a system. Work does move in seasons. Budget cycles, launches, academic terms, emergencies. Humane leadership doesn't pretend every week is identical. But "it's just a busy season" is one of the workplace's most respectable lies. A true season has a beginning and an end, a reason, specific priorities, and lessons learned. If the work never eases, it is not a season. It is the operating model.
Make the tradeoff visible. When new work arrives, I am learning to say the sentence out loud: "I can move this forward. Here is what I'm currently committed to. Which item should shift?" That is not resistance. It is capacity planning. Leaders who won't acknowledge tradeoffs don't eliminate them; they force employees to make them privately, usually by sacrificing quality, health, or their evenings and weekends.
Keep some slack, and stop apologizing for it. The software consultant Tom DeMarco wrote a whole book in 2001 arguing that the pursuit of total efficiency makes organizations brittle. A team scheduled to the edge of endurance has no room for the emergency, the mentoring conversation, the idea that arrives sideways, or the mistake that needs unwinding. The first surprise breaks it, and the workplace then depends on somebody becoming heroic again. Slack is not waste. It is the margin that makes the next miracle unnecessary.
Make meetings move the work. A meeting should produce something a shorter message could not: a decision, a resolved conflict, coordination of work that is truly interdependent, something that must be made together. Before calling a meeting, ask what decision must exist when it ends, who truly needs to be there, and whether the meeting is compensating for ownership nobody has assigned. If every recurring meeting had to periodically justify its continued existence, most would fail.
Remember that power changes the meaning of a message. Technology has made it possible to reach people continually. An "optional, no rush" evening email is not optional to someone whose performance you evaluate. Delay the nonurgent message. Distinguish urgency from enthusiasm. Create fewer channels that have to be monitored, and make decisions easy to find so nobody has to chase them later.
Cut the fat, not the human. Efficiency becomes its own kind of waste when it removes judgment, relationships, dignity, or the time it takes to think. Good streamlining removes duplication, unnecessary approvals, repeated data entry, ambiguous handoffs, status theater, and preventable chasing. It preserves conversation, learning, care, and the ability to respond intelligently when reality declines to follow the procedure.
Define "enough" before ambition defines it for you. Without an explicit definition of done, a capable person can always improve the document, refine the system, answer one more message. Excellence quietly becomes endlessness. Ask what quality this work actually requires, when refinement stops producing value, and whether you are improving the outcome or soothing your anxiety by continuing to work. As a compulsive optimizer, I can report that sometimes the disciplined choice is to stop optimizing.
Protect people from your own strengths. This is the one that makes me squirm. My CliftonStrengths results include Achiever and Responsibility, which helps explain why getting things done feels satisfying and leaving something unfinished can feel very uncomfortable. Those tendencies can be useful. They can also make it difficult to recognize when I’m doing too much, or quietly making too much look reasonable. Sometimes what I call a high standard is simply a habit I haven’t questioned. Whatever drives us, our ways of working can become expectations other people feel obliged to meet. The question to sit with is: if everyone worked the way I work under pressure, what kind of workplace would we have built? That shifts the standard from “Can I sustain this?” to “Should this become normal?”
Practice recovery without making people earn it. Rest is usually treated as the reward for finishing everything, which guarantees that conscientious people never get it, since the work is never finished. A healthier model treats recovery as part of the work cycle. Leaders shouldn't merely permit vacations and boundaries; they should build workflows that don't punish people for using them. For me, that means learning to leave unfinished work at work without reading it as negligence. There will always be more work. Leadership requires knowing what may safely remain undone.
From shielding to highlighting
None of this means you stop caring about the people around you. It means changing how you protect them: from individual heroism to systemic transparency.
Let the system feel the friction. When a deadline is unrealistic, name the bottleneck and negotiate the scope, resources, priorities, or date instead of quietly eating the difference. Do not disguise where the process is broken. When you do have to step in and save something, expose the cost: "We met the deadline, but it took twenty hours of overtime, which is not sustainable for the next cycle." And aim your empathy at people rather than processes. Validate a colleague's frustration and stand with them as they push back on an unreasonable demand, but stop acting as the solo buffer that makes the demand look reasonable.
Start small. Pick a low-stakes boundary and see how the system reacts when you don't cushion it. Write yourself a script for communicating capacity problems that doesn't sound like refusal. Make a list of the gaps you are currently bridging and mark the ones that drain you most. It takes a surprising amount of courage to stop fixing things, especially when fixing them is what earned you your reputation as a ‘miracle worker’.
What practice cannot do
Personal practice has limits, and pretending otherwise would turn this into the kind of advice I distrust. No boundary solves chronic understaffing. No calendar discipline repairs unclear authority or mistaking wishes for plans. One person cannot compensate for every institutional dysfunction, and the attempt is a fast track to burnout.
But that limit doesn't weaken the premise. It sharpens it. I may not control the structure, but I can stop training myself to reproduce it.
That is the line between this and ordinary productivity advice. The goal here is not to squeeze more work out of ourselves. It is to examine the habits, assumptions, and small daily exercises of power that eventually harden into a workplace culture, and to decide, while the stakes are still our own, which of them we would be willing to impose on someone else.
Kirk, remember, was delighted with Scotty's answer. "Your reputation is secure," he said, and went back to the bridge. He never asked why his chief engineer needed the padding in the first place, or what the ship would have looked like if its engineers had been allowed to tell the truth. Nobody ever fixed the maintenance schedule on the Enterprise. They just kept a miracle worker on staff.
Someday I may be in a position to shape workloads, meetings, priorities, and expectations for other people. But the workplace I want to lead cannot begin someday. It begins here: in what I accept, what I question, what I stop doing, and the hour at which I finally close the laptop and go home.
