How to explain technical things verbally

1. Communication is a reception problem, not a broadcast problem

When you’re explaining something, take responsibility for their understanding. Are you sure they understood it? Ask them to say it back in their own words. If they didn’t, how do you improve your explanation?

2. Start with context

Why should your listeners care? If you’re not sure if everybody is on the same page, ask! “Does everybody here know why understanding HTTP is important?”

3. Work one level of abstraction at a time

Define explicitly what you are abstracting away as a black box. Then, explain the interactions between components at that level of abstraction.

The key is to explain one level of abstraction at a time, instead of oscillating between levels mid-sentence. This works because scoping what you know and what you don’t know prevents the listener from being overwhelmed.

4. Get it right the first time

The failure mode to avoid is blurbing the first thing that comes to mind, then going “so to put that more clearly…”.

It is cheaper to spend 1 minute running the explanation in your head/with a piece of paper, then saying it once, rather than transmitting an incorrect mental model and correcting yourself. Every mistake causes cognitive dissonance and takes up working memory of the recipient, leaving less to interact with the ideas usefully.

5. Scaffold with pen-and-paper

As I progress through an explanation, I find it useful to write some things down:

Writing down a scaffold frees up your working memory to discuss each component independently. It also gives the listener an accurate summary of the discussion for posterity.

6. Anticipate confusion and use emphasis

For example, imagine a security engineer explaining a data leak to non-technical colleague:

“The login was fine, authentication worked as intended. But the attacker logged in, incremented the order id, and read other people’s orders, so there was a problem with the authorization code.”

The explanation is technically correct, but potentially confusing. The colleague’s working memory now contains:

  1. Security guy says the security code works.
  2. But the attacker came in and read other people’s data anyways.
  3. Security guy then says the security code doesn’t work???

This is cognitive dissonance, which needlessly consumes the listener’s mental energy.

A better way to start would be:

“Authentication worked as intended, but authorization was broken.”

Using emphasis, you preempt confusion between the two related-but-distinct concepts. The listener can then ask you about the difference.

Even better yet, motivate the difference first:

“What happened was our app checked the attacker had the right password when they logged in. However, the code to read order IDs didn’t check if your account number matched the order ID’s account number”

and introduce the terminology afterwards:

“In security lingo, authentication worked but authorization was broken.”