Five things people get wrong about AI at work
The myths that come up a lot when I teach, and what I've actually seen.
When I teach, the same few myths keep showing up, whether it’s one person or a full room. Here they are, and what I’ve actually seen.
1. “It’s going to replace my job.”
In my experience it takes over chores, not people. The copying, the reformatting, the first drafts. The judgment part, knowing what’s right for this client on this day, stays with you. If anything, you get more time for it.
2. “It’s always right.” (Or its twin: “It’s always wrong.”)
It’s often right and sometimes confidently wrong, both at once. Treat it like a fast first draft from a new teammate: useful, and worth reading.
3. “You need to know how to code.”
You can start with clear instructions and no code at all. Explain the task the way you’d explain it to a coworker. Code helps for some things, like automating spreadsheet work, but it’s not the price of entry.
4. “It’s only for big companies.”
Some of the most useful wins I’ve seen are tiny. One person, one weekly task, a little time back every week. You don’t need a budget or a project plan for that. You need one task and half an hour.
5. “I’ll get to it once things calm down.”
Things don’t calm down. The people who get the most out of AI start before they feel ready and build the habit. Waiting for the right moment mostly means waiting.
One worry that isn’t a myth
“I’m nervous I’ll mess something up.” That one’s fair, and I don’t brush it off.
The answer is to start with work only you will see, and to read it before anyone else sees it. Nervous is a pretty good place to start from.