The need for change in healthcare organizations is constant: new legislation, accreditation, information system, service line, organizational structure or patient flow. However, many transformations do not last in the field, despite the correctness of the decision. The procedure is published, training is provided. The team returns to the old method after a while.

The problem isn't always employee resistance. The purpose of the change may be unclear, workload may not be taken into account, leaders may give a different message, or the new method may not be supported by daily systems. Change leadership is the discipline of establishing workable conditions before convincing people.

Concrete the reason for the change

“We are going digital,” “we are improving quality,” or “we are institutionalizing” are not sufficient explanations for the employee. It should be clearly explained which problem will be solved, what will change for the patient and employee, what will not change, and what the success criterion is.

The change narrative must answer three questions:

  • Why now?
  • What exactly will be different about the day-to-day job?
  • How will we know if this is working?

Involve affected groups early

If process design is done only in the management room, exceptions in the field will not be seen. Physicians, nurses, administrative staff, technical staff and employees in patient contact experience different effects. They need to be represented at the design stage.

Participation does not mean that everyone has veto power. Management determines the decision framework. The field team contributes to feasibility, risk and detail design.

Get leaders to show the same behavior

If senior management continues to ask for the old report while demanding the new process, the team will understand which system is the real one. The credibility of change is measured by leader behavior.

Common message, decision and exception rules that managers will use should be determined. Line managers are change leaders who not only deliver announcements, but also answer questions, remove obstacles, and gather feedback.

Calculate workload and capacity impact

The new system may require additional registration, training and learning time in the initial period. If this load is deemed invisible, the employee tries to bypass the new application with a shortcut. Transitional capacity, support channel and priority changes should be planned.

If it's not clear which old job will stop, the new job will just be overhead. With every transformation, we ask “what do we give up?” The question should be asked.

Use the pilot as a controlled learning area

The pilot is not a show to confirm a previously made decision. It is the learning phase where the design is tested and corrected in the real environment. Scope, duration, success criteria and stopping condition must be determined in advance.

Not only satisfaction from the pilot team; Data on processing time, errors, rework, patient impact and support needs should be collected. The design should be revised according to the results.

Separate education from behavior change

Certificate of participation is not proof of practice. Training should be role-based, with real tasks and scenarios. Critical skills should be verified by observation or practice.

After the training, there should be on-site coaching, quick reference material and a question channel. For new employees, the change should be included in orientation.

Read resistance as information

Not every objection is against change. The employee may be experiencing a patient safety risk, missing resources, system incompatibility, or role conflict. Objections should be evaluated according to theme and reason.

Untrue rumors must be corrected quickly and with clear information; Justifiable operational obstacles should be included in the solution list. The team that gives feedback but does not receive any response will become silent over time. This causes management to lose risk signals.

Support persistence with the system

The new way of working should be embedded in procedure, job description, information system, performance indicator, meeting agenda and manager control. When the old form and old access channel remain open, the team reverts to the old method.

Reviews can be made at 30, 60 and 90 days after the change. Undesirable side effects and differences between units should also be examined as well as the result.

Practical takeaway

Change leadership in healthcare is not about making a powerful announcement. It is to clarify the purpose, include the field in the design, align the leader behavior, manage the transition load and make the application permanent with the system.

Successful change is not about people remembering the new method. It has become more difficult and meaningless to return to the old method.