Showing posts with label work. Show all posts
Showing posts with label work. Show all posts

Tuesday, July 6, 2010

Weasel words to avoid at work

"Try"
"Try" is a weasel word. "Well, I'll try," some people say. It's a cop-out. They're just giving you lip service, when they probably have no real intention of doing what you ask. Remember what Yoda says to Luke Skywalker in "Star Wars": "Do or do not--there is no try."

"Whatever"
This word is a trusted favorite of people who want to dismiss you, diminish what you say, or get rid of you quickly. "Whatever," they will say as an all-purpose response to your earnest request. It's an insult and a verbal slap in the face. It's a way to respond to a person without actually responding. When you say "whatever" after another person has said his or her piece, you have essentially put up a wall between the two of you and halted any progress in communicating.

"I'll get back to you"
When people need to buy time or avoid revealing a project's status, they will say, "I'll get back to you," and they usually never do. If people say they will get back to you, always clarify. Ask them when they will get back to you, and make sure they specify the day and time. If they don't, then pin them down to a day and time and hold them to it. If they won't give you a day or time, tell them you'll call in a day or week and follow up. Make sure you call and get the information you need.

"Yes, but . . ."
This is another excuse. You might give your team members suggestions or solutions, and they come back to you with "Yes, but . . ." as a response. They don't really want answers, help, or solutions. You need to call the "Yes, but . . ." people out on their avoidance tactic by saying something like "You know, Jackie, every time I offer you a suggestion you say, 'Yes, but . . . ,' which makes me think you don't really want to solve this problem. That's not going to work. If you want to play the victim, go right ahead, but I'm not going to allow you to keep this up." After a response like that, you can be assured that the next words you hear will not be "Yes, but . . ."!

Thursday, April 22, 2010

Communicating with your idiot boss

Scott Herrick at Cube Rules, a job-advice blog, points out three mistakes we all make when reporting in to that lump in the corner office.

Explaining your entire thought process without a decision request

Remember the writing rule that says the first sentence of your paragraph should explain what is coming in the rest of the paragraph? Same situation here. Managers are used to making decisions, so tell your manager up front what you are requesting. Once you say what you are expecting, you can then go through the reasons why and your supervisor will know where you are headed. The longer it takes for you to put out your request, the more your supervisor will try and figure out what you want instead of listening to what you are saying.

Failing to prototype your work

Ever had your supervisor give you a small project with a due date out a couple of weeks? How many times have you taken that project, thought you understood the deliverable, then presented your work on the due date and were told it was all wrong?
It happens all the time. The higher up you go in the organization, the more likely it is to happen — because no one wants to bother the mucky-muck, but to deliver.

When you get a project, take one point and follow it through to the end. Then, after completing this in a couple of days — about 5-10% of the total project, show your work to your manager. Now you will discover all the hidden requirements your manager assumed you knew when you said yes to the project. Now you will find the right level of detail. Now you will find if you are writing for the right audience. Now you will find if you are using the right delivery tool for the work.

Providing activities in status reports instead of accomplishments

In bigger corporations, status reports are common. Most managers don’t tell you what they want in them or, if they do, they focus on activities, not accomplishments. Don’t fall for this trap.
Your accomplishments are your results that can get included in your performance review. Or your resume. Your accomplishments become the stories you tell your hiring manager for your next gig. Even if your manager wants to know that you attended twenty meetings last week, put in the twenty meetings but also include what you accomplished as a result of the meetings.