CONTENT SYSTEM ADOPTION INSTITUTIONAL CONSIDERATIONS Charleen Khane – Sr. Assoc. Dean of Distance Learning & Media Services Eva Smith – CIS Faculty Kevin Shanley – Distance Learning Program Coordinator
Jan 02, 2016
CONTENT SYSTEM ADOPTIONINSTITUTIONAL CONSIDERATIONS
Charleen Khane – Sr. Assoc. Dean of Distance Learning & Media ServicesEva Smith – CIS Faculty
Kevin Shanley – Distance Learning Program Coordinator
Session Focus
• The purpose of this session is to describe an approach for analyzing and determining organizational readiness for Content System adoption.
Session Focus
• We will share:– Methods used by Edmonds Community
College to plan and pilot a Content System adoption strategy
– Lessons learned– Planned next steps based on this
analysis
Approach
• Typical implementation of technology– Turn it on….thud….$$$$….
• Is there a better way?– An ecological approach– Information ecology model
Approach
Approach• Understand organizational ecosystem
– People– Information/Content– Processes and Culture– Tools/Technology Environment
• Understand the “species”– Do “SWOT” Analysis
• Identify Strengths and Weaknesses• Identify Opportunities and Threats
• Determine next steps
Leadership and Change
• External knowledge – Bb Consultants– Content Management Research
• Strategy– Avoid the THUD!!! …. $$$$– Avoid poisoning the environment– Create positive change– Sow the seeds for future success
Institutional Readiness
• Internal knowledge– Focus Groups– Interviews– User Surveys
• Organizational culture– Social and Political Factors– Policies and Practices– People - Spheres of Influence
Policies and Practices
• Content lifecycle– Defined policies– User practices
• Information security– Who has access?– Who manages privileges?
• Content ownership– Consistency of practices
Technology Infrastructure• Technology landscape
– Where content currently resides• Cost benefit analysis
– Data storage models• Local vs. outside (i.e. ASP)
– Traffic & bandwidth• Pilot projects
– Instructional– Institutional
Tools
• Technology (Bb Content System)– Usability testing– Feature & integration testing– Is the tool ready?
• People– Attitudes– Needs– Capabilities
Content Types
• Documents– Word processing, spreadsheets, etc.
• Images, audio & video• Databases• Etc.• Why does this matter?
Content Uses• Content inventory audit
– What exists & why?
• Use cases– Who manages the CRUD– Why & how content is used
• Metadata– Information architecture
• Natural patterns of organization• Labels
– Findability
Phased Adoption
Lessons Learned
• Risk is greater when more are involved• Institutional content management
requires more discipline & structure• Testing the waters is worth the time,
reduces the risk, and identifies the value• Analysis is tool independent• Ask the “why” questions before the
“what” and “how”
Is your ecosystem ready?
• For Us: – We’re proceeding cautiously– Continuing to identify the value of
shared content– It’s evolving…
• Questions?
Thank You!Eva Smith – [email protected]
Kevin Shanley – [email protected] Khane – [email protected]