Not all institutions have the human resources and technological know-how to buy software that fits into their existing ecosystem. The process for procurement is fraught with challenges. It can be vendor-driven where institutions do not have a proper roadmap and strategy for how they are purchasing software. In addition, once the need has been identified, success depends on which stakeholders are involved and when in the process they are brought in, as well as how the institution plans (or does not plan) to measure the success of the implementation. The result is institutions sometimes end up with software that does not meet their needs.
We mapped the current technology procurement process at post-secondary institutions and overlayed any gaps we identified that are important in helping procure the right solutions. To do this, we took a deep look at the different triggers that initiate the software-purchasing process, the motivations of the stakeholders, the involvement (or lack thereof) of necessary departments such as IT in the process, taking into account the proposal process i.e. RFP vs Direct Purchase.
We then created an example of an ideal process by including the missing steps to be considered in order to ensure success.
The result was a procurement process map that serves as a guide for institutions to avoid common pitfalls that lead to procuring software that either does not integrate well with their existing solutions or does not work well to meet the needs of the intended users.