Releases of software products follow each other at an increasingly rapid pace. Whereas previously it could take a few years before a new version was released, this now happens much more frequently. A new release brings new possibilities. At the same time, moving to a new release also brings challenges and costs. The pros and cons at a glance:
Why WEL on the latest version of software:
- Safety first: New software products tend to be more secure and reliable than older products. And data security is extremely important. You don't want sensitive company information to be out in the open or not comply with laws and regulations (think AVG).
- Best performance: The performance of your system depends on many factors. Consider the hardware you use and the quality of connections. But the software also plays a role. New software products typically function faster and better, operate using improved technology and are compatible with other modern applications.
- Latest features: A common reason to upgrade to a new software version is the new features. Finally that new feature you've been waiting for!
- Taking small steps is easy: By regularly moving to a new version, you are always taking a small step as an organization. And that's much easier than doing nothing for years and suddenly taking a giant step.
- Ability to support: A limited number of software versions are supported by vendors. By using the latest version, you avoid having to pay for bug fixes yourself.
- Custom prevention: This does not apply to your Microsoft Word version, of course, but relates to the ERP system, for example. By upgrading to the latest version, you may be able to get rid of custom solutions because the standard provides for them.
Why NOT on the latest version of software:
- Greater chance of bugs: With new releases, there is a high probability of bugs; small errors in the software. These are discovered and fixed in the standard only after the release is released.
- No added value: Don't choose a new version of the software purely because it's new. If it doesn't add anything, don't do it. It often takes more time, effort and money than you think for the organization and each user to switch to the new software.
- Too much pressure on the organization: Each new version must be fully tested by the organization. It must be verified that all processes are still supported. In addition, work instructions and documentation must be adapted to the latest version. This brings with it additional workload and should not be at the expense of daily operations.
- Lots of customization to go along with it: If your organization (in e.g. ERP or CRM) uses custom functionality, then this must be migrated to the latest version each time you switch. This can be very costly and complicated.
René Welmerink is Application Developer at Dysel and turns modern technology into practical and useful applications for customers.
