So much emphasis is put on "the process".
What if the process fails? Do you patch it on the fly as problems arise? Or do you sit down in a post mortem and figure out how to fix the process on a more permanent basis?
What if the process fails because the people involved don't/can't/won't follow it properly? Do you adjust the process to fit the people, or do you expect the people to adjust themselves to fit the process? What if the people are incapable of adjusting? What if multiple attempts have already failed?
When your job title includes the word "analyst", doesn't that mean you're expected to analyze something? Like, actually put some thought into it? Maybe even do a little research?
Should I be expected to take someone seriously when they tell me how things should work, when I know full well that they have no clue?
[sigh]
I'd have to get too specific if I listed out the rest of my complaints. Suffice to say that I am particularly irritated today.
Fortunately, I arrived at work early, which means I get to leave early. Let's hope I make it until 5:30 without ripping somebody's head off and squishing it under the sole of my shoe.
skip to main |
skip to sidebar
Baring of soul in progress.
4 comments:
Wow... You and I sound a lot alike when it comes to work! I'm an 'analyst', too, but I've given up analyzing because no one listens anyway. We have a number of broken processes, or ones that just don't make any sense. Problem is, with a company this large there's about two years of red tape & approvals to wade through until something even begins to change.
Am SO glad it's Friday...
*hugz* Hang in there, weekend comin' up! ^_^
Edit: I forgot to mention, I wonder if I might be starting to burn out on the whole IT career thing. I went to school for a programmer analyst diploma, but a) I didn't finish because financially,I needed to go back to work full-time and couldn't swing both on my schedule, and b) coding wasn't so terrific on my stress levels! (I went semi-catatonic during the Assembler module.) I've since found out that I'm a lot more comfortable with hardware & software configuration, so I'm sticking with that even though it pays less. Money is nice, but it's not too useful if you're in no shape to spend it...
I think they call you an "analyst" when they don't quite know what else to call you.
We must work in the same company. I'm pretty sure. The larger the pay, the stupider they get. They don't listen to common sense and look at you like you have two heads when you try to stream-line something. I'm amazed my company has been in business for so long.
They let the good workers leave when they should invest in them.
Rrrrr.
I'm glad you surfaced. I was beginning to wonder if you got snowed in or something.
I'm not actually an analyst, there's only one guy in my department who is, and he's... well... less than competent in my opinion.
Then again, my opinion isn't the one that counts, as I'm reminded repeatedly by my manager who makes decisions that completely fly in the face of reason or logic.
I swear, I really do feel like I'm taking crazy pills. Like maybe the few people I get irritated with are actually exactly right all the time, and I'm the one who just doesn't get it.
Post a Comment