Explaining explaining: a quick guide on explanatory writing
lucasfcosta.com
lucasfcosta.com
One concrete takeaway for me is: I often lead with the history of a problem in order to give it some gravitas, but maybe I'll try the advice of swapping the order up, and starting with the concrete thing of what it is we're going to accomplish.
I read a lot of blogs that make that mistake of starting off a post by droning on for paragraphs about the background, history, or context they want to set for the blog — but I need to know why I'm here in the first place. The title got my attention, but it still doesn't totally tell me what I'll get out of this.
A 'history of a problem' section also has to try and be concise and use really engaging language (it's hard) otherwise those background intros can feel like a chore to read and people will leave.
I like to inject humor and write in the vernacular[0]. Doesn't always win me friends, but folks seem to like it, for the most part.
I'm not big on "hard and fast rules." I find things like passive voice can actually be the best thing, in places.
There is, unfortunately, no single best explanation for all audiences.
It all depends on the expertise, experience, level of English/other language of the audience.
For example, when teaching programming to students who have a solid background in math, it is quite easy to teach functions and recursion in an abstract manner. Students familiar with the Cartesian plane will find it nice to get started programming by doing graphics programming.
Also, the three-step structure he advocates is a bad idea, as described here (IIRC): https://www.youtube.com/watch?v=vtIzMaLkCaM
Of course, you might be the great exception, a perfectly reasoning actor, which we hear so much about in thought experiments.
Also no, explaining things well is very difficult. Otherwise there wouldn't be so much bad explanatory writing out there. If you think it's easy, then you are either naturally skilled at it, or you are actually bad at it and don't realize.
But you don't need to follow any advice if you do not seek to get ahead (i.e., better) in some sense. So, that doesn't make sense as a counterargument. OP's point is that you can become better at explaining, but that on its own does not add value. This is quite evident in scientific writing. Plenty of well-written papers are rejected if they do not provide sufficient value.
It doesn’t just randomly happen to be convincing. The convincing part is why it works at all.
Can you give an example of writing that does this? Is it more about making declarations (with sources I hope) to nudge the reader to your beliefs? I'm not sure how you convince intelligent people without some explanations.
Examples of explanations without convincing can be found in most academic writing.
ALthough, I think that the first link is a better version of the two.
At the end of the day, humans are emotional beings first and thinking beings second. Explanatory writing speaks to the latter. Meanwhile stories connect with our basest programming, thanks to the ability to evoke emotion (when written well, of course).
If writing to persuade: yes, the writing needs to be clear and succinctly relay information. But most importantly, it needs to speak to our deepest emotions and desires. When an audience is made to feel differently, they think differently too.
I'm OK with that up to a point because those who can have advantages over those who can't. I'm an engineer who writes well (mother was a PhD in English - could not escape it).
For example, think this is kind of missing the point:
> Simply tell people you’re going to teach them how to wash their clothes.
That recommendation will be valid for some audiences some of the time.
Some people want to read about the history of fabric softeners. Some people won't understand why washing clothes is important and need to have the "why" before their ape brains can focus on the "how". Some people are just there because they have to be there and are going to be hard to reach, and you might have to get creative in order to make the material seem relevant to them. Explaining things is not a one-size-fits-all process.
People seem to need some kind of personal connection to the content, and some motivation to care about it, before they can understand it. That's the point of getting readers "hooked", as the author says. But the mechanisms for "hooking" will necessarily vary depending on who the reader is.
People also need to make relatively small logical connections. The process of learning and understanding is generally incremental. Once in a while, when learning something, the learner has a flash of great understanding, but those moments are rare relative to learning one small fact at a time. And usually those great moments of understanding only happen when the learner first accumulates many many small bits of understanding first.
A learner who is personally connected to the material they are learning will have an easier time transitioning into learning it, because the subject is smaller smaller leap away from what they already know/understand.
Therefore the author I think has the right idea and clearly has a reliable formula, but they don't understand why their own formula works!
The author has found that telling stories is a great way to get people interested in the material. That's not because stories are a magic explanation bullet. It's because, for the audience that they generally write for, stories are a great way to provide context and a basis of intuition for the material. Having context and the basis of intuition brings the audiences closer to understanding the material, which eases the transition into the more technical or complicated parts of the explanation.
So yes, most people respond well to stories. But figuring out what story to tell it can be challenging.
To explain something truly well, you need to know the motivations and and pre-existing knowledge of your audience. You need to bring your material to where the audience is at, or at least make a connection from your material to there.
I think there are a lot of other small aspects here as well, having to do with the way individual small pieces of information or structured, how to build ideas, when to challenge the learner and when to assist them, etc. but I've already written way too much in this post.
If you can't get into the heads of those you are communicating with, you will mostly fail in your writing objectives. And this isn't simply what they are thinking now; it's meta-thinking and meta-meta-thinking as well as the environment (with resources available, rules and limitations, etc.) in which they information will be used.
* Use a structure of "what I'll explain, explanation, what I explained" (aka intro, body, conclusion)
* use concrete examples instead of starting off abstract
* write well
Pretty underwhelming list tbh. There are many more small tips I'd personally include. But, what this does have is still agreeable.
But don't take my word for it. There are language and writing experts who are more articulate and detailed than I who can tell you:
Here is a Boston Globe language columnist on why it's so awful: https://people.brandeis.edu/~smalamud/2006ling100/frankenstr...
UPenn professor: https://languagelog.ldc.upenn.edu/nll/?p=26621
More ink spilled than 100s of _Elements of Style_ about what's wrong with it: https://duckduckgo.com/?q=what%27s+wrong+with+elements+of+st...