The Art of the Non-Technical Explanation

You know the look. The moment you start talking about "APIs" or "the cloud" and your mom's eyes glaze over. Your cousin nods along but you can tell he's mentally planning dinner. The family group chat devolves into screenshots of error messages and frantic "what does this mean?" pleas.

It's not their fault. You're speaking a different language.

Here's the truth: being able to explain technology to non-technical people is a harder skill than actually building it. And it's the one that will save your sanity at every family gathering.

First, Kill the Jargon

Every technical term you use is a wall. Not a bridge.

Let's play a game. Which of these sounds clearer?

"I updated the DNS records to point the A record to our new server's IP address."

Or:

"I changed the address book so when people type your website, it sends them to the new computer hosting it."

The second one works because DNS = address book. Server = computer. IP address = house number.

The rule: If you can't explain it using objects from a kitchen or a desk, you're still being technical.

Here's a translation table for the most common jargon:

The Analogy Toolkit

The best explanations don't teach technology — they map it to something your listener already understands.

For how the internet works: It's a postal system. Your computer has an address (IP). Websites have addresses (domain names). Data gets chopped into letters (packets) and mailed between computers. Routers are the postal workers sorting mail. Sometimes a letter takes a different route if a road is closed.

For why passwords matter: It's like the lock on your front door. A strong password is a deadbolt. A weak one is a sticky note. Reusing passwords is having the same key for your house, your car, and your safety deposit box — if someone copies it once, they get everything.

For why updates matter: Imagine your house has a leaky roof. Every time it rains, water gets in. An update is someone coming to patch the hole. Not updating is letting it rain until the ceiling collapses, then being surprised.

For why cloud storage isn't "free": Nothing is free. When you store photos on a free service, you're paying with data about yourself. It's like staying at a hotel for free — but the hotel gets to watch you sleep and sell that information to advertisers.

The 3-Second Rule

Here's a brutal test: Can you explain the core idea in one sentence that takes under three seconds to say?

If you can't, you haven't distilled it enough.

Bad: "We use an asynchronous event-driven microservice architecture with a message queue."

Good: "We break big jobs into smaller chores that run themselves when they're ready."

Bad: "It's a blockchain-based distributed ledger using proof-of-stake consensus."

Good: "It's a shared notebook nobody can erase, so everyone trusts what's written."

Three seconds. No more. This forces you to find the soul of the concept.

The Empathy Pyramid

Most technical explanations fail because the explainer jumps to the wrong level.

Imagine a pyramid with three levels:

1. What it does (top) — the outcome, the benefit
2. How it works (middle) — the mechanism at a high level
3. Why it works (bottom) — the technical foundation

Non-technical family members live at level 1. They care about what it does for them.

When your aunt asks "What's ransomware?" don't start talking about encryption algorithms.

Start here: "It's a digital kidnapper. Someone locks up all your photos and files, then demands money to give them back."

That's the what. Now she knows why she should care. Then you can briefly touch on how it happens — "usually through a fake email attachment."

Never dive to level 3 unless they ask.

The "So What?" Filter

Before you say anything technical, filter it through this: If I say this, will the person care?

If the answer is no, don't say it.

Your dad does not care that you use Linux. He cares that your computer doesn't crash.

Your mom does not care about your CI/CD pipeline. She cares that the website loads when she clicks.

Your cousin does not care about your database indexing strategy. He cares that the app feels fast.

Every technical detail should pass the "so what?" test. If you can't finish the sentence "And that means you will notice ______", then you haven't connected it to their life.

"Kubernetes orchestrates our containers" — so what?

"So even if a server catches fire, your video keeps playing without buffering."

Now it matters.

The Hunting Analogy (For When They're Stuck)

Sometimes people get stuck on a specific concept. When that happens, switch to a hunting analogy.

Every technology problem is a version of: "I need to find something / do something / protect something."

• Need to find info? You're a hunter tracking an animal.
• Need to protect data? You're building a fortress.
• Need to fix a bug? You're a detective finding who poisoned the village well.
• Need to scale up? You're building a bigger barn.

Analogies are cheat codes for understanding.

How to Handle the "Can You Just Fix It?" Question

The hardest conversation isn't explaining technology — it's explaining why you can't magically fix everything.

Standard script:

"You're asking me to [action]. I can do that, but it's like asking me to repaint your house while you're still living in it with all your furniture. I need to [time], and I need [access/info]. When would be a good time to sit down for 30 minutes?"

This works because it: 1. Acknowledges the request positively 2. Gives a concrete analogy for why it's not instant 3. Asks for a specific commitment

One Final Rule

Never make them feel stupid for not knowing.

If someone asks a "basic" question, that's brave. They trusted you enough to admit they don't know. Honor that.

The best response: "That's a great question. Most people don't know, but here's how I think about it..."

Then explain. Patiently. With an analogy from their world, not yours.

Because at the end of the day, the most important thing is that person feels heard — not that you feel smart.

That's the difference between a lecture and an explanation.