# What gets better > **What you will learn** > The answer to "fine, it's good, but what do I use it for." Five real tasks, > with the actual input and the actual output. ## The big picture first The work AI is good at has something in common. > **Making 1 out of 0**, and **making many into few**. People spend most of their time on **writing the first line in front of a blank screen** and **reading something long all the way through**. Those two are exactly where AI is strongest. Conversely, **polishing a 1 into a 10** and **judging whether something is right** are still better done by people. So the good pattern is **AI drafts, a person judges.** Now the five, one at a time. --- ## 1. Long into short — cutting reading time ### The situation A supplier sent back a revised 12-page contract. You need to know what changed and you have no time to read it. ### What you write ``` Below is a contract a supplier sent us. Tell me about any clauses that could work against us. Look especially at payment, termination, and liability. (paste the contract) ``` ### What comes back ``` Three places worth checking. 1. Payment (Article 7) Reads "within 60 days of acceptance." That's longer than the usual 30. 2. Termination (Article 12) They can terminate on 30 days' notice, but there's no corresponding termination right on our side. 3. Liability (Article 15) No cap on damages. This is normally limited to the contract value. ``` ### What changed Instead of reading twelve pages you learn **where to look** and check only those parts. The judgement is still yours — whether what AI flagged is actually a problem is for you to decide. > It did not cut your time. It **decided where your time should go.** --- ## 2. Writing the first line — killing the blank screen ### The situation A delivery slipped by a week. You need to write an apology to the customer and the first sentence will not come. ### What you write ``` Draft an apology email to a customer. Situation: a parts supply problem delayed delivery by 7 days. The new date is March 15th. As compensation we'll offer 5% off the next order. Polite but not too long — about five sentences. ``` ### What comes back ``` Subject: Delivery schedule update and our apologies Dear [Name], I'm writing to sincerely apologise that a parts supply delay has pushed our delivery back by seven days. The revised date is March 15th, and we are doing everything we can to complete it sooner. To make up for the inconvenience, we would like to apply a 5% discount to your next order. We are strengthening our supply chain management so this does not recur. Thank you for your understanding. ``` ### What changed This draft does not go out as-is. You adjust it to your company's voice, put in the right name, add anything missing. **But you did not start from a blank screen.** Editing is far faster than writing. --- ## 3. Scattered into ordered — making a table ### The situation You took notes in a meeting but they are all over the place. You have to tidy them up and share them. ### What you write ``` Turn the meeting notes below into a table. Columns: Topic / Discussion / Decision / Owner. (paste the notes) ``` ### What comes back ``` | Topic | Discussion | Decision | Owner | |----------------|----------------------------------|---------------------|-------| | Shipping fees | Free over $30? | Revisit next week | Sales | | Product launch | April is tight, May is better | Moved to May | PM | | Support | Many complaints about slow reply | Add one headcount | Ops | ``` ### What changed Same information, now in **a form you can read.** This job is not hard, but it takes time. Simple work that takes time is exactly the work worth handing off. --- ## 4. Another language — situational, not dictionary ### The situation You need to email an overseas supplier in English. Machine translation comes out subtly wrong. ### What you write ``` Write the following as a business email in English. It's a first contact with this supplier, so keep it formal. Content: we'd like to receive a product catalogue, especially the industrial line. We also want to know minimum order quantity and lead times. ``` ### What comes back ``` Subject: Product Catalogue Request — Industrial Line Dear Sir or Madam, I am writing on behalf of (company) to request your product catalogue, with particular interest in your industrial line. Could you also advise on the minimum order quantity and typical lead times for these products? We look forward to hearing from you. Kind regards, (name / title / company) ``` Feed the original straight into a translator and "we'd like to receive a catalogue" comes out as `We want to receive a catalogue`. The meaning is right, but it is not how a first approach to a supplier reads. The version above is rewritten into the shapes English business email actually uses — `I am writing to request…`, `Could you also advise…`. ### What changed A translator **moves sentences across**; AI **writes for the situation.** It honours conditions like "formal" and "first contact." Rather than transposing your original sentence by sentence, it rewrites it the way it would be written natively. --- ## 5. When you are stuck — generating a list ### The situation You have been told to "think about how we get more new customers." You have no idea where to start. ### What you write ``` I run a neighbourhood butcher shop and want more new customers. Suggest about 10 things I could do without spending much money. For each, give me a rough cost and how long it takes to set up. ``` ### What comes back Ten of them. The first three look like this. ``` 1. Cut-by-cut cooking cards Plenty of customers hesitate at a cut because they don't know how to cook it. Cost £30–60 (printing) / 1 week to set up 2. Weekend pre-orders for regulars Locking in Saturday volume cuts waste and saves customers the queue. Cost nothing (phone/text) / 3 days 3. Cross-referral with the nearby deli Same customers, no overlap in what you each sell. Cost nothing / 2 weeks (needs a conversation) ``` ### What changed Eight of the ten may be things you already knew or that do not fit your situation. **But if two are usable, that is a win.** This is for generating a starting point for thinking. Choosing from ten is easier than squeezing ideas out of a blank page alone. ## What the five have in common ```mermaid graph TD A["Where people spend time"] --> B["Reading something long"] A --> C["Writing the first line"] A --> D["Changing the shape of things"] B --> E["AI makes a draft"] C --> E D --> E E --> F["A person judges and polishes"] ``` Every one is **AI drafts, a person judges.** AI is not producing the final deliverable. > **The most common mistake** > Using what AI gave you as-is. A draft is a draft. Why, in > [things to watch out for](/guide/ai-cautions). ## Common questions ### "My job isn't like any of these." Those five are only examples. The test is this: > **If words move through it, it is a candidate.** Count how much of your day is reading, writing, organising, or explaining documents. In most desk jobs it is more than half. ### "I tried it and the results were mediocre." Usually because **the question was too short.** Look at the examples again — every one **describes the situation and attaches conditions.** The technique is in [getting the answer you wanted](/guide/ai-how-to-ask). --- ## Check yourself **1. What do the tasks AI is good at have in common?**
Answer **Making 1 out of 0** (first lines, generating lists) and **making many into few** (summarising, organising). Judging correctness and putting on the final polish are still better done by people.
**2. In the contract example, what was actually reduced?**
Answer Not reading time — **the time spent finding what to read.** The judgement is still yours; whether the three clauses it flagged are really problems is something you have to check.
**3. How do you tell whether your work is a candidate for AI?**
Answer Ask **whether words move through it.** If you read, write, organise, or explain, it is a candidate.
--- Now it is your turn. The next chapter is a first conversation you can simply follow along with → [Your first try](/guide/ai-first-try)