Problem Solving
It is 10:42 AM at the Puurs biologics facility. During the TIER 1 meeting, the Quality KPI turned red: three consecutive OOS results on the lyophilization line. The shift supervisor opens ProBeya, navigates to the Quality board, and clicks + New Analysis. She selects Ishikawa, titles it "Lyo Chamber 4 — Residual Moisture OOS (Batch LY-2026-0847)," and assigns the cross-functional team. Within minutes, the investigation has a structured home, an audit trail, and a direct link to the corrective action that will follow.
This is what structured problem solving looks like when it is embedded in the daily operating rhythm rather than buried in a shared drive somewhere.
Why Structured Problem Solving Matters
The Toyota Production System teaches that problems are gifts — but only if you treat them with rigor. In pharma manufacturing, unstructured investigations produce two failure modes: the root cause is never found (leading to recurrence), or the wrong root cause is identified (leading to ineffective CAPAs that satisfy auditors but do not fix the process).
ICH Q10 Section 3.2.1 requires pharmaceutical manufacturers to implement a corrective action and preventive action system. FDA 21 CFR 211.192 mandates investigation of unexplained discrepancies. EU GMP Chapter 1.4(xiv) calls for root cause analysis as part of the pharmaceutical quality system. None of these regulations prescribe a specific methodology — they require that the methodology be documented, justified, and traceable.
ProBeya provides the digital infrastructure to meet these requirements while keeping the investigation team focused on the science, not the paperwork.
Seven Methodologies for Different Problems
ProBeya supports seven complementary root cause analysis methods. The choice of methodology is not arbitrary — it should match the complexity and nature of the problem.
| Method | Best For | Pharma Example |
|---|---|---|
| 5 Whys | Simple, linear cause chains | "Why did the label printer jam?" — single equipment fault |
| Ishikawa (6M Fishbone) | Complex, multi-factor problems | Residual moisture OOS with potential Man, Machine, Material, and Method contributors |
| WWWHWWH | Problem scoping before deeper analysis | Framing a new deviation before deciding on investigation depth |
| A3 | Toyota-style single-page problem solving | Yield loss improvement project on a tablet press line |
| IS/IS NOT | Distinguishing what the problem is from what it is not | "Why did Lyo Chamber 4 fail but not Chamber 3?" |
| 8D (Eight Disciplines) | Customer-facing or cross-functional problems | Supplier complaint investigation requiring containment + permanent fix |
| DMAIC | Data-driven, statistical process improvement | Reducing fill-volume variability on a liquid filling line |
Start with WWWHWWH to scope the problem clearly. If the cause chain appears straightforward, use 5 Whys. If multiple factors interact, use Ishikawa. If you need to distinguish between what changed and what did not, use IS/IS NOT. For large cross-functional investigations that require containment actions, use 8D. For projects requiring statistical rigor, use DMAIC. For everything else, A3 provides a clean single-page structure.
Worked Example: From Deviation to CAPA to Verification
Day 1 — The Problem Surfaces
During the TIER 1 morning meeting, the QC analyst reports three consecutive OOS results on residual moisture for lyophilized product. The team lead creates an action on the Quality board: "Investigate Lyo Chamber 4 OOS — Batch LY-2026-0847." Priority: Critical. Due date: 5 days.
Day 1 — Scoping with WWWHWWH
The QA manager opens the action, clicks Link Analysis, and creates a WWWHWWH sheet to frame the problem:
- What happened? Residual moisture results of 1.8%, 1.9%, 2.1% vs. specification of ≤1.5%
- Who detected it? QC analyst during in-process testing
- Where did it occur? Lyophilization Chamber 4, Building B
- How was it detected? Routine Karl Fischer titration
- When did it start? Batch LY-2026-0847 (first occurrence), but review shows borderline results on prior two batches
- Why does it matter? Patient safety — excess moisture accelerates degradation of the biologic
- How much impact? Three batches on hold, estimated EUR 2.4M at risk
Day 2 — Root Cause Analysis with Ishikawa
Armed with the scoped problem, the cross-functional team (QA, Production, Engineering, QC) conducts a fishbone analysis:
- Man: Operator followed SOP correctly — confirmed via electronic batch record
- Machine: Vacuum pump maintenance log shows pump was serviced 3 days prior — potential contributor identified
- Material: Same API lot used in Chamber 3 (which passed) — ruled out
- Method: Lyo cycle parameters unchanged — verified in SCADA historian
- Measurement: Karl Fischer instrument calibrated and within tolerance — ruled out
- Environment: HVAC data shows humidity spike during loading — potential contributor identified
The team identifies two potential root causes: (1) vacuum pump gasket was replaced with a non-OEM part during maintenance, and (2) humidity excursion during chamber loading.
Day 3 — 5 Whys to Drill Down
The team runs 5 Whys on the vacuum pump finding:
- Why did the chamber not reach target vacuum? The vacuum pump underperformed after maintenance.
- Why did the pump underperform? A non-OEM gasket was installed during the service.
- Why was a non-OEM gasket used? The approved spare was out of stock.
- Why was the approved spare out of stock? The reorder point was not set in the CMMS.
- Why was the reorder point missing? The spare part was added to the BOM after the last CMMS migration but the reorder trigger was never configured.
Root cause: Missing reorder trigger in CMMS for critical lyo vacuum pump gaskets after system migration.
Day 4 — Submission and Review
The investigation lead clicks Submit to move the sheet to Completed status. The QA Director opens the sheet, reviews the evidence chain, and clicks Review to formally sign off. The system records:
- Who reviewed (QA Director)
- When the review occurred (timestamped)
- That the reviewer is different from the creator (segregation of duties)
This creates the audit-ready record that satisfies ICH Q10 and EU GMP Annex 15 requirements for documented investigation with independent review.
Day 5 — CAPA Linkage
The corrective action — "Configure reorder triggers for all critical lyo spare parts in CMMS" — is tracked on the Quality board. The problem-solving sheet is linked to this action via the Root Cause section, creating bidirectional traceability: from deviation to investigation to corrective action.
Lifecycle and State Machine
Problem-solving sheets follow a controlled lifecycle that prevents skipping steps — critical in GxP environments where the review process is a regulatory requirement.
| Transition | Action | Who | GxP Significance |
|---|---|---|---|
| Draft → In Progress | Team begins analysis | Any board member | Investigation initiated |
| In Progress → Completed | Analysis finished, submit for review | Sheet creator | Ready for independent review |
| Completed → Reviewed | Formal sign-off by reviewer | Board admin or workspace admin | Maker-checker principle satisfied |
| In Progress → Draft | Revert to draft for rework | Any board member | Allows correction before review |
In pharma environments, the reviewer should be different from the person who created the sheet. ProBeya records both the createdById and reviewedById with timestamps, providing the electronic equivalent of two signatures on a paper investigation report. This follows the maker-checker principle required by EU GMP Annex 11 Section 12.4.
The state machine enforces valid transitions. You cannot jump from Draft directly to Reviewed — the system will reject the request. This prevents circumventing the formal review process.
PDF Export for Regulatory Submissions
Every problem-solving sheet can be exported as a formatted PDF report suitable for inclusion in deviation packages, CAPA files, or regulatory submissions. The PDF includes:
- Organization header and sheet metadata
- Full methodology content (whys chain, fishbone diagram, or structured answers)
- Linked action details
- Creator and reviewer information with timestamps
- Audit trail of status transitions
Navigate to the sheet and click Export in the toolbar to generate the PDF.
Integration with the Daily Operating Rhythm
Problem solving does not exist in isolation. In ProBeya, it is woven into the TIER meeting structure:
- KPI Boards: A red KPI triggers an action. The action triggers an investigation. The investigation produces a root cause. The root cause drives a CAPA. The CAPA is tracked until verified. The KPI returns to green. Full loop.
- Escalation Engine: If a problem-solving sheet remains in Draft for too long, the linked action's due date approaches, and the escalation engine surfaces it to TIER 2 management.
- TIER Meeting Mode: During the daily standup, the facilitator reviews open investigations alongside overdue actions. The team can see which problems are being actively worked and which are stalled.
Review the problem-solving list weekly filtered by Status = Draft. Sheets that remain in draft for more than 48 hours often indicate that the team is stuck and needs coaching or additional resources. This is a leading indicator of investigation quality.
Use the Status = Completed filter to identify sheets awaiting your review. Aim to review within 24 hours of submission to maintain investigation momentum and demonstrate management commitment to the quality system.
When documenting observations in a 5 Whys or Ishikawa, be specific and factual. "The pump was not working well" is weak. "Vacuum pump VP-401 achieved only 85 mbar vs. target of 50 mbar at T+45 minutes per SCADA trend" gives the investigation team something to work with.
Permissions
| Action | Required Role |
|---|---|
| View problem-solving sheets | Any board member |
| Create new sheets | Any board member with write access |
| Update sheet content | Sheet creator or board admin |
| Submit for review | Sheet creator |
| Review (formal sign-off) | Board admin or workspace admin |
| Link to action root cause | Any board member with write access |
| Export PDF | Any board member |
| Delete sheets | Board admin or workspace admin |
Related Features
- Action Log — Link root cause analyses to tracked actions for full deviation-to-CAPA traceability
- KPI Boards — Red KPIs are the trigger that starts the problem-solving cycle
- Escalation Engine — Escalate unresolved investigations through the TIER hierarchy
- Routines — Standardized investigation routines ensure consistent methodology application