How Would You Learn to Use AI at Work If You Were Starting From Zero?
If I had zero experience with AI today, I wouldn't start by taking a 20-hour course.
I wouldn't spend a week comparing AI tools.
I wouldn't try to understand how large language models work.
And I definitely wouldn't attempt to learn every new AI feature being announced.
I'd start with something much simpler:
I'd find one annoying task I already do at work and try to make it easier with AI.
That's because the biggest problem for AI beginners usually isn't access.
It's knowing where to start.
You've probably seen people casually mention that AI saves them hours. You've watched someone generate a polished email in seconds. Maybe you've even opened an AI chatbot yourself, typed something, received a mediocre answer, and thought:
"I don't really understand what I'm supposed to be doing with this."
You're not bad at AI.
You probably just haven't had a system for connecting it to your actual work.
If I were starting from zero, this is the path I'd follow.
1. First, Ignore Most of What You've Heard About AI
The AI world is noisy.
Every week there's a new tool, model, feature, automation platform, prompting technique, or productivity hack.
For someone starting from zero, that creates a dangerous trap:
Learning about AI starts replacing actually using AI.
You can spend hours watching videos about AI agents without having AI help you write one email.
You can bookmark hundreds of prompts without using one on tomorrow's work.
You can compare five different AI assistants when the one you already have access to is perfectly capable of helping with your first experiment.
So I'd narrow the goal dramatically.
I'd ask three questions:
What do I repeatedly do?
Which parts take longer than they should?
Which parts involve writing, summarizing, organizing, researching, brainstorming, or processing information?
That's your starting point.
For example, an HR professional might repeatedly summarize interview notes.
A salesperson might write follow-up emails.
An administrator might turn meeting notes into reports.
A manager might prepare weekly updates.
A freelancer might turn rough ideas into client deliverables.
You don't need to "learn AI."
You need to learn where AI fits into your job.
2. Pick One Annoying, Low-Risk Task
If I were starting tomorrow, I'd deliberately choose a small task.
Not something mission-critical.
Not a sensitive decision.
Not something where an incorrect answer could create serious consequences.
I'd choose something repetitive and easy to review.
Good first experiments include:
Drafting a routine email
Summarizing meeting notes
Creating an agenda
Turning notes into a report
Rewriting complicated information
Brainstorming possible ideas
Creating a checklist
Summarizing research
Organizing unstructured notes
Here's my favorite beginner test:
Find a task that normally takes you at least 10 minutes and see whether AI can produce a useful first pass.
Suppose you regularly write a weekly project update.
Instead of starting from a blank document, give AI the raw notes and explain what you need.
You might say:
"Turn these project notes into a concise weekly update for my manager. Organize it into completed work, current priorities, blockers, upcoming deadlines, and decisions needed. Don't invent information that isn't in my notes."
Then review the result.
Maybe it's 70% useful.
That's fine.
You've just discovered something important.
You don't need AI to magically produce the perfect answer.
You need it to reduce the amount of work you have to do yourself.
3. Learn One Prompting Framework Instead of Memorizing "Magic Prompts"
Beginners often think they're bad at prompting because their first few responses aren't very good.
Usually, the problem is simply a lack of context.
Compare:
"Write a report about this."
with:
"You are helping me prepare a weekly operations report. Using the notes below, create a concise report for a manager. Highlight completed work, unresolved issues, upcoming deadlines, and decisions that require attention. Use clear headings and bullet points. Don't add facts that aren't provided."
The second instruction gives AI a much better definition of the job.
A useful beginner framework is:
Role + Context + Task + Audience + Constraints + Output
You don't have to use those exact words every time.
Just remember that AI works better when it understands:
What is happening?
What do you want done?
Who is this for?
What should it avoid?
What should the final result look like?
And don't expect your first prompt to be perfect.
Treat prompting as a conversation.
If the response is too long, say so.
If the tone is wrong, explain the desired tone.
If it missed important information, provide more context.
If the structure is poor, show it the structure you want.
You're not looking for a magic sentence.
You're learning how to direct an assistant.
4. Turn One Successful Prompt Into a Repeatable System
This is where AI becomes much more valuable.
Imagine you discover that AI does a great job turning your meeting notes into a follow-up summary.
Don't type the same instructions from scratch every week.
Save them.
Better yet, turn them into a reusable template.
For example:
Meeting purpose: [insert]
Attendees: [insert]
Notes: [insert]
Then your saved instructions can tell AI to produce:
Key decisions
Action items
Responsible people
Deadlines
Unresolved questions
Follow-up communication
Now you've gone from experimenting with AI to creating a small workplace system.
I'd use this progression:
Try it → Improve it → Save it → Reuse it → Automate later
Notice that "automate" comes last.
You don't need complicated integrations on day one.
First prove that the workflow is useful.
Then make it repeatable.
Eventually, you can explore more advanced automation if the task justifies it.
You can also build a small personal AI toolkit around the work you actually do:
One workflow for writing.
One for summarizing.
One for processing information.
One for brainstorming.
One for a repetitive task.
That's already enough to make AI genuinely useful.
5. Learn AI by Solving Real Problems
If I were starting from zero, I wouldn't make "become good at AI" my goal.
I'd make solve one problem with AI my goal.
Then another.
Then another.
Your work becomes your curriculum.
The cycle is simple:
Find → Try → Review → Improve → Save → Repeat
Find something repetitive.
Try using AI.
Review the result carefully.
Improve your instructions.
Save what works.
Then repeat the process with another task.
Over time, you're building something far more valuable than a collection of AI trivia.
You're developing the ability to recognize:
"This is a task AI can probably help me with."
That's the real workplace skill.
Of course, AI output still needs human judgment. Check important facts, protect confidential information, follow your employer's policies, and don't blindly accept an AI-generated answer simply because it sounds confident.
The point isn't to replace your judgment.
It's to give your judgment a better starting point.
If I Were Starting From Zero Today
I'd keep the first day incredibly simple.
I would find one task I dislike.
I'd give AI enough context to help with it.
I'd review the result.
I'd improve the prompt.
I'd save what worked.
And I'd do it again tomorrow.
That's it.
Because the goal isn't to become the person at work who knows the most about artificial intelligence.
It's to become the person who knows how to make AI useful for their actual job.
And if you're starting from zero, you don't necessarily need another enormous AI course or another list of 100 tools.
You need a practical system that helps you go from "I know I should probably use AI" to "I just used AI to save myself 20 minutes."
That's exactly why I created AI in a Day: The Non-Technical Professional's Playbook for Automating Work, Looking Smarter.
It's a 25-page playbook for non-technical professionals who want to stop merely exploring AI and start using it on real work—with practical prompts, workflows, and a straightforward system you can apply immediately.
You don't need to learn everything about AI. You need to know how to start.

Replies