Building a Culture of Quality: Inside Leanabl's Lean Approach

What "Quality Culture" Usually Means

In medical device regulatory and quality work, "culture of quality" appears regularly in mission statements, audit responses, and corporate values documents. It is rarely defined operationally. The phrase usually means something like: people care about doing the work correctly.

The phrase is true and the underlying intent is good. But it tends to be unfalsifiable — every team would describe itself as caring about quality. The differences between teams that actually produce quality work and teams that produce findings appear at the operational level, not at the values level.

A few specific operational habits that we have noticed distinguish strong quality cultures from weak ones, and that we deliberately cultivate at Leanabl.

Habit 1: Findings Are Not Failures

The strongest quality cultures we have worked with treat audit findings — internal or external — as process intelligence, not as performance failures. The reaction to a finding is: what does this tell us about the process design? What is the root cause? What is the systemic fix?

The weaker cultures treat findings as personal failures. The reaction is to identify who made the mistake, to discipline or retrain that person, and to assume the process is fine. The next audit reveals a similar finding because the process was actually the issue.

The difference is observable. A team that treats findings as intelligence:

• Opens CAPAs quickly without blame
• Documents root cause analyses honestly (including procedural and systemic causes)
• Implements process changes rather than personnel changes
• Closes CAPAs only when the underlying process has been verifiably improved

A team that treats findings as failures:

• Resists opening CAPAs ("this was a one-time mistake")
• Documents superficial root causes ("operator error")
• Implements retraining rather than process change
• Closes CAPAs based on time elapsed rather than verified improvement

We deliberately train clients out of the finding-as-failure pattern. It is one of the highest-leverage cultural shifts.

Habit 2: Documentation Carries Its Weight

A strong quality culture has documentation that the team uses. A weak quality culture has documentation that the team avoids.

The test is simple: pick a procedure and ask three people who should be using it to recite (or summarize) what it says. In a strong culture, the recitation matches the procedure. In a weak culture, the recitation describes whatever the team actually does, which often differs from the procedure.

Procedures that are operationally accurate get used and refined. Procedures that are aspirational or theoretical get ignored. Over time, ignored procedures accumulate findings because the audit compares the procedure to the practice, and the practice diverges.

The fix is not to enforce procedure adherence. The fix is to write procedures that match operational reality, then improve operational reality where it falls short of the standard required.

Habit 3: Senior People Do Quality Work

In strong quality cultures, the most senior practitioners spend meaningful time on direct quality work — pulling samples, reviewing records, observing operations, reading complaint summaries. The seniority is operationally present.

In weak cultures, senior people delegate quality work entirely and engage only when escalation occurs. The signal to the team is that quality is junior work; the work attracts junior energy.

This is not a question of staffing levels. It is a question of where senior attention goes. A small team with senior attention engaged in quality can produce stronger work than a large team where senior attention is elsewhere.

Habit 4: Cross-Functional Quality Reviews

Strong quality cultures bring engineering, regulatory, clinical, and operations into the same room for quality reviews. The functions hear each other's perspectives on quality issues; the issues get resolved at the cross-functional level rather than thrown over walls.

Weak cultures run quality reviews inside the quality function. Engineering hears about quality findings only when they are asked to implement corrective actions. Clinical hears about post-market findings only when they affect labeling. The functions stay siloed.

A simple practical step: the quarterly quality review (CAPA status, complaint trends, audit findings, PMS data) is a multi-function meeting. Attendance is not a courtesy invitation; it is a working session where the functions share data and decide together.

Habit 5: Process Improvement Is Continuous, Not Episodic

Lean principles — applied to manufacturing originally and to broader operations more recently — center on continuous small improvements rather than periodic large overhauls. Quality cultures that have absorbed this tend to:

• Update procedures incrementally as the team finds better ways
• Treat each CAPA as input to a broader process improvement, not just as a fix to a specific finding
• Maintain a backlog of small process improvements that get implemented continuously
• Avoid the "QMS rewrite project" that consumes 6–12 months every few years

The continuous-improvement pattern produces compounding gains. The episodic pattern produces visible peaks (the QMS overhaul) and invisible decay (the years between overhauls).

Habit 6: External Honesty

Strong quality cultures are honest with regulators. When a finding is real, they acknowledge it. When a process gap exists, they describe it. When a CAPA is taking longer than expected, they explain why.

This is operationally counterintuitive — the assumption is that regulators are adversaries and disclosure increases enforcement risk. In practice, regulators (FDA inspectors, MFDS auditors, Notified Body assessors) consistently respond positively to honest engagement and negatively to evasion. The cost of being caught in evasion is significantly higher than the cost of disclosed weakness.

Korean MFDS auditors specifically — in our experience — respond well to direct acknowledgment of issues paired with clear corrective action plans. They respond poorly to defensive posture even when the underlying issue is minor.

What We Try to Do at Leanabl

Our team operates under the same habits we describe above:

• Internal findings (in our own engagements) are documented openly and discussed
• Procedures we write for ourselves match what we actually do
• Senior practitioners stay engaged in direct work, including QA-type activities on our deliverables
• Cross-functional review is built into our engagement model (RA, QA, clinical, manufacturing all on the same calls)
• Improvements to our methodology happen continuously, not in big-bang overhauls
• We are honest with clients about what we are uncertain about, what is going well, and what is going badly

We try to model these habits with clients because the modeling is more effective than the abstract advice. Clients who work with us through one or two engagements often adopt the habits internally because they see them in operation, not because we recommend them in a slide deck.

Where This Comes From

The operating principle — People First, Technology Lean — is the upstream source. People-first means cultivating the operational habits that make quality work flow through the team. Technology-lean means the documentation, tools, and processes support the work rather than substitute for the work.

The culture is the operational expression of the principle. It is not a separate program.

Where Leanabl Plugs In

For clients building or refining their own quality culture, the work tends to live inside an eQMS engagement — not as a separate cultural change project, but as habits embedded in the QMS operation. For Korean-specific quality culture work that supports KGMP audit readiness, Korea Audit Readiness and Korea QMS Foundation integrate the cultural work with the procedural work. For our broader perspective on how this connects to mission, see Our Philosophy and Mission & Vision.