All AI videos

AI video

1,368 AI Failures and What They Teach About Evals — Vishal Srivastava & Tanmay Sah, New York Life

Vishal Srivastava and Tanmay Sah classify 1,368 public AI incidents and propose a failure-driven build, break, and fix loop for higher-risk systems.

AI Engineer · 2026 featured video

Watch on YouTube

What this video shows

The speakers group 1,368 records from a public incident database into technical strength, deployment controls, and business impact, with 13 sub-areas that they say cover about 98% of the sample. They report that weak controls such as monitoring and human review are closely associated with harm.

Use the taxonomy to ask what your current suite omits. Rank cases by affected people, reversibility, money, legal duty, and scale. Seed known failures into a safe environment, verify that the grader catches them, and require evidence for escalation and recovery paths.

Use NIST's AI Risk Management Framework to connect test priorities with organizational risk.

What you will learn

  • Test deployment controls and business consequences alongside technical output.
  • Spend more evaluation effort where a wrong action is costly or hard to reverse.
  • Seed failures to verify that the evaluator can detect them.
  • Use incidents to add regression cases rather than only to update a risk register.

How to apply this safely

  1. List technical, control, and business failures for one use case.
  2. Score impact, exposure, reversibility, and detection delay.
  3. Plant one safe example of each high-priority failure in the test environment.
  4. Confirm the grader, monitor, escalation, and recovery path all respond as intended.

Important limitations

  • Public incident databases can undercount private failures and overrepresent events that attract reporting.
  • A taxonomy that covers the reviewed records does not prove it covers future incidents.
  • Association between weak controls and harm does not establish one control as the cause.
  • New York Life employs the speakers, and the talk does not provide an independent replication package.

Sources to check

Continue learning on Learnetto