Latest
What You Have to Decide Before Anybody WritesWriting It Before You Need ItCross Training Covered Everything Except the Role That Mattered MostBehind the Book: You Don’t Own Anything AnymoreBehind the Book: The Woke VirusBehind the Book: Galactic InvasionWhat’s New at The Writing King: Week of November 8, 2026Alexander Zhidkov: Decision MakingJessi Szurek: Expand Your RangeYou Don’t Own Anything AnymoreThe Budget Decided How My Department Was ShapedWhy Your Competitor’s Book Is Working and Yours Would NotWhy Are These Guys Smiling? A Business Book That Became a Wrestling MemoirPangram Wants to Decide Who Gets PublishedWhat You Have Enough Material For Right NowWhen a Book Is the Wrong ToolThe Woke VirusGalactic InvasionChatGPT Turns Four: From a Free Research Preview to GPT-6What’s New at The Writing King: Week of November 1, 2026Diwali: The Festival of Lights and the Story Behind the LampsHow Much Water and Power Does Heavy AI Use Take? I Ran My Own NumbersBad Boys: Ride or Die (2024)Vesuvius Day: The Teenager Who Wrote Down Pompeii’s Last DayAnti-Communism Week: Remembering the Writers Communism SilencedVoyager 1 One Light-Day: Fifty Years to Travel One Day of LightVellum Added an Optional AI Feature. A Pile-On Killed It in a Day.Are AI Subscriptions Losing Money? The Gym Membership Math Says NoAI Terms Every Writer Should Know, and Why Each One MattersWorking While Sick: What 24/7 On Call Cost MeHe Banned AI From His Writing Group. His Own Cover Got Called AI Slop.Who Writes the Fake Fan Mail Authors Get? Inside the Scam CompoundsSMS Appointment RemindersJoe Rockey: Ghostwriting His BookDarrell Stern: Stop Being Invisible, Become UnmissableFree BooksHow to Turn Your Expertise Into a Book People Want to Read | The Expert MethodWhat’s New at The Writing King: Week of October 25, 2026Challenger Remembrance Day: The Engineer Who Wouldn’t SignJoel Salomon: The Truth About MoneyReddit Is Putting Up a Login Wall. Wikipedia Won’t Be Far Behind.Victoria Chemko: The Body Is the First TechnologySir Patrick Stewart: A TributeA Year in the Bank: ADHD, Face Blindness and the Freedom to Walk Out | The Impossible Puzzles Show, Episode 326A Yale Economist Says We Won’t Be Missed. He Forgot the Bread Line.Walter Koenig: A TributeAI Has Paid Off Outside Tech. Apollo Is Reading the Wrong Scoreboard.I Don’t Post Bad ARC Reviews. I Send the Author a Note.The Little Red Book of Stuff That Works!Your Kids Are Your Own Fault
The Writing King Your Ethical Ghostwriter. Your Story, Done Right.

I Became a Manager in 1981. The Hard Part Was People Sitting Ten Feet Away.

TL;DR: I became a manager in 1981, when delegating to somebody ten feet away was the hard part. After nearly two decades running technical operations at Trader Joe’s, the mechanics have changed completely and the underlying job has not. The managers who succeed are the ones who decide well with incomplete information and build capacity and not output.

I became a manager in 1981. The biggest challenge, at the time, was delegating work to people who sat ten feet away.

That sounds trivial now. It wasn’t. Handing something to a person you can see, then watching them do it slower and differently than you would have, is the hardest thing a new manager has to learn, and proximity makes it worse instead of better. You can see every choice they make. The temptation to lean over and take it back is constant.

Nearly two decades later I was running technical operations at Trader Joe’s, in a company that prided itself on moving fast. The mechanics of the job by then were unrecognizable. The thing underneath hadn’t moved at all.

What has changed about management?

Nearly all of the practical apparatus.

Your best developer is in another country. Your newest hire expects a say in significant decisions inside their first month. Two people who have never met in person, who communicate through a chat channel, can develop the kind of mutual resentment that needs a mediator and a conversation most managers have no idea how to have.

None of those situations existed in 1981 and nothing I learned covers any of them. The org chart, the weekly meeting, the walk through the department that told you what kind of week everybody was having: all of it assumed you could see people.

None of those situations existed in 1981 and nothing I learned covers any of them.
Share on X

What I learned the hard way at Trader Joe’s is that the managers who succeeded were the ones who could make good decisions with incomplete information and build trust with people they didn’t see every day.

What has not changed?

The core failure, the one I made first and watched almost everybody else make since.

I made it first because nobody taught me anything else. I was promoted from programmer to supervisor of eight people, because management was the only way to make money on a raise. I had no management experience, no classes, no nothing. Later I went on to VP. Did I know what I was doing back then? Not a prayer.

A manager takes on the difficult piece themselves because they can do it faster and the deadline is real. It works. The thing ships. And the team has learned nothing, and is exactly as dependent on that manager as it was before. That’s the job being done backwards, and it feels like leadership the entire time it’s happening because the output is good.

Output versus capacity on a team
Aspect Output Capacity
Definition What got delivered this quarter What the team could deliver next quarter without you
Visibility Visible, so reviews can look excellent Not visible, so it gets confused with output
How it gets made Manager takes the difficult piece because they’re faster Let them do it worse than you would
Week-off test Everything waits for you Work moves without you
The team afterward Learned nothing and stays dependent on the manager Improves, and the manager can take a holiday

What is the difference between output and capacity?

Output is what got delivered this quarter. Capacity is what the team could deliver next quarter without you in the room.

A manager takes on the difficult piece themselves because they can do it faster and the deadline is real.

