Project Implementation; Software Rollout Approaches

When analyzing alternate approaches for rolling out a new software product, consider information density versus percent of population.

For example, you can start with low information density (less functionality, fewer features, etc.) in a large percent of the population (or for everyone), and then roll out more features over time.

Or you can start with high information density (heavy or full functionality) for a small percent of the population (i.e. a pilot group), and then roll it out to wider audiences over time.

Neither approach is wrong. It all depends on the situation, the nature of the product, and where the risks lie.

For example, if the audience for the software can be isolated easily and there are no major issues with rolling out to wider audiences piecemeal, then it may pay to start with high information density in a pilot group.

But if there are major risks to rolling it out piecemeal (such as a need to maintain multiple systems, etc.) and basic features will do for phase 1, then the alternate approach might be a better choice.

One thing's for sure. To begin with high information density in a large or total percent of the population is usually a mistake (unless the full information density is necessary for the product to work, in which case the schedule needs to include time for full rollout and extra testing).

Just some things to think about when planning your next software rollout.