Bad Process Kills Good People

On a factory floor, you knew whether you'd had a good day. The parts moved down the line or they didn't. You assembled ten cars or you assembled six. The work was right in front of you, and so was the verdict.

Knowledge work took that away and never replaced it with anything.

We spend our days moving information into and out of computers, surrounded by a constant, low-grade question: what am I actually supposed to be doing, and how would I know if I'd done enough? No little reel pops up at 4 p.m. to confirm you hit "good enough." There's just more. More email, more tickets, more pings, more knocking at the door asking how you're using AI today. One-piece flow — the idea Toyota and Deming built modern manufacturing on, where a single unit moves cleanly through the line — has no real equivalent here. Knowledge work isn't one-piece flow. It's many-piece stress.

That's worth sitting with, because the systems we work in are not neutral. They carry judgment. And that judgment, more than the raw volume of the work, is what quietly wears good people down.

The factory floor at least knew what a good day looked like

The old assembly line was brutal in a lot of ways, but it was legible. Each person applied their piece, the line advanced, and by the end of the shift the output was countable. Just as important: the waste was countable too. A jammed machine, a pile of defective parts, a bottleneck — you could see it. It was sitting right there on the floor.

Knowledge work hid all of that. You can't see a stalled decision. You can't point to the meeting that should have been an email, or the email that should have been a meeting. And because the work is invisible, so is the slack. Someone can mail it in for a day, a week, sometimes a whole quarter, and nothing on the surface changes. There's no pile of defective parts. There's just a vague sense that things are harder than they should be, and no obvious place to point.

So instead of measuring the work, we started measuring the people. Management sets up reporting based on throughput — status columns, dashboards, activity logs — because throughput is the one thing that looks like the factory floor. But throughput in knowledge work often measures motion, not progress. And now you're inside a system that's forming an opinion about you based on numbers that may have nothing to do with whether the actual work is getting done.

Email is a judgment machine

Cal Newport has a book called A World Without Email, and the core insight is that email isn't just a tool we use badly — it's a system that produces a particular kind of stress by design. It matches how a small tribe communicates: shout the information out, get it off your plate, let someone else catch it. That works great around a campfire. It scales into a nightmare.

Because underneath most email is a quiet transfer of stress. "You don't have all the information — please send me the following." Now the pressure lives on someone else's desk, and you've felt productive without actually moving the work forward. Nobody has ever looked at their inbox and thought, if only I had more emails to handle today. The volume itself renders a verdict. Five hundred unread messages doesn't feel like a queue. It feels like an accusation.

That's the tell. The system isn't neutral about your day. It's judging it.

Bad process kills good people

Here's the phrase that stuck with us: bad process kills good people.

The trouble is that when you're inside a bad process, you rarely suspect the process. It's human nature — unless you're a masochist — to reach for "I must be doing something wrong" before "the system I'm standing in is broken." So the ops person stays late, blames themselves, and grinds harder against machinery that was never going to cooperate.

But at some point the evidence tips over. When the last four people in your seat got fired, downsized, or quietly burned out, it stops being a human problem and becomes a process problem. The role isn't failing because of who's in it. It's failing because of what surrounds it.

You can see the same logic play out at the organizational scale, where layoffs have become the single most reflexively pulled lever for managing performance. .

Judgment is where creativity goes to die

The deeper cost of a judgmental system is what it does to your ability to fix anything.

On a manufacturing line, if you get punished for surfacing waste, you learn to hide waste. You make excuses for it, you route around it, you stop pointing at it. In knowledge work that instinct is even stronger, because the waste was invisible to begin with — it costs you nothing to keep it buried.

And a system that judges you produces one of two responses, neither of them useful. You shrink — your confidence contracts, and you start operating from a defensive crouch. Or you inflate — you get grandiose and combative, armoring every decision with layers of frustration. Martin Seligman called the first one learned helplessness: keep punishing effort and people simply stop trying to improve their situation. Neither the shrinking nor the puffing up leaves any room for the thing you actually need, which is the calm, curious headspace where someone looks at a broken process and thinks, I could fix that.

You cannot redesign a system while it's busy rendering a verdict on you. The judgment has to come off the table first.

"I have 500 emails" is a sentence you can live with

Which points at the way out, and it's smaller than you'd expect.

There's a real difference between these two sentences:

I got 500 unread emails.

I have 500 emails.

The first is a judgment. It carries defeat, self-recrimination, the whole learned-helplessness spiral. The second is an observation. It's just a fact about the current state of a queue. Same inbox, completely different relationship to it. One leads to shutting down. The other leaves the door open to why is this like this, and can I change the system so it stops demoralizing me?

This is borrowed from mindfulness, but there's nothing mystical about it. It's the discipline of separating what's true from how you feel about what's true — of meeting the workload as information instead of as a scoreboard. The work is the same either way. The judgment is optional, and the judgment is the part that's actually hurting you.

What that looks like on a Tuesday

None of this means quitting your job to hand-assemble furniture in a barn. It means a few small, unglamorous moves that lower the judgmental load enough to think straight.

Add friction to the systems that grab you. You can't announce that you'll only check email at 10 and 4 — you'll get run over. But you can quietly make the app harder to fall into, answer on your own cadence, and here's the non-negotiable part: don't drop anything. Capture every request, from your boss and your boss's boss on down, and keep delivering. When you're less distracted, throughput usually goes up, not down. The friction buys you the room; the reliability keeps you safe inside it.

Get up and move. If you work from home, the walk to a meeting room that used to space out your day is gone, and nothing replaced it. Put it back on purpose. It's not a productivity hack. It's a way to step outside the system long enough to stop being judged by it.

And underneath all of it, own the work without narrating it as a referendum on you. Ambiguity is going up, not down — more tools, more interruptions, more AI, more open questions about what good enough even means. That's not going to resolve itself. The one thing you can control is whether you meet it as an observation or as a verdict.

Chop wood, carry water. Do the work. You don't have to grade yourself on every log.