Field Note: When Your AI Says No, What Does It Cost You Not to Know?
Back to BlogFrom Substack

Field Note: When Your AI Says No, What Does It Cost You Not to Know?

You have an incident response plan for a data breach. You almost certainly don't have one for the day your AI is found to be failing a protected group. A real case shows what that costs.

Dr. Dédé Tetsubayashi|2 min read|July 14, 2026

The Return | Field Notes | AI Incident Response | 10 min read


The algorithm that said no & the missing playbook.

This is the sixth field note. When I drafted the June and July arc, this article used a hypothetical: imagine your AI tool produces a discriminatory outcome — what then? Between drafting and publishing, the hypothetical stopped being hypothetical. A case over a healthcare AI system called nH Predict advanced through the courts in 2026, and it is the clearest illustration I have ever seen of what happens to an organization that deploys a demographic-sensitive AI system and has no plan for the day it is found to be failing people. So I am rewriting this field note around the real thing.


Thanks for reading Dr. Dédé! This post is public so feel free to share it.

Share

Your organization has an incident response plan for a cybersecurity breach. You have one for a data leak. You have one for a service outage. These plans have detection mechanisms, severity tiers, containment procedures, communication trees, and post-incident reviews, and they are rehearsed, because everyone understands that the difference between a managed incident and a catastrophe is whether you had the plan before you needed it.

Do you have one for an AI bias incident? For the day your hiring tool is found to have been systematically downranking candidates with non-Western names? For the day your customer-facing system is shown to produce different response quality based on a customer’s perceived demographic? For the day a tool you deployed as a productivity enhancer turns out to have been quietly failing a protected group for months?

In most organizations, the answer is no. There is no playbook. And the cost of not having one is no longer something I have to ask you to imagine, because a case currently in litigation shows it in detail.

THE THREE-QUESTION PULSE

  1. Does your organization have any documented process for responding to an AI bias incident? (Yes / In progress / No / I don’t know)

  2. How would a bias incident most likely first surface in your organization: employee complaint, customer complaint, internal monitoring, audit, or external/legal?

  3. Since the 2026 regulatory rollbacks, has your organization’s appetite for AI fairness work gone up, down, or stayed the same?

Read more

Enjoyed this? Read more on Substack

This piece was originally published on Dr. Dédé's Substack. Subscribe to get every new essay and field note in your inbox.

Ready to act on this?

See where your organization stands on AI governance — or talk it through with Dr. Dédé.

Want more insights?

Explore more writing on AI governance, tech equity, and inclusive innovation.

Back to All Articles