You pay for ChatGPT, Claude, Copilot or Gemini. A few people use it to tidy an email or summarize a document. Nobody has said it is a waste, and nobody can point to the part of the week it has taken over. You suspect there is far more in it, and you are right.
The question is usually asked about the tool: what can it do? It is easier to answer from the other side. Look at the work your people already do and ask which of it could arrive prepared. A draft, a comparison, a sorted list, a checklist with the gaps marked: the part that takes an hour before anyone can make a decision.
That work falls into two piles. Some of it repeats, the same way, every week, and can be written down once and run by a whole team. Some of it never repeats, and there the assistant helps a person think, one question at a time. Repeatable work and ad hoc work shows how to sort a week into the two. This piece is about the first pile, because that is where most of the value is and where most teams have not started.
The name for where most companies are is undirected: the tools are on and paid for, and each person is left to work it out. A plan is what directs them. Why plan how your company uses AI? sets out what changes the week after a one-page plan exists, and How organizations plan their use of AI shows how to write one.
Why it has not stuck yet.
Four causes turn up again and again. You will probably recognise more than one.
- Everyone prompts differently.Two people ask for the same thing in their own words and get two different answers. Nobody can say which is right, so nobody trusts either, and the work goes back to being done by hand.
- Nobody wrote down what good looks like.The experienced person knows what a good version contains and what to leave out. That knowledge is in their head. The assistant has only the request, so it guesses.
- The work needs records the assistant never sees.A close needs the ledger. A call needs the account history. A ticket needs the order. If the records stay in the accounting system, the CRM and the help desk, the assistant works from what someone remembers to paste in.
- Nobody is named to check the result.When anyone may review it, no one does. Mistakes reach customers, someone gets burned, and the team goes quiet about using it.
Pick one piece of work.
Do not start with a list of everything the assistant could do. Start with one piece of work and test it against four questions.
- It repeats weekly.Something done every week gives you a fresh case each time to check the instructions against.
- It starts from records someone can export.A spreadsheet, a report or a folder of documents. If the starting point is a conversation nobody wrote down, choose something else first.
- One person already reviews it.If a named person already looks at the result before it goes anywhere, that person becomes the checker for the new way too.
- A mistake would be caught before it leaves the building.Pick work where an error reaches a colleague, not a customer or a regulator, until you trust the instructions.
If a piece of work passes all four, it is a good first one. If it fails one, look for a neighbour that passes.
Four examples.
Each of these names the input, what is prepared and who decides.
- Finance.The input is the trial balance and the bank and card exports at month end. What is prepared is a checklist of what is reconciled, what is missing and which entries need a second look. The controller decides what is posted. The month-end close checklist is a free template for this.
- Sales.The input is the account record, the last few emails and the notes from the previous call. What is prepared is a one-page brief: who is on the call, what was agreed, what is open and what to ask. The account owner decides how to run the call. The sales call preparation brief is a free template for this.
- Support.The input is the week’s tickets from the help desk, with the order details. What is prepared is a sorted queue: category, priority and route, with urgent tickets held for a person. The support lead decides what happens to each. The support ticket triage template is free.
- Operations.The input is whatever the best person on the team does and explains aloud: a handover, a setup, a weekly check. What is prepared is a written procedure in the order the work happens. The person who does the work decides whether it is right. The SOP from how the work is done template is free.
The templates are samples and a starting point. Change them to fit how your team works.
From a loose prompt to shared instructions.
Take a 35-person company that installs and services water filtration systems. Its support team of three answers about 40 emails a week, and the support lead wants the Monday queue sorted before anyone starts. Here is how the work moves from a loose prompt to something all three use.
- The loose prompt.One person types: “Sort these tickets and tell me which are urgent.” She gets a list. A colleague pastes in the same tickets with his own wording and gets a different list. Each calls a different set of tickets urgent.
- Write down what good looks like.The support lead sits with the two of them and writes five lines. The categories the team uses. What makes a ticket urgent: water leaking, no water, or a customer who has written twice. What a first reply must include. What it must never promise, such as a refund or a visit date. What to flag for her instead of drafting.
- Add the records.The instructions say what to use: the help desk export for the week and the order list for each customer. The team exports both on Monday morning and uploads them with the instructions.
- Test on last week.They run the instructions on the previous week’s tickets, whose real answers they already know. Where the sort disagrees with what the team did, they ask who was right. Sometimes the instructions change. Sometimes the team learns it was inconsistent.
- Name the checker.The support lead reads the sorted queue and the draft replies before anything goes out. She changes what she disagrees with, and each correction becomes a line in the instructions.
- Share one copy.The instructions live in one shared document. Everyone uses that version, and only the support lead edits it. Whoever runs it on a Monday starts from the same page, and the team has one place to improve it.
At each step a person decided. The assistant sorted and drafted. The support lead approved, and every reply went out under a person’s name.
What to do this week.
Choose one piece of work that passes the four questions. Ask the person who does it best to write down what good looks like in a page. Name who checks it. Run it once on last week’s records before anyone relies on it.
That is how a team starts to 10X the ROI of its existing AI: one piece of work at a time, with the preparation done before a person decides. 10X the return on the AI you already pay for sets the method out in eight steps, with a sheet to fill in. The Workflows Directory holds free templates for work like the examples above. They are samples and a starting point, and you can open one and adapt it for your team.