Why activity feels good—but doesn’t always fix anything
Why “doing something” feels like progress
Checking a box feels productive.
You sent the email.
You updated the SOP.
You held the training.
You documented the CAPA.
It feels like the problem is handled.
But here’s the hard truth: activity is not the same as impact.
In regulated environments, it’s easy to confuse motion with improvement. And that false comfort is how the same problems keep showing up—again and again.
Activity vs impact
Activity = something was done
Impact = something actually changed
You can complete an action perfectly and still:
See the same deviation next quarter
Repeat the same protocol error
Reopen the same CAPA
Get the same audit finding
Why? Because the action didn’t change how the system behaves.
Why checking the box fails
1. It focuses on completion, not effectiveness
Many actions are designed to be easy to document, not effective:
“Staff were retrained”
“Procedure was reviewed”
“Reminder email was sent”
These are measurable actions—but they don’t tell you whether:
Behavior changed
Risk was reduced
The error became harder to repeat
Completion is not proof of improvement.
2. It rewards speed over thinking
Checkbox culture encourages:
Quick fixes
Reused templates
Generic CAPAs
“Good enough” responses
The goal becomes closing the item, not solving the problem.
That’s how organizations end up very compliant on paper—and very fragile in practice.
3. It avoids the uncomfortable questions
Real improvement requires asking:
Did this action actually change outcomes?
Can the same mistake still happen tomorrow?
Are we relying on memory, or did we change the system?
Checkboxes don’t like those questions. Systems thinking demands them.
What real improvement looks like
Real impact shows up when:
Errors stop repeating
Variability decreases
Teams catch issues earlier
Fewer controls are needed over time—not more
That doesn’t happen by adding more tasks.
It happens by changing how the work is designed.
Where Kandih comes in
Kandih doesn’t just ask, “Was the action completed?”
We ask, “Did it actually work?”
Specifically, Kandih helps teams:
Review actions against real-world outcomes
Identify whether a fix reduces risk or just creates paperwork
Redesign studies, workflows, and checks to prevent recurrence
Replace checkbox CAPAs with system-level changes
Align actions with measurable improvements, not assumptions
If an action doesn’t change behavior, reduce risk, or block failure—it doesn’t count.
Bottom line
Checking the box feels good.
But feeling productive is not the same as being effective.
If your system improves only on paper, the problem isn’t solved—it’s postponed.
Kandih helps organizations move beyond activity and focus on actions that actually change outcomes.
References
FDA – Quality System Regulation Preamble (CAPA Effectiveness)
ISO 9001:2015 – Clause 10.2: Nonconformity and Corrective Action
https://www.iso.org/standard/62085.html
ICH Q10 – Pharmaceutical Quality System
https://database.ich.org/sites/default/files/Q10_Guideline.pdf
Reason, J. (2000). Human error: models and management. BMJ
https://www.bmj.com/content/320/7237/768
ASQ – Corrective Action Effectiveness: Why CAPAs Fail
Greenlight Guru – Why CAPAs Fail Without Measuring Effectiveness
https://www.greenlight.guru/blog/debunking-8-commonly-held-capa-myth