Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

TCPR Sub-committee Communication Plan

...

Table of Contents
minLevel1
maxLevel1

Introduction

Purpose

This plan identifies stakeholder groups, key messages, goals/objectives, and communications tools that will be used to ensure that information related to the CLSP implementation of Alma and Primo VE systems is shared in a timely, accurate, and effective manner with external stakeholders. It also establishes a formal comprehensive plan for communications to stakeholders.

The purpose of this plan is to define how and what the TCPR Sub-committee will communicate to core and external audiences surrounding implementation of the new, next-generation ILS.

[below from Terms of Reference - incorporate?]

Supports the Project Management Office in providing communication about planning and implementation of the library services platform ensuring information is appropriately distributed to all staff who need to be informed within each library. For example:

  • Support the writing of communication needs of the project whenever possible

    • Recommend and review communications for the PMO to ensure we are using the voice of participating libraries.

Scope

This plan addresses the communication role & responsibilities of the TCPR Sub-committee, according to the CLSP Communications Framework - is only to external stakeholders

...

  • Ensure stakeholders at all levels receive accurate, timely, and useful information about the process and outcomes

  • Ensure that the information library and IT staff receive correctly shapes their understanding of and preparation for implementation at their institution and ensure appropriate lead time for local preparation

  • Ensure stakeholders’ expectations are realistic by shaping Day 1 and long-term vision (focusing on a shared platform developed with best practices, quality, and efficiency in mind)

  • Articulate milestones and accomplishments; share big-picture road map

  • Communicate success stories, recognizing the contributions of people and teams

  • Provide opportunities for discussions across all levels

  • Ensure that communication is effective by soliciting feedback from stakeholders

For External Stakeholders

  • Build acceptance of the new platform by reinforcing benefits, flexibility, and thoughtful planning – and by underlining that the driving force in making decisions is based on the needs of students and staff, and enhancing capacity for collaboration across college libraries.

...

Communication Tools/Channels

Communication tools/channels for each stakeholder group have been identified below. A variety of tools will be used to ensure communication is distributed effectively. New or improved methods of communication will be incorporated when identified.

External – for TCPR Committee to determine

  • [Example] Library and higher education conferences and publications

  • [Example] Talking points [think of better name] for internal staff to allow them to speak with consistency regarding naming conventions, expectations about system functionality, and the process for managing user feedback. [Example] Develop template, schedule, and method for distributing regular updates to library staff and administrators. The current recommendation is to develop a monthly update in the form of a “newsletter” to be emailed to the MCLS and the LIBS_ALL discussion list, providing a summary of current progress and updates from the Working Groups, along with updates on implementation milestones/timeline, training opportunities, feedback/testing opportunities, and a clear path for users to submit feedback and ask questions. This information will also be made available on the Next-Gen ILS section of the FALSC website.

  • [Example] Identify opportunities to leverage existing social media messaging platforms and campaigns

Process

All communications to be reviewed by ISC?

Communication Activities and Timelines

...

Overview by Phase

Dates and activities are subject to change based on needs of the project.

...