Thursday, February 4, 2016
The problem branch
My library system has always had a "Problem Branch". You can easily determine which branch this is by asking the employees of my library system if they've ever worked at another branch. When it turns out that pretty much everyone hired in the last five years started out at one particular branch, that, right there, is your problem branch.
As openings come up through the system, staff from the problem branch leap on them as their opportunity to escape. Indeed, they will chew off their own foot to do so. But as the problem branch constantly cleaves off their ever disappearing staff members, they find that no one ever wants to fill their newly opened positions. And so all of their openings must all be filled by new hires from outside our system.
Our current problem branch currently has four openings. Normally I wouldn't much concern myself with the new hires for some other branch, but I know just how much of a problem our problem branch is. I understand I will be seeing most of those people, and working beside them, as soon as they can get here, which will always be as soon as they possibly can.
As newer employees these people have a very narrow frame of reference for library work. They also, more importantly, tend to be far more politic than us grizzled old timers. So when I ask them "How was it over at The Problem Branch?"
They say "It really wasn't that bad. I mean, not that bad."
But then they fall quiet for bit, and look down, and something dark passes before their eyes, and we don't discuss it anymore.
Labels:
analysis,
clerking,
co-workers,
libraries,
management,
psychology,
tombs,
work
4 comments:
If you were wondering, yes, you should comment. Not only does it remind me that I must write in intelligible English because someone is actually reading what I write, but it is also a pleasure for me since I am interested in anything you have to say.
I respond to pretty much every comment. It's like a free personalized blog post!
One last detail: If you are commenting on a post more than two weeks old I have to go in and approve it. It's sort of a spam protection device. Also, rarely, a comment will go to spam on its own. Give either of those a day or two and your comment will show up on the blog.
Subscribe to:
Post Comments (Atom)
So what keeps the Problem from being solved?
ReplyDeleteManagers and management is my go to for answering questions such as yours.
DeleteGreat blog post today. Makes one curious about the "problem" branch.
ReplyDeleteThank you so much for your kind comment and appraisal! I can see how it would make one curious. My original attempt at the subject went at it very directly, but it sure ended up elliptical, didn't it? As you may imagine any of my co-workers, throughout my library system, even those who barely know me, could probably read this and give you a specific name.
Delete