AI-assisted tasks run fast when you name the output format first, make the model flag ambiguity, treat the first result as a draft you check against the source, and pick one small workflow to repeat.
You hand the AI a real piece of work, get back something accurate and unusable, and conclude the tool is not for this kind of task. In most cases the model was not the problem. The missing piece was a middle step between "AI can do this" and "AI did this for me today".
This guide sets out that middle step as a short method, drawn from five worked examples: a pile of supplier emails, an eleven-page tangle of meeting transcripts, three documents due in one week, three important messages that needed a last read, and the question of which workflow to build first.
The task was to summarise who owed what by when from nine supplier emails in three formats, with a Friday deadline. The first request, "a summary of these emails", returned a paragraph of prose. It was accurate, and it still meant re-extracting every date and amount by hand.
The second attempt named the output first: a table with supplier, amount and due date as columns, before the emails were described at all. Two emails had conflicting amounts within their threads, so the request also asked the model to flag conflicts rather than resolve them quietly. That flag caught a discrepancy before it reached anyone else.
The first table was still a draft. One date did not match its source email. Spotting it took one read-through of five rows. In the source article's account the whole job took twenty minutes: three prompts, one conflict settled with a phone call, one date corrected and a final read. That is the ordinary work of checking output against a source, the same check you would give a summary from a junior colleague.
State the shape you want (a table, a memo, a set of headings, a two-paragraph summary) before you describe the material. The structure then arrives because it was asked for, not guessed. The output that needed the least editing in the example was the one built from the most specific request.
Tell the model what to do with doubt: flag conflicting figures, mark what is unclear, say what is missing. Left alone, it will resolve a conflict silently and present the result with equal confidence.
Read the output with the original beside it. A short structured output (a five-row table) is quick to verify, which is another reason to ask for structure. A paragraph is slower to check and slower to fix.
The same habit applies when the task is to improve your own writing. Before sending something important, ask three questions of the page:
In the source example, the third question caught a curtness the writer had read as calm. A second pair of eyes, in that article's phrase, can be a different set of questions rather than a second person. It cannot settle how direct to be with a particular client. That judgment stays with someone who knows the person.
For proposals, memos and updates, the example found the same method worked for all three:
Structure gets the three documents started. A proposal still needs a sales instinct about what the client cares about, a memo needs an understanding of who will read it and what they care about, and an update needs honesty about what happened that week.
One further example shows the value of sequence. A client sent eleven pages of transcripts, half-finished requirements and side notes and asked for "something we can actually build from". The pass that worked had three steps in a fixed order:
Skipping the order causes trouble in both directions. Naming sections before you know the topics gives headings that do not match what is underneath. Moving content before grouping gives a document that has to be reshuffled.
If you can build only one repeatable workflow this month, the source article's advice is to pick one that meets three tests:
| Test | What it means |
|---|---|
| Fixes something you already do badly | Better to improve the meeting prep you rush than to start a report you have never written |
| Has a before and after you can feel | A two-hour task becoming a fifteen-minute one earns trust at once |
| Small enough to build in an afternoon | If it needs a project plan first, it is the wrong first workflow |
Only the person doing the work can say honestly which task drains the most energy. Do not choose by what would look impressive on a slide.
A workflow you actually run every week beats a perfect one you built once and never opened again.
How to break a task into steps and write down the handover point, usually just before the first judgement call, where AI output ends and human responsibility begins.
Team AI Training · 4 minAnalysis · 20 September 2026Checking AI output has a real time cost that productivity claims omit, and this piece shows how to price it and when it cancels out the saving.
Team AI Training · 4 minGuide · 20 September 2026Four structural prompt patterns that hold up on messy real documents, including showing the actual template, naming what to ignore, requesting uncertainty flags and chunking long files.
Team AI Training · 3 minIf this is the question on your desk, a thirty-minute call tells you whether the service fits, or that you do not need us yet.