This blog post over at 37 Signals about the preoccupation with the number of features in software development made us think of the flip side: the allure of a multitude of features in purchasing software for a firm. Rather than focusing on benefits to the users, we are guilty of tallying up the features added since the last release. Other pitfalls include:

Different features appeal to different constituencies. When looking at putting software on everyone’s desk or expensive enterprise applications, justifying the large expenditure means getting majorities on management committees to sign off. So we play to our audience, touting different features to different principals to get them to sign-off on the purchase.

Even incredibly smart people fall for the “more is better” argument. Quantity is viewed as value when the price is similar. That value is completely lost if the software becomes too complex or confusing to use. Microsoft’s latest release of Office is notable for its rethinking of the interface after market testing found that users were requesting “new features” that were already in the software but hidden behind menus.

The devil is in the details. Next to lawyers and politicians, sales people are great parsers—saying less to portray the product as delivering much more. Once in users hands, features that looked great on the spec sheet and the tightly scripted demo do not work as promised or their benefits are not as great as expected.

The end result is usually confusion and never-ending calls to the help desk. As consultants, administrators and IT managers, we have to manage the purchasing decision much better. We must frame the purchasing discussion around critical features, not an accounting of a myriad nice-to-have ones. Software purchasing decisions should focus on benefits to the firm rather than appealing to building coalitions through feature-“pork.”