The First Right-Sided Investigation Workshop We Run With Clients

What Left-Sided and Right-Sided Investigations Actually Mean

The left side of a deviation investigation is the descriptive work. What happened, when, where, who was involved, what equipment was running, what batch was affected. This is necessary work. It produces the factual baseline that any downstream analysis depends on. The trouble is that for many quality organizations, the descriptive work also becomes most of the work. Investigators write detailed narrative reports, attach supporting evidence, document interview notes, and close out the investigation having produced a comprehensive description of a problem and a thin corrective response.

The right side is the analytical and corrective work. Why did the deviation actually occur, not just at the level of immediate cause but at the level of system contributor? What corrective action will eliminate the underlying contributor, not just patch the immediate symptom? How will we know the corrective action worked, six and twelve months out? This is where the corrective and preventive value lives, and it is where time investment most directly affects the deviation rate going forward.

The terms “left-sided” and “right-sided” are not standard regulatory vocabulary. They are a working shorthand we use in client engagements to make the imbalance visible. When a quality leader can see, on a single page, that their investigation team is spending 40 hours per deviation on description and 4 hours on corrective design, the imbalance becomes harder to ignore. The shorthand makes the conversation possible.

Why Most Investigations Skew Left

The leftward skew is not a failure of investigator competence. It is a structural product of three forces that quality leaders should name explicitly before trying to shift the work.

The first force is inspection readiness. Investigation reports are inspectable artifacts, and the most visible inspection finding is a report that omits relevant facts or lacks supporting evidence. Investigators learn, early in their careers, that thorough description is the safest path through an inspection. The lesson is not wrong, but it produces an investment imbalance over time.

The second force is templated workflows. Most QMS platforms structure investigations with extensive descriptive fields, multiple narrative sections, and lighter scaffolding for root cause analysis and corrective action design. The platform itself signals where the work belongs. When the template gives an investigator twenty fields for description and three fields for corrective action, the investigation will reflect that ratio.

The third force is the calendar. Deviation closure timelines are typically 30 to 60 days. Within that window, investigators have to produce a report, route it through review, get approvals, and close. Description is faster than analysis. Under time pressure, the right-sided work compresses first.

Naming these three forces in the workshop is itself part of the intervention. Investigators who understand why they have been spending time the way they have been are more willing to shift than investigators who are simply told the current pattern is suboptimal.

The Workshop Structure We Run

The first right-sided investigation workshop we run is typically two days, with eight to twelve participants from quality, manufacturing, engineering, and validation. Day one establishes the diagnostic. Day two builds the new pattern. The structure is deliberately not a training session. Participants do not learn investigation theory. They restructure their own organization’s investigation work.

Day one runs three sessions:

• Session 1: Time accounting. Participants take five recent deviation investigations from their own organization and break out the hours spent on each major activity: description, root cause analysis, corrective action design, effectiveness verification, documentation, and review. The numbers are usually surprising. We have never run this session and had the right-sided work exceed the left-sided work.
• Session 2: Repeat deviation analysis. Participants look at the previous twelve months of deviations and identify how many are direct repeats or close variants of earlier deviations. The repeat rate is the measurable consequence of corrective action thinness. A 30 percent repeat rate is common in our client baselines.
• Session 3: Template audit. Participants examine the actual QMS template for their investigations and count fields by category. The structural imbalance in the template usually mirrors the structural imbalance in the work.

Day two runs three more sessions:

• Session 4: Right-sided template design. Participants redesign the investigation template with more weight on root cause analysis structure (fishbone, five-whys, or fault tree), corrective action specification, and effectiveness verification criteria. The redesign is bounded by what is feasible to implement in their actual QMS platform.
• Session 5: Time reallocation. Participants set a target time allocation for future investigations and design the operational changes (workflow updates, reviewer expectations, escalation triggers) that will produce that allocation.
• Session 6: Effectiveness verification rigor. Participants establish the criteria for effectiveness verification: what evidence will demonstrate that a corrective action actually worked, and at what time horizon? Most baseline programs verify effectiveness through “no recurrence in 30 days,” which is too short to be meaningful.

