Considering Your Options

Have a clear understanding of the problem you’re trying to solve before looking at technology. Engage all stakeholders to build consensus around the core issues, and who you are trying to serve before researching technical solutions. This avoids finding solutions in search of a problem, which is often a significant waste of time and money. 

You want to be more efficient and scalable and you understand where you want to improve. By clearly stating your problem, core issue, or business process needing improvement.

Group of people implementing a project

Problem identification / Needs Analysis

  • What problem are you trying to solve? and how will this help solve it?
  • What business process(es) are involved in this problem?
  • Does solving this problem align with the university’s strategic goals?
  • Are there departments with a similar process you can collaborate with?
  • Could existing solutions on campus be adapted to meet your needs?

 

Product selection

  • Is this a major vendor for this type of product? 
  • Is it used outside of higher education, or is it a mainstream solution? 
  • Have you talked to any other hi-ed institutions who’ve successfully implemented this solution?
  • Would you like a technology consultation?
Decorative illustration representing digital content creation, showing three people near a giant desktop computer and mobile device, with puzzle pieces and green leaves in the background.

 

Feasibility / Resourcing Needs

  • Who will administer the solution? 
  • Do you have a dedicated position to administer the solution?
  • Do team members have the capacity to implement and maintain the solution? (don’t trust the vendor estimate)
  • What department involvement is required to successfully implement this solution?
  • What institutional data is required for the solution to work as expected? 
  • Which PSU systems will this solution interact with? 
  • Do you have approval from the data owner or steward to interact with this data?