It's All About Support: Strategies for introducing and supporting a course management system on a university campus
Download as PPT, PDF0 likes241 views
The document outlines support strategies for implementing a course management system (CMS) at Wake Forest University, highlighting a successful pilot project with Blackboard's CourseInfo that involved extensive training and faculty engagement. Key lessons learned include the importance of faculty involvement, ongoing training, and providing robust support systems to address resistance. The document also emphasizes that while CMS can enhance educational processes, they may not suit all faculty and should be part of a broader educational technology initiative.
![For More Information Contact us: Roz Tedford: [email_address] Giz Womack: [email_address] Visit our Web Pages http://www.wfu.edu/Library/ITC/training/ Check out BlackBoard’s CourseInfo http://www.blackboard.com/](https://image.slidesharecdn.com/educause2000a-110630130203-phpapp02/85/It-s-All-About-Support-Strategies-for-introducing-and-supporting-a-course-management-system-on-a-university-campus-10-320.jpg)
It's All About Support: Strategies for introducing and supporting a course management system on a university campus
- 1. It’s All About Support Strategies for introducing and supporting a course management system on a university campus. Rosalind Tedford, Information Technology Center Manager, Wake Forest University H. David Womack , Information Technology Specialist, Wake Forest University EDUCAUSE 2000 Nashville, TN October 10 th - 13 th
- 2. Background Early Course Shell Attempt Failure (WFU Template – Lotus Notes Based) Demand for CMS Remained Course Shells Task Force selected BlackBoard’s CourseInfo in December 1998. Pilot Project – Spring 1999
- 3. The CourseInfo Pilot 25 faculty from across the university. Recruited from Template users and through recommendations from Academic Computing Specialists. Included ‘techies’ and ‘non-techies.’ Extensive training classes – 4 hours. Support through listserv. Follow-up meetings for feedback. Huge success – Pilot users recommended we keep CI and move to full implementation.
- 4. Continuing Project CIT agreed to commit to CourseInfo. Web Page set up for links to documents and FAQ. Listserv continued. 250+ faculty have been trained on CourseInfo. 130 classes in Spring 2000, close to 200 in Fall 2000. Branching out into more advanced training. Showcase planned for the fall. Increased use for non-academic projects.
- 5. Lessons Learned: Introducing a CMS to Faculty Start with the Faculty and include them at all phases. Look for ‘early adopters’ in your faculty population and get their buy-in for a pilot project, but include all types of faculty from early on. Expect resistance and prepare for it. CMSs can be a huge benefit to some, burden to others. Training, training, training. Understand the limitations of the product, and be honest with the faculty about them.
- 6. Lessons Learned: Supporting Faculty using a CMS Get the infrastructure in place before the pilot. Training is your best support. Get trusted department to handle training and support. Establish a listserv for users and support personnel. Establish web pages for access to support documents. Allow faculty to encourage and support each other as much as possible. Establish strong relationships with vendor.
- 7. What to Expect from Faculty Resistance Indecision Acceptance Enthusiasm Higher Expectations Greater Demands Disappointment
- 8. Final Thoughts CMSs represent a major rethinking of classroom processes. Respect this. CMSs will not work for every faculty. No one should be required to use them. The availability of training and support should be continually marketed. Not all faculty are ready at the same time to adopt a CMS, so training should be an ongoing option.
- 9. Final Thoughts, cont. CMSs should be one component of an educational technology initiative and can be an incentive for many faculty. Be prepared to work with them on other ways to incorporate technology in their classes when CMS is not the answer. Understand the limitations of your product and work with the vendor to improve the product where possible, and to work with the faculty to find work-arounds for the other areas.
- 10. For More Information Contact us: Roz Tedford: [email_address] Giz Womack: [email_address] Visit our Web Pages http://www.wfu.edu/Library/ITC/training/ Check out BlackBoard’s CourseInfo http://www.blackboard.com/