Upload
leslie-dare
View
153
Download
2
Embed Size (px)
Citation preview
Leslie Dare, Ed.D.Sandy H. JonesEddie Lovett, II, M.Ed. Lisa P. Zapata, Ph.D.
Student AffairsDivision of
Deliberate Technology Planning in Student Affairs: Taming the Tech Tiger
ACPA/NASPA2007 Joint Meeting
Orlando, FLApril 2, 2007
Presentation Agenda
Overviews Technology Administration Survey Why Technology Planning? Process Final Products Implementation of Technology Checklist Results Lessons Learned
Overview
NC State University
Established 1887: Land-Grant Institution 31,000+ students
50 States 99 Countries
8,500+ employees 10 Colleges
Division of Student Affairs
Mission: The Division of Student Affairs provides programs and services for students and the larger community to enhance quality of life, facilitate intellectual, ethical and personal growth, and create a culture which engenders respect for human diversity. It is through these activities that we promote student learning with our principle of “Students First.” 35 Units
600+ Employees
Student Affairs Units & ProgramsParents & Famil ies Services
Women’s Center
Chaplains Cooperative Ministry
University Career Center
ROTC
Upward Bound/Talent Search
University Scholars
Campus Activit ies
Student Health Services
University Housing
Carmichael ComplexFacil i t ies & Operat ions
Wolfcamp
Student Media
Music
Mult icultural Student Affairs
Center Stage/Arts Outreach
Physical Education
Greek Life
Crafts Center
Caldwell Fellows
Student Conduct
Distance Education& Technology Services
University Student Centers
Gallery of Art & Design
Counsel ing Center
University Dining
Dance Program
University Theatre
Student Org Resource Ctr
Health Promotions
Campus Recreation
Research & Assessment
Student Leadership, Ethics& Public Service
TechnologyAdministration
Survey
Technology Administration Survey
Conducted in 2005 by Dare, Zelna, and Thomas 1154 colleges and university (ACPA and NASPA members) 36% response rate Focus on Technology Administration
Planning Practice Staffing Technologies
252
158
0
50
100
150
200
250
300
Does Student Affairs at your institution engage in centralized, formal technology planning?
YES61.46%
NO 38.54%
74
120
74
137
0
20
40
60
80
100
120
140
Identify the option that most closely describes technology leadership for Student Affairs at your institution. (Defined as providing general oversight for technology planning and/or implementation, and serving as a liaison with other institutional technology units.)
Full-TimePosition18.27%
Hat29.63%
Committee18.27%
None33.83%
Type of Technology Leadership
Helps us meet broad goals:
Providing a “seamless integration of technology” is one of our Division Objectives.
Supports our University Vision of an “efficient and effective operational enterprise.”
Why Technology Planning?
Technology has grown and changed faster than our budgets.
Units not budgeting for technology
Funding is scarce for innovations
Our Own Story (probably much like yours!)
Technology has grown and changed faster than our skills.
“Administrative Assistant as webmaster” is no longer sufficient
Need professional technology staff
Our Own Story (probably much like yours!)
Still trying to achieve efficiencies across the Division.
Need for centralized staffing
Need for centralized training
Need for sharing of resources (budgets, personnel, equipment, software licensing, etc.)
Our Own Story (probably much like yours!)
Decision to Engage in Tech Planning Move away from random decisions and actions to
deliberate planning. Provide foundation to guide our decision-making about
technology at the Division level. Provide guidance for departments on the nuts and bolts
on how to plan for technology. Provide structure for existing technology staff roles
(LANTechs and Webmasters).
Our Own Story (probably much like yours!)
Process
People Distance Ed & Tech Services Distance Education/Technology Advisory Group
(DETAG) Department Heads Departmental LANTechs & Webmasters Vice Chancellor for Student Affairs Division of Student Affairs
Process
Information (Final Products) Division Technology Plan Departmental Technology Checklist Other (not our focus today)
Standard Duties for LANTechsStandard Duties for Webmasters
Reminder: All documents available online - see last slide for URL.
Process
Process - Division Technology Plan
Twelve significant versions from first draft to final, approved document.
Started at 2 pages (v.1), grew to 8 pages (v.8), then back down to 3 pages (v.12).
Began December 5, 2003 (v.1); completed August 9, 2006 (v.12)
Process – Tech Checklist
Eleven significant versions from first draft to final, approved document.
Started at 8 pages (v.1), gradual decrease to 4 pages (v.11).
Began February 6, 2006 (v.1); completed February 6, 2007 (v.11).
Implementation ofDepartmental
Technology Checklist
Checklist is the document that each department is required to complete.
Taking it on the road Buy in Accuracy Dialogue
Implementation of Dept. Tech Checklist
Pilot Small unit - Women’s Center Large unit - Student Health Services Result: Revision of Checklist form
Meetings DETS Director DETAG representative Department Director Others as requested by Dept. Director Division Budget Officer
Implementation of Dept. Tech Checklist
Do we have to meet? Some resisted meeting…too bad! Dialog resulted in much richer data
Feedback to the Departments Unplanned: “How do I do X?”and “I wish I could…” Planned: Recommendations based on meeting Planned: Recommendations based on analysis
across the Division
Implementation of Dept. Tech Checklist
Results
Results
Our initial assessment (based on our observations) has been confirmed. Many departments are not satisfied with the status
quo with regard to budget, staffing and support.
Most departments are not engaged in much (if any) tech planning.
Most departments recognize the need to engage in more tech planning.
Lessons Learned
Support and final approval from the Chief Student Affairs Officer is critical.
Have multiple check-points for approval (internal and external).
Solicit involvement from external resources and partners (your campus Information Technology unit, Internal Audit, Student Affairs peers).
Lessons Learned
Consider any institutional-level technology planning that might already be in the works.
Committee approach: diversity is important (geek, non-geek; professional staff, support staff, etc.)
People want their technology to work. We had little resistance to the concept of technology planning.
Lessons Learned
Entering purchased items into a technology “line” in the budget is very different from actually planning in advance for technology in those lines.
Face-to-face meetings created a setting where directors learned more about their technology operations.
Data collected through this process can be helpful later in justifying requests for new technology resources (funding, positions, etc.).
Questions& Answers
Leslie A. Dare, Ed.D.Sandy H. JonesEddie Lovett, M. Ed.Lisa P. Zapata, Ph.D.
Division of Student AffairsNC State UniversityCampus Box 7301Raleigh, NC 27695-7301
[email protected][email protected][email protected][email protected]
• This Presentation and Projecthttp://www.ncsu.edu/student_affairs/techplan/
• Trends in Technology Administration in Student Affairshttp://www.ncsu.edu/student_affairs/naspa05/
• Distance Education & Technology Services (Student Affairs, NC State)
http://www.ncsu.edu/student_affairs/dets/ •Division of Student Affairs (NC State)
http://www.ncsu.edu/student_affairs/