Sunday, August 15, 2010

The limiting power of jargon and the importance of understanding why

Next time you use a piece of jargon, have a think about what you’re actually saying, do you know why the jargon describes what you think you’re saying?

Jargon is a great tool, it can provide a quick, simple way of describing a complex concept when among people of compatible technical knowledge - concepts like Standard Operating Procedure (SOP), describes in 2 seconds what could take hours to explain.

The problem with jargon is that we generally understand what we’re describing but often forget why it is described or done that way. We can end up either make changes to what the jargon describes without understanding their impact or limit ourselves within the confines of the jargon, preventing us from reaching our objectives.

This week I heard a piece of jargon used to describe a particular sporting team training time and method. The crux of the problem was the inability of a team member to make the time, what was lacking was an understanding of why the training time was as it was, a detailed understanding could have lead to an adjustment of the schedule to produce the same result, instead the term became a road block and the desired result wasn't achieved because the Jargon limited the capacity of the team members to think differently.

Next time you use a piece of Jargon to describe a way of doing things, make sure you understand why, and if you dont, use plain english - sometimes it can take longer to use less time.

No comments:

Post a Comment