Hi there!
Welcome to the 28th edition of Work in Beta.
In this edition, we explain what it really means to be an “AI-native” professional. It’s not about the tools you own or how clever the answers look on your screen. It’s about how you work. And it’s a choice anyone can make, starting with one task this week.
Also, if you’ve been wanting to start with AI but feel drowned in the noise, too many tools, too many opinions, no clear starting point, we’ve built free AI Starter Kits for exactly that. Short, practical micro courses delivered by email. Pick a tool, open it up, and start building from the first lesson.
So, let’s dive in!
IF YOU ONLY HAVE 2 MINUTES
Image Credits: ChatGPT / Work in Beta
THE ‘HOW TO’ PLAYBOOK
Are You AI-Native? Most People Aren't.
Image Credits: ChatGPT / Work in Beta
Think about how you use AI on a normal day. You’re working. You hit a wall. You open AI in another tab, ask your question, copy the answer, close the tab, and get back to work. AI is a place you visit when you’re stuck. A quick detour. Then you’re back to doing the real work on your own.
Some people don’t work that way. They don’t visit AI when they’re stuck. They work with it the whole time. Before they even start a task, they’re already asking: which part of this should AI do? Which part is mine? What does it need from me to be useful here? For them, AI isn’t a detour from the work. It’s part of how the work gets done.
That second group has a name. People call them AI-native. Most people think it comes down to which tools you own, or how clever the answers look. It doesn’t. Better answers are a nice side effect. The real difference is in how you work.
It’s also a choice. Nobody hands it to you. PwC surveyed workers around the world and found only 14 out of every 100 use AI every day. The ones who do say they get more done, feel safer in their jobs, and earn more. The gap isn’t who has access. Almost everyone does now. The gap is who decided to change how they work. Slowly, that is becoming the line between people who keep growing and people who stay stuck.
AI-native isn’t something you use. It’s how you work.
The easiest way to picture it: think of AI as a brand-new helper on their first day. Fast. Eager. Willing to do almost anything you ask. But it knows nothing about you, your job, or what a good result looks like. Whether that helper is useful depends entirely on how you work with them.
AI-native people are simply very good at working with this helper. That skill breaks into five small habits. We call it the AI-Native Stack. Let’s walk through all five using one boring, everyday job: the weekly report you have to send every Monday.
Habit 1: You set the helper up first
A new helper can’t help if they know nothing. So before you ask, you tell them what they need. For the weekly report, that means: what the report is for, who reads it, what happened last week, what counts as good, and what to leave out. You don’t type “write my weekly report” and hope. You hand over the background first.
Then you save that background somewhere (a folder, a saved chat, a file) so you’re not explaining it from scratch every Monday. We showed how to build this in Your Personal AI Operating System.
Quick check: if a coworker borrowed your AI setup, would they get the same quality? If yes, you built real context. If it only works because you keep re-explaining, you’re still winging it.
Habit 2: You hand over a slice, not the whole job
You don’t drop your entire job on a new helper on day one. You give them a piece. For the report, let AI gather the numbers, compare them to last week, write a rough first draft, and point out anything odd. You keep the parts that need you: what actually matters, what to flag to your boss, and what to say to people.
Quick check: before you ask AI to do something, ask yourself. Am I handing over the whole job, or one slice? AI-native people hand over slices.
Habit 3: You check the work
A new helper makes mistakes, and they say wrong things in a very confident voice. So you check their work before it goes out, on two things. Is it true? Do the numbers, names, and dates match the real source? Is it good? Does it say the right thing for the people reading it, or is it just smooth and empty? You’re not the one writing anymore. You’re the one checking. You’re the editor now.
Quick check: if one wrong number would embarrass you, it needs checking. And if you can’t say why one draft is better than another, you don’t yet know what good looks like. We drew this line between what to trust and what to check in Are You Using AI on the Wrong Work?.
Habit 4: You save the way that worked
The first time they get a great result, most people close the tab and forget how they did it. Next week, they start over. An AI-native person does the opposite. When something works, they save it: the instructions, the background, the checklist, the shape of a good report. Now next Monday isn’t a blank page. It’s a setup you reuse.
This is where the time really adds up. A marketer at Asana, Sheila Head, used AI to review projects after a big team offsite. That review used to take her 3 to 4 hours. Once she turned it into a saved setup, it took about 45 minutes. Same job. She just stopped rebuilding it from scratch every time. We went deep on this in You Think You’re Good at AI. Are You?.
Quick check: saving time once is luck. The same setup saving you time every single week is a system.
Habit 5: You teach the helper a little more each time
When the helper gets something wrong, you have two choices. You can sigh and say “AI is useless at this.” Or you can ask why. What did it not know? Did I forget to tell it who the report was for? Then you add that missing piece to your setup, so it won’t make the same mistake next week.
Quick check: if you’re fixing the same mistake for the fifth week in a row, you’re not really working with AI. You’re renting the same bad result over and over.
How You Actually Become One
You don’t become AI-native by learning every tool or sitting through a big course. You become one, by picking one job you already do every week and working through those five habits on just that one job.
Start small. Not your whole job. One task: the weekly report, the meeting prep, the emails you always put off, the same message you rewrite every month. AI-native starts where a repeated task meets your judgment.
And don’t wait for your company to sort this out for you. Most haven’t. Degreed asked 2,700 leaders about it and found only 13 out of 100 organizations give people all the support they need. So don’t wait for permission. Start this week, then do it again next week, a little better.
Mistakes We See People Make
The “I’m not techy enough” trap. People think AI-native means young, or technical, or obsessed with gadgets. It doesn’t. It’s just how you run the work you already do. Your age and job title have nothing to do with it.
The tool collector. Some people sign up for every new AI app and feel productive doing it. But collecting tools isn’t the same as building the habits. Tools keep changing. The five habits stay the same.
Handing over the decision. AI can line up the options and lay out the facts. It cannot own what happens after you choose. Hand over the busywork. Never hand over the judgment.
The renter. Fixing the same thing by hand, week after week, instead of saving the fix once. If you keep paying for the same result, you never actually own it.
Do This Week
Pick one task you do every single week. Just one.
Run it through the five habits: tell the AI what it needs to know, hand it one slice, check what comes back for true and for good, save the setup that worked, and note one thing to fix next time.
That one task, done that way, is you becoming AI-native. Not the tools. The habit.
Final Thought
The people who get the most out of AI aren’t the ones with the most apps or the cleverest prompts. They’re the ones who quietly changed how they work. That choice is open to anyone, at any age, starting with a single task. Pick yours this week.
- PD & Sonali