What I am about to say may sound very elementary at first; however, it warrants careful thought. It is often very difficult for those looking at Project Management solutions to decide what type of system they should look at and subsequently move to.
The fact that a system is being looked at in the first place is usually a result of trying (and failing) to solve problems that currently exist and are causing headaches. At first glance, it is usually easier to go with the simplest system that appears to fix the problems and deals with the limited issues “where it hurts the most”. The choice may also involve the general misconception that everyone can learn a simple system quicker and that it will quickly solve a few of the current problems (but only a few of them). Comparatively, in the medical world, this means to “treat the symptoms but not find the cure.”
It seems that in many cases, the issue of “Cloud” based software solutions versus traditional self-hosted solutions has become the primary decision point for companies procuring project management/accounting software. Unfortunately, this sometimes happens at the expense of what should be the single most important consideration: functionality.
Functionality is the hard part. It is the hardest for the software company to deliver; the hardest to implement; the hardest for users to understand; and the hardest for purchasers to evaluate. Getting from functional evaluation through to completed functional implementation means “rolling up one’s sleeves” and doing some very detailed work. Unfortunately, all too often, the specter of doing this due diligence is more than people want to embark on. Furthermore, because of all the industry-wide buzz and hype regarding “the Cloud,” people become easily distracted, and end up focusing all of their attention on the Cloud issue.