Have You Set the Right Objectives for Your Software Rollout?

If you are just starting out as a rollout project manager or owner you might be considering what objectives a software rollout should have to ensure that you achieve and deliver the intended business results for your company. Or if you are already experienced in this field you might want to know if your way of setting objectives is correct. So, to help you I’ll share what types of objectives I believe every rollout should have.

First, the reason why any company rolls out new software is that it wants to gain a certain business result therefore each software rollout should have a business impact objective. This type of objective focuses on whether the organization achieves its intended business results. The business impact objectives can be tangible and intangible. Tangible objectives are often quantitative such as increased revenue and efficiency. Intangible objectives are often qualitative such as improved teamwork and leadership.

Second, I believe that every rollout should have an adoption type of objective. An adoption type of objective focuses on whether the target audience has adopted what is necessary to make the rollout successful. It can be, for instance, necessary behaviour (e.g., using the software and following the related practices), beliefs, values, assumptions, skills, knowledge or other types of change. I define each adoption type that is relevant for a specific rollout and the target level to be achieved.

Third, I also believe that rollouts should have a satisfaction objective. A satisfaction type of objective provides immediate feedback throughout the rollout from the target audience and is essential in order to maintain a good grip on the rollout project. Also it provides an overview of whether the target audience’s overall satisfaction with the ways of working has improved as a result of the rollout.

And last but not least, I believe that each software rollout should be managed as a project according to best project management practices. So it means that there should be project management objectives for each rollout.

I hope you find this blog post useful. If you have any questions please let me know in the comments section and I’ll try to answer personally to as many questions as I can.

To your software rollout success!