Insolence
Ever since my system went live some months back, the senior management have been pushing for some interfaces to other systems. The thing is, after attending several discussions, it is quite clear that the business aspect of the interface seems to be ridden with obstacles. For obvious reasons, everyone wants to protect their turf, hence, the less impact the better. Well, the customer project manager for my system is a very shrewd woman (lets call her Mother). Her background in consultancy firms, bulldozer strategies and buddy-buddy relationship with the COO make her a force to be reckoned with. This story takes place after around three or four meetings with the other system (lets just call them Vendor X). The ball had fallen back into my court:
Mother: From the last meeting, it was said that Vendor X cannot interface to the Host, hence we shall look for alternative's at our end.
(........... lots of ding-dong ............)
(........... no conclusion on which point to interface ............)
(........... no conclusion of how much data to exchange ............)
Vendor X: (an Indian with an annoying British slang) I think, you're not ready to talk to us. You don't even know what you want. After you're done. Then call us in. I think it is a waste of time.
(........... shocked ...............)
Mother: (with flint in her voice) In that case, IT please take note that Vendor X should continue to explore interfacing to the Host. I think that they shouldn't go through us to get the information. Do whatever research you need. The system is there. Get the data. I think that is the right approach.
(........... chaos and panicky chattering at Vendor X's end ...............)
(........... my skinny boss smiles at me and I knowingly smile back at him ...............)
(........... the ball is back in their court, hehe ...........)
Lesson: Gajah lawan gajah, kancil mati di tengah. The mousedeer should stay out of the way when elephants are fighting .. or it might end up splattered in the middle....
(Keep your mouth shut and stay out of the way when titans clash)
Mother: From the last meeting, it was said that Vendor X cannot interface to the Host, hence we shall look for alternative's at our end.
(........... lots of ding-dong ............)
(........... no conclusion on which point to interface ............)
(........... no conclusion of how much data to exchange ............)
Vendor X: (an Indian with an annoying British slang) I think, you're not ready to talk to us. You don't even know what you want. After you're done. Then call us in. I think it is a waste of time.
(........... shocked ...............)
Mother: (with flint in her voice) In that case, IT please take note that Vendor X should continue to explore interfacing to the Host. I think that they shouldn't go through us to get the information. Do whatever research you need. The system is there. Get the data. I think that is the right approach.
(........... chaos and panicky chattering at Vendor X's end ...............)
(........... my skinny boss smiles at me and I knowingly smile back at him ...............)
(........... the ball is back in their court, hehe ...........)
Lesson: Gajah lawan gajah, kancil mati di tengah. The mousedeer should stay out of the way when elephants are fighting .. or it might end up splattered in the middle....
(Keep your mouth shut and stay out of the way when titans clash)
Comments
Anyway... dude, get yourself straight and look it from the process perspective. Find some support facts to see whether the interface is really necessary... :p
BTW, alwayz remind the mother to KISS... not kissing you but Keep It Simple Stupid .
HAHAHAHAHAH!!!! xD
MF licked the cream off Mr Oreo.
@BBear:
You're a big bear!
@Grat:
I still wanna work there you know... :P
@TZ:
Hahaha. Jemur nyawa.
Yes, I like STUPID!
The whole thing is too convoluted. Manual is best. :P
@Evann:
:P
@JJ:
Skanky fish?!
Since typically management likes to "bully" the IT personals. May be you and your skinny manager can komplot with vendor x against the business/management? Like saying, "That feature/functionality is not in the original requirements specification. Therefore it is out of scope. And if the management wants it to be implemented, it will cost the business more $$ and a new addon project be initiated."
(or something along those lines) Then the ball will be back in the management's court.
Haha... the panic and squabbles. Also just my 2cents worth of thoughts.