The Evolution of Business Intelligence at SPC: One Year Later January 2013 Florida Association of Institutional Research Annual Conference

January  James Coraggio Associate VP, Institutional Effectiveness, Research, and Grants  Dan Gardner Coordinator, Institutional Research and Reporting Institutional Research and Effectiveness St. Petersburg College P.O. Box 13489, St. Petersburg, FL (727) FAX (727)

January  SPC - established in 1927  9 Campuses in Pinellas County  First FCS college to offer baccalaureate degrees; 1,061 ( ); cumulative 5,179 degrees ( )  FTE: 22,350  Graduates: 6,003  Fall 2012 credit enrollment: 33,232 (unduplicated)

January FAIR presentation 2011 Using Business Intelligence to Improve Student Success %20Business%20Intelligence%20FINAL.pptx

January This presentation will describe: 1)Where we were… 2)Where we are.. 3)Where we will go…

January Two-to-three weeks to complete a data request Discussions became stale Arguments over the data definitions New questions once data is received take another two-to- three weeks to get answered

January SPC exemplified the ‘data-rich, information- poor’ institution. Staff need timely information for decisions to maximize student success. SPC needed to leverage data from across the College by linking multiple data systems and elements in one reporting interface.

January SPC needed: –timely, relevant, and valid information at the college, campus, and program levels, –in an easy-to-interpret format to support evidence-based decision-making, –and drive performance improvement.

January  Step 1: Acknowledge that data in its purest sense is not very useful.  Step 2: Design a tool that defines, aggregates, and organizes the data into useful and relevant information for the stakeholders.  Step 3: Provide end-user training to assist them in correctly interpreting and using information properly.  Step 4: Consistently remind all end-users that data and information can be powerful, but it is only the start of the conversation.

January Allows college employees the ability to quickly access information required to make decisions to improve student success. Designed to provide standardized information to end- users and key stakeholders with the ability to look at data measures through multiple views. Measures can be rolled up and viewed at the aggregate institutional level or an end-user can ‘drill- down’ and view the same data measures at the campus or program level.

January Executive Partnership Development Executive Dissemination Administrative Dissemination Student Success Partnership Refinement Advisor Dissemination Partnerships for Specialized Solutions Staff Dissemination Partnership for Integrated Solutions Innovation TransferRefinement

January Active users, n = 204 New users in process = 60 (primarily academic advisors) Training completed, headcount –Level 1 trained = 175 –Level 2 trained = 82 –Total number of persons trained (level 1 & 2) = 257 Type of users: Executive Team, Provosts, Deans, Program Directors, Functional Administrators, Advisors

January

January Culture of Inquiry We encourage a data-driven environment that allows for open, honest dialogue about who we are, what we do, and how we continue to improve student success. Transparency We embrace openness in communication by providing access to college processes and procedures, expenditures, institutional effectiveness, and student success rates.

January The most important element of the SPC Pulse philosophy has been end-user empowerment.

January Training Schedule, January & February 2013 Level 1; 1/8, 1/25, 2/5, 2/22 Level 2; 1/8, 1/25, 2/5, 2/22 Update for Deans, Deans meeting Advisor Tarpon Springs: 1/25 Update for Associate Provosts: 1/29 Advisor Clearwater: 2/15

January Building competence among executive and academic leaders Managing Accelerated Expectations and Enthusiasm Ensuring security/privacy Documenting while building Limited Resources Tailoring specialized solutions

January More robust cohort data Prediction information (Predictive Analytics) Human Resources data Further developed Finance data

January Resources, Resources, Resources! Leadership support Cross functional development team Financial support for technology/ infrastructure requirements End-user buy in and involvement in the development Managing expectations

January