1. Use Google Chrome as your browser.
  2. Ask everyone using the mobile app to ensure that their phone or tablet has ‘autoupdate apps’ turned on.
  3. Don’t allow frustration with JobFlow to build up amongst your team.
  4. Run your existing Job management system alongside JobFlow for a period of time but keep this period to no more than a month.
  5. Recognise that the successful implementation of JobFlow in your business will require a significant commitment from you and your people during the first 2-3 months of operation.

Use Google Chrome as your browser.
Everything we build for JobFlow is optimised for use with Google Chrome and all of our release testing is done in Chrome. Though JobFlow should, and normally will, work in other browsers, there are technical and performance differences between browsers that sometimes result in problems.

Ask everyone using the mobile app to ensure that their phone or tablet has ‘autoupdate apps’ turned on.
You need your drivers to keep their apps up to date to ensure that they are always running on the latest improvements and fixes. Many enquiries to our support team related to the app are for things that have already been fixed. You can always check which version of the app a phone is using by going to the JobFlow app menu and selecting the info item. The app version number will be displayed on the resulting screen.

Don’t allow frustration with JobFlow to build up amongst your team.
There are lots of reasons why people become frustrated with software in the early stages of an implementation. Things behave differently from what they are used to and this can be intimidating for some people, especially when working under pressure. Often this frustration manifests as complaints about the software, but if addressed early most of these obstacles can usually be fairly easily overcome. If left to fester the frustration is sure to spread and the risk of implementation failure rises exponentially. If you’re encountering frustration don’t wait, call us (0800 562 008) and we’ll help you work through the issues - we’ve seen most of them before. Don’t expect your team to soldier on and work it out, as it is always possible they have encountered a genuine bug. Just note the job number and let us know as soon as possible – we’ll check out logs and can almost always get to the bottom of your issue.

Do run your existing Job management system alongside JobFlow for a period of time so that you can validate performance, but keep this period to no more than a month. Communicate this to your team so that they know when the double handling of job information can be dispensed with.
We’re confident in our system but we know that we have to prove this to you and your team. We also know that during the implementation period not everyone is going to be able to use the system to the same degree of proficiency. That said running two systems side by side creates extra work for everyone so the sooner you can get to the point of switching off the old system the sooner you and your team can begin to realise the benefits of JobFlow. When implemented fully these benefits should be felt both by the business and its people.

Recognise that the successful implementation of JobFlow in your business will require a significant commitment from you and your people during the first 2-3 months of operation.
Unlike almost any other piece of software you will have encountered before, JobFlow is likely to touch almost every part of your business. Your implementation will likely require us to tune JobFlow to fit your business processes and sometimes you may need to adjust your existing business processes to fit JobFlow. This all takes time and effort. To minimise the length of this period there are a number of additional things you can do:
• If possible try to avoid a Winter implementation – you 100% do not want to be still learning the system in the white-hot furnace of Spring. Summer and Autumn implementations have proven to be the most successful because the pressure on your people is not so intense and you have some breathing space to adjust your approach if you encounter issues.
• Be clear with your team about why you’re doing this and what the expected benefits will be – for the business but just as importantly, for them as individuals.
• Be clear that the success of the implementation is the responsibility of all team members and that it’s a condition of their employment. One ‘bad apple’ can quickly spread negativity to other team members and have a significant negative impact on the success of your implementation.
• Be clear with your team that you expect it will take 2-3 months for the system to bed down and that you know this will require extra effort their part. Perhaps consider a little reward for the team once they get through it.

Did this answer your question?