Don’t get me wrong. I’m not a grammar purist. I do love the language. I’ve threatened to get out my marker and correct errors on public signs, but I’ve never actually done it. I believe usage defines language rules rather than the other way around. But I think we demonstrate our professionalism by how we use language.
I taught programming classes a little while ago. I had a student tell me he intentionally went into programming so he wouldn’t have to spell. And he’s right. Someone can create a variable or object and name it anything they want as long as they spell it the same way when they use it as when they created it. But I looked him in the eye and said, “Yes, but if you’re misspelling the word ‘credit’ when you’re asking a customer to share credit card information, that customer will have second thoughts about trusting your program. Your professionalism is on the line with how you communicate with your customers.”
So the number one tool you have is to proof your work. How many of us
read that memo one more time before we click the send button? Not as
many as you’d think. At least read it before you send it.
As a former radio announcer, there’s another variation I suggest… proof your writing out loud.
You'll be surprised at what you catch just by saying what you're
reading. I’ve had colleagues come into my cubicle and catch me
whisper-reading my script or training manual. That naturally cleans up
my overly complex paragraphs.
The third powerful tool is to get a
colleague to go over your writing. Sometimes we get too close to what
we’ve written. Another pair of eyes is invaluable in clearing up foggy
writing.
So good grammar and good writing don't happen by accident. Use these three proofing methods to immediately improve them.
I'm reminded that we deal in an international marketplace. I know, too, that English is difficult to master. The time investment it requires pays off in rich dividends in professionalism and in relationship building.
Besides, proofreading our work is a professional habit, no matter which language we're using.
No comments:
Post a Comment