Using RACI to Manage Complex Health IT Projects

Complex health IT projects involve large stakeholder groups, competing priorities, and decisions that need to move through multiple levels of an organization. As projects grow, accountability can become unclear, consultation can expand beyond what is practical, and decision making can slow to a crawl. 

A basic RACI matrix works well for many projects, but large, multi-phase initiatives often require a more structured approach. The challenge is not that RACI stops working, it is that responsibility, accountability, and consultation become more difficult to manage as complexity increases.

Used strategically, advanced RACI approaches do more than clarify roles. They help project managers create clear decision pathways, manage stakeholder involvement, and maintain momentum when completing perspectives threaten to stall progress. 

🏗️ Layered RACI architecture

Larger projects often need more than a single RACI table. When everything is captured in one view, decisions get muddled and escalation paths are unclear. A layered approach creates structure, showing which decisions stay within a team and which move upward. This clarity helps leaders stay focused on the right level while giving team members and stakeholders confidence that their concerns will be addressed. 

Think about three layers of responsibility:

Strategic level

High-impact decisions about budgets, timelines, and overall direction belong here. Even if the project is part of a broader program, there are always decisions that connect the project back to organizational priorities. This level often involves executive sponsors, senior leaders, or a steering committee. While decisions at this level may not be frequent, they shape whether a project continues as planned, shifts direction, or pauses. 

Project level

This layer focuses on keeping multiple work streams aligned. Stakeholders usually include the project manager, operational leaders, and IT team leads. Weekly or bi-weekly discussions focus on resolving dependencies, addressing shared resource needs, and confirming integration decisions. The emphasis is on ensuring the individual work streams move forward in sync.

Work stream level

This is where detailed responsibilities are defined for specific tasks within a work stream. Roles here are responsible for activities like application build, drafting test scripts, validating workflow details, or preparing training materials. These decisions typically stay within the work stream unless they create cross-project impacts. 

For layered approaches to succeed, escalation paths must be clear, boundaries around decision authority must be defined, and information needs to flow consistently across levels. Done well, this prevents executives from drowning in day-to-day details while ensuring frontline contributors know where to turn when issues require higher-level decisions.

📡 Integrating RACI with governance and communication

Layered RACIs are most effective when connected directly to governance and communication structures. If they exist as separate project documents, people often default back to existing organizational processes. That can create confusion, duplicate discussions, and uncertainty around decision authority.

➡️ Governance alignment: RACI roles should align with the authority of steering committees and escalation pathways already in place. Accountability should also connect with the performance measures that leaders use to track progress.

➡️ Communication integration: A RACI matrix helps define who receives updates, how meeting agendas are structured, and who is responsible for reporting. Aligning with established communication plans ensures stakeholders get the right information without being overloaded. 

➡️ Documentation strategies: A RACI is most powerful when tied to the tools people already use. For example, if the risk register lives in Teams, the RACI should specify “maintain risk register in Teams” instead of just “maintain risk register.” Connecting accountabilities to the systems people already work in makes the document meaningful and practical.

🧩 Managing the consultation explosion

One of the most common challenges in complex projects is consultation. Everyone wants input into decisions, whether because of their expertise, their operational responsibilities, or the potential impact the decision may have on their area. Without structure, consultation can expand indefinitely and slow progress. Most of us have attended meetings where many participants had little reason to be there. Advanced RACIs help define who genuinely needs to contribute, when their input is needed, and when decisions can move forward.

Instead of relying on a single “Consulted” category, advanced RACIs can introduce additional structure:

Tiered consultation: Define who must be consulted directly, who only reviews, who is simply notified, and who needs awareness after the fact.

Expertise-based grouping: Organize consultation by knowledge area. For example, clinical workflow decisions should involve relevant clinical departments, while technical architecture belongs with IT specialists, and regulatory compliance requires targeted input from compliance experts.

Another helpful technique is time-boxing consultation. Set standard times for feedback, such as five business days, with flexibility for urgent or complex items. Make it clear when presenting the RACI what happens if deadlines are missed so decisions can move forward.

🔄 Evolving RACI over time

In long initiatives, RACI assignments should evolve as the project moves through phases. This doesn’t mean people’s job roles change, but their responsibilities within the RACI shift as work progresses. For example:

➡️ Planning may require broad consultation and careful decision-making.

➡️ Design and build benefit from more streamlined authority, where project leads and SMEs take on greater accountability.

➡️ Testing should widen consultation to include end users for validation and feedback.

➡️ Go-live requires rapid escalation and clear accountability so issues are resolved quickly.

➡️ Optimization shifts accountability toward operational leaders as the project transitions to steady state.

Reasonable maintenance means updating RACIs at phase gates or major milestones, not for every minor personnel change or after every project meeting. Updates should focus on clarifying evolving responsibilities without overwhelming stakeholders with constant revisions. This balance keeps the RACI relevant without turning it into an administrative burden.

🌐 Advanced RACI as a leadership tool

Advanced RACI strategies transform a basic matrix into a framework for leading complex projects. By layering decision-making, aligning with governance, structuring consultation, and evolving responsibilities over time, project managers can bring order to complicated environments and keep momentum steady.

The greatest value is not the document itself. It is the clarity the document creates. When people understand who makes decisions, who provides input, and when issues need to be escalated, projects spend less time navigating uncertainty and more time delivering results.