The scenario is played out every day. You engage a vendor to install a module, new feature or a completely new implementation. Then you sit down and tell them how unique your organizational processes are and how you need to customize how the software functions.The secret is that most organizations have the same processes. Vendors are able to develop solutions that meet the 80/20 rule. In other words, your processes should be the same as 80 percent of the rest of the industry. So what do you do to find out how your organization is doing? You need to develop a solid GAP analysis. What are you doing that is different than what other organizations are doing? Does it really make sense to keep doing it this way? Is this a perfect time to tweak your processes?Keep in mind that vendors will be happy to provide you with custom code and screens…for a nominal fee. Don't unless your ready to add extra expenses to your project and address the issues you will encounter during upgrades. Some features that were developed as part of the software workflow may be affected. Additionally, you might not get the ROI you hopped for because you still kept bad processes in place. The more you chip away from the standard or "vanilla" install, the more likely you will encounter issues down the road.
There are two sides of this argument, from a client perspective and from the vendor. What has been your experience during customization?
