Explain like mom

Explain Like Mom 👩

Purpose

Your mom asks "what do you do at work?" and you freeze. You could say "I'm a DevOps engineer optimizing CI/CD pipelines" but her eyes would glaze over before you finish.

This skill translates technical concepts into plain language with analogies anyone can understand.

When to Activate

• "Explain [technical thing] to my parents"
• "How do I describe my job to non-tech people?"
• "My client doesn't understand why this matters"
• "ELI5" or "explain like I'm five"
• Preparing for family gatherings
• Writing for non-technical audiences

The Translation Framework

Step 1: Identify the Core

Before translating, ask:

• What does this actually DO (not how it works)?
• Why should anyone care?
• What's the real-world impact?

Step 2: Build the Analogy

The Analogy Generation Formula:

[Technical Thing] is like [Everyday Thing] because [Shared Property].

How to generate analogies for ANYTHING:

1. List the key properties of the technical thing (3 max)
2. Find something in daily life with the same properties
3. Map the relationship, not the object

Technical Thing	Key Property	Daily Life Equivalent
API	Intermediary that takes requests	Waiter
Cache	Stores frequently used items nearby	Kitchen counter
Encryption	Transforms to unreadable, reversible	Secret language with friend
Load Balancer	Distributes work evenly	Airport check-in lines
Recursion	Thing that calls itself	Russian nesting dolls
Version Control	Track all changes, go back anytime	Google Docs history

The Formula in Action:

"What's a CDN?"

1. Key property: Copies of content stored in many locations closer to users
2. Daily life equivalent: Chain stores vs. single store
3. Map it:

"It's like how Starbucks has locations everywhere instead of one giant store downtown. Instead of everyone traveling far to the one location, there's a copy near you. CDN does that for websites — copies of the content stored around the world so it loads faster."

Step 3: Calibrate to Audience

Different listeners need different depth:

Audience	Goal	Approach
5-year-old	Wonder, not accuracy	Magic + simple cause/effect
Mom (60+)	General understanding	Household analogies, skip "why"
Non-tech colleague	Enough to collaborate	Business impact, light mechanics
Client	Trust your expertise	Outcome focus, minimal jargon
Curious friend	Real understanding	Can go deeper, check interest

Calibration questions:

• Do they actually want to understand, or just making conversation?
• Will they need to explain this to someone else?
• How much time do I have? (30 sec vs 5 min)

Step 4: The Second-Hand Test

Success = they can re-explain it.

"So mom, if Auntie asks what I do, what would you tell her?"

If she can say it back in her own words → you succeeded. If she says "something with computers" → try again.

Why this works:

• Forces you to be simple enough to transfer
• Reveals what actually stuck
• Catches jargon that slipped through

Translation Examples

Jobs

Technical Title	Plain Language	Analogy
DevOps Engineer	"I make sure the tech plumbing works so the website doesn't break"	Building superintendent
Data Scientist	"I find patterns in big piles of information to help make decisions"	Detective with spreadsheets
UX Designer	"I make apps easy to use so people don't get frustrated"	Interior designer for software
Product Manager	"I decide what features to build and make sure everyone's on the same page"	Movie director
Backend Developer	"I build the behind-the-scenes stuff that makes apps work"	Kitchen staff (vs. waiters)
Frontend Developer	"I build what you actually see and click on"	Interior decorator
Machine Learning Engineer	"I teach computers to recognize patterns, like how you recognize faces"	Dog trainer for computers
SRE	"I make sure websites stay up and fix them when they break"	Hospital ER doctor for websites

Concepts

Concept	Bad Explanation	Good Explanation
Blockchain	"A distributed ledger using cryptographic hashing"	"Imagine a notebook that everyone has a copy of, and every time someone writes something, it appears in everyone's book instantly. Nobody can erase or change old pages because everyone would notice."
API	"An application programming interface for system communication"	"It's like a waiter in a restaurant — you tell the waiter what you want, they go to the kitchen, and bring back your food. The API takes your request, gets what you need from somewhere else, and brings it back."
Cloud Computing	"Virtualized infrastructure as a service"	"Instead of buying a whole computer, you rent a piece of a giant computer somewhere else, like renting an apartment instead of buying a house."
Machine Learning	"Algorithms that learn from training data to make predictions"	"You know how you learned what a cat looks like by seeing thousands of cats? Computers learn the same way — show them enough examples and they start recognizing patterns."
Encryption	"Asymmetric cryptographic key exchange"	"It's like a special lockbox where you can put a letter in, but only the person with the right key can open it. Even if someone steals the box, they can't read what's inside."
Bug	"A software defect causing unexpected behavior"	"A typo in the instructions that makes the computer do the wrong thing. Like if a recipe said 'add 10 cups of salt' instead of '1 teaspoon.'"
Latency	"Network delay in packet transmission"	"The time it takes for your message to get there, like the delay between talking and hearing yourself on a bad phone connection."
Bandwidth	"Data transfer capacity"	"How wide the pipe is. A garden hose vs. a fire hose — both carry water, but one carries a lot more at once."

Cryptocurrency Specific

Concept	Mom-Friendly Explanation
Bitcoin	"Digital money that's not controlled by any bank or government. It's like gold, but on the internet — there's only so much of it, and people trade it."
Mining	"Computers solving puzzles to verify transactions and earn Bitcoin as a reward. Like a lottery where your ticket is doing math homework."
Wallet	"An app that holds the keys to your digital money. It doesn't actually hold the money — it holds the password to access it."
NFT	"A digital receipt that proves you own something online. Like having a signed certificate for a famous painting, but the painting is a jpeg."
DeFi	"Banking without banks. Imagine if you could lend money to strangers, earn interest, and get it back — all automatically, with no bank in the middle."
Smart Contract	"A vending machine for deals. You put in what was agreed, and it automatically gives the other person what they were supposed to get. No trust needed."

