Skip to main content

How to Set Up a Change Help Desk That Supports Employees Through Adoption

Set up a change help desk to give employees a clear support path during adoption. Define scope, intake, triage, escalation, knowledge base, and manager roles, then review trends to fix issues, update training, and improve the change plan.

Introduction: why this action matters for adoption

A change help desk gives employees somewhere reliable to go when the new process, tool, policy, structure, or behavior becomes real in their work. That matters because change management is not only the announcement of a future state; ACMP defines change management as the application of processes, tools, and techniques that help individuals or groups transition from current state to future state so business outcomes are achieved [ACMP, 2012]. (cdn.ymaws.com)

This action sits in governance, planning, and operating model design. It defines how support demand will be captured, triaged, answered, escalated, measured, and fed back into the change plan. Prosci’s ADKAR model is useful here because employees may be blocked at different points: awareness, desire, knowledge, ability, or reinforcement [Prosci ADKAR, n.d.]. (prosci.com)

What this action is and when to use it

A change help desk is a structured adoption support mechanism. It may include a mailbox, ticket queue, chat channel, hotline, floorwalkers, super-user network, office hours, searchable FAQ, and manager escalation route. The key is not the channel; it is the operating agreement behind it.

Use it when the change affects daily work, has many impacted employees, creates repeated “how do I?” questions, introduces compliance risk, or requires behavior change after go-live. GOV.UK guidance on user support recommends planning enquiry types, demand, staffing, service levels, and performance measures, and using support feedback to improve the service [GOV.UK Service Manual, n.d.]. (gov.uk)

Preparation: inputs, stakeholders, materials, timing, and decisions needed

Before launching, gather the change impact assessment, role-by-role process maps, training materials, known risks, go-live calendar, escalation contacts, and adoption success measures. ACMP identifies change impact, readiness, stakeholder engagement, training, coaching, resistance management, and performance measurement as core change management knowledge areas [ACMP, 2012]. (cdn.ymaws.com)

Decide who owns the queue, which issues the help desk can resolve, which issues go to project, HR, IT, legal, operations, or sponsors, and what service levels are realistic. Service desk practice commonly uses a central point of contact, request handling, knowledge management, reporting, and SLA concepts; adapt these for adoption support rather than copying an IT incident model wholesale [IBM, n.d.]. (ibm.com)

Step-by-step facilitation guide

  1. Define the support purpose. Facilitate a 45-minute decision meeting with the sponsor, change lead, project lead, operations owner, and service owner. Agree whether the desk is for questions, issues, access problems, policy interpretation, resistance signals, or all of these.

  2. Segment impacted users. Separate audiences by role, location, manager, shift, system access, and risk level. This supports targeted help, which aligns with PMI’s guidance to measure and understand stakeholder readiness, attitudes, and capability [PMI, 2015]. (pmi.org)

  3. Design intake and triage. Create categories such as “how-to,” “defect,” “process exception,” “policy concern,” “training gap,” “manager escalation,” and “resistance or sentiment.” This prevents the help desk from becoming an unstructured complaint inbox.

  4. Set decision rights. State what agents may answer immediately, what needs subject matter expert review, what requires sponsor decision, and what must become a formal change request.

  5. Build the knowledge base. Start with the top expected questions, role-based job aids, “day one” scenarios, and known workarounds. ATD emphasizes making relevant tools and resources widely available and removing on-the-job barriers to change outcomes [ATD, n.d.]. (td.org)

  6. Prepare managers. People managers should not be bypassed. Prosci’s CLARC roles position managers as communicators, liaisons, advocates, resistance managers, and coaches [Prosci CLARC, 2021/2025]. (prosci.com) Give managers a separate escalation path, scripts, and trend reports.

  7. Launch with clear expectations. Tell employees when to use the desk, what response time to expect, what information to include, and how urgent issues are handled.

  8. Review trends and act. Hold daily reviews during go-live, then weekly reviews during stabilization. CIPD notes that effective employee voice depends on complementary channels, leadership support, and managers listening and acting on feedback [CIPD, 2026]. (cipd.org)

Example: how this could be applied in a real change initiative

A company implementing a new expense approval process launches a help desk two weeks before go-live. Before launch, the team identifies likely questions: delegation rules, mobile receipt capture, approval thresholds, and what happens to in-flight claims. During the first week, tickets show that field employees understand the policy but struggle with mobile uploads. The change lead adds a two-minute video, updates the FAQ, asks managers to reinforce the upload steps in team huddles, and escalates a usability defect to the product owner. This turns help desk data into adoption action, not just issue closure.

Roles and responsibilities

Role

Responsibility

Sponsor

Defines success, removes barriers, and approves decisions that affect policy, scope, or operating model. Prosci says sponsors help define success and align stakeholders on measurable outcomes [Prosci Success, n.d.]. (prosci.com)

Change manager

Designs the help desk operating model, reviews adoption trends, and adjusts the change plan.

Help desk lead

Manages intake, triage, service levels, reporting, and knowledge base quality.

Subject matter experts

Resolve complex questions and approve standard answers.

People managers

Coach employees, surface local barriers, and reinforce the change in team routines [Prosci CLARC, 2021/2025]. (prosci.com)

Adoption leads or super users

Provide peer support, test job aids, and identify recurring workflow friction.

Common mistakes to avoid

  • Launching a mailbox without ownership, triage categories, service levels, or escalation rights.

  • Treating every issue as a communication problem when the root cause may be process design, training, workload, access, or resistance.

  • Bypassing managers; this weakens coaching and local sense-making.

  • Measuring only ticket closure while ignoring adoption, proficiency, sentiment, and recurring barriers.

  • Keeping feedback inside the help desk instead of feeding it into project decisions and continuous improvement.

Measures of success or adoption indicators

Use a balanced view. Operational indicators include ticket volume by category, response time, resolution time, first-contact resolution, backlog age, repeat issues, knowledge base usage, and unresolved escalations. Adoption indicators include training completion, role readiness, confidence, usage, compliance with the new process, proficiency, error rates, cycle time, and rework. Prosci describes adoption measures such as speed of adoption, ultimate utilization, and proficiency [Prosci Success, n.d.]. (prosci.com) PMI recommends measuring before, during, and after change so leaders can identify barriers to benefit realization [PMI, 2015]. (pmi.org)

Checklist for the change manager

  • Confirm the help desk purpose and scope.

  • Identify impacted audiences and likely support demand.

  • Define channels, hours, service levels, and escalation rules.

  • Create triage categories and standard response templates.

  • Prepare SMEs, managers, adoption leads, and sponsors.

  • Publish employee instructions and manager guidance.

  • Review trends at a fixed cadence.

  • Convert recurring issues into actions: better job aids, process fixes, sponsor decisions, or reinforcement.

Optional reusable template: change help desk operating agreement

Field

Working decision

Purpose

What adoption problem is this help desk solving?

Audience

Which roles, teams, locations, or employee groups are in scope?

Channels

Email, ticket portal, chat, hotline, office hours, floor support, manager escalation.

Categories

How-to, access, defect, policy, exception, training gap, resistance, enhancement.

Service levels

Initial response target, resolution target, urgent escalation rules.

Decision rights

What can agents answer, what needs SME approval, what needs sponsor approval?

Reporting cadence

Daily during go-live; weekly during stabilization; monthly during sustainment.

Success measures

Operational support metrics plus adoption, proficiency, behavior, and benefit indicators.

References

Related Articles
Did this answer your question?