Technical jargon refers to a terminology that is non-formal, yet acceptable within a group of technical specialists. Jargon terminology has no meaning to other people outside the profession. Formal documents are presented in simple terminology without using a lot of jargon so that anyone can read it easily. However, professionals in a given group use technical jargon to better communicate various requirements in that profession. To these groups the terms used are acceptable and understood well. In fact, it is recommended as they are known to improve understanding in the process of communication.
When technical jargon is used in business communication and formal reports, it becomes hard for managers in other departments to understand. Some terminologies used might not be acceptable to them and as such can annoy the intended people. For this reason, that the primary responsibility of telecommunication managers or project managers is to ensure that reports or documents presented to members of staff or any interested party have proper formal terminology. Memos, conversations in official meetings and other reports must adhere to the right formal terminology acceptable to all. Project managers need to ensure that employees that use these terminologies comprehend the boundary to which the terminology is used. The telecommunication or project manager should translate any document written in technical jargon to the right terminology before presentation to intended audience.
Documents meant for general communications and which are used by everybody in the organization should be written in simple language so that everybody understands. Technical jargon can be used in documents that are intended for technicians and a group of professionals only.
The climate registry. (2009). Job description: Technical manager. Retrieved August 15, 2011, from The climate registry: http://www.theclimateregistry.org/downloads/TCR_Technical_Manager.pdf
Wessels, D. J. (2009, February). The strategic role of project management. Retrieved August 15, 2011, from PM World Today: http://www.pmforum.org/library/papers/2007/PDFs/Wessels-2-07.pdf