Continual Improvement

This lesson isn't another explanation of an ISM Code requirement. Lessons 1 through 7 gave you the system — the SMS, the DPA, findings, audits, Management Review. This one is the playbook for actually running that system well, year after year, instead of watching it quietly decay between audits.

Why Companies Stop Improving

It rarely happens on purpose. A company passes its DOC renewal, the SMS is declared "working," and attention quietly moves elsewhere — until the next audit forces a scramble. The pattern isn't laziness; it's usually one of these three failure modes:

• Audit-driven improvement only — nothing changes between external audits, so the same categories of finding keep recurring on a 2-5 year cycle.
• Data collected, never used — near-miss reports, internal audit findings, and Master's Reviews pile up but never get analysed for patterns.
• Improvement treated as a project, not a habit — a burst of activity follows a bad finding, then fades once the immediate pressure lifts.

Continual improvement, properly run, is what prevents all three — it's a standing habit, not a response to crisis.

The PDCA Cycle

Plan what needs to change, based on real data. Do — implement the change on a manageable scale first. Check whether it actually worked, using the same verification principle from Lesson 5's audit lifecycle. Act — roll it out fully if it worked, or adjust if it didn't. Then repeat, because continual improvement means the cycle never formally ends. This is the same structure behind Lesson 4's Corrective Action Lifecycle and Lesson 7's Management Review — PDCA is the general pattern those two specific processes are both built from.

Seven Real Sources of Continual Improvement Data

Most companies already generate all of this data — the gap is usually in connecting it to actual decisions, not in collecting more of it:

Notice crew suggestions sit on this list alongside formal audit data. Crew on board often spot a recurring friction point long before it becomes a Non-Conformity — a genuine continual improvement culture treats that input as seriously as an external finding, not as an afterthought.

KPIs Worth Tracking Between Audits

The Near-Miss Reporting row is worth pausing on: a rising near-miss count usually means crew trust the reporting process, not that safety is declining. A company that sees near-miss reports drop to zero has far more often stopped hearing about problems than stopped having them.

Interactive: Improvement Planner

Turn one real problem into a structured improvement plan, the way a genuine PDCA cycle requires.

Frequently Asked Questions