There’s a sentence I hear all the time. It shows up in different versions, but it’s always the same idea underneath.
“I’m not a tech person.”
People say it like it’s a fact about themselves, the same way they’d say their height. And then they use it as the reason they haven’t started with AI. They figure AI belongs to people who code, or people who work in tech, or people who understand what’s happening under the hood.
I want to push back on that gently, because I said the same thing about myself. I’m not a tech person either. I still say it. And I use AI almost every day to build real things.
Here’s what I’ve learned: the qualification for using AI well was never technical skill. It’s knowing your own work. And you already have that.
The hard part of AI isn’t the part you think
Let me tell you what using AI actually looks like, because if you haven’t started, you might be picturing something harder than it is.
You open a website. There’s a box. You type into the box, the way you’d type a text message. The AI types back.
That’s it. That’s the technical part. If you can send a text, you already have the tech skills.
So why do some people get useful answers while other people get generic mush? It’s not because the first group is more technical. It’s because they gave the AI something to work with. They described their situation clearly. They explained what they were trying to do, what they were working around, and what a good result would look like.
In other words, the real skill isn’t typing. It’s context. And context comes from knowing your work — the details, the problems, the shortcuts, the things nobody notices until they go wrong.
That’s not a tech skill. That’s a job skill. And you’ve been building it every shift you’ve worked.
Your job has been training you this whole time
Think about what you actually know because of your job.
You know where the process breaks down, because you’re the one who deals with it when it does. You know which questions customers ask over and over. You know the workaround everyone uses because the official way doesn’t work. You know what your manager forgets, what the new hires struggle with, and what would fall apart if you called out sick for a week.
None of that is written down anywhere. It lives in you.
Now here’s the thing about AI: it’s very good at general knowledge and very bad at knowing your specific situation. It has read half the internet, but it has never worked your job. It doesn’t know your customers, your systems, or your Tuesday problems.
You do.
So when you sit down with an AI tool, you’re not the beginner in the room. You’re the one holding the information the AI can’t get anywhere else. The AI brings the general. You bring the specific. The specific is the valuable part.
Most people have this backwards. They think they need to learn a lot about AI before they can use it. Really, the AI needs to learn from them — and they’re the only ones who can teach it.
Start at your job, not at the tool
Most AI education starts at the tool. Here’s ChatGPT, here’s what a prompt is, here are ten prompts to try. That’s not wrong. It’s just out of order for a lot of people.
Because if you start at the tool, you end up staring at the empty box wondering what to type. The box can’t tell you what matters about your work. Only you know that.
So I’d flip the order. Before you worry about which AI tool to use or how to phrase anything, get clear on your side of the conversation first. What do you actually do all day? What do people count on you for? What frustrates you enough that you’ve built your own way around it?
Those answers are the raw material. Once you have them, the typing part is easy. You’re not searching for magic words. You’re just describing work you know better than anyone.
This is the idea I keep coming back to in everything I make: you don’t work for AI, and you shouldn’t wait for it to figure you out. You direct it, using what you already know. (If you want the fuller version of that thinking, my free book Direct the Work walks through it from the beginning.)
One practical way to start
If you want a place to begin that starts at your job instead of at a tool, I built one.
It’s called Your Job Is the Clue. It’s a free guided tool that walks you through a short set of questions about the work you already do — what you handle, what people rely on you for, what keeps coming up. At the end, it hands you one practical idea for your next move, plus a starter prompt you can take into ChatGPT, Claude, or Gemini.
It takes about fifteen minutes. There’s no signup and nothing is saved. It’s just you and your own answers.
You don’t need to become a tech person first. You don’t need to study AI for months before you’re allowed to touch it. You need what you already carry into work every day — and a way to see it clearly enough to use it.
Your job is the clue. It always was.