Top 10 tips for successful implementations
- Specification. As one of our most successful clients says: “Specification, specification, specification “. Define as clearly as you can what you want to achieve (which will take some work) – and make sure you know how close your chosen solution can get to it
- Interface? Decide early on if you need data from your mobile solution to automatically feed data into and out from other systems you have in the business. Check carefully that the solutions you are looking at can handle an interface
- Connectivity. Be ruthless on connectivity – make sure your solution will still enable your teams to work IN THE GEOGRAPHICAL AREA WHERE YOU OPERATE when the signal is poor on non-existent. You should never lose data in the field! You may need a 4G/5G dongle or a second sim card from a different phone network to give you comms resilience
- Documented processes. You need to have your current processes documented to efficiently implement a of mobile workforce solution. Also – don’t just transfer all your back office processes into the field – your mobile operatives may rebel if you make them your new administrators. Make sure the minimum functionality is available in the mobile solution – not ALL the functionality! KISS approach is best
- It’s not about the handsets. Try not to concentrate too much on the mobile devices other than the fundamentals. Is it Android, Apple or Windows. There is a lot of choice. Focus instead on where improved efficiencies will give the greatest benefit to your organisation and concentrate on implementing solutions in these areas first
- Be sceptical. Ask every question you can think of during the vendor selection – even the awkward ones. These should be the vendor’s FAQs. Include where you think there is a gap and press hard to get clear answers to minimise risk downstream
- Partnership. Just plug in and go may be the cheapest, but it may not be the most efficient. Even if the solution is standardised your processes and systems may have to change. A partnership approach with your chosen vendor could make a real difference and help make you successful in your software product selection
- Resource & project manage implementation. Concentrate on the issues and opportunities in your organisation today and keep an eye on the future. Once your system is bedded in you will want to develop it as your needs change. Make sure your solution can grow with your business and that there are resources to make this happen. Do not get hung up on perfection either
- Involvement. Be sure to involve the operative teams and other back-office departments and functions in your implementation. Don’t make it too complicated or onerous for them either. Resistance to change is common (we’re all human!) – but if they won’t use your new system, your investment is going to fall short from the outset
- Get commitment to invest money, time and resources. Try to get a ‘White Knight’ (Product Owner) at senior level as a sponsor for the introduction of your solution. Report to Board monthly on progress. This type of project will require money to invest and, more so, internal resources from the organisation. A senior sponsor can be a real help when cross-department processes need to be tweaked to or resources committed to the project. Also, they are likely to have specified, downselected and rolled-out a new software product in their previous or current role, so ask them about all the pitfalls and how to derisk the entire process – from selection to operational support
What are your experiences of specifying, trialling, selecting and operating a new software product? Contact us to let us know what you learned along your journey.
