Two different unrelated events this month made me think more about the role of "Confusion Matrix". In one event, I was having some conversations with the clients where discussions emerged about reporting metrics on false negatives and false positives on how accurately AI predicted risks and mitigations for product development. In another event, I was working with doctoral candidates who were not thinking about confusion matrix in the context of ethical decision making. As I reflected on this gap between scholars and practitioners, I felt compelled to emphasize, "A metric can tell us how often an AI system is right or wrong. Leadership must ask who is harmed when it is wrong." This thought process differentiates accuracy, explainability, and explicability that requires leaders to use the confusion matrix as a tool in their congoing governance.
In a nutshell,
- Accuracy measures performance.
- Explainability measures the reasoning behind a prediction.
- Explicability measures ethical and social accountability.
Suppose the model produces these results:
| Actually Fraud | Actually Legit | Total | |
|---|---|---|---|
| AI says Fraud | 80 True Positives (TP) | 90 False Positives (FP) | 170 Transactions |
| AI says Legit | 20 False Negatives (FN) | 810 True Negatives (TN) | 830 Transactions |
| Total | 100 Fraud Transactions | 900 Legit Transactions | 1000 Transactions |
When reading this table, TP and TN are our win! That is, the model's prediction aligned with the reality. So, the model appears reasonably effective because it correctly identifies 890 (80 TP, 810 TN) of 1,000 transactions, giving it 89% accuracy.
But this accuracy alone hides an important story. The model identifies 170 (80 TP, 90 FP) transactions as fraudulent. Only 80 TP are actually fraudulent. Therefore, its precision is approximately 47%. This is a powerful reminder that when this AI model says something is fraudulent, it is wrong more than half the time! Then, how do we hold ourselves accountable to end users in the product delivery chain? (regardless of your role in using the AI model) You can see the ethical lens evolve.
Now consider recall, or false positive rate.
- Recall is the ratio of TP/(TP+FN). So, the model identifies 80 of the 100 fraudulent transactions. Its recall is 80%. That metric sounds promising and positive until we ask another question: What is the impact of our solution to the people in the 20 fraud transactions the model missed? These are now ethical leadership questions. The organization absorbs the financial risk, while potentially allowing additional fraudulent activity to occur.
- False Positive Rate is the ratio of FP/(FP+TN). So, the model wrongly classified 90 of the 900 transactions. What would be the impact to customers? Perhaps, they may experience delayed payments, frozen accounts, additional verification, reputational consequences, or loss of access to required timely services.
Connections to Ethics
The 11% (90 FP + 20 FN / 1000 Total) therefore creates two different types of harm. I view the false positives (FP) raise questions about justice, autonomy, non-maleficence, and fidelity while the false negatives (FN) raise questions about beneficence and non-maleficence. If we think of AI as an actor in the solution-engineering, what abuser persona could AI unintentionally be playing? So, the bigger governance questions we should ask as leaders is if this level of error acceptable for our customers when using AI? That question cannot be answered by the model and data. It must be answered by leadership with human insight and intervention.
| Metric | Group A | Group B |
|---|---|---|
| Accuracy | 92% | 87% |
| Precision | 70% | 42% |
| Recall | 84% | 76% |
| False Positive Rate | 5% | 14% |
| False Negative Rate | 16% | 24% |
The organization's overall accuracy may still look acceptable. But the experience of the two groups is dramatically different. A customer in Group B is substantially more likely to be incorrectly flagged and more likely to have a fraudulent transaction missed. I hope we can see how the algorithmic bias becomes a leadership issue in this case. The leader should not immediately conclude that the model is discriminatory. The numbers alone do not establish causation. Instead, they should trigger investigation.
The governance level leadership questions all of us should think as part of both problem-solving and decision-making involve (examples):
- Why is the error distribution different?
- What characteristics or historical patterns are influencing the model?
- Are those differences legitimate or artifacts of historical inequity?
- Are some communities bearing a disproportionate share of the system's errors?
- What happens to people after they are flagged?
- Can they challenge the decision?
- Who reviews the decision?
- How quickly can an error be corrected?
- What happens if the model continues producing the same pattern six months from now?
- Who absorbs the risk of our misses?
In my opinion, this is explicability in action. Explainability tells us why the model produced the prediction. This can be on a dashboard but leadership needs explicability that asks whether the prediction and its consequences are ethically defensible. Holding ourselves accountable for the errors our models cause to the people and society is a governance decision. Confusion Matrix is not just a data science technique. It is an ethical lens to risk driven development. This is why I propose that we shift more into the "Accountable AI" than limit ourselves to "Responsible AI."
What do you think?
No comments:
Post a Comment