Years ago I used to be an English teacher. If I had one piece of advice for nonfiction writers who are aiming to inform or persuade, it would be:
write your blog post like it’s a picture book
Picture books are short. They use easy-to-understand words. They have extremely simple structures with a beginning, middle and end. And, crucially, they include pictures.
Why should you picture-book-ify your posts? I have three reasons for you:
It’s respectful to your readers
It’s harder to screw up
All else being equal, it’s more persuasive
1. respect your readers with small words
EA Forum readers are busy people: CEOs, university students, parents, people working on international development in the field, professors, researchers (and sometimes even many of these things!).
You don’t want to waste their time by making them unsure what you mean or whether your post would be useful for them.
Writing simply means they can more easily understand what you’re trying to say and how useful it would be for their work and life.
2. avoid screw-ups with small words
Small words are easier to read when you’re tired, definitely. They also (usually) make you less likely to miscommunicate or be misunderstood.
I’m not talking about specific technical terms that might be essential to your work. I’m talking about the words around those. You probably do need to use words like external validity or corrigibility, but you could probably swap as these efforts proceed for as we keep working.
3. persuade people with small words
I heard once that people are more likely to be persuaded by suggestions written in plain English. I don’t remember the mechanism, but it seems intuitive to me - suggestions written in plain English are easier to understand, quicker to digest, and will make your reader feel smarter than suggestions written in complex language.
I’m glad my small words have been so persuasive. So how do you picture-book-ify your post?
make it shorter (try to stick below 1000 words, break into multiple posts if necessary, keep paragraphs short as well if people will be reading on mobile)
use easy-to-understand words
simplify (and signpost) your structure
add pictures (or graphs, or maps, or tables, or…)
For the first two points, use the Hemingway Editor to simplify your writing. I use it constantly.
And for a good example of what I’m talking about, check out the 80,000 Hours classic 2017 guide.
They break up the text with illustrations that reinforce their main points. They have a clear, logical structure that you can see on the left-hand side of the page. The Hemingway Editor says it’s written at a Grade 7 reading level (appropriate for a 12 year old reader). It’s not short at just over 4000 words, but the paragraphs are short and it’s easy to find your place again if you need to take a break. This is exactly what I’d like to see more of on the Forum!
See a great Forum post like this? Please let me know in the comments.
If you enjoyed this post, you might enjoy these other EA Lifestyles posts:
I think the strongest argument for using small words, simpler sentence structures, etc, is that many EAs aren't native English speakers. Using simpler language makes the posts more accessible to them. That said, Google Translate and other forms of machine translation are becoming increasingly good, so I wouldn't be surprised if that particular problem fixes itself in 1-3 years.
That said, I think your third point is plausible, but the first two are less so.
When I conducted a Twitter poll of what my follower's reading SAT (an American college entrance test) scores are, of the people who took the SAT, ~1/3 of followers claimed to have the highest possible score, and ~1/2 of followers claimed to have a score in the 99th percentile. Now, it is very possible that those people were lying. But if you lie about how good you are at reading, dumbing down my word choices probably wouldn't make you feel more respected.
Sounds good, especially when you want to write blog posts for worldbuilders who don't have a lot of specialised knowledge.
Here is an example I wrote about city agriculture after an energy decline. Maybe I could use this strategy to write worldbuilding blog posts?
Food and water
People couldn't trade food over long distances. So they ate food grown nearby. Everyone grew crops and took care of them. They grew food forests in parks and boulevards. These forests had fruit and nut trees, shrubs, veggies, herbs.
People prunned weeds. They kept calendars for sawing and harvesting. They catched rain in containers. They weaned the grains and stored them indoors. They made manure. They kept chickens and other birds inside. They grew copiced trees in their parks and boulevards. And they cut their branches.
People used stationary bicycles to power electric stoves. Others used solar stoves. Yet others used camping stoves. They cooked fresh or nonperishable food. Meat was rare.
People socialized while cooking. They also cooked in community kitchens. These kitchens were in appartment buildings or restaurants. Kids played, friends talked, neighbors banqueted.
People moved water from rivers through channels. Or they took it by hand. They purified the water at home. They flushed waste down the toilet. Or they made manure. They sold manure to villagers. People used toilet waste in fish ponds. Algae multiplied and fish ate the algae. People then fished them.
By the way, this was grade 5 level text, so no wonder it's that simple.
People also say "expain this to a 11 year-old and you'll understand this". It seems like this Hemingway app is useful for the Feynman technique.
Some good advice here, but I don't think it applies universally. I like forum posts that use (correct) technical language when it conveys important information, and I think some of the best forum posts are dense and carefully-argued. I think some amount of jargon is okay too, though probably worth trying to avoid.
Very much agree that technical terms and jargon should be used when there's a reason!