Introduction: why this action matters for adoption
During change, employees often receive scattered emails, slide decks, meeting notes, FAQs, training links, and policy updates. An online content management system gives people one reliable place to find what is changing, why it matters, what it means for their role, and what action to take next. This matters because communication is a core factor in project success; PMI found that effective stakeholder communication is a crucial success factor and that ineffective communication puts a significant share of project value at risk [PMI, 2013]. (pmi.org)
For change managers, this action is not just a communications tidy-up. It is an adoption support mechanism: a practical asset that reduces uncertainty, equips managers, reinforces consistent messages, and helps impacted groups move from awareness to action.
What this action is and when to use it
An online content management system is a managed digital support channel for change information. It may be a change hub, intranet site, knowledge base, portal page, microsite, or structured folder experience. The key word is “managed”: the system has owners, governance, audience segments, current content, simple navigation, and clear calls to action.
Use it when the change affects multiple groups, spans several weeks or months, creates repeated questions, requires role-specific instructions, or depends on managers and adoption leads using consistent material. Do not use it as a substitute for leadership communication or manager conversations. Prosci’s benchmarking identifies senior leaders as preferred senders for organizational messages and immediate supervisors as preferred senders for personal-impact messages [Prosci, 2022]. Gallup similarly describes manager conversations as the “last mile” of effective change communication [Gallup, 2024]. (prosci.com)
Preparation: inputs, stakeholders, materials, timing, and decisions needed
Start with the adoption outcome, not the platform. Gather the case for change, impacted groups, role impacts, milestone dates, training requirements, policy changes, support routes, known resistance themes, and approved key messages. GOV.UK content guidance advises that content should meet valid user needs and be based on actions or tasks, which is especially useful during change because people are usually asking, “What do I need to do?” [GOV.UK, n.d.]. (gov.uk)
Involve the sponsor, change manager, communications lead, people managers, adoption leads, SMEs, HR or legal reviewers where needed, IT platform owners, accessibility support, and a small sample of impacted users. Before launch, decide who owns the site, who approves content, how often it is reviewed, what is personalized by audience, what is searchable, what is archived, and which analytics will be monitored. The U.S. Department of Labor recommends mapping planning, publication, updating, and retirement workflows so teams know who is involved and where bottlenecks may occur [U.S. Department of Labor, 2023]. (dol.gov)
Step-by-step facilitation guide
Define the audience and adoption tasks. Facilitate a working session with the project team and representatives from impacted groups. For each group, write the task they must complete, the question they are likely to ask, and the decision or behavior the change requires.
Design the content structure around user needs. Avoid organizing the site around project workstreams unless users think that way. A practical structure is: “What is changing,” “What it means for me,” “What I need to do now,” “Training and support,” “Manager toolkit,” “FAQs,” and “Latest updates.” This reflects task-based content design guidance [GOV.UK, n.d.]. (gov.uk)
Create a message hierarchy. Put the essential message first: why the change is happening, why now, what is changing, who is affected, what action is required, and where to get help. Prosci recommends answering the “why” early and equipping preferred senders with aligned messages [Prosci, 2022]. (prosci.com)
Write in plain language. Use short headings, direct verbs, visible dates, and clear calls to action. Digital.gov’s plain language guidance emphasizes creating, designing, and testing content so the intended audience can understand it [Digital.gov]. (digital.gov)
Build governance before publishing. Assign an owner to every page. Add “last reviewed” dates. Create a rapid update path for urgent changes and a retirement rule for outdated content. This prevents the hub from becoming a stale archive [U.S. Department of Labor, 2023]. (dol.gov)
Test with real users. Ask employees and managers to find three things: what changes for them, what they must do next, and where to get help. Watch where they hesitate. Test search terms, mobile access, permissions, and accessibility. WCAG 2.2 provides current recommendations for making web content more accessible and usable across devices [W3C, 2024]. (w3.org)
Launch through human channels. Ask sponsors and managers to introduce the hub in meetings, not only by email. McKinsey’s transformation research highlights the importance of engaging employees and line managers, including line-manager briefings and cascaded communication [McKinsey, 2017]. (mckinsey.com)
Monitor, adapt, and reinforce. Review analytics, questions, sentiment, training completion, and adoption data weekly during high-change periods. Update content based on what people are searching for, misunderstanding, or avoiding.
Example: how this could be applied in a real change initiative
A company rolling out a new HR case management system creates a change hub six weeks before go-live. Employees see a simple page explaining what will change, when to stop using email requests, and how to submit a case. Managers get a separate toolkit with team talking points, a five-minute meeting script, and FAQs about escalations. HR service agents get role-specific process guides and known-issue updates. After launch, the change team notices repeated searches for “urgent payroll issue” and adds a visible decision guide. This turns the hub from a static announcement site into an adoption support tool.
Roles and responsibilities
The change manager facilitates the design, keeps the hub aligned to adoption risks, and reviews insights from analytics and feedback. The sponsor owns the case for change and reinforces the hub as the source of truth. People managers personalize the content in team conversations. Communications ensures clarity and channel alignment. SMEs verify accuracy. IT manages access, search, and technical reliability. Impacted employees test whether the content answers real questions.
Common mistakes to avoid
The most common mistake is building a link library instead of a decision-support channel. Another is publishing everything for everyone, which forces employees to interpret what applies to them. A third is allowing outdated FAQs, duplicate files, or conflicting versions to remain online. Also avoid relying on self-service alone: Prosci, Gallup, and McKinsey all point to the importance of leaders and managers in helping people interpret change [Prosci, 2022; Gallup, 2024; McKinsey, 2017]. (prosci.com)
Measures of success or adoption indicators
Measure whether the system helps people act. Useful indicators include visits by impacted group, repeat visits before key milestones, failed search terms, top questions, content freshness, manager toolkit downloads, training registrations, support ticket themes, pulse-survey confidence, and completion of required adoption behaviors. Pair content analytics with business adoption metrics, because page views alone do not prove behavior change. PMI’s emphasis on business-benefit communication is a reminder to connect communication measures to project outcomes [PMI, 2013]. (pmi.org)
Checklist for the change manager
The hub has a named owner and update cadence.
Each page has an audience, purpose, owner, and review date.
Content answers: why, why now, what changes, what it means for me, and what to do next.
Managers have tailored talking points and FAQs.
Content is written in plain language and tested with users.
Accessibility, mobile access, permissions, and search have been tested.
Outdated content has a retirement process.
Feedback routes are visible.
Analytics and adoption indicators are reviewed regularly.
Sponsors and managers actively point people to the hub.
Optional reusable page outline
Page title: What [change] means for [audience]
Last reviewed: [date]
Who this is for: [role/team/location]
What is changing: [plain-language summary]
Why this is happening now: [business reason]
What you need to do: [action, deadline, link]
What support is available: [training, manager, help desk, office hours]
Common questions: [top five]
If you disagree or need help: [feedback/escalation route]
Owner: [name/function]
References
Prosci. “Communications Checklist for Change Management.” Published October 27, 2022; updated August 5, 2025. https://www.prosci.com/blog/communications-checklist-for-change-management
McKinsey & Company. “The people power of transformations,” within “The science behind successful organizational transformations.” February 10, 2017. https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/successful-transformations
Gallup. “Disruptive Change Is Hitting Leaders and Managers Hardest.” May 23, 2024. https://www.gallup.com/workplace/645152/disruptive-change-hitting-leaders-managers-hardest.aspx
Project Management Institute. “The Essential Role of Communications.” May 2013. https://www.pmi.org/learning/thought-leadership/pulse/essential-role-communications
GOV.UK Content and Publishing Guidance. “Identify user needs.” Date not stated. https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/plan-manage-content/identify-user-needs/
U.S. Department of Labor. “Content governance: lightweight practices your team can adopt now.” May 8, 2023. https://www.dol.gov/agencies/eta/ui-modernization/use-plain-language/content-governance
Digital.gov. “Plain language guide series.” Date not stated. https://digital.gov/guides/plain-language
World Wide Web Consortium. “Web Content Accessibility Guidelines (WCAG) 2.2.” W3C Recommendation, December 12, 2024. https://www.w3.org/TR/WCAG22/