Leading a Team Through Change

Understand the change first

Before briefing the team, clarify the reason, intended result, scope, decision ownership, timing, and evidence available. Ask sponsors which matters are fixed and which remain open. A manager cannot explain every executive choice, but should avoid filling gaps with confident speculation. Record questions that need an authoritative answer.

Translate the initiative into local work: responsibilities, workflows, customers, tools, interfaces, measures, and current commitments. The same announcement can affect roles differently. Avoid describing the change as merely a mindset issue when people are identifying real dependencies, workload, skill needs, or loss of useful practices.

Communicate boundaries honestly

Tell the team what has been decided, why leaders say it is changing, what is still unknown, and when more information is expected. Distinguish a proposal from a final decision. Repeating an unverified answer to appear composed can create more confusion when it changes. Correct prior information visibly when new facts arrive.

Do not promise job outcomes, workload relief, or implementation details outside your authority. For employment implications, follow formal communication and involve qualified organizational partners. Managers can still be useful by explaining process, documenting questions, arranging access to support, and advocating for decisions the team needs to continue responsible work.

Create real participation

Ask affected employees where the proposed change conflicts with actual work, customer needs, controls, or dependencies. Invite alternatives within the stated boundary. Participation is credible when people know which decisions their input can shape and later hear how that input was used, declined, or deferred.

Make several routes for feedback available where practical, since a large meeting will not surface every concern. Managers should not label disagreement as a personal inability to change. Examine the substance and distinguish an implementation risk, missing information, competing interest, and refusal to follow a legitimate final decision under policy.

Guide transition through evidence

Maintain a simple change log covering decisions, owners, impacts, risks, training, support, and unresolved questions. Review it with the team as work progresses. Pilot or stage reversible elements where appropriate, but do not present every change as an experiment when people have no choice about the final direction.

Watch operational evidence and employee feedback without claiming a universal emotional journey. Different people may respond differently for valid reasons. Adjust implementation when evidence supports it, explain retained decisions, and recognize additional work. After stabilization, review what the team learned and which temporary controls or meetings can now end.

Introduce a new case-management system

A service team must adopt a new system, but the workflow design and migration sequence can still change.

1. Explain the confirmed platform decision, intended operating need, known timing, and the workflow and sequence choices that remain open.
2. Map current case handling with frontline staff and identify customer, privacy, handoff, and data-quality risks requiring owner review.
3. Use a limited workflow rehearsal to gather evidence, record unresolved decisions, and revise training and migration support.
4. Publish decisions and reasons, correct changed information, and review operating issues after adoption before removing temporary support.

Team change log

Keep this record visible through the transition so announcements, open choices, risks, and commitments do not become mixed together.

• Change frame: reason, intended result, confirmed decisions, assumptions, unknowns, and authoritative owners.
• Local impact: roles, customers, workflows, dependencies, current commitments, skills, tools, and employment-process questions.
• Participation and decisions: open choices, input routes, proposals, decision date, owner, rationale, and feedback response.
• Transition evidence: risks, controls, support, learning, operating signals, corrections, and items to retire after stabilization.

Common mistakes

• Presenting uncertain information as settled because the manager wants to appear confident.
• Inviting broad feedback after all implementation choices have already been closed.
• Calling evidence-based concerns resistance instead of examining the operational risk they describe.

Try one

Sources

• CIPD change management factsheetProfessional guidance on planning organizational change and supporting the people affected by it.
• CIPD line management factsheetProfessional guidance on the people-management responsibilities and support needs of line managers.