Someone Has to
Pick It Up

A piece of paper lay on the floor and people stepped around it. There was nothing unusual about that. The paper wasn't dangerous, it wasn't blocking the doorway, and it didn't belong to anyone passing through. Eventually somebody bent down, picked it up, and dropped it into a trash can. The entire event probably lasted less than a minute, and everyone who walked past it had a perfectly reasonable explanation for doing so.

It wasn't their paper. It wasn't their job. Someone was paid to clean the building. All of that was true, and someone still had to pick it up.

There is a category of problems that survives largely because responsibility is unclear. Organizations know this well. When something belongs to a particular person, it usually gets handled. When it belongs vaguely to everyone, it can remain untouched for a remarkably long time. We see the same thing outside organizations. A branch falls into the street. Something spills in a store. A gate is left open. Everybody sees the same problem and, just as quickly, sees the same escape. Someone else will take care of it.

Sometimes someone else should. I don't want an untrained stranger repairing an electrical panel because he has developed an enthusiasm for personal responsibility. There are good reasons for expertise, procedures, and clearly defined jobs. But most of the things we step around aren't electrical panels. They're pieces of paper.

The phrase “not my job” has always interested me because it can mean two very different things. Sometimes it is a necessary boundary. People shouldn't be expected to absorb every responsibility neglected by someone else, and organizations can become dependent on reliable people until competence itself becomes a punishment. Other times “not my job” means something closer to: I could solve this easily, but I have found a defensible reason not to. The words sound the same. Most of us know the difference when we say them.

I remember watching a new supervisor ask a receptionist to do something. I don't even remember what the task was, which probably tells you how ordinary it must have been. What I do remember is the answer.

“Well, that's not my job.”

The supervisor answered almost immediately.

“You're right. You don't work here any longer.”

Abrupt? Certainly. Perhaps more abrupt than it needed to be. I don't know enough about everything surrounding that moment to judge it now, and I wouldn't hold it up as a model for management. But I remember what happened afterward. For a while at least, attitudes toward the phrase “not my job” changed.

I've seen the milder version of the same thing plenty of times since, minus the drama. A print job jams the office copier, and three people notice before anyone clears it, because clearing a jam isn't assigned to anyone in particular and nobody wants to be the one who volunteers and then can't fix it. A supply closet runs low and everyone assumes purchasing already knows. The pattern rarely announces itself as a moral failure. It just looks like busy people reasonably deciding that a small problem belongs to whoever set up the department to handle small problems, and discovering that no such person exists.

The incident with the receptionist stayed with me because both people were, in a narrow sense, making a claim about responsibility. She was defining the limit of hers. He was defining what belonging to the workplace required. Somewhere between those two positions lies a question every organization eventually has to answer: are we hired only to perform the tasks listed beside our names, or are we also expected to notice what needs doing and help move the work forward when we reasonably can?

A workplace becomes brittle when every request is met first with an examination of whether the task appears in somebody's formal description. Anyone who has spent much time around organizations has seen how absurd this can become. The problem sits in plain sight while people discuss whose problem it is.

Most of us know the difference between being exploited and being asked to help. We may not always like the difference, but we usually recognize it.

That is where ordinary responsibility becomes difficult to reduce to policy. Nobody can write a job description covering every moment when a capable person encounters something that needs doing. At some point judgment has to enter. If I am here, I see the problem, I can reasonably help solve it, and doing so does not require skill I don't possess or authority I don't have, the fact that I didn't create the problem may not be the only fact worth considering.

Neighborhoods work the same way, on a longer timeline. A streetlight goes out and everyone assumes the city already knows. A pothole widens for a season because reporting it seems like someone else's civic duty. Eventually someone calls, usually the person most inconvenienced by it rather than the person most capable of fixing it, which tells you something about how these things actually get solved. Capability and inconvenience rarely belong to the same person, and problems tend to move slowly until they collide.

Families know this territory too. There are dishes nobody remembers using, trash nobody admits filling, lights apparently left on by an unknown intruder, and pets theoretically owned by the household but fed by one actual human being. The discussion over whose responsibility something is can require more energy than doing it. Workplaces aren't much different.

The people worth watching are often the ones who prevent those discussions from becoming necessary. They see something small and handle it without converting the act into a statement about their own virtue. They don't need anyone to know. In fact, the absence of an audience may be what makes the act useful rather than performative.

No policy can settle this once and for all. Every organization, every family, every stretch of sidewalk eventually produces its own version of the paper on the floor, and the answer arrives the same way each time: not through a policy, but through someone deciding, in the moment, that the thing in front of them was worth thirty seconds.

That doesn't make every problem mine. There are people who spend their lives rescuing others from consequences and eventually discover that their helpfulness has taught everyone around them to be less responsible. Sometimes the right thing is to pick something up. Sometimes the right thing is to leave it long enough for the person who dropped it to notice. Adulthood contains a surprising amount of figuring out which is which.

The person who finally picked up the paper didn't become a better human being than everyone who passed before. Perhaps he was simply less distracted. Perhaps the trash can happened to be in his direction. We don't know. What we do know is that the paper stopped lying on the floor because one person, for whatever reason, decided it had traveled far enough as somebody else's problem.