- Acknowledge that there still needs to be good processes in place regardless of the technology solution chosen. -The next critical step is to write down and note the problems that need to be solved. -Create a list of the solutions and see which one best solves the problem or most of the problems. - Look at ease of use for respective solutions, as difficulty to use software is usually a hinderance for users and reduces buy-in. - Ensure that all users and stakeholders are part of the process all the way and that there is open dialogue about the items listed above. - Understand that no software is perfect, so the choice may be one that is 80% there, with providing the solutions needed (and doesn't perform some non-critical functions)

Our approach would have been somehow similar to this. Additionally we would be considering few things before introducing tech into the system. 1. Brainstorming case studies and comparing use cases with the stakeholders for outlining scope of work. 2. Carefully comparing the long term advantages between a 3rd party technology solution and a custom developed technology based on use case. 3. A technology demonstration should be there for the key persons. 4. And finally we would have gone for testing.

I want to start with questions for the team. I expect a lot from collective intelligence. 1. What frictions in processes are wasting valuable time? AI and technology in general solve process problems. 2. What technologies have our partners found useful? Are they getting value that we have not even imagined? 3. What technologies will help us take limited resources to grow in size and impact? 4. What technologies will reduce data silos so that we have better analytics? 5. Which technologies are more intuitive and take less effort to teach new staff? 6. Which technologies are web based and accessible to staff at all sites? 7. Can we quantify time savings, learning, value added and price to compare solutions?