Historically, using legacy software, each major branch of a company could have their own system that met their particular needs. Unlike legacy software, enterprise resource planning (ERP) software requires that the same software be implemented in each branch or office. As a result, now branches must somehow come to agreement on software choices. A number of firms have employed ranking mechanisms where branches or their representatives effectively vote, via their rankings, to determine which software is used. Unfortunately, this can mean the introduction of gaming behavior as branches try to get the software that they think best meets their particular needs. The purpose of this paper is to review some of that gaming behavior and investigate the impact of those behaviors in the ERP requirements analysis process, ERP evaluation process, and with ERP system choice, based in the context of three real world cases.