This is the fifth post in our series on Successfully Implementing Project Management Software

We have all seen how people get very feature greedy when implementing software systems. Most new systems will perform many different functions, some of these new to staff members. The stats tell us, if you try to implement all of these features at once you will increase the scope of the project and therefore the likelihood of failure. This really applies to project management software which can be very multifaceted.

Simply put the reason you will fail with this 'all at once' approach is you will spook your staff. Most people don't like change, particularly if it comes with a perceived increase in work load. If you want people to use the system to do things they don't already do plan to release the system in steps. For example getting everyone to create project plans in your new application is a project in itself. If you do succeed at just this one thing I would consider that a massive success. 

Once you have everyone using the project management software for the simple things it's not going to be difficult to slowly broaden the scope of its functionality. If you then want them to forecast, work request, time sheet..etc make those into subsequent projects and leave them well alone till people have fully adopted the first release.

I would suggest ordering the different phases of the project by how beneficial to staff they are and how easy they will be to roll out. Create a long term plan for the whole roll out and move towards that goal in incremental releases. 

Just remember, if you have something complex to roll out.. do it once step at a time

This is the third post in our series on Successfully Implementing Project Management Software.

You can get a package that ticks all the boxes but if the users don't love it, they won't use it. Similarly another great way to get people to dig their feet in is to make a decision for them. Lets face it most Project Management staff have been waiting for years to get their hands on some good project management software. A great way to turn them against the project is to force something on them, particualualy when another part of the business made the decision. Its critical to get people involved in the decision making process. If they don't buy in there is no project management software package on earth they will commit to using properly.

Make a short list then let the end users try each one. Get them to setup a project, forecast and schedule each other onto it. Watch them use it and pretty soon the right software will be obvious. 

The right software will be easy, intuitive and get the job down quickly. 

This is the first post in our series on Successfully Implementing Project Management Software.

The simple problem with software purchasing decisions these days is people make it harder than it needs to be. The "correct" way to pick an application for your business is a long and academic one. You do analysis, determine weighted requirements, then go to market looking for alternatives which you compare with your requirements. This may not be for everyone, particularly for those with smaller businesses looking to fulfill minimal requirements. If you know your not going to do it the hard way and just want some quick pointers please read on....

Step 1.  Pick something simple

The process for successfully implementing project management software is different for each organisation. It comes down to what is right for the culture and complexity of the business. My advise would be figure out exactly what you need and pick the simplest tool for the job. You need something that will make your job easier rather than simple increase your data entry. It's very difficult to get people to add things to their work load so don't expect people will rush to use your new package if the tool requires alot of effort to produce results people don't already need.

In my experience this is the number one cause of failer, lets face it if you install something simple and get 100% of people to enthusiastically use it then you have suceeded. If you install something which promises to control every aspect of your business and only a couple of staff seriously use it then your've failed.

Systems have to be seen to help, not add workload.