# Ethics and responsible use at work
Your manager asks for a draft performance review of a colleague by Friday. You paste their last six months of work into ChatGPT, get a polished review back in 90 seconds, edit two sentences, and send it. Did you do anything wrong?
That question has no single answer, and that is exactly the point. Responsible AI use at work is rarely about breaking a clear rule. It is about a hundred small judgment calls where the rule does not exist yet. This lesson gives you a simple checklist to make those calls well.
Most workplaces in 2026 still have vague or missing AI policies. That leaves you exposed. If something goes wrong, "the tool did it" is not a defense. You are accountable for what you send, sign, and publish.
The good news: you do not need a law degree. You need a few honest questions you can ask yourself in under a minute.
Let's build that checklist by walking through real dilemmas.
Back to the review. The problem is not that AI helped you write. The problem is what went *into* it.
You pasted a colleague's work history into a public chatbot. Depending on your settings, that data may be used to train future models or stored on servers outside your company's control. You may have just leaked private HR information.
The fix is structural, not moral. Use an enterprise tool where your data is not used for training (ChatGPT Enterprise, Claude for Work, or Gemini in Google Workspace all offer this), or strip out identifying details before pasting.
There is a second issue: fairness. AI can flatten nuance and amplify bias. A review that says someone is "not a strong cultural fit" might be the model echoing patterns that disadvantage certain groups.
So the question is not "can AI write this?" It is "would I stand behind every sentence as my own judgment?"
Should you tell your manager the review was AI-assisted? A useful test: would disclosure change how the work is trusted or used?
A performance review is a high-stakes human judgment. Yes, disclose that AI assisted, and confirm the assessment reflects your own view. A first draft of a routine status email? No one needs a disclaimer.
A marketing colleague wants to clone the CEO's voice to narrate an internal training video. It would save a recording session. The CEO is busy. What's the harm?
A deepfake is synthetic audio, video, or images that convincingly imitate a real person. Tools to make them are now cheap and fast.
The harm is consent and precedent. Even for an "internal, harmless" use:
Voice-cloning fraud is a real and growing attack. The U.S. FTC has documented scams where cloned voices are used to impersonate family members and executives. See their consumer guidance on AI voice cloning.
Rule of thumb: never synthesize a real person's likeness without explicit, documented consent. Treat a cloned voice like a signature: powerful, and dangerous if forged.
You build a small script that automates a report your coworker spends two days a month producing. It works great. Do you ship it?
This is the dilemma people avoid because it feels like betrayal. Automating a task can quietly reshape or eliminate a job. Hiding it is the wrong move; so is pretending the impact does not exist.
Here is a tiny, realistic example of the kind of automation that triggers this question:
import pandas as pd
# Read this month's raw sales export
df = pd.read_csv("sales_october.csv")
# Build the summary a colleague used to assemble by hand
summary = (
df.groupby("region")["revenue"]
.agg(["sum", "mean", "count"])
.round(2)
)
summary.to_csv("monthly_report.csv")
print("Report generated. Saved 2 days of manual work.")Twenty lines, two days saved. That is the power and the responsibility.
The responsible path: be transparent early. Tell the coworker and your manager. Frame it as freeing up time, not cutting headcount, and let the people affected have a voice. Whether the job changes is a leadership decision, but you control whether it happens *honestly*.
Across those three dilemmas, the same five questions kept surfacing. This is your checklist. Run it before any meaningful AI-assisted task.
Before you paste, ask: would I be comfortable if this text appeared on a public website? If not, use an enterprise tool, anonymize it, or do not paste it.
AI hallucinates, meaning it invents facts, citations, and numbers that look correct. Check anything you will rely on. You own the errors.
Especially for decisions about people (hiring, reviews, lending, discipline), ask whether the model is reflecting unfair patterns. Add a human check.
No cloning voices, faces, or writing styles of real people without permission. No passing off someone's data as fair game.
If yes, disclose that AI assisted. If the work carries your judgment or authority, say so explicitly.
A simple way to remember it: Data, Accuracy, Fairness, Consent, Transparency.
Knowledge check
1. According to the lesson, what is the fundamental challenge of responsible AI use at work in 2026?
2. In the performance review dilemma, why does the lesson call the fix 'structural, not moral'?
3. The lesson offers a test for whether you should disclose that work was AI-assisted. What is that test?
4. Select ALL of the concerns the lesson raises about using a public chatbot to write a colleague's performance review.
Select all the correct answers.
5. Select ALL statements that reflect the lesson's reasoning about accountability and judgment when using AI at work.
Select all the correct answers.
"Disclose AI use" is good advice that is easy to over- or under-apply. Use this rough scale.
These are like using spellcheck or a calculator. The work and judgment are still yours.
A clean, low-friction line works fine: *"This draft was prepared with AI assistance and reviewed by me."*
When unsure, ask the model to challenge you:
I used you to help write [describe the task].
Acting as an ethics reviewer, list the top 3 risks
in how I'm using this output: privacy, accuracy,
fairness, consent, or transparency. Be blunt and specific.This will not make the decision for you, but it surfaces blind spots in seconds. Treat its answer as a prompt for *your* thinking, not a verdict.
These actions are compiled in the role's Playbook.
Then you set a personal standard and document it. Three moves:
1. Default to enterprise or local tools for anything work-related, so your data is not used for training.
2. Keep a one-line note of where you used AI on important deliverables. If asked later, you have an answer.
3. Raise the gap. Tell your manager the team needs a basic AI policy. Volunteering to draft it is a fast way to look like a leader, not a liability.
For a solid, free framework to point colleagues toward, the NIST AI Risk Management Framework is the most widely referenced public standard, and it is readable without a technical background.
Responsible AI use is not about fear. It is about ownership. The model is a very capable assistant that has no accountability, no memory of consequences, and no stake in your reputation. You have all three.
So treat every output as a draft that becomes *yours* the moment you send it. That single mindset shift handles most situations the rules have not caught up to yet.