Introducing new software in a healthcare setting is never purely a technical project. It affects people, processes and established ways of working, often across busy teams where time is limited and continuity of care must be protected.
Even well-designed technology can struggle to deliver its intended benefits if the people expected to use it are not prepared, involved and supported. Change management in healthcare should therefore begin alongside technical planning, rather than being treated as a final step before go-live.
The HSE’s Digital Health Strategic Implementation Roadmap reflects this approach. It identifies workforce capability, supportive culture, communication and participation as important parts of digital transformation. While the roadmap focuses on Ireland’s health service, these principles are relevant to healthcare organisations everywhere.
At DMF Systems, we combine technology implementation with clear communication, practical training and ongoing support. Drawing on our experience working with healthcare teams, here are six change management practices that can help make software implementation and adoption more successful.
1. Communicate early and often
If you take one piece of advice from this blog, make it this: the value of clear, timely communication cannot be overstated when it comes to change management. Communication should begin well before the software is introduced. Staff need a clear understanding of:
- What is changing
- Why the change is happening
- When it will take place
- How it will affect their role and daily work
- Where they can go with questions or concerns
One announcement is rarely enough. People absorb information at different times, and their questions often become more specific as implementation approaches. Regular updates help keep staff informed and give project teams an opportunity to address uncertainty before it becomes resistance.
It is also helpful to use several communication channels. Depending on the organisation, this might include team meetings, emails, staff briefings, intranet updates and department-level discussions. The aim is not simply to send information, but to create opportunities for questions, feedback and honest conversation.
During a recent rollout of Inter-AHP, DMF Systems worked closely with the hospital’s project team from the outset. Communications began early, continued throughout the project and used different channels to reach the staff involved.
This reflects the HSE Health Services Change Guide, which places people at the centre of change and highlights the importance of engaging those who may be affected.
2. Tailor the change to the people affected
A hospital is not one audience. Different departments, professions and teams have their own workflows, pressures and priorities. A new system may change one team’s work significantly while having a much smaller effect on another.
Hospital-wide communications can provide useful context, but they should not be the only source of information. Effective change management considers what each group needs to know and how the change will affect the work they carry out every day.
Before implementation, take time to identify the groups involved and understand:
- How they currently complete the relevant tasks
- What will change in the new system
- What questions or concerns they are likely to have
- What training and support will be most useful
Inter-AHP was rolled out department by department across Health and Social Care Professional teams. Each department received communications relevant to its stage of the rollout. This allowed the project team to focus its attention on the staff currently preparing for the change, rather than asking every department to absorb the same information at once.
Tailoring the approach in this way can make communications more relevant and support more meaningful engagement.
3. Identify change champions early
Change champions are people within a department or team who help colleagues understand and prepare for a new way of working. They provide a familiar point of contact and can help connect the wider project team with day-to-day staff experience.
Depending on the project, champions may help to:
- Build awareness of the upcoming change
- Reinforce key communications
- Encourage participation in training
- Answer straightforward questions
- Gather concerns and feedback from colleagues
- Identify areas where further support may be needed
This can be especially valuable in healthcare environments, where staff may be more comfortable raising practical concerns with a trusted colleague who understands their role.
Departments identified champions early during a recent Inter-AHP rollout. These champions supported the project within their own teams and helped maintain a connection between the implementation process and the people who would use the system.
Champions should not be expected to carry the change management alone. They need clear information, access to the project team and a defined understanding of their role. With the right support, however, they can make change feel more approachable and relevant.
4. Provide flexible, practical training
Healthcare staff work across different roles, locations and schedules. A single training session at a fixed time is unlikely to suit everyone, particularly in clinical settings where attendance may be affected by patient needs.
Where possible, offer more than one way to learn. This could include:
- In-person sessions
- Live online training
- Recorded sessions
- Quick-reference guides and other supporting materials
- Access to help after training has finished
Training should also reflect real workflows. A tour of every software feature may be less useful than showing staff how to complete the tasks they will perform most often. Practical examples help people connect the technology to their responsibilities and understand how it will fit into their working day.
For the recent Inter-AHP implementation, users were offered both in-person and online training, with access to a recording afterwards. This gave staff greater flexibility and allowed them to revisit the material when needed.
The HSE’s Digital Health Strategic Implementation Roadmap also highlights the need to invest in digital skills and capability so healthcare staff have the confidence and resources to adapt to new ways of working.
5. Consider a phased rollout
Not every software implementation needs to happen across the entire organisation at once. In many cases, a phased rollout can make the change more manageable for staff, project teams and support resources.
Rolling out by department, location or user group can help an organisation to:
- Reduce disruption
- Focus training and support where they are needed
- Identify issues at an earlier stage
- Gather feedback from initial users
- Apply lessons before later phases begin
For Inter-AHP, the department-by-department rollout allowed communications, training and support to be planned around each team’s implementation. It also gave the project team a clearer view of how adoption was progressing at each stage.
A phased change management approach still requires careful coordination. Timelines, dependencies and expectations should be clear, particularly where departments work closely together. When planned well, however, phasing can create valuable room to listen, learn and adjust.
6. Measure adoption, not just deployment
Going live confirms that the software has been deployed. It does not necessarily mean that the change has been successful.
Before implementation, agree on what successful adoption will look like. Measures will vary depending on the system and setting, but may include:
- Staff confidence in using the software
- Ease of use
- Understanding of new processes
- Training attendance and effectiveness
- Common questions or challenges
- Usage and adoption levels
- Changes in the time or effort required to complete key tasks
Feedback should be gathered at more than one point. A pre-implementation survey can help establish a baseline and reveal existing concerns. A follow-up survey can show how staff experience has changed and where further guidance or support may be needed.
Surveys were carried out before the Inter-AHP rollout to understand staff experience and help assess the implementation. This provided a broader view of success than deployment alone.
Feedback is most valuable when it leads to action. Share the themes with the project team, respond to recurring issues and let staff know how their input is being used.
Change management continues after go-live
Change management in healthcare does not end when new software is switched on. Go-live marks the beginning of the next phase, when staff begin using the system in real situations and discover questions which only emerge through experience.
Continue listening to users, answering questions and monitoring adoption. Refresher training, updated guidance and additional support may all be needed as the software becomes part of everyday work.
Technology delivers lasting value when it supports healthcare professionals and fits effectively into their workflows. That is why DMF Systems works alongside healthcare organisations before, during and after implementation, combining technical delivery with the communication, training and support needed for successful adoption.
To discuss your healthcare software requirements and how DMF Systems can support your implementation, get in touch with our team.
