Aaron N. Tubbs bio photo

Aaron N. Tubbs

Dragon chaser.

Twitter Facebook Google+ LinkedIn Github

Congratulations Sarah! I’d love to say more, but it’s not my place; she’ll have when/what to disclose. :) Suffice to say, things just got more interesting!

I’ve decided to continue my series on bitching (which is to say stating the obvious) about work. Today’s topic is one-off requests.

Aaron’s Axiom of Requests:

There is no such thing as a one-off request.

In theory, a one-off request is a great idea. There is some extenuating circumstance that makes it necessary to have package X installed for one person just this once. However, this never happens. As soon as you do it for one person, you have to do it for everyone. Kindergarten had something right… You would think we’d grow out of this, but trying to set policy after the fact never works. “That was against policy, we could only do that for one person on an exception basis” never stands up to a managing director that says “do it for me on an exception basis too.” Policy has to be set down from the start, and that means that there can be no one-off requests; the rules have to be followed to a T every time, or else things aren’t going to work.

I don’t really mean all of that, but I would say that nine times out of ten, doing a favor or something that is supposed to be a special isolated bit of work always ends up expanding into a big heap of additional crap.

Not much detail to this rant, for the time being. Maybe more next time, when I cover short-term solutions (hint: there’s no such thing … only long-term disasters).