Most operational problems that look like operator error aren't. Usually something upstream is causing the downstream failure: the process, the SOP, the environment. Getting to the root of it changes what the intervention looks like entirely.
"Embedding root cause analysis into how you review problems (not just as a post-incident tool) changes what the data can tell you over time."
I approach improvement methodically: define the problem precisely using data, trace it to root cause using structured methods (Fishbone, 5 Whys), then design and test the intervention. Most of the problems I've fixed looked like operator error on the surface. They weren't. Getting to the actual root cause changes what the fix looks like entirely.
How introducing RCA (Fishbone diagrams and 5 Whys) shifted a UK pharmaceutical warehouse from reactive error management to structured process improvement. No new technology. No capital spend.
The measurement framework, reporting tools and process changes that drove a 21% year-on-year improvement in lines picked per hour, with no new equipment and no capital spend.
About these cases
These problems were costing the operation time and money before the work started. The fixes held because they addressed the actual root cause, not the surface symptom. Paulo Gomes has worked in regulated pharmaceutical distribution for 10 years.
