Jargon is a constant issue for writers: to use it or not to use it. I recently did NOT use it when I should have. Here is what happened:
I sent invoices to two clients and included this statement: "Payment is due within 20 days, or a 1 percent interest penalty will apply." Although both clients had agreed to this payment arrangement, in both cases I had not received payment after 25+ days. When I followed up, I learned that the Accounts Payable departments, whose job it was to pay the invoices on time, had not even noticed my statement. One let me know the problem:
If you expect payment within 20 days, write "Net 20." That is what we understand.
To me, "Net 20" is jargon. To Accounts Payable, it’s the thing that gets their attention. My solution: use "Net 20" if I want to get paid within 20 days.
Here is another situation, but the writer opted for jargon:
Reading my email the other day, I noticed the title of the lead article in an e-newsletter, WebProNews: "Is SEO Rocket Science or a Colonoscopy?" The writer had my attention with that odd question. To read on happily, all I needed to know was this: What is SEO?
I read the entire article. I still do not know what SEO is or what the piece was about. The author did not offer even a hint of a definition. He did say that SEO is neither rocket science nor a colonoscopy, so he answered his question, but there was nothing else there for me.
For that writer, an easy solution would be to define SEO just once. Readers like me would learn something. And readers who know the term already would not be offended by a brief definition or spelling out of the abbreviation, would they?
It all comes down to our readers. If we want our readers to see value in our articles or pay our invoices, we need to use language they recognize.
Lynn
