Change analysis for root cause investigation
What is Change analysis for root cause investigation?
Change analysis is a root cause investigation technique that systematically compares conditions, processes, equipment, personnel, and environmental factors between normal operations and the circumstances that existed at the time of an adverse event. The underlying logic is straightforward but powerful: if something happened differently this time than it normally does, that difference — alone or in combination with other changes — may be causal. Change analysis is particularly valuable for events that seem to 'come out of nowhere': a process that has run safely for years suddenly produces an adverse event, not because of random chance but because something changed.
The change analysis process begins by establishing a baseline — a clear description of how the process operates under normal, no-event conditions. It then systematically inventories every difference between that baseline and the conditions present at the time of the event: who was involved (different personnel, different staffing ratios, travelers or agency staff), what equipment was used (recently serviced, recently replaced, recently updated), what environmental conditions existed (time of day, census, concurrent events competing for attention), what organizational context was present (recent policy changes, training rollouts, system updates, leadership transitions), and what physical differences existed in the immediate environment.
Change analysis is especially effective as a complement to other root cause investigation methods. A fishbone diagram maps the categories of potential contributing factors; change analysis populates those categories with specific, verifiable differences between normal and event conditions. A 5 Whys investigation follows a single causal chain; change analysis ensures that the team doesn't commit to that chain before checking whether a recent change might explain the event more directly. In complex events, change analysis often identifies the initiating condition that other methods then analyze in depth.
When to use it
Use change analysis for events that occur in processes with an established track record of safe performance — where the question is not 'what is chronically wrong with this process?' but 'what was different this time?' Change analysis is particularly valuable immediately following adverse events, when memories are fresh and evidence of pre-event conditions is most available. It is also valuable for clusters of events that appear temporally correlated with an organizational change — a new EHR module, a policy update, a staffing model change, a physical plant renovation — where the temporal pattern suggests causality but the mechanism is not yet understood. Change analysis should be used in conjunction with event reporting trend analysis, which can identify correlations between organizational changes and event rate changes that are not visible in individual event investigations.
Healthcare example
A hospital's quality team noticed a statistically significant increase in medication transcription errors on three inpatient units over a six-week period, beginning approximately two weeks after a scheduled EHR software update. A change analysis was initiated, comparing pre-update and post-update conditions systematically. The review found that the software update had modified the display format of the medication administration record in a way that changed the visual grouping of medications administered at similar times — a change that was not documented in the update release notes and had not been included in the staff notification about the update. A simulation exercise with pharmacy staff confirmed that the new display format was causing a pattern of misidentification between medications with similar administration times but different routes. The change analysis identified the mechanism within five business days of initiating the review — a timeline that would not have been achievable with a broader investigation approach that wasn't specifically looking for differences between pre-event and event-period conditions.
How ImprovementFlow supports Change analysis for root cause investigation
ImprovementFlow's event trending allows quality teams to identify temporal correlations between organizational changes and event rate changes — detecting the signal that a change analysis is warranted before conducting the investigation.
Event timestamp data combined with organizational change records (EHR updates, policy effective dates, staffing model changes) enables systematic comparison of event rates before and after changes — providing statistical grounding for change analysis findings rather than relying solely on post-event narrative reconstruction.
Safety event records capture the context of each event — time of day, unit census, staffing configuration, equipment in use — in a structured format that makes systematic comparison between event conditions and normal operating conditions tractable rather than requiring manual file review.
When change analysis identifies a specific organizational change as a contributing factor, ImprovementFlow's improvement project framework provides the structure to document the finding, design a corrective response, and track implementation — including temporary risk mitigation measures while a permanent solution is developed.
Integration with process compliance monitoring allows the team to assess whether the organizational change affected compliance rates for key safety processes — providing an additional data dimension for change analysis that goes beyond event rate comparison alone.
See how ImprovementFlow supports your analysis work
Most customers begin with safety reporting or huddle boards and expand from there. No enterprise commitment required.