Years ago I read a productivity post I can't find anymore. Something about "dealing with inefficient people." The argument was clean: some people get things done, some don't, here's how to manage the ones who don't. Stay detached, apply a little pressure, route around the blockers.
I liked it at the time. When you're buried under someone else's missed deadlines, being told "stop making it personal and just get the outcome" feels like practical wisdom.
But I've since managed teams, been managed, and made enough of my own messes that the framework started to feel incomplete. Not wrong, exactly. Just covering maybe 60% of the picture.
The binary doesn't hold
The original framing splits the world cleanly: efficient people on one side, inefficient people on the other. That's satisfying when you're frustrated. It doesn't survive contact with actual coworkers.
The person who takes three days to reply to your Slack might be doing the only work that actually matters this quarter. The person who responds instantly to everything is sometimes doing it because they can't prioritize — it's easier to look busy than to choose.
Efficiency isn't a trait. It's contextual. Someone looks "inefficient" when their constraints, priorities, or incentives don't match yours. And you usually can't see those from the outside.
Which means: "this person is inefficient" is a conclusion. "This process keeps producing bad outcomes" is a starting point.
Indifference works until it doesn't
The emotional detachment advice is genuinely good. Don't make it personal. Protect your energy. I still think it's the right first instinct when something's blocked.
The problem is it stops there. If your only move is routing around someone, you've accepted a permanent drag. You've built a workaround you'll maintain indefinitely, and you haven't fixed anything.
The more effective move is curiosity — not the confrontational kind, just "help me understand what's blocking this." Most of the time you'll find out they're waiting on someone else, or nobody told them it was urgent, or there are five other things on their plate that their manager considers higher priority than your request. The issue dissolves.
That five-minute conversation usually gets you further than any amount of pressure.
Pressure works once
Social pressure — asking uncomfortable questions in public, going over someone's head, making them feel accountable in front of peers — works in the short term. People comply when they feel exposed.
But they remember. Someone who felt pressured will do that specific thing and then avoid you. You've won a task and traded away the relationship. Over a year, that math rarely works out.
People who feel supported want to help. People who feel judged do the minimum to make you go away.
The part nobody writes about
What if you're the slow one?
If you've ever insisted on a process that someone else found pointless, you were the inefficiency in their day. If you've created a form, a checklist, a review step, or an approval flow that slowed someone down — even for a good reason — you were their red tape.
This doesn't mean those processes are wrong. Efficiency is relative to goals, and different people in the same org often have legitimately different goals. The finance sign-off process feels like an obstacle until you're the one explaining how $80k got spent without authorization. The legal review delaying your launch isn't someone being slow; it's someone managing a risk you haven't thought about yet.
Dismissing other people's processes as "artificial constructs" assumes you have the full picture. You usually don't.
It's almost always the system
Most "inefficient people" are just people inside broken systems.
Bad handoffs. Unclear ownership. Deadlines that were implied but never stated. Goals that got set in a doc nobody reads anymore. Communication split across six tools where context dies in transit.
Fix those and most of the people you were frustrated with start performing fine.
Think about the last time someone gave you a slow response. Did you tell them when you needed it? Did they know it was on the critical path? In a lot of cases, what looked like a people problem was a context problem — and the system made it easy to drop the ball.
The boring structural stuff matters more than it feels like it should: who owns what, what does "done" actually mean, how does information move by default. Get that right and you spend a lot less time being frustrated.
Let things fail sometimes
Sometimes the right call is letting someone fail.
Not out of cruelty — out of the recognition that if you always step in, always provide the answer, always catch the project before it hits the ground, you've made yourself the load-bearing wall. People around you never develop their own instincts because they've never had to. They've just watched you handle it.
Letting someone experience the consequence of a flawed approach, when the stakes are low enough, teaches things that feedback can't. Real judgment comes from living with a bad decision, not from being told about one.
The key is doing it on purpose. You're not abandoning people; you're giving them room to figure something out for themselves.
If there's a version of the original framework I'd actually use now, it's not "some people are efficient and some aren't." It's closer to: something here isn't working, figure out why before you figure out who.
Most of the time, the problem isn't the person.