This arstechnica.com article highlights a point that I think is something of a shortsighted view of the integration of software and business processes. It's the choice between choosing to modify the software or the business processes, so that they integrate in a way so that they add value.
There is no single answer, the reality is that each project is different from each other. As such, when the upgrade is being done one should map out when is modifying the software or the business process will bring the most value. In short, choose to modify the one that has to adapt to the other in order to make things work to the best of their capabilities.
It's also important to have in mind that, sometimes you're going to have to modify both in order to achieve the results you're looking for at the end.
That's why having a clear idea of how you're doing things, and the results you want to achieve. Only with this in mind, and fully mapped out, you can make the choice of what software you need to get and if you need to modify it in order to make it work for you. The same goes for your business processes, since the new software can be the key factor in making any changes in your processes be made smoothly.
Trying to force business processes to work with a certain software, or vice versa, is the recipe for waste of money and time. When making any kind of change in order to improve your business, make sure that what's change actually adds value.
Change only those things things that will bring the results you want, or add the value you need to bring in.
No comments:
Post a Comment