Finding the root cause

KUALA LUMPUR: Finance Minister II Datuk Seri Amir Hamzah Azizan disclosed to the Dewan Rakyat that multiple failures contributed to seven troubled investments of Lembaga Tabung Haji (TH) experiencing total losses. This situation extends beyond simple accounting concerns; it is rooted in financial misconduct and investment errors, according to Amir.

He emphasized that accounting, akin to a thermometer, merely indicates the presence of an issue, not its resolution. The true focus should be on addressing the underlying cause - stagnant investments, unchecked risks, and flawed decision-making.

Organizations frequently encounter various problems. A process breakdown, a customer complaint, an audit finding, a delayed project, or a financial loss may arise. The typical response often involves rectifying the immediate issue and then moving on. However, merely fixing the symptom does not guarantee that the problem will not reoccur.

This is where Root Cause Analysis (RCA) comes into play. RCA is a systematic method employed to uncover the fundamental reasons behind a problem. It goes beyond the question, "What went wrong?" to delve deeper into "Why did it go wrong in the first place?" The goal is not to assign blame but to comprehend the conditions, vulnerabilities, and failures that enabled the issue to manifest.

A frequent error in problem-solving is conflating the symptom with the root cause. For instance, an organization might discover a duplicate payment made. The immediate corrective measure could be to recover the extra funds. Yet, this does not elucidate how the duplicate payment occurred. A deeper inquiry might reveal a lack of system validations for preventing duplicate invoices or unclear responsibilities for invoice verification.

The duplicate payment is the immediate problem; the absence of an effective preventive control could be one of the root causes. If management merely recovers the money and advises employees to "be more careful," the same issue might resurface. RCA aims to tackle the root cause instead.

RCA is especially crucial for auditors. An audit finding that merely states that "procedures were not followed" may be technically accurate but may not offer management a comprehensive understanding. The auditor should question why the procedure was not followed. Was it unrealistic? Was the training insufficient? Was responsibility unclear?

Was supervision weak? Was the control poorly designed? Was there inadequate staffing? Or was management oblivious to a significant risk? A robust audit finding not only identifies the control failure but also pinpoints the underlying cause. This differentiation is vital because actions based on superficial causes often prove ineffective.

For example, retraining employees might not resolve a problem stemming from a poorly designed system or excessive workload.

Avoiding a blame culture is essential in effective RCA. While employees may commit mistakes, organizations must scrutinize why the mistake was possible. If a single employee frequently makes the same error, the issue could be related to training or competence. If many employees make the same mistake, the organization should consider whether the process or control itself is deficient.

A blame-oriented approach may prompt employees to conceal mistakes. Conversely, a learning-oriented approach encourages transparency, allowing the organization to enhance its systems. The ultimate goal of RCA is not to produce an impressive analysis. Instead, it is to ensure that corrective actions address the underlying cause and minimize the likelihood of recurrence.

Corrective actions should thus be precise, measurable, and assigned to accountable individuals. Management should also set timelines and monitor whether the actions have been successful. For instance, replacing a faulty machine might resolve an immediate problem. However, if the root cause was inadequate preventive maintenance, simply replacing the machine may not suffice.

A more effective solution could involve implementing a preventive maintenance program, assigning clear ownership, establishing monitoring procedures, and defining escalation protocols. In conclusion, Root Cause Analysis is fundamentally about learning from problems rather than merely reacting to them. It enables organizations to transition from symptom treatment to sustainable problem-solving.

For managers, it provides a systematic approach to understanding recurring failures. For auditors, it enhances the quality of audit findings and recommendations. For employees, it fosters a culture where problems are examined objectively rather than concealed or blamed on individuals. The most crucial insight is simple: solving the problem is not the same as solving the cause of the problem.

Organizations that consistently inquire, "Why did this happen?" and act upon the answers are far more likely to prevent recurrence, fortify controls, enhance performance, and build organizational resilience.