The Three Shifts We Drive in Day One

Day one is designed to produce three shifts in how participants think about their investigations. These shifts have to land before day two will produce durable redesign work.

The first shift is from “deviation investigation as documentation” to “deviation investigation as preventive intervention.” Participants who have spent years optimizing for inspection-ready narratives have to internalize that the actual value of the investigation is the deviation that does not happen six months later because the corrective action eliminated its underlying cause. The narrative is necessary but instrumental.

The second shift is from “root cause as a single category” to “root cause as a system of contributors.” Most baseline investigations identify a single root cause, often a human error or an equipment failure. Right-sided investigations identify the system of contributors that produced the deviation: the training program, the procedure clarity, the supervisory presence, the equipment maintenance cadence, the upstream material variability. ICH Q9’s quality risk management thinking applies here. The FDA’s Q9(R1) Quality Risk Management guidance articulates the layered risk thinking that produces multi-contributor root cause analysis.

The third shift is from “corrective action as a discrete fix” to “corrective action as a system intervention.” A discrete fix changes one procedure or replaces one piece of equipment. A system intervention changes the training, the supervisory pattern, the maintenance cadence, or the material specification that produced the deviation. System interventions are harder to design and harder to verify, but they produce non-recurrence at scale rather than non-recurrence in a single observed case.

Measurable Outputs From the Workshop

A two-day workshop should produce measurable outputs that the client can hold themselves accountable to. The outputs we expect from the engagement are documented at the end of day two and tracked at 90 days and 180 days post-workshop.

The Friction Points That Always Show Up

Across the engagements we have run, three friction points show up almost every time. Naming them in advance lets the client anticipate them rather than be surprised.

The first friction point is QMS platform constraint. Most QMS platforms can be reconfigured to rebalance investigation templates, but the reconfiguration requires platform vendor engagement and IT change control. The client team has to plan for a multi-week reconfiguration cycle. Workshop participants get excited about the redesign on day two; the platform constraint slows the implementation, which can produce frustration if not anticipated.

The second friction point is reviewer expectations. Reviewers who have been trained to verify thoroughness of description will continue to verify thoroughness of description, even after the workshop. The reviewer expectation needs to be reset explicitly, usually through a calibration session with the reviewer cohort. Without this, investigators rebalance their work and then get pushback from reviewers, which produces the worst possible outcome: investigators have done the harder work and are penalized for the easier work they no longer did.

The third friction point is the calendar. Right-sided work takes longer per investigation in the near term, even if it reduces total work over twelve months through repeat deviation reduction. Quality leaders have to commit to absorbing the near-term time cost, which means either accepting longer closure timelines for the first few months or accepting investigator overtime. There is no shortcut. The investment is real and has to be made visible to the leadership chain before the workshop, not after.

Sustaining the Change After the Workshop

A two-day workshop is the start, not the substance. Three practices sustain the change over twelve months.

The first is monthly investigation retrospectives. The quality team picks one closed investigation from the prior month and reviews it together against the right-sided pattern. Where did the work land? Where did the team revert to old habits? What needs to be reinforced? The retrospective is short, one hour, but consistent. It surfaces the slippage early.

The second is effectiveness verification documentation. Every corrective action that closed in the first 180 days post-workshop gets formal effectiveness verification, with documented criteria and a documented outcome. The effectiveness verification reports become part of the QMS evidence base and demonstrate the trajectory to inspectors. This practice aligns with the guidance in the FDA’s inspection guides on what inspectors look for in CAPA effectiveness.

The third is repeat deviation tracking. A simple dashboard shows the count and rate of repeat deviations over rolling 90 and 180 day windows. The trend line is the most important visible signal of whether the workshop produced durable change. When the repeat rate starts moving, leadership gets visible evidence that the investment in right-sided investigation is producing operational return.

The cumulative effect is that within 12 to 18 months, quality organizations that go through this workshop and sustain the practices produce a measurably different deviation portfolio. Fewer deviations, fewer repeats, more defensible CAPAs under inspection, and an investigation team that is operating closer to where the value actually lives.

References & Sources