Two different reasons an answer is too long
The first is padding: preamble, restatement of your question, a closing summary of what was just said, three sentences of hedging. This is pure waste and you can switch most of it off with one line.
No preamble. Do not restate the question. No closing summary.
That single line removes perhaps a fifth of the length of a typical response, and it costs nothing, because none of what it removes was information.
The second reason is content. The answer is long because the subject has six parts. Cutting here is a trade, and pretending otherwise is how people end up with confident two-sentence summaries of things that needed six.
Knowing which of the two you are dealing with is the whole lesson.
How to specify length
Say the number, and say the unit that matters. “Under 150 words” is enforceable and roughly honoured. “Three bullet points” is more precisely honoured than a word count, because counting to three is easy and counting to 150 is not. “Two paragraphs” works. “Concise” does not; it is an adjective and it means whatever the model’s training suggests.
Expect word counts to be approximate. A model does not count words as it writes; it produces text that is about the right length, because length correlates with things it can sense. Ask for exactly 50 words and you will usually get 44 to 58. If the number matters (a character limit on an SMS, a field in a form) check it yourself, or ask for the count in the output and then check that.
Give a range rather than a maximum when quality matters. “Between 120 and 180 words” produces better writing than “under 180”, because a bare maximum is a pressure in one direction and things get dropped to satisfy it.
The cost of a tight limit on a hard question
This is the part that catches careful people.
For anything requiring several dependent steps, the text is where the work happens. A model asked to compare four insurance policies in exactly forty words has almost no room in which to do the comparing, so what you get is the shape of a conclusion with very little behind it. The number will look confident. It has to be, since there is no space for a caveat.
If accuracy matters more than brevity, split it:
First, work through the comparison in as much detail as you need. Then, at the end, give me the two-sentence version under the heading SHORT.
You read the short version. The long version exists, so the short one is a summary of some reasoning rather than a guess wearing a summary’s clothes. And if the short version surprises you, the working is right there.
This is the single most useful move in this module, and it generalises: reasoning first, tidy output last.
When brevity is the actual requirement
Sometimes short is not a preference, it is the spec. A push notification. A subject line. A message that has to be read on a phone in a queue.
In that case, say the destination, not just the number:
This is a WhatsApp message that will be read on a phone. Under 300 characters. One idea. No greeting, no sign-off: they know who I am.
The destination implies constraints you would otherwise have to write out one at a time, and it stops the answer arriving in a form that technically meets your word count and is still unusable.
The direction people get wrong
Most people over-ask for short. They are reacting to the padding problem and applying the fix to the content problem.
The better default: ban the padding permanently, put it in your standing brief, and then set length by what the answer actually needs. You will find that with the preamble and the closing summary gone, most answers are already about the right length and you have one less thing to specify.
A worked line you can steal
For everyday work:
No preamble, no closing summary, no restatement of my question. Answer in as much space as the content needs, and if that is more than 200 words, give me a two-line version at the top under BOTTOM LINE.
You get the short version for reading and the long version for checking, with the padding gone from both.
Every lesson here is open. Your progress is recorded once you pass the AI, Actually Explained exam.
Check your understanding
An analyst asks for a 40-word verdict comparing four suppliers on price, lead time and reliability. The verdict reads well but turns out to be wrong about lead times. What is the most likely mechanism?
Pick the one you would defend. Your answer stays private.
Stuck on something?Ask Asha, your AI tutor