Communication Within the Company
Programmer to Team Leader:
- We can’t do this proposed project.
- It will involve major design change and no one in our team knows the design of this legacy system.
- And above that, nobody in our company knows the language in which this application has been written.
So even if somebody wants to work on it, they can’t. If you ask my personal opinion, the company should never take these types of projects.
Team Leader to Project Manager:
- This project will involve a design change.
- Currently, we don’t have any staff that has experience in this type of work.
- Also, the language is unfamiliar to us, so we will have to arrange for some training if we take this project.
In my personal opinion, we are not ready to take on a project of this nature.
Project Manager to 1st Level Manager:
- This project involves a design change in the system.
- We don’t have much experience in that area.
- Also, not many people in our company are appropriately trained for it.
In my personal opinion, we might be able to do the project but we would need more time than usual to complete it.
1st Level Manager to Senior Level Manager:
- This project involves design re-engineering.
- We have some people who have worked in this area and others who know the implementation language. So they can train other people.
In my personal opinion we should take this project, but with caution.
Senior Level Manager to CEO:
- This project will demonstrate to the industry our capabilities in remodeling the design of a complete legacy system.
- We have all the necessary skills and people to execute this project successfully.
- Some people have already given in house training in this area to other staff members.
In my personal opinion, we should not let this project slip by us under any circumstances.
CEO to Client:
- This is the type of project in which our company specializes. We have executed many projects of the same nature for many large clients.
- Trust me when I say that we are the most competent firm in the industry for doing this kind of work.
It is my personal opinion that we can execute this project successfully and well within the given time frame.
i can totally relate… thought i quit programming long ago… its pretty much same in all IT related companies.
for these special situations, God created crazy men. Thanks to them, the CEOs and everyone down the road has some nightmares.
In four words…’Communication Gap’, ‘Hypocrisy’, ‘Cheating’…
The likely result…the project is likely to involve inordinate delays and probably not meet the quality standards expected by the client. Besides raising work-related stress levels throughout the organisation…
Who or what could suffer? The organisation…in terms of the long term relationship that could have been built with the client and the prospects of which, if the same performance is repeated, are bound to be adversely affected…
Whatever happened to the ‘Business Ethics’ that so-called Thought-Leaders and Management-Gurus keep harping on? In layman’s terms…whatever happened to the old adage, “Honesty is the best policy.”?
I am sure that long-term relationships, whether personal or professional (even between organisations), can prosper only if based on honesty. Everything else can lead only to short-term gains…
HOW THE HELL did your name come instead of mine??? is it some serious conspiracy or what :’(
ej
This is called Software Service Industry. Every new project is a new domain and uses new tools. Engineers will definitely object. The upper managers have to transform the negatives to positives! There is no other way for service industry to exist and grow!! Well, I moved out of this industry tired of hiding truths and uttering lies….
Thanks for such indepth comments … but it still do happen at almost every IT place ….!