How to use AI to turn dense information into something a person can act on
Most documents bury what matters in what doesn't. AI can pull those things apart — if you tell it what matters.
Most documents are not written to be read. They're written to be complete. Financial statements account for everything; reports cover every angle; meeting notes capture everything said. The result is that the thing that actually matters — the number to act on, the decision to make, the sentence that changes everything — sits somewhere in the middle, indistinguishable from the rest.
AI can reverse this. The technique is to feed it the raw material and tell it what the reader needs to walk away with. The output quality depends almost entirely on how clearly you specify who is reading it and what they need to do with it.
The gap between data and communication
A bank statement tells you every transaction. What most people need is a clear picture of where the money went and what to do differently. Those are not the same thing. The first is a record. The second is communication.
The same gap appears in almost every professional context. A legal contract tells you everything the parties agreed to. What you need to know is the three clauses that carry real risk. A research paper describes the full method and every result. What you need is whether the finding holds and what it means for your decision.
The raw version isn't wrong. It's just not written for you. AI can bridge that gap by translating between the comprehensive and the actionable — but only if you explain which direction you're travelling in.
What to give it and what to ask for
The input matters less than the instruction. You can paste in a full document, a transcript, a spreadsheet turned to text. The model can work with dense material. What it can't do without guidance is decide what the reader needs to know.
The useful instruction names the reader and names the action. Not "summarise this" — that produces an abstract. But "tell me what this means for someone who needs to decide whether to sign it" or "what does a person spending $2,000 more than they earn need to hear first?" The more specifically you describe who is reading and what they'll do next, the closer the output gets to something usable.
Format matters too. A decision memo reads differently to a set of priorities. A three-point summary reads differently to a paragraph of analysis. Ask for the format the reader will actually encounter it in.
Plain language is a design decision
There is a style of AI output that is technically accurate and completely unusable. Hedged, passive, measured — it covers all cases and serves none of them. This is what you get when you don't specify. "The report indicates that expenditure exceeded income by approximately $2,000 during the reference period, with primary categories including housing, food, and family-related costs" is correct. "You spent $2,000 more than came in. Most of it went to housing, food, and family" is the same sentence written for a person.
The difference is in what you ask for. Plain language does not emerge automatically from AI; it emerges when you make it a condition. Ask for short sentences. Ask for the most important thing first. Ask it to write as if the reader has ten seconds, not ten minutes.
Specificity is part of this. Percentages and actual numbers are usually more readable than generalities. "64% of your spending went to three categories" is faster to process than "the majority of expenditure was concentrated in a small number of areas."
When the document resists being summarised
Some material genuinely cannot be condensed without losing what matters. A contract with interconnected obligations. A technical specification where every number depends on the others. For these, the task isn't compression — it's navigation. Ask the model to tell you where to look, not what to think.
"What parts of this document carry the most risk?" is a better instruction than "summarise this contract." "What are the three things a non-technical person needs to understand about this spec?" is more useful than "explain this."
The model is also good at identifying what's missing. Paste in a document and ask what questions it doesn't answer. This is particularly useful for anything you're about to sign or act on. The gaps in a document are often more important than its content.
Matching the output to the reader
The same information reads very differently depending on who's receiving it. A financial summary for someone who has never looked at a budget needs different language than one for someone who reads balance sheets every day. An explanation of an AI-generated report for a client needs to be built differently than one for a colleague who built the model.
Before you run anything, think for 30 seconds about who will read the result and what they know. Feed that to the model as context. "Write this for someone who knows nothing about accounting" and "write this for a CFO who wants the variance explained" will produce outputs so different they're almost different documents. Neither is wrong. One is right for your situation.
What usually goes wrong
The most common failure is treating the first output as finished. AI summaries often land at the right level of compression but miss the register — too formal, too clinical, too abstract. The fix isn't to start again. It's to paste the output back and tell it exactly what's wrong.
"This is too hedged — remove the qualifications and just state what's true" is a one-line instruction that often produces a far better version in seconds. "Put the most important number in the first sentence" costs nothing to ask.
The second failure is over-summarising. When a document is compressed too far, the result is technically accurate but useless — a list of topics rather than an account of what they mean. If you find yourself reading an AI summary and still needing to go back to the original, the summary wasn't specific enough. Ask it again with a clearer instruction about what the reader actually needs to know.
The check that matters
Before sending anything produced through this process, read it aloud. Not to check for typos — to check whether it sounds like a person wrote it. If you find yourself stumbling on a phrase, so will the reader. If a sentence is technically correct but feels like a machine wrote it, the reader will feel that too.
The goal is not a document that is shorter. It's a document where the thing that matters is unavoidable.
Drawn from chapter 3.2 of AI Magic 2033.
