Skip to main content
Machine Learning & Deep Learning

⏱ About 15 min15 XP

Using Deep Learning Responsibly

Lesson 7 catalogued what goes wrong with deep learning. This lesson is about what to do about it — not as a policymaker writing regulations someday, but as a person using AI tools right now. Responsible use is a skill you can practice, and it starts with one honest observation: the tool is powerful and limited simultaneously.

The Human Oversight Principle

Human oversight means keeping a person — someone with accountability, context, and judgment — involved in decisions that matter. It does not mean checking every output before it leaves the computer, which would be impractical. It means designing systems and workflows so that consequential decisions are reviewed by a human before they take effect, and so that humans retain the ability to override, correct, and audit the AI. In medicine, AI may flag a potential diagnosis in an X-ray, but a licensed radiologist reviews the flag before any treatment decision is made. The AI accelerates the radiologist's work; it does not replace their judgment. In content moderation, AI classifiers make an initial call on millions of posts per hour, but human reviewers audit samples, handle appeals, and set the policies the AI enforces. The AI scales a human-designed system; it does not substitute for one. The principle scales down to personal use. When you use a language model to draft an email, you are the human in the loop — review it before sending. When you use an AI to summarize a document, verify the summary against the original before relying on it. Your involvement is the oversight.

The Stakes Determine the Oversight Level

Not every AI output needs intensive review. The right level of oversight scales with the stakes. Using autocomplete to write a text message to a friend: low stakes, low oversight fine. Using AI to draft a medical summary, a legal document, or a news article: high stakes, careful verification required. Match your scrutiny to the consequences of being wrong.

Verification: How to Check AI Output Verification is the practice of confirming that an AI output is accurate, complete, and appropriate before using it. Several concrete strategies help. Cross-reference with primary sources. If a language model gives you a fact, look it up in a source that independently knows — an encyclopedia, an official report, a peer-reviewed study. Do not use the AI's own output to verify itself. Ask the AI to explain its reasoning. Sometimes errors become visible when you ask 'how did you get that?' An AI that cannot explain a claim may be confabulating. Test with known examples. Before relying on an AI system in a new domain, test it on cases where you already know the correct answer. If it fails on known cases, do not trust it on unknown ones. Be especially skeptical of specific details. Language models hallucinate statistics, citations, names, and dates more often than they hallucinate general concepts. Treat any specific fact — a number, a name, a date, a citation — as requiring independent verification. Honest Limits: What to Say and Not Say One of the most important practices is being honest about what an AI helped with and what it may have gotten wrong. In academic work, using AI without disclosure is a form of misrepresentation. In professional work, presenting AI output as authoritative when you have not verified it is a form of negligence. Honest limits also means being truthful about uncertainty when communicating AI output to others. 'The AI suggested X, which I have verified against source Y' is responsible. 'The AI says X' passed along without verification transfers the hallucination risk to someone less equipped to catch it.

Designing Systems With Responsibility Built In

Individual practices matter, but responsibility at scale requires thinking about how systems are designed. The lesson here connects back to Lesson 6's point about power concentration: whoever builds and deploys a deep learning system makes design choices that affect everyone who uses it. A well-designed system includes: clear documentation of what the model can and cannot do; testing against the specific failure modes from Lesson 7 before deployment; monitoring performance after deployment, especially for distribution shift; mechanisms for users to report errors and get corrections; human escalation paths for high-stakes decisions. None of these are technically exotic. All are choices. When a deployed AI system lacks them, that is a design decision — and someone made it. Asking 'who is accountable when this fails?' is always a legitimate question.

Start With a Question, Not a Trust Level

Rather than deciding 'I trust AI' or 'I don't trust AI' in general, ask a specific question each time: What are the failure modes for this particular model on this particular task? What would it cost me if the output is wrong? That question discipline is more useful than a blanket policy.

Prompt Challenge

Write a prompt that asks a language model to help you research a topic for a school report, while building in safeguards against hallucination.

Your prompt should…

  • instruct the model to state clearly when it is uncertain or does not know something
  • ask the model to provide verifiable sources or indicate that you will need to find them independently
  • specify the format and length of the response so it is easy to fact-check

What does 'human oversight' mean in the context of AI?

Why should you cross-reference AI-generated facts with primary sources rather than asking the AI again?

Oversight Protocol Design

  1. Pick a context where AI might be used: a school nurse using AI to suggest when to call parents, a teacher using AI to give feedback on essays, or a city using AI to decide which potholes to repair first.
  2. For your chosen context, design a minimum oversight protocol with exactly four steps: one for before deployment, one for ongoing monitoring, one for handling errors, and one for informing users.
  3. Be specific — 'check the model' is not a step; 'test the model on 50 labeled examples from our own school data and require 90% accuracy before use' is.
  4. Present your protocol to the class and invite critique.