Most advice about AI at work is either "it will replace you" or "it makes things up, ignore it." Both are useless when you have a job to do on Tuesday. You need a sharper question: which parts of my work does this help with, and which parts does it quietly damage?
Here is the most useful distinction I know. It is not about topic. It is about where the truth lives.
Truth in the text vs truth in the world
When the answer is inside the text you provided, the model is strong. Summarise this eight-page circular. Rewrite this complaint letter so it is firm but not rude. Pull every deadline out of this contract. Turn these rough notes into a paragraph. The material is right there. The model is reorganising, compressing, rephrasing. It has everything it needs.
When the answer lives out in the world, the model is guessing from patterns. What is the current stamp duty rate in my state? Did this supplier actually deliver in March? What was the exact wording of the 2019 amendment? What is my patient's potassium level? None of that is in the conversation. The model will still answer, fluently and in full sentences, because producing plausible text is what it does. That fluency is the danger. A wrong answer does not arrive looking wrong.
So the first sorting rule: if you did not give it the facts, do not trust the facts it gives back.
Where it earns its keep
Across very different jobs, the same shapes of task keep paying off:
- The blank page. A first draft of anything. A parent letter, a tender response, a policy note, a product description. Drafts are cheap to fix and expensive to start.
- Compression. Forty pages down to one. A two-hour meeting down to seven decisions.
- Translation between registers. Legalese into plain language for a client. Clinical notes into something a family understands. English into Spanish, Hindi, Yoruba, Tagalog — good, not perfect, and better if you can read the output.
- Structure from mess. Sixty open-ended survey answers sorted into eight themes. A pile of receipts turned into a table.
- The thing you can nearly do. A spreadsheet formula, a regex, a SQL query, a bit of Excel VBA. You cannot write it, but you can test whether it worked.
Where it will hurt you
- Anything where being 95% right is a failure. Dosages. Tax filings. Court deadlines. Structural loads. Not "never use it" — never use it *unchecked*.
- Recent and local specifics. Last month's circular from your ministry. Your state's fee schedule. Your company's leave policy. Unless you paste it in.
- Counting and exact arithmetic across long documents. "How many invoices are over 50,000 naira" is a spreadsheet question, not a chat question.
- Judgment that is yours to make. Should we fire this person. Should this student repeat the year. Is this client lying. It will give you an answer. That answer carries no accountability, and yours does.
Do this today
Write down the five things you did last week that took over thirty minutes and were mostly typing or mostly reading. That list is your real curriculum. Most people find two or three of them are pure text-shuffling, and those are the ones to hand over first.
Before you move on