Guides · 15 Aug 2026

Write the task the way you would for a new starter

The people who get the most out of a coworker are not the ones who write the cleverest instructions. They are the ones who stop trying to.

There is a habit people bring from chatbots, and it costs them the first week. They write a paragraph of scaffolding — you are an expert finance assistant, think step by step, be concise — and then, somewhere at the end, the actual job.

Delete the scaffolding. Write the job.

#What a good first task looks like

Here is one that works, in full:

Chase whoever is late paying us. Leave Northwind alone, they always pay late. Anything over £5,000, check with me before you send it.

Twenty-eight words. No role-play, no formatting instructions, no thinking directives. It contains the three things that actually matter, and nothing else.

The job

Chase late payers. Not "analyse receivables" — the thing a person would do on a Tuesday.

The exception

Leave Northwind alone. Every real job has one. Naming it up front is the difference between work you can use and work you have to check.

The limit

Over five thousand, ask. This is the sentence that lets you stop watching.

The three parts of that task. Everything a chatbot prompt usually opens with is missing, on purpose.

#Why the scaffolding hurts

Two reasons, and the second is the one people miss.

The first is obvious: instructions about how to think compete with information about what to do. You have spent your attention budget on style.

The second is that scaffolding is not reusable. A paragraph tuned to one question is a paragraph you rewrite for the next one. A plain job description is a standing instruction — you can say do this every Monday and it means something, because it was never about one moment.

#Correct it once, out loud

The first result will be wrong in some small way. This is the most important thing that happens all week, and most people handle it badly by rewriting the original instruction.

Do not rewrite. Correct, in a sentence, where you are:

Not that Halcyon invoice, that one is disputed. Never chase a disputed invoice.

Rewriting the prompt gets you the same outcome once. Correcting gets you the outcome forever, and everyone else on the team inherits it.

That sentence is now a rule. It is attached to what it corrects, it carries your name, and it shows up next time as "I skipped the disputed one".

#Three tasks worth starting with

Pick something with a clear finish line and a low blast radius. Good first jobs share a shape: repetitive, boring, and obvious when done wrong.

  1. The inbox nobody owns. Read it, answer what is answerable, hand you the rest with a one-line summary each.
  2. The weekly thing you always do late. The report, the reconciliation, the follow-ups. Ask for it every Monday at eight.
  3. The chase. Invoices, missing documents, unanswered requests. It is the job that most rewards never getting bored.

Bad first jobs: anything where the standard lives in one person's head, and anything where a mistake is expensive and invisible. Get to those in week three, after corrections have taught it your standard, and with a limit set.

#What changes by the second week

Almost nobody keeps writing tasks. They start writing responsibilities.

Week one

Chase the late payers this week

A task. It has a beginning and an end, and when it ends you write another one. This is a tool you operate.

Week two

Do this every Monday from now on

A responsibility. It survives you being busy, and it carries every correction anybody made to it. This is a job that has left your desk.

The same person, two weeks apart. The difference between these two sentences is the whole product.

Questions people ask after this

How should I write a task for an AI coworker?

Write the job, not the instructions for how to think about the job. A good task names three things — the job, the exception, and the limit above which it should ask you — and nothing else.

Do I need to tell it to be an expert, or to think step by step?

No. That scaffolding competes with the information about what to do, and it is not reusable — a paragraph tuned to one question is a paragraph you rewrite for the next one.

What do I do when the first result is wrong?

Correct it in a sentence, where you are, rather than rewriting the original instruction. The correction becomes a rule that carries your name and applies next time, and everyone else on the team inherits it.

What is a good first job to give a coworker?

Something repetitive, boring, and obvious when done wrong. The inbox nobody owns, the weekly thing you always do late, or the chase — invoices, missing documents, unanswered requests.

Oliviero Pinotti

Founder

ShareXLinkedIn

Put one on a real job this afternoon

Connect one tool and give it one task. You will know inside ten minutes.