AI Ethics in Practice: Questions Every Business Should Be Asking Before Deploying AI

The Ethical Questions That Rarely Get Asked Until Something Goes Wrong

The deployment of AI systems in business contexts has outpaced the development of frameworks for evaluating whether those deployments are appropriate, fair, and aligned with the values the organization claims to hold. When an AI hiring tool is later found to have systematically disadvantaged certain groups of applicants, the ethical failure was present in the design and deployment decisions made before the system went live — decisions made without the questions that would have surfaced the concern.

Business leaders who would never knowingly create discriminatory hiring practices, mislead customers, or violate privacy are doing all three things inadvertently through AI systems deployed without adequate ethical scrutiny. The questions that follow aren’t a complete ethics framework — they’re the starting points that catch the most common and most consequential ethical failures before deployment rather than after.

Who Does This System Affect and Were They Consulted?

Every AI system has direct users (the people who interact with it) and affected parties (the people whose lives it makes decisions about, who may never directly interact with the system at all). A hiring AI has direct users who are the recruiting team; its affected parties are job applicants who are evaluated by it and who may never know an AI system was involved in their rejection. An AI customer service system has direct users who are customers; its affected parties include the employees whose work it replaces.

The people most affected by an AI system are frequently the least consulted during its design. The applicants who would be evaluated by a hiring AI weren’t consulted about the criteria it uses. The customers who would interact with an AI service agent weren’t asked whether they’re comfortable with that interaction. Designing AI systems without consulting the people they’ll most significantly affect produces systems that serve the interests of the deploying organization while potentially working against the interests of the people it ostensibly serves.

What Data Was This Trained On and What Biases Did That Data Contain?

AI systems learn patterns from training data, and training data reflects the world as it was — including historical inequities, discrimination, and representation gaps. A credit scoring AI trained on historical lending data learns from data in which lending was discriminatory; a facial recognition system trained on datasets overrepresenting lighter-skinned faces performs worse on darker-skinned faces. The AI doesn’t create these biases — it finds and amplifies them.

The due diligence question: what is the provenance of the training data, and what audits have been conducted for the biases that data might contain? For purchased AI systems or vendor-provided models, this requires asking the vendor for documentation of training data sourcing, bias auditing, and performance metrics disaggregated by demographic group. Vendors who can’t or won’t provide this information are implicitly acknowledging that they don’t know their system’s biases — which is itself important information.

How Will Errors Be Detected, Corrected, and Communicated?

All AI systems make errors. The relevant question isn’t whether errors occur but what happens when they do: how will the system’s errors be detected (rather than silently accumulating), how quickly can errors be corrected, who bears the cost of errors when they affect specific people or groups, and what obligation does the deploying organization have to communicate about errors to those affected?

AI systems in consequential decision-making contexts — hiring, lending, medical diagnosis, insurance underwriting, criminal justice — have error rates that translate directly into real harm for real people. A false positive in a fraud detection system that locks a legitimate customer out of their bank account is an error with immediate, concrete harm. The dispute resolution process (or absence of one) for people harmed by AI system errors is an ethical design choice that should be explicit rather than an afterthought discovered when the first harmful error occurs.

Is There Meaningful Human Oversight and When Is It Engaged?

Human-in-the-loop processes — where humans review, approve, or can override AI recommendations — are the primary mechanism for catching AI errors before they become consequential harms. The ethical question is whether the human oversight is meaningful or performative: a human approving 95% of AI recommendations without reviewing them isn’t providing oversight; they’re providing authorization for the AI to operate with a human rubber stamp.

The conditions under which human override should be not just possible but actively required: decisions with high stakes for specific individuals (termination, denial of credit, medical diagnosis), decisions at the margins of the AI system’s training distribution (cases that are unusual in ways the AI may not handle well), and any case where the affected person requests human review. An AI system with no meaningful human override path, or with override processes designed to be impractically burdensome, is operating without the accountability that consequential decision-making requires.

RELATED ARTICLES

The AI Tool That’s Changing Research: How to Use AI Literature Search Effectively

The Research Workflow That Used to Take Days Academic and...