People don’t quit companies. That line gets repeated so often it has lost most of its meaning, but the reason it stuck is that it’s mostly true. Someone takes a job because of the company. They stay or leave because of the person they report to.
I managed people for a long time, starting in my twenties and eventually at the executive level. I don’t manage anyone now, and I’m not looking to. I’ve done it, I learned what I was going to learn from it, and the title never meant much to me anyway. These days I’m the one doing the work and reporting to someone else.
That turns out to be a useful place to write from. I know what I expected of myself when people reported to me. I also know what it feels like when the person you report to doesn’t hold up their end. Most management writing comes from one side of that desk. I’ve sat on both.
The five things a manager owes every employee
When I managed people, I came to a fairly simple conclusion about what the job actually was. It wasn’t to be liked. It wasn’t to be the smartest person in the room. It was to make sure the people who worked for me could succeed at what I’d asked them to do.
That broke down into five responsibilities. If I failed at any of them, the failure was mine before it was the employee’s. Now that I’m on the other side, they’re the same five things I look for in whoever I report to.
1. The tools to do the assignment.
This sounds obvious until you look at how often it’s ignored. A developer asked to ship faster while working on a five-year-old laptop and a staging server that goes down twice a week is not being managed. They’re being set up. If someone doesn’t have what they need to do the work, nothing else on this list matters.
2. The training, knowledge and reasonable time to complete it.
Hiring a capable person doesn’t mean hiring a person who already knows your systems, your customers, and the unwritten rules of your organization. Competence transfers. Context doesn’t. If a manager hands someone an assignment they’ve never been shown how to do and they get it wrong, the manager didn’t discover a weak employee. They discovered a gap they should have closed.
3. Clear and precise direction.
Most bad work I’ve seen, from either side, traces back to a vague request. “Make the site better.” “Get the campaign out.” “Clean this up.” The employee fills in the blanks, guesses wrong, and then hears about it. If a manager can’t explain what “done correctly” looks like, they haven’t finished thinking about the assignment yet, and they shouldn’t hand it off.
4. Measurable goals the employee understands.
Not just goals the manager understands. Goals the employee understands. There’s a difference between someone who has been told the target and someone who knows how their work moves it. The second one can make decisions on their own. The first one has to keep asking.
5. Everyone working toward that goal, as a team.
If one person is measured on speed and another on quality and neither knows what the other is being asked for, you don’t have a team. You have two people who are going to end up frustrated with each other over something management created. Alignment is a management job. It doesn’t happen on its own.
One more rule: self-relieving stress
There was a sixth thing I held myself to, and it’s the one I’ve rarely seen written down anywhere.
I never gave an employee an assignment they couldn’t relieve by action.
Every assignment carries stress. That’s not a problem; some pressure is what gets work done. The problem is stress an employee can’t do anything about. If someone is being held responsible for a deadline that depends on a vendor they can’t call, a decision that’s sitting on someone else’s desk, or a number that moves for reasons outside their job, then they’re carrying a weight with no way to set it down. Nothing they do on Monday makes Tuesday better.
I called the alternative self-relieving stress. The assignment should be built so that the pressure goes away when the work gets done. If they can’t make it go away by working, the assignment is wrong, or it belongs to someone else, or it belongs to me.
This is the manager’s version of a question every employee already knows how to ask: is what I’m being blamed for something I can actually fix? When the answer is no for long enough, you get the pattern I describe below under “Why they leave.”
The study that changed how I think about this
Years ago I read about a survey that I’ve never forgotten, and it turned out to be older than I assumed. In 1946, a researcher named Lawrence Lindahl asked employees to rank ten things they wanted from their jobs. Then he asked their supervisors to guess what the employees would say.
Employees put “full appreciation of work done” first. “Feeling in on things” was second. Good wages came in fifth.
The supervisors guessed wages would be first. They put appreciation eighth.
The study was repeated in the 1980s. The gap was still there.
I want to be careful about what this does and doesn’t say. It doesn’t say pay doesn’t matter. Pay people badly and they will leave, and they should. What it says is that once pay is reasonable, it stops being the thing that keeps someone. And it says that managers, as a group, have been wrong about this for a very long time, and wrong in a specific direction. They think people want money. People want to know that what they did was noticed.
I can confirm that from where I sit now. I’ve watched it from the manager’s chair and I feel it from the employee’s. Nothing about it changed when the title went away.
Look at the top two employee answers next to the five responsibilities above. “Feeling in on things” is what happens when someone understands the goal and knows why the assignment matters. “Appreciation of work done” is what happens when the loop gets closed on work that was done well. They aren’t separate from the five. They’re what the five feel like from the employee’s side of the desk.
Why they leave
Here is the pattern I’ve seen more times than I can count, and I’ve seen it from both angles.
A good employee gets hired. They’re given unclear direction, so they guess. They guess wrong a few times and get corrected. They guess right most of the time and nobody says anything, because that’s just the job. Eventually every conversation with their manager is about what went wrong, and the good work becomes invisible.
They don’t quit right away. First they stop caring about the parts nobody notices. Then they stop offering ideas, because ideas invite more correction. Then they start answering recruiter emails. By the time they give notice, they’ve been gone for months.
The manager, when asked, will usually say the employee lost motivation. That’s true. What’s missing is the second half of the sentence: the employee lost motivation because the conditions for keeping it were never provided.
This is the question I used to ask before deciding someone was the problem. It’s also the question I ask now, from the other direction, before deciding I’m the problem. Is this a people problem or a system problem?
- Did they have the tools?
- Did they have the training?
- Was the direction clear, or did someone assume it was?
- Did they know what the goal was and how it was measured?
- Was anyone else pulling in a different direction?
If the answer to any of those is no, the manager has work to do before they have any business evaluating the employee.
Why they choose you
The flip side is simpler than most management writing makes it sound.
People choose to work for a manager who gives them what they need, tells them plainly what’s expected, gets out of the way, and notices when they deliver. That’s it. No motivational speeches. No culture decks.
I know this because I saw it happen. I had people from other departments ask to transfer onto my team. They weren’t chasing a raise or a title; the move usually came with neither. They’d watched how my team worked. They saw that people were treated fairly, that the team pulled in one direction instead of competing with itself, and that when someone did good work, I said so in front of their peers rather than in a hallway afterward. That was enough to make them want in.
That last part costs nothing. It’s the one thing on this entire list that requires no budget, no approval, and no process change. And according to eighty years of survey data, it’s the thing employees want most and the thing managers most consistently underestimate.
It’s also, for what it’s worth, the thing I notice most now that I’m the one being managed.
The other side of the ledger
None of this means I never let anyone go. I fired plenty of people. And when I did, I told them the same thing every time: I’m just the messenger. You fired yourself.
That wasn’t a line to soften the conversation. It was the logic of the whole arrangement. The five responsibilities cut both ways. If I’d given someone the tools, the training, clear direction, and a goal they understood, and everyone around them was working toward the same thing, then I’d held up my end. What was left was whether they chose to do the work. Some people didn’t. At that point I wasn’t making a judgment about their ability. I was confirming a decision they’d already made.
This is why I insisted on going through the list first. Not to protect the employee, and not to protect myself, but because the list is what made the outcome fair. If I’d skipped step three and fired someone for guessing wrong, that was on me. If I’d done all five and they still didn’t show up, the conversation was short and it was honest. Nobody in that room had to wonder whether it was deserved.
The managers who struggle most with firing are usually the ones who can’t answer the five questions with a straight face. The ones who can rarely lose sleep over it.
And as an employee, I hold myself to the same standard. If I’ve been given the five and I don’t deliver, that’s mine. No amount of complaining about management changes it.
The uncomfortable part
If you manage people and someone good just left, the honest exercise is to go back through the five responsibilities and grade yourself before you grade them. Most managers won’t do this. It’s much easier to decide the person wasn’t a fit.
Sometimes they weren’t. But in my experience, on both sides of the desk, that’s the exception. The rule is that a capable person was put in a position where success was harder than it needed to be, and nobody told them when they got it right.
You can fix that. It doesn’t take a raise. It doesn’t even take a title. I know, because I gave mine up and I still see the same things I saw when I had it.
Leave a Reply