more than a training manual: using wikis to get everyone on the same page
DESCRIPTION
NACADA Conference - Salt Lake City, 2013 Brian Koslowski & Katie McFaddin, Brandeis University PJ Dickson, Bentley UniversityTRANSCRIPT
More Than a Training Manual:Using Wikis to Get Everyone on the Same Page
Brian KoslowskiKatie McFaddin
Brandeis University
PJ DicksonBentley University
© druclimb, Flickr Creative Commons
Today we will cover…
- the advantages and disadvantages of utilizing a wiki for paperless training
- what resources/skills are required to get started
- how to launch, build, and control access to a wiki
- how this project has evolved over several years
© druclimb, Flickr Creative Commons
• Fast and significant turnover• Weak program and materials for training new advisors• Little formal recording of institutional memory• Information sharing cumbersome, time consuming
© phillacombe, Flickr Creative Commons
“Will I Get a Training Manual?”
What Happens After Training?• Even as established Advisors we found ongoing challenges:
• Complex Internal policies/procedures• Depth of Information
• Things outside the norm• Responsibilities unique to one team member
• Efficiency and Quality Control• Email templates
• Easy Access to Information
© phillacombe, Flickr Creative Commons
- Not eco-friendly- Not easy to link to
resources- Typically one
person’s project -Hard to find info- Immediately dated
- Available online- Free- Can control
access- Content is
searchable - Designed for
group input- Dynamic
Paper WikiX
Why Did We Choose a Wiki?
- Hard to search- Up to date info
exists alongside archived info
- Difficult to access off campus
- Not contextualized or indexical
ServerX
Edit Write Save
Starting our wiki required…- $0- Minimal computer skills- 1 hour delegation meeting- 5-10 hours of individual work
building and populating the pages
Additional page ideas…Staff vacation calendar
Kudos on staff accomplishments
Advisor home contact information
Meeting minutes
Favorable conditions
Collaborative cultureLack of training materials and/or institutional memoryNuanced messaging/policiesInfrequent but involved processesIndependent responsibilitiesNeed to improve quality without sacrificing quantityThreat of turnover
© isdky, Flickr Creative Commons© Orin, Flickr Creative Commons
CollaborativeCentralizedEnvironmentally friendlyEasy to updateHolisticIndependent of a serverCommunal constructivism(Virtual) Community of practiceTrust
Benefits
© Orin, Flickr Creative Commons
ChallengesSome people prefer paperLimited formatting Requires universal involvementRequires frequent updatingInternet-dependentSecurity--we don’t post student data
© karmark, Flickr Creative Commons
We’ve learned that…Pages are born and pages dieSome things are not worth constant updatingSome people are more drawn to the wiki than othersEmail templates are universally loved
© isdky, Flickr Creative Commons
Questions?
© isdky, Flickr Creative Commons