What Farm Radio Updates Teach About Plain Language
My grandfather listened to the same farm radio broadcast every morning for forty years, a fifteen minute segment that covered weather, grain prices, and livestock advisories in language plain enough that a tired man drinking coffee before...

My grandfather listened to the same farm radio broadcast every morning for forty years, a fifteen minute segment that covered weather, grain prices, and livestock advisories in language plain enough that a tired man drinking coffee before dawn could absorb all of it without rewinding anything, on a format with no rewind button at all. I did not think about that broadcast as a communication model until much later, when I started training corporate writers on plain language and realized farm radio had solved the problem decades before any style guide I was handed at work.
Farm broadcasting had no choice but to be plain. Its audience was listening while working, distracted, often outdoors, with genuinely important decisions riding on getting the number right the first time, whether to sell grain today or wait, whether to move livestock ahead of weather. There was no format for a confusing sentence to hide in, because a confused farmer could not ask the radio to repeat itself.
What made those broadcasts work
The structure of a good farm radio segment is almost mechanically simple: the most actionable number first, the reasoning second, and any caveat last, always in that order, never rearranged for style. A grain price segment would state the price immediately, not after a preamble about market conditions, because a farmer deciding whether to sell needed the number before anything else, and everything after it was supporting detail he could take or leave depending on how much time he had that morning.
That ordering discipline is rarer in professional writing than it should be, particularly in reports and memos where the habit is to build up to a conclusion through several paragraphs of context, as though the reader needs to be walked through the reasoning before being trusted with the answer. Farm radio never had that luxury, because the audience's attention could not be assumed to survive a slow build.
Why plain language got confused with simple content
A common misreading of plain language advice is that it means dumbing down complicated material. Farm radio is useful evidence against that assumption, because the actual content, futures pricing, weather system behavior, livestock health advisories, was genuinely complex, and none of it got simplified in substance. What changed was the sentence structure carrying it, not the sophistication of the information itself. A skilled broadcaster could deliver a nuanced market read in language a distracted listener could follow, without cutting a single meaningful detail.
I push back hard, in my own training sessions, on the idea that plain language means less information. It means the same information ordered so the reader's effort goes toward understanding the content, not toward decoding the sentence carrying it. Complexity in the subject matter is fine. Complexity added by the writing itself, on top of an already complex subject, is the actual problem plain language solves.
A distracted, busy reader is not asking for less to be said. They are asking for nothing extra to stand between them and the part that changes what they do next.
Applying the same discipline to a written report
Most written business communication has more room than fifteen minutes of live radio, and that extra room is exactly what tempts writers into the slow build farm radio never allowed. The fix is not to write shorter documents by default, it is to structure them with the same ordering discipline: the actionable conclusion first, in plain terms, followed by the reasoning for readers who want it, rather than the reverse. A reader who only reads the first paragraph should still walk away with the correct decision, the same way a farmer catching only the opening line of a broadcast still got the number that mattered.
| Farm radio habit | Written equivalent |
|---|---|
| Price or advisory stated in the first sentence | Conclusion or recommendation stated before the analysis |
| Reasoning follows, kept short and concrete | Supporting detail placed after the headline finding, not before it |
| Caveats stated plainly, not buried in qualifiers | Risks or exceptions named directly, in their own sentence |
The parallel goes further than tone. Farm broadcasting also had to serve an audience managing genuinely unpredictable conditions, and outfits covering that world in more depth, including sites like Farm Zone, still carry some of that same discipline in how they lay out planning and equipment guidance, leading with the practical decision a reader is trying to make rather than the theory behind it.
If you write reports, memos, or updates for a busy reader, try applying the farm radio ordering test to your next draft: read only the first sentence and check whether it alone gives the reader the actionable conclusion, before any of the reasoning that built up to it. The same discipline of leading with what matters most shows up from a different angle in what gaming voice chat teaches about brevity, and both belong to communication skills, where plain is never the same thing as simple.
More in Communication Skills
Communication Skills
Reading the Room When the Odds Change Mid Game
I once watched a room go quiet three full seconds before a presenter had said anything to explain why.
Communication Skills
What Gaming Voice Chat Teaches About Brevity
I managed a distributed engineering team for six years, and the best callout I ever heard on a work call was not on a work call...
Communication Skills
Giving Feedback That People Actually Use
A press secretary I once managed received the same note from me for three straight months: be more concise in briefings.