AI Specific

Concept	Mom-Friendly Explanation
ChatGPT	"A computer that learned to write by reading the entire internet. You ask it questions and it writes answers based on patterns it learned."
LLM	"A computer that's really good at predicting the next word. That's all it does — but it does it so well it seems smart."
Training	"Showing the computer millions of examples until it learns the pattern. Like how you learned to read by seeing thousands of words."
Hallucination	"When the AI makes something up confidently because it's good at sounding right, not at being right. Like a BS-er in a meeting."
Prompt	"The instructions you give the AI. The better your question, the better the answer."
Fine-tuning	"Extra training for a specific job. Like a general doctor doing extra training to become a heart surgeon."

Template: Job Description for Family

**What I tell recruiters:**
[Jargon-filled job title and responsibilities]

**What I tell mom:**
"I work with computers. Specifically, I [simple verb] [relatable thing] 
so that [outcome people understand].

Think of it like [analogy]: [explanation of how analogy maps to job].

On a typical day, I [2-3 concrete activities anyone can picture]."

Example:

**What I tell recruiters:**
"I'm a Site Reliability Engineer responsible for infrastructure automation, 
incident response, and maintaining 99.99% uptime for distributed systems."

**What I tell mom:**
"I make sure websites don't break. When you use an app and it works 
smoothly? That's because someone like me made sure the behind-the-scenes 
stuff is running right.

Think of it like being a building superintendent: I don't design the 
building, but I make sure the plumbing works, the lights stay on, and 
I fix things when they break — often before anyone notices.

On a typical day, I check that everything's running, write tools that 
automatically fix common problems, and when something breaks at 3am, 
I'm the one who gets the call."

Analogy Patterns That Work

The Kitchen Analogy (for Software)

Software Concept	Kitchen Equivalent
Frontend	The dining room (what customers see)
Backend	The kitchen (where the work happens)
API	The waiter (takes orders, delivers food)
Database	The pantry (stores ingredients)
Cache	The prep station (frequently used items ready)
Bug	Wrong ingredient in a recipe
Deployment	Opening the restaurant for the day

The City Analogy (for Networks)

Network Concept	City Equivalent
Server	A building that provides services
Client	A person visiting the building
Internet	The road system
Bandwidth	Road width
Latency	Distance to travel
Firewall	Security gate at city entrance
DNS	Street address system

The Office Analogy (for AI/ML)

AI Concept	Office Equivalent
Model	New employee
Training	Teaching the new hire
Fine-tuning	Specialized training
Inference	Doing the actual work
Hallucination	Confidently giving wrong info
Prompt	Instructions from manager

Commands

"Explain [concept] like I'm explaining to my mom"
"Translate this job description for normal people"
"ELI5: [technical topic]"
"How do I explain [my job] at Thanksgiving?"
"Make this jargon-free: [text]"

Common Failures (and Fixes)

Failure 1: The Jargon Swap

What happens: Replace one jargon with another.

❌ "A container is like a virtual machine but lighter" ✅ "A container is like a lunchbox — it has everything the app needs to run, packaged together, so you can move it anywhere"

Why it fails: "Virtual machine" means nothing to mom. Fix: Every term in your analogy must be everyday words.

Failure 2: The Accuracy Trap

What happens: So worried about being precise that you add caveats.

❌ "Well, it's KIND of like a library, but not exactly, because actually the data isn't really stored that way, and there are indices, and..." ✅ "It's like a library. Good enough."

Why it fails: Caveats confuse. Precision is for experts. Fix: Accept that analogies are imperfect. Directionally correct > technically precise.

Failure 3: The Multi-Metaphor Pileup

What happens: Stack multiple analogies hoping one lands.

❌ "It's like a waiter, but also like a translator, and kind of like a phone operator..." ✅ "It's like a waiter. You tell the waiter what you want, they go get it."

Why it fails: Multiple metaphors create confusion, not clarity. Fix: One analogy. Commit to it.

Failure 4: The "Let Me Start From The Beginning"

What happens: Explain all prerequisites before the actual thing.

❌ "So first you need to understand how the internet works, and then TCP/IP, and then..." ✅ "You know how you send a text? This makes sure it gets to the right person."

Why it fails: They asked about one thing, not a CS degree. Fix: Answer the question. Add background only if they ask.

Failure 5: Missing the Real Question

What happens: Explain the thing, but not what they actually wanted to know.

Mom: "What do you do at work?" ❌ [10-minute explanation of Kubernetes] ✅ "I help keep websites running so they don't crash. Like a building maintenance person, but for the internet."

Why it fails: They wanted to understand your life, not your tech stack. Fix: Answer the underlying question. Usually it's "should I be proud?" (yes) or "is this a real job?" (yes).

---

Anti-Patterns

❌ Don't	✅ Do Instead
Use acronyms without explaining	Expand and simplify
Assume any background knowledge	Start from scratch
Say "it's complicated"	Find a simpler analogy
Explain HOW it works	Explain WHAT it does and WHY it matters
Use analogies that require tech knowledge	Use household/everyday analogies
Stack multiple metaphors	One analogy, commit to it
Add caveats for precision	Accept imperfect but clear

Response Principles

1. Start with WHY they should care — Impact before mechanism
2. One analogy is enough — Don't stack multiple metaphors
3. Concrete beats abstract — "10 million users" not "at scale"
4. Test with actual non-tech people — If mom doesn't get it, iterate
5. It's okay to lose precision — Better understood than accurate