• “Ade McCormack sounds a much-needed clarion call for IT to "grow up" and become a mature business function.”

    Nicholas Carr, author of Does IT Matter? and The Big Switch. Former executive editor – Harvard Business Review

    Subscribe to this blog

Enter your email address:

Delivered by FeedBurner

Technobabble

June 16, 2008

A Law Against Word Pollution?

When Seth Godin points out that people can get "hung up on catch phrases and jargon that work great when everyone understands what we mean, but fail to bring understanding to outsiders. Yelling louder isn't always the answer. Changing your words might work better." I think of technobabble.

The story in his post sounds like a typical conversation between technologists and users. It is natural for the marketing departments of tech companies to create new jargon.

Perhaps a law is needed to restrain such companies from what is in effect word pollution? Words need to be carefully introduced once they have been reviewed by national (eg IEEE) and international committees (ISO) made up of users, technologists and vendors. It might slow down the spurious tech themes that are designed to relieve tech-vulnerable executives from their funds.

April 21, 2008

Speak English, Not Technobabble

Ben Worthen writes about a CIO who hates technobabble: Ramon Baez of Kimberly-Clark.

He writes:

"Baez has tried to eradicate tech speak and acronyms since joining the consumer-goods giant a little over a year ago. He’s starting with the emails that the information-technology department sends out whenever it has to make changes to a system. You probably know these messages: They’re the ones that make your eyes glaze over for the three seconds it takes to find the delete button."

This is refreshing. Baez has a career in any organisation that sells electrical or electronic products never mind as a CIO. The fact that he has to bring in intermediaries is a sad reflection on the IT industry. We have to raise our game. However it is a move in the right direction. What must technologists be thinking when they send out an email that refers to the TFPS server? It is as if an entry requirement for a career in IT is to have proven record of being empathy-free.

(Here are my observations on where technobabble comes from.)

April 17, 2008

Getting Sued for Technobabble

Ben Worthen's post SAP Sued Over Tech Jargon struck a chord.

He writes:

"Software giant SAP is getting sued for failing to deliver an “out-of-the-box integrated end-to-end solution that increases…effectiveness.” Amazingly, the meaning of these buzzwords may cost SAP over $100 million."

It is time for the tech-sector to speak business, particularly when it comes to dealing with users / customers. This applies to the service desk and the sales contract. If Sap has promised an ‘out of the box solution’ then one would expect a plug and go software package that met the documented requirements of the customer.

The question is whether the customer articulated their needs accurately in the Invitation to Tender. Anyone who expects enterprise applications software to map directly onto their business processes has either studied the proposition in great detail prior to purchase or is living in fantasy land.

See also my post Where Tech Jargon Comes From.

March 03, 2008

Where Tech Jargon Comes From

Where does tech jargon - or technobabble - come from, as Ben Worthen asks in his WSJ post, Where Tech Jargon Comes From: An Insider’s View.

I have some theories:

Geek chic – The IT industry has its roots in science; on day one those in IT were indistinguishable from scientists. Subsequent advances in technology have, in effect, dumbed-down the skills required to be a technologist. Despite that, they have retained the ‘scientist’ mindset and so display many of the associated traits. Communicating effectively with lesser intellects (i.e. users) unfortunately is not one of them. To the outside world the IT department can seem like an exclusive club, where users are not welcome. The feral nature of some technologists can lead to pack behavior, which results in younger techies mimicking the behavior of the ‘alpha technologist.’ So the ability to confuse users is passed down from generation to generation.

Tensions – Tensions between the IT department and users underpin the evolution of the IT industry. In essence there is an ongoing dispute over who controls the IT assets. It’s much like a restaurant where the customers (users) are constantly vying to bring in their own food and cooking equipment, and the staff (IT department) are insistent that all the cooking is done in the kitchen using restaurant produce. This leads to mutual suspicion and ultimately a breakdown in trust. Some technologists will use jargon as a form of verbal chaff to confuse and disorient the users -- a technique that gives the technologist a sense of power over their ‘adversaries.’

Emotional Intelligence – Traditionally, IT people generally have high IQs. Anyone who has ever argued with a techie will have felt the full brunt of their logic. But sometimes it is not smart to be right. Management consultants generally recognize the wisdom in not alerting the client to the fact that he is an idiot or one’s partner that she should lose some weight. Many technologists fail to understand this perspective. As well as being a little too direct at times, the problem manifests itself through a lack of empathy or emotional intelligence. Such technologists happily talk to users as if they are also technologists and so make no allowance for the fact that they do not understand technical jargon. The lack of an empathy gene leads to jargon-rich communications from the IT department.

Technology vendors – The battles raging in the IT industry are often literally a war of words. If one technology company can be seen to be associated with a given buzzword then this makes subsequent marketing easier. Hence the marketing departments of many technology vendors spew out new terminology in the hope that some of it will stick to the market. This often results in technologists confusing each other, sometimes by accident and sometimes to assert the techno-pack pecking order. An overall lack of standards in the IT industry in respect of terminology has led to many synonyms and homonyms. This increases miscommunication both within and across the IT department sand bags.

Perhaps this is where industry regulatory efforts should be focused?

What are your experiences with technobabble?