Sort of as a follow-on to the post about project management and b-schools, I thought that I would post something (a bit one-sided) about the use of Microsoft Project in management consulting projects. I dislike the tool and sometimes even discourage the use of the tool by consultants running projects. Here's some reasons why:
- While project management is a function that moves things ahead, Microsoft Project as a tool can create barriers to communication. For the average user, there's generally not enough flexibility to do things like highlight workstreams in an engagement, create a view of danger/risk points in a project, show progress to plan plainly, and summarize a project plan on one chart.
- Because the tool is not part of everyone's basic software configuration, there are additional barriers to communication because the native file format often cannot be easily exchanged with clients, colleagues, etc. who need to work and update things in real-time. Project plans in Microsoft Project need to get exported to things like PDF files, etc.
- Updating the project plan can become a project in of itself and prevent the project manager from doing other important things like communicating with stakeholders, managing risks, working to solve problems, and completing tasks.
Getting the theme behind my dislike for the software?
I much prefer using something like Powerpoint or Excel for developing project plans. I like Powerpoint because of its visual nature (which can be helpful in managing projects and leading people). I like Excel because of its greater structure over Powerpoint and ubiquitous availability to business people.
Am I right? Probably not entirely, but I have definitely seen the types of recurring problems described above in many engagements. The negatives often outweigh the benefits of using a more structured tool fit for purpose.
