Root Cause Analysis (RCA)

Root cause analysis (RCA) asks why a problem happened and what changes could reduce the chance of its return. A team starts with a clearly described event, builds a timeline, checks evidence, and examines contributing conditions. Tools such as the five whys or cause-and-effect diagrams can guide discussion, but forcing one tidy 'root cause' can conceal multiple interacting failures.

Consider a service business whose online estimate form stops sending leads after a website update. The visible symptom is a drop in inquiries. Investigation might uncover an incompatible plugin change, missing automated tests, and monitoring that did not alert anyone. Restoring the form addresses the immediate impact; improving release checks, rollback procedures, and alerts addresses the conditions that allowed the outage to persist.

Good RCA separates supported findings from speculation and assigns corrective actions with owners and validation dates. It is not a blame exercise or a promise that every incident can be prevented. In cybersecurity operations, the current NIST incident-response guidance emphasizes continuous learning and improvement as incidents are handled. RCA is broader than an SEO audit: the same method can examine operational, customer-service, technical, or safety failures.