A pretty nifty feature in Microsoft Project is the ability to define a project through the use of the project guide.  The project guide is a cool little wizard that walks you through setting up a project, assigning resources to the project, tracking progress, and reporting on progress.  What I like about this wizard is not only the help it gives newbie project managers, but also is a great reminder of the cool MS Project capabilities for more seasoned MS Project project managers.  

To get started with this cool project management software tool do the following:

So let's cut to the chase...

You may be a great consultant, one who effectively applies his or her wisdom and experience to help his or her client solve some tough business problem.   That's all fine and well.  When it comes to facilitation, though, it's a different ballgame and a very different approach to problem solving.  I like to think of the difference as follows:

Excerpted from The Truth about Getting Your Point Across…and Nothing But the Truth 

Several years back a colleague of mine (I'll call the colleague "Nellie") was managing a very high-visibility project. This project was high on the radar of key executives all the way up to the CEO of the company and any major mis-steps would send fireworks up the chain faster than lightning.  This was one of those "thrill-seeker" projects; definitely high risk but also of high reward if the project was successful.  Nellie was up to the challenge and willingly accepted the assignment.

Talk about your character-building experience...

I was a young hot-shot project manager on an engagement that I had sold to a client.  I had it all planned out and had delusions of completely delighting my client with an issue-free project.  It all seemed so simple, then the project started...and never finished.

I'll spare you the gory details of my harrowing experience but what I can tell you is that I put more focus on selling and planning the project than I did on its execution.  I took a naive attitude of the project being able to pretty much run itself with some junior analysts running the day-to-day aspects of the work.  It blew up in my face and I got booted from the client never to return again.  It was my inaugural visit to the project management guillotine. 

Typically, career choices are made based upon responsibilities, compensation, or prestige where a businessperson makes a change to get a higher salary, more responsibility, or greater prestige. What about the situation, though, where the driver behind a career choice isn’t any of these; where it’s the needs of a child that drive the change? My choice was precisely that.

Trevor was a happy, normal, active baby. He was able to laugh, coo, cry, and do all of the other normal things that his big sister, Briana did at that age. To my wife Patty and me, everything seemed to be just fine. At about age two, we noticed that Trevor was hardly saying any words and was very into his own world with puzzles, coloring, and videos. 

Some time back I was responsible for a portfolio of projects being done within the finance organization of my company.  One of the projects was outsourced to a large consulting firm who supplied the project management, analysis, and development resources to the project.  I would hold weekly meetings with the project manager who consistently gave me a "thumbs up" on the project up to the first key milestone being hit.  When the week of the first milestone approached, he announced that the milestone was going to have to slip by a week to ensure successful delivery.  The next week came along and again the project slipped a week.  This went on for two more weeks with the promise of "we'll for sure nail it next week."  I decided to do some crawling around the project to assess where the project was really at.  Turns out we were at least a month away from delivering to the milestone which was already a month late.

Excerpted from The Project Management Advisor - 18 Major Project Screw-Ups And How To Cut Them Off At The Pass (Prentice Hall, 2004)