Imagine you hired someone, sat them at a desk, and every now and then wandered over and asked them a question.
They'd answer it. Then they'd sit there until you came back.
That's how most people use AI. And it's why it feels like a handy tool instead of a member of the team.
When you ask AI a question, you get an answer. Then you've got to do something with that answer. Copy it, fix it, paste it, chase the next step.
When you give AI a job, it does the work. It knows what's coming in, what you need at the end, and how to get from one to the other.
Here's the difference:
Question: "Can you write a caption for my post about Friday?"
Job: "Every Monday, write my seven posts for the week from this list of topics, in my voice, using my three content pillars, with a hook in the first line, and save them to my scheduling sheet."
The first one saves you five minutes. The second saves you a morning, every week.
Ethan Mollick, the Wharton professor who wrote Co-Intelligence, has a rule for this: treat AI like a person, but tell it what kind of person it is. A job description does exactly that.
Here's what goes in mine:
The role. Who is it? "You're my weekly content assistant." "You're my bookkeeper's offsider."
What it's responsible for. One job. Not everything.
How often. Daily, weekly, every fortnight, when I type "run".
What it gets given. The files, notes, apps or information it starts with.
What it hands back. The exact output, in the exact format. Paste in an example of a good one.
The rules. What always goes wrong. What it should never do. What needs my sign-off.
Who checks it. Usually me. Sometimes someone else.
That's it. Same as you'd write for a person, except you only have to write it once and it never forgets.
Not everything needs to be a job. If it's a one-off, just ask your question.
But if it ticks any of these, it's a job:
You do it every week or every month.
It follows roughly the same steps each time.
You put it off because it's boring.
It's the thing that slides when you get busy.
That last one is the big one. The jobs that keep sliding are usually the back-end ones. Money, marketing, admin. The ones nobody's waiting on, so they never feel urgent.
I've got AI doing a daily brief at 6am, a weekly social media batch, a fortnightly check for someone I work with, and a board of advisers I run decisions past. Each one started as a job description. None of them started as a question.
I wrote about the whole set-up in How I actually use AI to run three businesses and a community.
Each one started as a job description. None of them started as a question.
Pick the job you dread the most.
Write the job description using the seven points above.
Give it to AI and run it on a real week.
Every time something's off, change the job description so it doesn't happen again.
After three or four runs, it'll be doing the job the way you would.
Then pick the next one.
Take my free quiz, Why isn't it getting done? It shows you which part of your back end you keep putting off and the real reason it keeps sliding. That's the first job I'd give to AI.


HI, I'M SAM
I've co-run a field service business for 22 years and served 12 years in the Navy. Now I help solopreneurs get the back-end stuff done, the money, systems, marketing and AI, so they get their weekend back.



NOT SURE WHAT'S SLIPPING?
Created with © systeme.io