Quite often software vendors have what they call “best practise” processes for their system. These are a good starting point as they are generally proven processes that work in other organisations. However, care must be taken so that the system does not dictate the processes that are undertaken as this may not achieve the required result.
As with System Reviews, Process Reviews are a good way to ensure that inefficient processes have not crept into the business. These quite often happen when something has changed in the business or something extra is required. Often people turn to Excel spread sheets to fulfil this requirement in the short term, but this could cause inefficiencies in the long term as processing starts happening outside the corporate systems and there is no longer a single source of truth. Good communication between the system administrators and business stakeholders can help to avoid this as business stakeholders will know if something additional is required and they can then approach the system administrator for a solution.
As mentioned above, care must be taken when only adopting vendor best practise processes. For example, the system may have quite a complex best process because this suits larger (more complicated) organisations, which, if adopted, could result in over-resourcing a particular area just to support the process. It would be better to use the best practise process as a base, then either build on or cut down where required to ensure it is a best fit solution for the business.
If you would like any assistance performing a process review or some guidance on how you could run such a process internally then please don’t hesitate to contact us and feel free to share this article on your social media pages using the share icons at the top of this page.