ALYSSA M. WECHSLER, M.PHIL. HUMPHREY COSTELLO, M.A. WYOMING SURVEY & ANALYSIS CENTER AT THE UNIVERSITY OF WYOMING ANNUAL CONFERENCE OF THE AMERICAN EVALUATION ASSOCIATION NOVEMBER 4, 2011 ANAHEIM, CA A Web Tool for Collecting County-Level Program Implementation Data for State- Level Evaluation
2 What to Expect The benefits of web-based reporting systems Steps for building a web-based reporting system Lessons learned from WYSAC’s system, PAPR Discussion
3 What to Expect The benefits of online reporting systems Steps for building a web- based reporting system Lessons learned from WYSAC’s system, PAPR Discussion
4 What to Expect The benefits of online reporting systems Steps for building a web-based reporting system Lessons learned from WYSAC’s system, PAPR Discussion
5 What to Expect The benefits of online reporting systems Steps for building a web-based reporting system Lessons learned from WYSAC’s system, PAPR Discussion
Wyoming’s Needs Guidance for Program Managers 6
Wyoming’s Needs Guidance for Program Managers 7 Goals, outcomes, indicators What gets measured gets done
Wyoming’s Needs Guidance for Program Managers 8 Goals, outcomes, indicators What gets measured gets done
Wyoming’s Needs Evaluation and data collection tool 9
Wyoming’s Needs A response to the changing political and economic environment 10
11 Benefits of Web- Based Systems A complex approach to a complex system Activity Outcome Goal
Benefits of Web- Based Systems A complex approach to a complex system 12
13 Graphic Representation of WYSAC Tobacco Evaluation Website Website Visualizer Application, Benefits of Web- Based Systems A complex approach to a complex system
Benefits of Web- Based Systems A complex approach to a complex system 14
Benefits of Web- Based Systems 1. Ease and consistency of data collection 2. Guidance for Program Managers 3. Ease of data management 15
Benefits of Web- Based Systems Ease of data compilation and reporting 16
17 Building a Web-Based Planning and Reporting System Lessons Learned 1. Identify needs 2. Identify users, user needs, and user roles 3. Build static mock-ups and flat files 4. Allow for repeated beta group input 5. Provide training for users o Identify needs early to avoid mission drift
18 Lessons Learned 1. Identify needs 2. Identify users, user needs, and user roles 3. Build static mock-ups and flat files 4. Allow for repeated beta group input 5. Provide training for users o Identify needs early to avoid mission drift Building a Web-Based Planning and Reporting System
19 Building a Web-Based Planning and Reporting System Lessons Learned 1. Identify needs 2. Identify users, user needs, and user roles 3. Build static mock-ups and flat files 4. Allow for repeated beta group input 5. Provide training for users o PAPR is not the same as paper! o Identify needs early to avoid mission drift
20 Building a Web-Based Planning and Reporting System Lessons Learned 1. Identify needs 2. Identify users, user needs, and user roles 3. Build static mock-ups and flat files 4. Allow for repeated beta group input 5. Provide training for users o Identify needs early to avoid mission drift o PAPR is not the same as paper! o Be prepared to invest lots of time and multiple iterations
21 Building a Web-Based Planning and Reporting System Lessons Learned 1. Identify needs 2. Identify users, user needs, and user roles 3. Build static mock-ups and flat files 4. Allow for repeated beta group input 5. Provide training for users o Identify needs early to avoid mission drift o PAPR is not the same as paper! o Provide training but also build system to stand alone o Be prepared to invest lots of time and multiple iterations o Provide training but also build system to stand alone
Discussion 22 Questions? What are we missing? What are you dealing with? Do you think an online planning/reporting system would be useful for you? How could we improve PAPR?
Contact Information Wyoming Survey & Analysis Center Alyssa M. Wechsler Assistant Research Scientist (307) Humphrey Costello Assistant Research Scientist (307)