28% of employed American adults already use ChatGPT for work. Most of them figured it out in an afternoon, not a bootcamp. Nobody gave them a certification. They just started typing.
If you've been waiting for the right moment to start using AI at work, this is your sign that the right moment was six months ago. But today is fine too. Here's how to actually do it, without the $997 course, the 47-tool stack, or the LinkedIn posts about your "AI journey."
How to use AI at work without overcomplicating it
The mistake most people make is treating this like a new skill that requires study. It's not calculus. It's closer to learning to use Google, except the results come out in full sentences and you have to tell it what you actually want.
Start here: open ChatGPT or Claude. Pick one. They're both free at the basic tier. Type something work-related that you'd normally spend 20 minutes on. See what comes back.
That's it. That's the orientation. Everything after this is just getting better at describing what you need.
The reason people don't start isn't that they lack tools or knowledge. It's that they're waiting to feel ready. You won't feel ready. You'll feel ready after you've used it a dozen times and it's saved you two hours on something tedious.
Start with the shit you hate
This is Rule #12 in Don't Replace Me, Dmitry Kargaev's field guide for normal people with real jobs. He calls it the 40% Rule: roughly 40% of most knowledge workers' tasks can be assisted by AI right now, today, without any special training. The trick is to start with the worst 40%, not the interesting parts of your job.
Think about your week. What made you want to stare at the ceiling?
The status update email nobody reads but everyone demands. The meeting notes you have to turn into action items. The job description HR asked you to write. The slide deck that's basically a bulleted list of things everyone already knows. The contract summary your client needs by Thursday. The performance review boilerplate.
That's your starting list. Not "how can AI help me think more strategically." Not "how do I use AI to disrupt my industry." Just: what is the tedious, time-draining, low-creativity work that fills your calendar and makes you feel like a human copy-paste machine?
Start there. It's unglamorous. It also works immediately. You'll get your first real win in 20 minutes, and that's what gets you hooked on the right thing: time back, not novelty.
The smart intern framework: how to actually prompt it
Bad prompts get bad results. Not because AI is dumb, but because you're talking to something that can't read your mind and doesn't know your context. Rule #13 from the book puts it plainly: talk to it like a smart intern.
A smart intern is capable, eager, and completely missing your context. They haven't sat in your meetings. They don't know your clients. They don't know your boss hates bullet points or that "streamline" is a forbidden word at your company. You have to tell them.
Here's a simple structure that works:
- Role: Tell it what it is ("You're a senior HR manager at a mid-size tech company")
- Context: Tell it what it needs to know ("We're doing annual reviews and I need to give feedback on someone who's technically strong but struggles with stakeholder communication")
- Task: Tell it what to do ("Write a draft performance review comment that's honest but constructive")
- Format: Tell it how you want the output ("Keep it under 150 words, no jargon, no bullet points")
That's it. Four things. You don't need to learn "prompt engineering." Anyone selling you a course on prompt engineering in 2025 is selling you something that was barely useful in 2023 and is mostly irrelevant now. The models got smarter. Clear instructions are enough.
If you don't love the first result, just say "make it shorter" or "make it less formal" or "that sounds corporate, rewrite it." It's a conversation. Go back and forth until you get something usable.
This came from a book.
Don't Replace Me
200+ pages. 24 chapters. The honest version of what AI means for your career, written by someone who actually builds this stuff.
Get the Book →What this looks like by role
Different jobs have different tedious work. Here's where to start depending on what you actually do:
| Role | Start here |
|---|---|
| Marketing | First drafts of emails, ads, social posts, briefs |
| Finance | Summarizing reports, writing commentary on data, formatting |
| HR | Job descriptions, offer letter language, policy summaries |
| Operations | Process documentation, meeting recaps, vendor comms |
| Legal | Contract summaries (not legal advice, summaries) |
| Sales | Prospecting emails, call prep, CRM note cleanup |
| Managers (all) | Performance review drafts, agenda creation, status updates |
The pattern is the same in every row: the output that somebody needs but that you'd rather not spend two hours writing. AI is not replacing your judgment here. It's replacing the blank page.
You review it. You edit it. You add the context it couldn't know. The first draft is just the part that was eating your afternoon.
Stop collecting tools
Here's where people lose the plot. They read a roundup article about "50 AI tools every professional needs" and spend three weeks exploring products instead of using AI for actual work.
Most of those tools are wrappers. A wrapper is a product built on top of ChatGPT or Claude with a prettier interface and a monthly subscription. Sometimes they're useful for specific tasks. Usually you don't need them.
The author of Don't Replace Me, who has built AI systems professionally, puts it plainly: "You don't need anything but Claude or ChatGPT. Everything else is mostly wrappers."
Pick two, maybe three tools total. For most people that's:
- ChatGPT (GPT-4o) for general writing and research tasks
- Claude (claude.ai) for longer documents, analysis, and writing that needs to sound more human
- Optionally: whatever AI is baked into the software you already use (Microsoft Copilot in Office, Gemini in Google Workspace)
That's a complete stack. You don't need Jasper, Copy.ai, Notion AI, and six browser extensions. Every hour you spend evaluating new tools is an hour you didn't spend using AI for actual work.
Master the two you have. Get fast at them. Then, if there's a specific workflow where another tool genuinely helps, you'll know it because you'll hit a real limitation, not because someone wrote a sponsored post about it.
The question nobody asks: should you tell anyone?
This comes up sooner than you'd expect. You start using AI, you get good results, and then you wonder whether to mention it to your manager or just quietly keep doing it.
The answer is more complicated than it sounds. About 68% of workers who use AI at work don't tell their employer, according to Microsoft's 2024 Work Trend Index. Some of that is caution about company policy. Some of it is fear of being judged. Some of it is just: nobody asked.
The short version: check if your company has an AI policy. Many do now, and they often restrict what data you can paste into external tools. If your company has one, know it. Don't paste confidential client data into a free-tier AI tool if the policy says not to. That's not paranoia, it's professional hygiene.
If your company doesn't have a policy, you're in the vast majority. Use common sense about what you share. Keep proprietary information vague or anonymized when you're using AI to help with it. "A manufacturing client in the midwest" instead of the actual company name. It's not complicated.
As for disclosure: you don't have to announce it. You also shouldn't lie about it. If someone asks how you turned that report around so fast, "I used AI to get a first draft and then edited it" is a fine and true answer. If that makes your boss uncomfortable, that's a different conversation.
Your first 72 hours: a simple plan
Don't make this a project. Don't schedule a "learning sprint." Just do this:
Day one: Pick one task from your actual to-do list today. Something you'd rather not do. Write a prompt using the smart intern structure above. See what comes back. Edit it. Use it.
Day two: Do it again with something different. Notice what kind of output you had to fix a lot. That tells you where you need to give it more context.
Day three: Find one more use case. Try a slightly more complex task. Maybe a short analysis or a document that requires structure.
By the end of 72 hours, you'll have a sense of what it's good at for your specific job. You'll have a few prompt patterns that work. And you'll have made a dent in some work you'd normally hate doing.
That's the whole thing. There's no phase two that requires a bootcamp. You learn by using it. The rest is refinement.
For the full framework, including how to audit your own tasks, identify your combination moat, and build AI fluency without losing what makes you valuable, Dmitry Kargaev lays it all out in Don't Replace Me.
What AI at work actually feels like once you're in the habit
After a few weeks, it stops feeling like a special tool and starts feeling like, as Kargaev puts it, "just your keyboard." It's infrastructure. You reach for it the way you reach for a search engine, except you get a useful answer instead of ten ads and three Reddit threads.
The people who end up ahead aren't the ones who learned the most about AI. They're the ones who got comfortable using it fast, while everyone else was still watching YouTube explainers about it.
According to Goldman Sachs research on AI's labor market impact, the productivity gains from AI adoption are real, but they accrue to workers who actually adopt it, not workers who have opinions about it.
The gap between "I know about AI" and "I use AI" is the gap that matters. Cross it. It takes one afternoon.
And if you want to go deeper on the stuff that actually protects your career long-term, not just how to save time on emails but how to build the skills and positioning that genuinely make you harder to replace, there's more on that here.
Frequently asked questions
How do I start using AI at work if I've never used it before?
Open ChatGPT or Claude (both free), pick one task you find tedious, and describe what you need using this structure: role, context, task, format. You don't need training. You need one real task to try it on. Most people get useful results in their first session.
Do I need to learn prompt engineering to use AI effectively at work?
No. Prompt engineering as a formal skill is largely obsolete with modern AI models. Clear, specific instructions work fine. Tell the AI what role to play, give it the relevant context, describe the task, and specify the output format. That's all you need.
What are the best AI tools for work in 2025?
For most professionals, ChatGPT and Claude cover everything. Both have free tiers. If your company uses Microsoft 365 or Google Workspace, there's AI built into those already. Avoid the impulse to collect tools. Pick two and get fast at them.
Is it cheating to use AI at work?
No more than it's cheating to use spell-check or a calculator. You're responsible for the output, which means you still need to review and edit what AI produces. If your company has a specific policy against it, follow the policy. Otherwise, you're just working smarter. More detail on the workplace politics of this is over here.
What tasks should I use AI for first?
Start with your most tedious, repetitive, low-creativity work: drafting routine emails, writing meeting summaries, creating first drafts of documents you'd rather not write, reformatting content, generating options for something you're stuck on. The goal is to get time back, not to immediately use AI for your most complex or judgment-heavy work.
How much time can AI actually save me at work?
It varies by role and how you use it. McKinsey's 2023 research on generative AI found productivity gains of 20-40% on specific knowledge work tasks. In practice: if AI cuts the time to produce a first draft from 90 minutes to 20, and you do that three times a week, you're reclaiming a few hours. That compounds fast.
