If an organization's requirements conflict with the software package chosen and the package cannot be customized, what must the organization do?

When an organization's requirements conflict with the chosen software package and that package cannot be customized, the best course of action is for the organization to change its procedures. This is because software packages are often designed based on best practices and standardized processes. If the software cannot be tailored to fit the organization’s specific needs, adapting the organization's procedures to align with the software can lead to more effective use and minimize disruption.

By opting to adjust its procedures, the organization typically aims to leverage the built-in efficiencies of the software and ensure that it can still meet its operational goals, albeit in a slightly different manner than initially planned. This not only preserves the investment in the software but also allows the organization to standardize operations around the chosen solution, which can enhance overall productivity and reduce training needs.

The other options, such as outsourcing development or redesigning the RFP, are generally more resource-intensive and complex. Outsourcing development might involve significant costs and time in creating a tailored system, while changing the evaluation process or redesigning the RFP would not address the immediate conflict with the chosen software and could lead to delays in implementation. These alternatives typically wouldn't provide a practical solution if the software is already in place and the organization's goal is to achieve effective usage without incurring additional expenses