Recently I said to a colleague, “We need to improve distribution channels for your piece.”
The colleague heard, “She is criticizing the way I distribute my work. In fact, she dislikes my work, and has no respect for the time and effort I put into it.”
Since then, every request to this colleague has been met with a wall of resistance. The question, “Which solution works best for our system?” receives the reply, “Any solution would require change.”
“Which would be most compatible?” I ask. The reply: a cut-and-paste document containing spec information from the websites of the vendors in question.
Even the body language is defensive: crossed arms, tight smile, refusal to meet the eye. Yet when asked, this colleague says, “My first priority is to help the group.”
The language of resistance is ultimately self-defeating. If this colleague feels disrespected, there are appropriate ways to address it. Instead, because his behavior is so unpleasant, the rest of the group tries not to include him in meetings. This fuels his paranoia and makes him even less effective.
Seth Godin recently blogged on the subject “What’s high school for?” His suggestions included adding project management, presentation skills and leadership training to the curriculum.
I love Seth’s blog and learn a lot from his insights, but I’m betting he doesn’t have high-school-aged children. Here’s what I want my kids to learn in high school:
- How to write a paper. I’m not talking about a research thesis. I’d be happy to see a one-page book report that was cleanly written and properly edited.
- Basic organizational skills. The typical teen has 5,000 songs filed and categorized on her iPod. Yet she either forgets to write down her homework assignments, or misplaces the paper she wrote them on.
- How not to phone it in. My kids are pretty smart, which means they can get decent grades on papers they write at 2 a.m. the night before they’re due, based on material taken from Wikipedia. I have been unable to convince them that there is an advantage to actually researching a topic and formulating original conclusions about it.
- How to answer the phone and/or email. If it’s not a text, it doesn’t get their attention, no matter how many times I point out that old fogies like college admissions people and employers still use the phone.
As for the other skills Seth recommends–to tell you the truth, I’d just as soon hold off on turning them into little consultants. But I heartily concur with his suggestion that we give them “An insatiable desire (and the ability) to learn more.” The question is, how?
Ragan has posted my latest rant, on grammar rules that were made to be broken. My favorite: it’s time to stop worshiping at the altar of Strunk & White. A lot of their style rules really suck. There. I said it.
On the subject of rule-breaking, I am also proud to announce my first piece for Salon, a personal essay about my unusual family. It has nothing to do with business writing, but I hope you enjoy it.
Everyone’s seen them: sentences, phrases or whole publications so awful they literally made you squirm. In honor of appalling writing–and the people who make it happen–I’ve created this sure-to-be-coveted annual trophy. Early submissions include:
“Out to the yard, where fantasy awaits.” (Residential real estate listing, presumably for a brothel)
“Our work will give you a piece of mind.” (Masonry company brochure)
Bring on the nominations!
Reader and Renaissance man Bob Parker brought my attention to Alfred Kahn, economist and former head of the Civil Aeronautics Board, who was perhaps best known for a memo he circulated in 1977 containing guidelines for the avoidance of “gobbledygook” in corporate speech. The whole thing is a gem, well worth the five minutes it will take you to read it. Here are a few of my favorite lines:
“If you can’t explain what you’re doing in plain English, you’re probably doing something wrong.”
“Try reading some of the language you use aloud, and ask yourself how your friends would be likely to react.”
On the passive voice: “Typically, its purpose is to conceal information: one is less likely to be jailed if one says ‘he was hit by a stone’ than ‘I hit him with a stone.'”
“I have heard it said that style is not substance, but without style what is substance?”
What indeed. The memo garnered Kahn a marriage proposal (he was already married) and newspaper editorials suggesting he be elected president and/or get the Nobel Prize. He died late last year, so perhaps it’s time to nominate him for sainthood.
Ragan.com has given me a bully pulpit once again: Check out 4 rules for using idioms in your writing, including current favorites like “he’s peeing on my leg, but it’s warm and it feels good.”
I’ve been reading about cover letter and resume snafus–some of them real doozies. One woman gave the owner of an escort service as a reference. A programmer’s cover letter ended with the line, “I look forward to negotiating my salary, as I feel confident that I am worth more than the $65,000 you are offering.”
By far the most common error is including extraneous information–especially if it makes you look bad. Examples: “I type 14 words per minute.” (The HR person groaned, “We didn’t even ask for typing speed!”) “My social skills have improved since I started taking Paxil.” “Please text me, as I don’t check my email or answer the phone.”
Before sending out a resume or cover letter, give it quick once-over to eliminate TMI. Then ask a friend to do the same.
It’s been an amazing week for office-speak. Between the hallway, the elevator, the conference room and the copy center, I heard the following:
“I’m in concert with the sales team.”
“Let’s cascade this memo.”
“It pleasures me to inform you….”
“Please govern yourself accordingly.”
“I need to give you a dump.”
And my favorite:
“Ping Doris and make sure it’s on her radar.”
In case your ears aren’t bleeding yet, here are a few more: action items, metrics, laser focus, tickler list, in the weeds. Aren’t you glad it’s Friday?
My latest Ragan.com rag–on ways to minimize gender bias in your writing–is here. Please read and comment!
Some jobs or projects have clearly defined boundaries. But many of us end up taking on responsibilities that aren’t listed in the job description.
This works out fine as long as the redefined job is properly resourced, properly valued, and has a reasonable–okay, feasible–set of deliverables. Otherwise it’s a train wreck.
How do you handle this situation? What language do you use to a) notify your manager that you believe the job parameters have changed, b) set the scene for renegotiation, and c) get yourself a better deal?