There’s nothing that I can think of to “shake up” business processes and the custom applications used to support those processes more than a personnel change. This is most clearly apparent in the small company applications used by a handful of key users in the company. If for whatever reason one of those key users is not available for an extended period of time and others are doing what was “their” job, questions are inevitably raised about “Why is this like this? Why are we doing this this way? Wouldn’t it be better to…?” In my experience while changes in business needs can elicit those same questions, by far the most dramatic and in-depth questions come from the change of personnel doing a job.
I have been dealing with a couple of situations in the past weeks that fall into this category — and the end result of those questions is, and will be, a much “cleaner”, “user-friendly” and “efficient” program. The change is good! It seems that the longer an application is used the more “set in our ways” we get about the program just “being” a certain way – rather than challenging either the process or the program. My clients are always encouraged to be on the lookout for potential changes to make their jobs easier, that’s just the kind of relationship that I’ve built with my clients, but it seems to take some dramatic change to elicit new requests. In so many cases the changes are not necessarily extensive — often just a “tweak” here or there that over time makes a significant contribution to efficiency.