Maintaining Engagement in Long Health IT Projects

It’s month twelve of your EHR transformation project. The executive sponsor who championed the effort has moved to a new role, your clinical champions are buried in their day jobs, and the finance team stopped attending status meetings three months ago. For some, the project still feels distant, and doubts begin to surface about whether the finish line will ever come into view.

f this feels familiar, you’re not alone. Every long project reaches this stage. What begins with energy and excitement slowly shifts into fatigue and uncertainty. People stop showing up, not because they don’t care, but because the day-to-day demands of healthcare never let up. Over time, some might even start to lose confidence that the end goal is achievable. 

This isn’t a sign of failure. It’s predictable. Stakeholder engagement is not about constant enthusiasm. It’s about sustaining influence, making sure decisions happen when they need to, and keeping the project moving when attention starts to fade. The projects that stay on track are rarely the ones with the fewest challenges. They are the ones where engagement was guided deliberately. 

Engagement follows a natural rhythm

One of the most important lessons in long projects is recognizing that engagement has a rhythm. It rises, dips, and rises again depending on the phase of work. Trying to keep everyone equally involved at all times usually creates frustration. Most projects move through phases that look something like this:

➡️ Early stage: High energy and strong participation
➡️ Middle phase: Energy fades as priorities shift
➡️ Pre-go-live: Attention increases as impact becomes real
➡️ Post implementation: Focus shifts toward stabilization and optimization.

Project coordinators and managers can use these cycles to plan engagement more intentionally. When enthusiasm dips, work can shift toward activities that need less stakeholder input but still move the project forward. Re-engagement points can then be built into the plan so stakeholders return when their input is needed. 

Project leads also need to recognize that some stakeholders are checkpoint participants who only need to be engaged when decisions are required. Others need more consistent updates to stay aligned. Understanding those differences helps leaders direct attention where it has the most value. 

The "what's in it for me" refresh is essential

Every stakeholder, no matter their role, quietly asks the same question: “what’s in it for me?” The answer changes over the life of a long project, and project leaders who fail to adjust the response risk losing relevance. 

At first, motivations often focus on solving current pain points or creating a future vision. As the months pass, new challenges appear, organizational priorities shift, and personal goals start to take centre stage. For some stakeholders, recognition, skill-building, or visibility become just as important as the project outcome itself. 

This is where leadership skills make a real difference. Short quarterly check-ins can surface shifting priorities and help project leads adjust how they frame the work. Depending on the size and scope of the initiative, this may be a formal conversation with stakeholder groups or a quick touchpoint with key individuals. What matters is using these insights keep the project relevant as the work evolves. 

Communication needs change over time

Keeping people engaged is not about sending more messages. Too much communication can overwhelm just as quickly as too little. The real skill is knowing when people need detail, when they need reassurance, and when they simply need to know what is changing. 

Some phases require high-touch updates, including kickoff, major milestones, issue management, and go-live preparation. During more stable stretches, lighter updates are often more effective. Re-engagement should increase when new risks emerge, scope changes require input, or when external factors shift the project’s direction.

Different groups also need different approaches: 
🔵 Executives usually want concise updates, clear risk visibility, and notification when decisions are required. 
🔵 Operational teams often prefer short, practical updates focused on upcoming impacts or actions. 
🔵 Clinical champions may need more frequent communication tailored to their workflow or specialty area. 

The guiding principle is clarity. Most people just want to know if things are on track, and scannable updates that answer “are we okay?” are often more powerful than a long status deck. Setting clear expectations about when stakeholders will receive updates also matters. Nothing erodes confidence faster than silence when stakeholders were expecting an update.

Small wins matter more than you think

When projects stretch over many months, progress can start to feel invisible. That’s why small wins matter. They help people see that the project is still moving forward, even when the final outcome remains far in the distance.

Visible progress builds confidence. Executives see that resources are being used wisely, teams feel that their effort is making a difference, and stakeholders regain belief that the long-term outcome is achievable.

Small wins might include:
✅ Completing a design phase 
✅ Finalizing a major build component
✅ Reaching a testing milestone
✅ Delivering early training sessions 

The most effective project leaders make progress visible and connect those milestones back to the larger goals of the initiative. That helps stakeholders understand how day-to-day project work contributes to the broader direction of the project.

Engagement requires patience and strategy

Sustaining engagement in health IT projects isn’t about keeping everyone excited all the time. It requires patience, timing, and consistent attention to how stakeholder needs change as the work progresses.  

Strong stakeholder engagement is rarely about personality alone. It depends on communication, trust, and the ability to bring people back into the work when their input matters most. 

The initiatives that succeed over long timelines are not the ones with the most enthusiastic stakeholders. They are the ones where engagement is guided deliberately, one phase at a time.