Top 3 Mistakes People Make with a Software Implementation Blog

Top 3 Mistakes People make with a Software Implementation

In Business Management Software by Hannah Munro

Reading Time: 2 minutes

1. Not scoping the business requirements thoroughly

No piece of software is perfect straight out of the box (the person trying to sell it to you will try and say it is) but most good suites of software have a number of settings, field customisation, reports and/or workspaces that need to be configured. How do you know this piece of software is going to do what you want if you haven’t discussed this need in detail with your implementation consultant?

A general overview of the capabilities of the system is completely different to a full software specification. So if your software partner isn’t including the time to fully scope your needs within the quote, you should be asking why and challenging them on it.

2. Skimping on training

There is always a need to keep the costs for every implementation to a minimum but cutting back on training can impact hugely on the effectiveness of your software. Without thorough training, your staff will lack the skills they need to work efficiently and to maximise your investment in your software. A staff member that struggles to find their way around your new system quickly becomes disenfranchised and disinterested, no matter how well you achieved initial staff buy-in to the project.

Software providers can often minimise the days allocated to training in order to make their proposal more attractive to you and more competitive against other companies.

3. I want it and I want it now

The downfall of many software implementations is to do everything in the first instance – and by this, I mean making the system all singing and all dancing from day one. The reality is that is too much for any organisation to take on, and the support requirements are huge meaning that your staff gets stuck in a backlog reducing productivity and becoming disenfranchised. Then you discover a few changes that need to be made, those may take some time or require retraining and you may incur additional costs that could have been avoided.

A more practical approach is a phased delivery. This phased approach can have a variety of levels within it. For example, you can phase system functionality, teams of users going live or both! Then with each phase, you do a review, implementing any changes before the next phase. This ensures a smooth, easy delivery that will fully meet your needs.

About ITAS

ITAS has been a Sage Business Partner since 1995. We combine good technical knowledge and experience of Sage 200 and Sage CRM software with thorough scoping techniques, project management skills and effective training to make sure you maximise your investment in Sage software.

Sage 200cloud Demo Banner