From Accuracy to Readiness: Metrics and Benchmarks for Human-AI Decision-Making
Organizations: Singapore Management University, Singapore
Abstract
Artificial intelligence (AI) systems are deployed as collaborators in human decision-making. Yet, evaluation practices focus primarily on model accuracy rather than whether human-AI teams are prepared to collaborate safely and effectively. Empirical evidence shows that many failures arise from miscalibrated reliance, including overuse when AI is wrong and underuse when it is helpful. This paper proposes a measurement framework for evaluating human-AI decision-making centered on team readiness. We introduce a four part taxonomy of evaluation metrics spanning outcomes, reliance behavior, safety signals, and learning over time, and connect these metrics to the Understand-Control-Improve (U-C-I) lifecycle of human-AI onboarding and collaboration. By operationalizing evaluation through interaction traces rather than model properties or self-reported trust, our framework enables deployment-relevant assessment of calibration, error recovery, and governance. We aim to support more comparable benchmarks and cumulative research on human-AI readiness, advancing safer and more accountable human-AI collaboration.
Figures & tables
Appendix figures & tables2 assets
Supplementary material from the paper’s appendix.
Appendix
| Metric (example) | Data source (trace) | U–C–I stage | Design action (what you do when it’s bad) |
| Outcome metrics (What happened?) | |||
| Team accuracy / TeamGain | Final decision , ground truth ; condition logs | Improve | Adjust delegation policy (when to defer / override); revise workflow to route high-risk cases to human review. |
| Regret_best / Oracle gap | per case | Improve | Diagnose collaboration failures (not model limits); target training on cases where either human or AI was correct but the team failed. |
| Error recovery vs. amplification | transitions + | Improve | Identify whether UI causes harmful flips; refine prompts/explanations to reduce changed-to-wrong; add guardrails for high-stakes edits. |
| Reliance & interaction metrics (How was AI used?) | |||
| Accept-on-wrong Reject-on-wrong | Agreement with AI ( ) conditioned on AI correctness | Understand + Control | Curate “failure sets”; add reliability cues; introduce regions-of-no-use; require justification or second-check for high-risk acceptance. |
| Metric (example) | Data source (trace) | U–C–I stage | Design action (recommended response) |
| Safety & harm metrics (What went wrong?) | |||
| AI-harm / AI-help | Help–harm decomposition from | Control + Improve | Add guardrails where AI induces harm; adjust autonomy (e.g., limit deferral) in high-harm regions; prioritize model fixes for harm-heavy slices. |
| Missed-help / Under-reliance | , , but | Understand | Improve “when to trust” instruction; show exemplars of correct AI behavior; add calibrated confidence cues for beneficial reliance. |
| Near-misses (high-risk disagreements) | High-stakes disagreement logs; risk labels; margin/uncertainty if available | Control | Trigger required second review; add risk-based escalation rules; refine “regions-of-no-use” policy. |
| Rule–behavior contradiction rate | Policy label + behavior event ( ) | Control + Improve | Fix workflow compliance gaps; redesign the UI to make required actions salient; update governance policy or training based on observed violations. |
| Rollback rate / Escalation rate | Rollback logs ; escalation logs | Control + Improve | Audit contested decisions; improve contestability pathways; adjust accountability and when rollback is encouraged. |