Ways you should not use AI at work - Be Aware
By Susan Gonzales on 08/11/2025 @ 08:28 AM
Generative AI tools are an incredible resource. Keep in mind they are tools! While it can be tempting to fully rely on them at work - remember - they are a resource. Beware of becoming dependent on these tools.
9 Things You Shouldn’t Use AI For at Work
AI is becoming a powerful tool in the workplace—helping us write emails, summarize reports, generate ideas, and even automate repetitive tasks. But just because AI can do something doesn’t always mean it should. Using AI the wrong way can lead to privacy risks, bad decisions, legal issues, or damage to your professional reputation. It’s important to know where to draw the line and when human judgment still matters most. Below are 9 situations where using AI at work can do more harm than good—and how to handle them more safely.
1. Don’t paste confidential or private data into public AI tools
AI tools like ChatGPT and others may store your inputs. That means any client info, internal documents, employee details, or business strategies you share could be at risk. If it’s not something you’d post on a public website, don’t put it into a public AI system.
2. Avoid using AI to write or review contracts and legal documents
AI doesn’t understand the law—it just predicts words that “sound right.” Relying on it for contracts, terms of service, or policy language can leave out important legal protections or introduce serious errors.
3. Never use AI to make hiring, firing, or HR decisions on its own
While AI can help sort resumes or draft interview questions, it shouldn’t be the final decision-maker. Automated decisions can introduce bias, misinterpret context, or create legal and ethical issues—especially in hiring or termination.
4. Don’t use AI to give legal, financial, or medical advice
AI is not a lawyer, accountant, or doctor. While it can provide general information, using it to make decisions in these areas can lead to misinformation, legal violations, or even harm to others. Always consult a certified professional.
5. Avoid presenting AI-generated work as completely your own
If AI helps draft a document, that’s fine—just be honest about it. Passing off AI work without disclosure can lead to ethical concerns, credibility loss, or even accusations of plagiarism.
6. Be careful using AI to respond to customers or the public
AI chatbots can sound robotic or give incorrect answers. If not reviewed, they can accidentally misrepresent your business, offend someone, or share outdated or misleading info. Always keep a human in the loop.
7. Don’t let AI write or review code without human checks
AI can help developers work faster, but it also makes mistakes—sometimes dangerous ones. It might generate insecure or buggy code, or overwrite important files. Always double-check AI-generated code before using it.
8. Avoid relying on AI note-takers for sensitive meetings
AI transcription tools can misinterpret what’s said and sometimes save or share the wrong things. They may pick up private side comments or jokes that shouldn’t be documented. Use them with caution—and always inform participants.
9. Don’t let AI make complex ethical or leadership decisions
AI can’t feel, reason through complex emotions, or understand nuance. Using it to make calls on sensitive issues—like company values, employee well-being, or crisis responses—can come across as tone-deaf or impersonal.
How to Use AI Wisely at Work Use AI for brainstorming, drafting, and routine tasks—not final decisions.
Always review and edit AI-generated content.
Don’t share anything you wouldn’t want public.
Be transparent when AI helps create your work.
Keep humans in charge of sensitive, strategic, or legal matters.
Final Thoughts AI is a helpful tool, but it isn’t a substitute for human judgment, empathy, or ethics. As these tools become more common in the workplace, learning when not to use them is just as important as knowing when to say “yes.” By using AI thoughtfully—and staying aware of its risks—you can keep your work smart, secure, and professional.
To learn more about the ongoing conversation that inspired this blog, check out this article from ZDNet.com.