These get confused constantly, because output is visible and capacity isn’t. You can run a team at high output for a year while building no capacity whatsoever, and every review will be excellent, and the team will fall over the first time you’re unavailable.

The test is simple and uncomfortable. Take a week off and see what happens. If everything waits for you, you’ve been producing output. If it moves without you, you’ve built something. I’ve been on the wrong side of that test. It’s not a pleasant discovery and it’s considerably better to have it while you’re still there to fix it.

Why does a book of principles not help?

Why a book of management principles does not helpNobody has a management problem in the abstract. There is a specific person, on a specific Tuesday, who has done something unexpected, and about four minutes to decide what to do. Principles are easy to agree with in an armchair and useless at that moment, because the difficulty was never understanding the principle. It was recognising which one applies while somebody is waiting for you to speak. That is why the book was written as three managers going through situations instead of as a list of lessons: you watch somebody make the decision badly and see what it cost, which sticks in a way a principle does not, and it means the next time the situation arrives you have seen it before.Why the principle does not help on TuesdayThe difficulty was never understanding it. It was recognising which one applies.1The principle is soundEasy to agree with in an armchair2The situation arrivesA specific person. A specific Tuesday.Something you did not expect.3You have four minutesAnd somebody is waiting for you to speak4Recognition is the hard partWhich principle applies here,and you have never seen this beforeWatching somebody make the decision badly, and seeing what it cost, sticks where a principledoes not.
Why a book of management principles does not helpNobody has a management problem in the abstract. There is a specific person, on a specific Tuesday, who has done something unexpected, and about four minutes to decide what to do. Principles are easy to agree with in an armchair and useless at that moment, because the difficulty was never understanding the principle. It was recognising which one applies while somebody is waiting for you to speak. That is why the book was written as three managers going through situations instead of as a list of lessons: you watch somebody make the decision badly and see what it cost, which sticks in a way a principle does not, and it means the next time the situation arrives you have seen it before.Why the principle does nothelp on TuesdayThe difficulty was never understanding it. It wasrecognising which one applies.1The principle is soundEasy to agree with in an armchair2The situation arrivesA specific person. A specific Tuesday.Something you did not expect.3You have four minutesAnd somebody is waiting for you to speak4Recognition is the hard partWhich principle applies here,and you have never seen this beforeWatching somebody make the decision badly, andseeing what it cost, sticks where a principle doesnot.

Because nobody has a management problem in the abstract.

You have a specific person, on a specific Tuesday, who has done something you didn’t expect, and you have about four minutes to decide what to do. Principles are easy to agree with in an armchair and useless at that moment, because the difficulty was always recognizing which one applies while somebody is waiting for you to speak.

That’s why I wrote the book as three managers going through the situations instead of as a list of lessons. You watch somebody make the decision, badly, and see what it cost. That sticks in a way a principle doesn’t, and it means the next time the situation arrives you’ve seen it before.

The book on this: Street-Smart Management Wisdom follows three managers through the situations you’re living, in 14 chapters, so you can watch somebody else make the mistake first.

My take

Take a week off and find out what kind of manager you are. If everything waits for you, you’ve been producing output, and the team will fall over the first time you’re gone. Build capacity instead, even when output earns you better reviews. Stop taking the difficult piece yourself because you’re faster. Principles won’t save you on a Tuesday with four minutes to decide, so learn from watching somebody else get it wrong.

What is the hardest part of becoming a manager?

Let them do it worse than you would. That’s the job. The alternative is a team that never improves and a manager who never gets a holiday.

Test for capacity. Take a week off and watch what happens.

Build trust deliberately, because it no longer accumulates on its own. Proximity used to do this for free. It doesn’t any more.

Decide with incomplete information. You’ll never have the full picture, and waiting for it is itself a decision, usually a worse one.

Handle the small resentments early. Two people who can’t see each other’s faces will assume the worst about tone, and it builds until it needs a mediator.

Forty-five years since I first had to hand work to somebody ten feet away, and I still think that was the correct thing to find difficult. Everything else in management is a variation on it.

From the author
Street-Smart Management Wisdom by Richard Lowe

Street-Smart Management Wisdom
Management books rarely change how anyone manages. Street-Smart Management Wisdom makes you the hero, with three managers who face what you’re about to face across fourteen chapters.

Frequently Asked Questions

What is the hardest part of becoming a manager?
Letting somebody else do the work worse than you would, on purpose, because that’s how they get better. Every new manager knows this intellectually and almost none of them can do it in the first year.
What is the difference between output and capacity?
Output is what got delivered. Capacity is what the team can do next time without you. A manager can produce excellent output for months while building no capacity at all, and the sign is that nothing runs when they’re away.
Has remote work changed the fundamentals of management?
It’s changed everything about the mechanics and nothing about the substance. You can no longer read a room by walking through it, so trust and clarity have to be built deliberately instead of accumulating by proximity.
Why does soloing a project hurt the team?
Because the team learns nothing and remains exactly as dependent on you as before. It feels like leadership because the work got done, and it’s the most common way capable managers become bottlenecks.
Do new managers need a management book?
They need something that shows the situations instead of lists the principles. Principles are easy to agree with and impossible to apply at the moment you need them, so the useful books put you inside the decision.

About the Author
Richard Lowe, professional ghostwriter

Richard Lowe is a professional ghostwriter and author with 113+ books authored and 54+ ghostwritten. Before writing full time he spent 33 years in enterprise technology, including 20 years as Director of Computer Operations and Technical Services at Trader Joe's. He writes nonfiction, fiction and memoir, and works with executives and experts on books that build authority.

More about Richard Lowe →

Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.

0 comments

No comments yet. Yours can be the first.

Was this useful?

Leave a comment