1. POWERED BY: A Successful Adoption Of Technology #NPPROTGC Ron Marzitelli Assistant Vice President of Information Technology School of Business & Technology, Excelsior College

2. POWERED BY: Ron Marzitelli Successful Adoption of Technology July 21, 2015 #NPPROTGC

3. POWERED BY:  Common Mistakes when Selecting Technology  Determining Business and Technical Requirements  Getting it Done  Governance  Questions and Answers Agenda #NPPROTGC

4. POWERED BY:  Business Requirements [need] not well defined  “Saw this great new application – can we use it here?”  “If you build it they will come.”  Technical Requirements not aligned with business requirements  “I want to get this software to do…”  “Everyone is using this shouldn’t we?”  Not an inclusive process  “We know nothing about that application”  “We’re not using that application!” Common Mistakes when Selecting Technology #NPPROTGC

5. POWERED BY: Modern Analyst. (2010). On the Edge of Business Analysis. Retrieved July 11, 2025 from https://stassoul1.wordpress.com/ #NPPROTGC

6. POWERED BY:  Have an existing process that works? – use it  Lead by the functional area(s) with IT involved  Define the business need understanding the organization’s  Vision  Mission  Business objectives  Identify key stakeholders (inclusive process) Determining Business Requirements #NPPROTGC

7. POWERED BY:  Interview stakeholders  Compile different perspectives to get the big picture  Prioritize the requirements (funding)  Change impact analysis  Seek consensus with other functional areas  Achieve clearly defined business needs Determining Business Requirements #NPPROTGC

8. POWERED BY:  Translate business requirements into technical solutions  Lead by IT but functional area(s) involved to  Know your IT shop’s capabilities  Ensure IT understands the business processes and procedures  Identify key stakeholders (inclusive process) Determining Technical Requirements #NPPROTGC

9. POWERED BY:  Must align with the business requirements  Ownership must be defined  Clearly defined technical requirements with measurable goals  Tip: Conduct demonstrations, a prototype or pilot Determining Technical Requirements #NPPROTGC

10. POWERED BY:  Resources  Business analyst  Project manager  Designate an executive sponsor or champion  Establish a committee or task force  Conduct interviews of stakeholders  Document the requirements  Tip: Create a Request for Proposal Getting it Done #NPPROTGC

11. POWERED BY:  Establish clear roles and responsibilities for determining requirements  Involve all who will be impacted by the technology from the start to receive buy in  Seek feedback  Surveys  Focus groups  Governance groups or councils Governance #NPPROTGC

12. POWERED BY:  Provide timely communication to all stakeholders  Changes in scope  Changes with requirements  Establish metrics  ROI  Success measures  Tip: Maintain governance for the entire life cycle Governance #NPPROTGC

13. POWERED BY:  Ensure the business drives technology acquisition  Identify the business need before considering the technical solution  Develop well defined business and technical requirements  Make the process inclusive  Build in success measures and accountability Take Away #NPPROTGC

14. POWERED BY: Questions and Answers #NPPROTGC