Politics in a Small Way 1

[jgoebel]

Alright, So I went above and beyond and created this tool that automatically stores project related emails to the appropriate project folder on our network. I mean, I put in a good deal of hours on this thing. I was kind of proud when I finally got it working, (I am an EE) with some interest/skill in programming and took the initiative to get this going. Our software development head was copied by me on one of my emails to the two administrative people my program would affect, and he basically wrote this email and copied the admins, head of IT, a few software Devs, etc,

and said that the software development department was working towards a solution on the project. I wasn't completely thrown under the bus but honestly I am just now starting to get the picture that some of how far you go is how you OWN stuff. I mean, hey, hes saying, this is a software Dev project, thanks for your interest/help, but when it comes to who ultimately is going to get their cuudoos, its going to be mr president saying thanks mr head of software guy for your great vision. Its kind of crap, especially when you consider that the only reason he even know anything about it or decided to make it happen in the first place was because he overheard a conversation between me and one of the software guys...

Silly different departments!

 

[KENAT]

jgoebel Politics, feel your pain. Doing work, other people taking credit, gets old.

KENAT, probably the least qualified checker you'll ever meet...

 

[rbulsara]

jgobel:

Get a patent on your idea. I am looking for such solution in our office.

 

[MikeHalloran]

EVERY software idea that you ever heard of or wished for is an 'ongoing project' in every IT Deparment, but there's a secret: Exactly NONE of them ever get finished. Seriously, I think they start layoffs when the backlog gets down to ten years.


Most IT departments answer to no one, certainly not mere Top Management. They expend more money than you could possibly believe on maintenance of programs that haven't changed in decades; I doubt they even know how to change them anymore.



Mike Halloran
Pembroke Pines, FL, USA

 

[MedicineEng]

Send an email with the tool, file, wahtever, that you created to head of software dep Cc to the Big boss(es), saying more or less this:
"Dear XXX,
Following your email of XXX, I found it a big coincidence that we both had the same idea to improve the office administrative work. This is a sign taht in fact this problem is affecting much more persons beside myself.In fact, I've been working for sometime out of office hours in a tool to address this exact problem. Please check the attachment. I believe that this will fully address the situation.
I would like to hear your oppinion regarding this development and when can it be fully implemented and shared with the rest of the office".

Like this you get all the recognition and anything that the guy does on top of your work will be based in your work and the big boss knows it.
Attention: If you send this email, make sure that your tool really works...

 

[jgoebel]

rbulsara -

Thanks for the encouragement.


Danke

 

[jmw]

You take your recognition where you can....amongst your peers is best cos management and It don't give a er, a hang for any other person's efforts. In fact, Not Invented Here Syndrome may not be an IT specific disease but I'd guess it comes close.

I feel exactly the same way about some of the stuff I've created and would rather put it in the public domain than see it gather dust in someone's in tray where it will probably remain till hell freezes over.

On the other hand, having identified the problem and rushed straight to create a solution isn't always the best practise. The correct procedure is not to assume that because you see the problem that your view of it is correct or that the issues you identify are the only issues. The best way forward is to collect the facts which means talking to other users to see what problems they have and what features they'd like. This lets other people buy into the problem and the solution.

Sometimes this procedure also lets you discover that someone else is "working on it" and not to waste your time.
Of course, the fact that until you did the work no one knew that IT had a project says they weren't doing it right or weren't doing it at all. If they were and they should be consulting the "clients" (that's you and everyone else with an interest) to find out what everyone needs so they can deliver the right solution. OK, you see the problem. This is how most developments should work, unless they are IT lead.

Incidentally, having gone out and developed the solution yourself, and on your own initiative I would guess the next step would have been to finish the project by implimenting it. Once in use, no matter what anyone says if IT pull it the screams would make even them quake a bit. What they'll do to save face is play with it for a week or two and then re-release it with just a few minor and meaningless changes. (just like the EU and its constitution.... you see everyone knows that trick).

JMW

http://www.ViscoAnalyser.com

 

[jgoebel]

Big brother is watching!