This is part one of a three-part series on Mastering Credibility. Part two is It's The Relationships You Build and part three is It's How You Deliver Results.
Jeff was the quintessential schmoozer.
He was one of those guys who was the life of the party. He could walk into any room and instantly be the one that everyone else focused on. His charm, wit, and charisma was the envy of his friends and colleagues. Being in his senior year of college, Jeff saw huge dollar signs in his future as a salesperson. Though he was an average student with average grades, Jeff felt that his ability to wine and dine customers was going to be his ticket to being a big-money salesperson. With his wit and charm, how could customers resist?
One of my column readers recently sent in this question: One of our senior project managers left abruptly in the middle of a 3 year million $ contract. What experience and education would you consider in promoting a replacement?
Ooh, good meaty problem. Not so simple a solution.
So okay, Microsoft Project is a super flexible tool in helping you as a project manager define your project tasks, dependencies, and resources. Quite frankly, though, the workplan you define in MS Project is only as good as the thought that goes into it. Too often I've seen savvy MS Project users completely bungle a project because, while the tool was being used appropriately, the workplan didn't make sense to the project team and didn't reflect what really needed to be done. The team consistently expressed confusion about what needed to be done by when because the project workplan wasn't reflective of the actual work which needed to be done. Great exercise in using MS Project, but poor execution of the project. Blech.
Contact Lonnie about article reprints. Please specify article you wish to reprint.
See Lonnie's Amazon Author Page