
Building a Community of Student Employees
Added by the EDUCAUSE Librarian
Professional Development
Building a Community of Student Employees
Does any higher education IT organization not hire students? Making them full participants in the IT community yields optimal results
At every turn, we hear that higher education IT units have more to do and fewer resources with which to do it. "Funding IT" remained the number one IT-related issue reported in the annual EDUCAUSE Current IT Issues Survey,1 and no one is surprised. The economic pendulum sweeps back and forth, but rarely has the top of the sweep provided adequate resources to maintain current services, upgrade critical infrastructure, and plan for and implement new technologies. Exemplary stewardship has always required that IT leadership leverage limited resources to meet the needs of the institutional community. Complementing the need to leverage resources is the academic community’s role in providing both academic and workplace learning opportunities and financial assistance to students—who traditionally work part-time, receive lower salaries, and generate fewer overhead costs than their full-time staff counterparts. Many other benefits, besides economic ones, accrue to hiring students. Jason Brown covered a number of these in the EQ article "Student Employees: Can Campus IT Departments Live Without Them?"2 It is not surprising, therefore, that IT departments have a long history of hiring students. The department, institution, students, and users benefit most from this practice when student employees are woven into the fabric of the IT community as full participants. By this I mean that they are treated as any other employee—with job descriptions, performance reviews, training and professional development, and a clear path for growth and promotion. Ronald Barden suggested that "Treating student workers the same as any other university employee is a win-win situation for students and the institution" in the EQ article "They Are Employees, After All!"3 Of equal importance, student employees should have the opportunity to contribute their ideas and expertise to decision making in the community. Individuals who share space, interests, and values and interact with each other build a community when they share a vision, respect each other, communicate clearly, and work as a team. The students hired do not automatically become a homogeneous group of like-minded individuals with good interpersonal skills and experience in working with others. They will need some help to get there. How can an IT department inject community building into all phases of a student employment program? They Are All StudentsAll student employees are first and foremost students, no matter their status (undergraduate, graduate, nontraditional) or the job for which they were hired. According to the EDUCAUSE Core Data Service results for 2002 and 2003, about 66 percent of IT student hires support the Help Desk, Desktop and User Support, and Instructional Technology and Student Computing. The remaining 34 percent spread over 9 other categories of support.4 From my own observation, nearly every unit of an IT department can benefit from adding students to the staff. Tech-savvy consultants can provide network infrastructure support. Programmers and Web developers can support a variety of short- and medium-term projects. Technical writers help develop documentation and training materials and assist the communications office with public relations and marketing collateral. General office, data entry, and financial processing skills are needed by the administrative units. A graphic artist can support the work of multiple units. Some of these roles might be complex enough to require more seasoned skills than the traditional undergraduate pool can supply. Fortunately, many IT departments have a wealth of expertise and energy available from graduate and nontraditional students who have the necessary experience and skills. Adding graduate and nontraditional students to a work group also adds a natural layer of mentors and role models for undergraduates. Graduate library science students, for example, can be exemplary employees in Web development because they understand information, information architecture, and technology and are service-oriented. They might also bring teamwork experience and workplace skills. And, they can be natural allies in efforts to build community. Finding FundingIT departments can find many ways to leverage limited funds through the judicious use of work study, cooperative agreements, graduate assistantships, and internships. Understandably, though, most student hires will be funded from the general IT budget. Other funding sources may have special circumstances. Funding from a student technology fee, for example, might be limited to specific student services. Work-study programs provide federal funds for salaries only. Students qualify for a certain amount of funding, and when that funding has been spent, alternate funds must be found to keep them on the payroll. Many colleges and universities provide a percentage of graduate assistantships for non-teaching/non-research positions and make them available to service units across the campus. Another option provides an internship where the student earns academic credit for IT work or is paid a salary. Cooperative agreements and other creative funding options depend on the specific situation. They are almost always based on collaboration and pooled resources, and, typically, they require more of a manager’s time than other positions. Once an IT department has secured funding, the position must be approved. Then the manager can recruit and interview potential student hires. HiringThough some of the paperwork and time needed to hire a student employee might seem onerous, a good hiring process clearly specifies the job’s duties and the skills and experience necessary to succeed in the position. It also clarifies the manager’s responsibilities for supporting the position. Just as for a full-time hire, consider the justification, funding source, position description and qualifications, reporting structure, hours and duration of work, salary ranges and promotion paths, work environment (facilities and equipment), opportunities for professional growth, and recruitment plan. Prospective student employees have the same considerations, although from their own perspective. Compensation and promotion opportunities for student employees must be equitable across the department and support professional development. Many rewards are possible besides a paycheck. In my experience, the most important reward is learning to work in a team environment with seasoned IT professionals. Close behind is the technical experience gained, enabling student employees to add knowledge and experience to a résumé. The recruitment process provides the first opportunity for community building. The interview is a two-way communication for developing basic expectations between the manager and the prospective employee. Active listening always helps to confirm expectations of the position and qualifications. Allow plenty of time to respond to the candidate’s questions. Provide a tour of the work environment. Introduce other team members and describe their roles in the group and how the candidate will fit into the group if selected for the position. Make the position’s role in the group a focus throughout the recruitment process. Policies and GuidelinesOnce hired, students can be integrated into the fabric of the existing unit or, if this is a new venture, transformed into a community that works as a team and cares about the work to be done. To help them do this, student employees need a framework that describes their relationships within the work community. The institution’s policies and guidelines for student employment should be posted online for hiring managers and student employees to reference. Items may include requirements for various job descriptions, grievance procedures, ethical conduct guidelines, and a definition of appropriate work, including skill expectation levels and maximum weekly time commitments. Departmental policies and guidelines should drill deeper into the relationships with student employees, perhaps outlining hiring, administrative, and related procedures. They may specify frequency of performance appraisals and policies for frequency and levels of pay raises. They may mandate customer service, diversity, or other on-the-job training and orientations for new hires. Additional guidelines might concern communication procedures, channels of authority, time and attendance, technical training, logical consequences for poor performance or inappropriate behavior, and, for some units, dress standards. Students might find such policies and guidelines bureaucratic or otherwise inhibiting to their creativity. Consider using positive statements instead of negative ones. If the item could seem arbitrary to a student, indicate the value that supports it. Few people want to work where the guidelines are all about what one can’t do or seem unconnected to the job. Guidelines and policies can go into a student employee handbook that addresses other elements of the work community. Office supplies, microwave and refrigerator rights, personal storage space, earphones and speakers, tips for getting along with others, and procedures to resolve conflict are just a few issues to include. The handbook can reference institutional and departmental policies and guidelines wherever applicable. Most student employees will welcome the opportunity to review and comment on handbooks. Schedule time with student staff, at least once a year, to review and update the handbook. They may volunteer to craft new sections or propose revisions to an existing one. A blog might complement the static handbook. A Common Vision and
|