Simon

Cumbria

IT

What a load of bull - to use the vernacular of the article.

The problem isn't that IT has its own language, it's that the rest of the business won't learn any of it. Go to any sector - wether it's engineering, HR, finance, whatever, and you'll find a similar level of sector specific terminology. It's essential for those involved to have a common understanding of what they are talking about.

I'm from an electrical background, so I know my VAr from my kW from my RCCD. If the conversation is about technical issues then the terms have to be used - it's no good waffling on about unspecified units of reactive power if the discussion is about the sizing for, say, an electrical installation. Anyone who intends to be involved in the project needs to learn the terminology that goes with it.

The problem is that everyone else in the business expects IT to talk to them on their terms - and at the same time will refuse to talk with IT on IT's terms. If the CIO is expected to know the difference between EBIT, GM, and RoRE then shouldn't the finance director be able to cope with a conversation about the capacity of the WAN to support his financial apps ?

Sure, the terminology can be overused, or used in inappropriate situations. What is probably more lacking is a better understanding of the limitations or the mere mortals who aren't in IT and adjust our use of language as required.