How many times have you gotten e-mails or text messages that refer to something so vaguely, you have no idea what the writer is trying to express? Or worse yet, the writer expresses a result, with no rationale for what caused it.Lesson ...
How many times have you gotten e-mails or text messages that refer to something so vaguely, you have no idea what the writer is trying to express? Or worse yet, the writer expresses a result, with no rationale for what caused it.Lesson LearnedWhen I first started managing projects, I had a project team member (let's call him Harvey) who used to come into my office, and say things like:"The client is so pissed, she's going to go directly to the president.""The entire process has blown up!""I don't think this one is even salvageable."Of course, it required me to ask a follow-up question to find out what was causing these tremendously awful scenarios. And when I did, I'd get another oblique description of how awful "it" was. Often, it took three or more questions, before I would find out what the problem was.And when I did, it was usually something VERY minor. Suffice it to say, I hated Harvey.Then, a co-worker/friend, Peter, taught me something very important. Ass-hats like Harvey were relishing the attent