Configuration vs. Customization - Devil's in the Details
Submitted Aug. 27, 2015
For several years I was the end user of the Personify AMS (now owned by TMA Resources) within a very large medical society. To be fair to Personify, many of the problems with the system were caused by a combination of communication breakdowns between their support and our users and developers over time. Every association feels that it is "unique" and must customize a system to be perfect for their systems and processes. While it is true that everyone does business differently, a major "lesson learned" was that it is actually possible to customize a system to the point where it is no longer effective, or where a change made in one part of the system will cause ten other things to break down the line. When my organization decided that a major upgrade of the system was in order, we at first assumed that making the move to a more modern version of Personify would be less cost and hassle than going to a completely different system. Over time, we became aware that despite already having paid for the full system once and for ongoing support, upgrading essentially meant going through an entirely new implementation. Coupled with negative experiences with Personify's project implementation team, we decided to pull back and to evaluate other options in the market, keeping Personify on the list as an option but looking at prices and timelines of major competitors. In the end we narrowed our prospective choices to Personify, Aptify and Avectra and ended up choosing Aptify due to its ability to configure - rather than customize - and to maintain upgradeability despite conforming to our processes and integrations. For many organizations, Personify may still be a great option and I have heard (but not experienced) that some of the staffing issues have been improved since TMA Resources became involved. The system is robust and offers fairly generous pricing options for small to mid-size associations.