Fluency Class 5 — Explaining Tech to Non-Developers

💬

Opening – Real-World Trigger

≈5-10 min • Connect to actual frustrations

🎯 Goal: Start with a real frustrating situation explaining tech

Share a trigger moment (choose one that feels authentic):

Option 1: "I just got out of a meeting where our CEO kept asking 'But why can't you just add that feature? It's just one button.' I tried explaining technical debt but his eyes glazed over. Anyone else deal with this?"

Option 2: "My mom called me yesterday to fix her email. I said 'just clear your cache' and she said 'clear my WHAT?' Made me realize how much jargon we use without thinking..."

Option 3: "A PM asked me yesterday to explain why we can't just 'copy-paste the code from the old app.' I had to stop and think—how do I explain technical debt to someone who's never coded?"

Then naturally ask: "When's the last time you had to explain something technical to someone who just didn't get it?"

💡 Important: Share REAL frustration, not sanitized stories. "My PM thinks everything is just 'adding a button'..." This builds authentic connection and gets students laughing about shared struggles.

🛠️ Facilitation Toolkit: If Struggling to Recall

"Think about your last sprint planning meeting—did anyone ask a question that showed they didn't understand the technical work?"
"Has a family member ever asked what you do for a living and looked confused when you explained?"
"When's the last time you had to write documentation? Who was it for?"

📚

Vocabulary Bank – Simplification Phrases

≈8-12 min • Learn through natural examples

📖 Phrases for Explaining Tech Simply

Demonstrate these by explaining a concept (like "What is an API?") in a complete dialogue:

Complete Example Dialogue – Explaining an API:

Non-tech person: "What's an API? Everyone keeps mentioning it in meetings."

You: "Good question! In simple terms, an API is like a waiter at a restaurant."

Non-tech person: "A waiter? How?"

You: "Think of it like this: You (the app) tell the waiter (the API) what you want. The waiter takes your request to the kitchen (the server), and brings back your food (the data)."

Non-tech person: "Oh! So it's like a messenger between two systems?"

You: "Exactly! To put it another way, it's a translator that lets different programs talk to each other."

Non-tech person: "But why is it important?"

You: "The key thing to understand is that without APIs, every app would need to build everything from scratch. APIs let us use existing services."

Phrase	Natural Usage in Conversation
In simple terms...	"In simple terms, an API is like a waiter at a restaurant"
Think of it like...	"Think of it like a translator between two programs"
Basically, what this means is...	"Basically, what this means is the app talks to the server to get data"
To put it another way...	"To put it another way, it's like a digital filing cabinet where we store information"
Without getting too technical...	"Without getting too technical, we use encryption to keep your data secure"
The key thing to understand is...	"The key thing to understand is that building this properly takes time—we can't rush it"

🔄 Quick practice (2-3 min): One person says a tech term ("database", "frontend", "debugging"). The other explains it in one sentence using 1-2 phrases from above. the first person plays confused and asks follow-up questions.

🎭

Practice Scenarios – Real Situations

≈8-12 min • Roleplay with different audiences

🎯 Practice explaining to different stakeholders

Choose 2-3 scenarios based on real work context. One person plays the non-technical person!

Scenario 1: Explaining to Your Non-Tech Family

Context: Your grandmother asks "What do you do at work all day? Do you just type on a computer?"

Challenge: Explain your actual job without using ANY jargon (no "deploy," "backend," "API," etc.). Use analogies!

Practice: 2-3 minute conversation. One person acts confused when you use jargon.

Scenario 2: Defending Your Estimate to an Impatient PM

Context: PM says: "Can't you just add a login button? Why does it take 5 days? I can add a button in Figma in 5 minutes."

Challenge: Explain the complexity (backend integration, security, error handling, testing) without sounding defensive or condescending.

Practice: Stay professional while explaining why "it's not just a button."

Scenario 3: Explaining a Production Bug to a Panicked Client

Context: Client calls: "The login is broken! This is a disaster! Did you break something in the last update?"

Challenge: Explain what happened, why it happened, and when it'll be fixed—while keeping them calm and maintaining trust.

Practice: Balance transparency with professionalism. Don't blame, explain.

🛠️ Facilitation Toolkit: Make It Realistic

Act genuinely confused: "I still don't understand what you mean by 'integrate'..."
Add pressure: "But the CEO wants this tomorrow!"
Interrupt with questions: Don't let student give a monologue—real people interrupt
If student uses jargon: "What's [technical term]? You lost me."

🎤

Main Conversation – Explain a Technical Concept

≈20-30 min • Interactive explanation practice

🎯 Explain a technical concept to a non-technical audience

One person explains + the other plays confused non-tech person asking questions

Choose Your Pathway Based on Student Level:

🟢 Path A: Confident Communicator

Student chooses a complex technical concept from their actual work and explains it. Focus on handling difficult questions and edge cases.

Challenge mode: Play a skeptical stakeholder. "But why can't we just..." / "Competitor X does this in half the time..." / "This sounds too expensive."

🟡 Path B: Needs Practice

Choose from the list below. More support provided—asking clarifying questions to help student build their explanation step by step.

Guiding approach: "Start by telling me what problem this solves..." / "Can you give me an example?" / "What analogy could you use here?"

🔵 Path C: Advanced (Add Stakeholder Complexity)

After explaining the concept, teacher adds stakeholder perspective questions to deepen critical thinking.

Challenge questions: "How would you explain this to the board of directors who care about ROI?" / "If you had to defend this decision to an engineer who disagrees, how would you frame it?"

Choose ONE concept to explain (or pick from your real work):

What is cloud computing? (Explain to your non-tech friend)
Why does software have bugs? (Explain to a frustrated client who thinks you're incompetent)
What do you actually do as a [your role]? (Explain to family/friends)
Why does this feature take 2 weeks to build? (Explain to impatient PM or stakeholder)
What's the difference between frontend and backend? (Explain to complete beginner)
What is technical debt and why should we care? (Explain to business stakeholders)

🎙️ How This Works:

Student: Explains the concept using simple language, analogies, and vocabulary from Part 2

Non-technical person: Interrupts with realistic questions:

"Wait, I don't understand what you mean by [technical term]"

"Can you explain that in a different way? I'm lost."

"But why can't you just [oversimplified solution]?"

"So basically, it's like [tests understanding with analogy]?"

"How long will this take? How much will it cost?"

🛠️ Facilitation Toolkit: Deepening Techniques

If explanation is too technical: "You lost me at [term]. Explain it like I'm 10 years old."
If student rushes: "Slow down—I need to understand this first before we move on."
To test understanding: "Let me see if I got this right..." (repeat back incorrectly to see if student catches it)
Success check: "Can you repeat that explanation back to me in YOUR words now?"

📝 Success criteria: At the end, teacher should be able to explain the concept back to the student in simple language. If teacher can't, the explanation wasn't clear enough—iterate until it works!

💡

Reflection & Real-World Application

≈5-8 min • Connect to actual work

🎯 Connect today's class to real professional situations:

Discuss naturally (not all questions, just what's relevant):

What was the hardest part about simplifying your explanation?
Which analogy or phrase will you actually use in your work this week?
Do you have a meeting coming up where you'll need to explain something technical? How will you approach it now?
What's one habit you'll develop for explaining tech better going forward?

💬 Real-world application: These skills aren't just for English class. You'll use them in: client presentations, stakeholder meetings, sprint planning, writing documentation, explaining estimates to PMs, onboarding new team members, and literally every time someone asks "what do you do?"

🎯

Homework – Real-World Practice

Choose one actionable task

📝 Apply Your Simplification Skills to Real Work

Choose ONE option that fits your current situation:

Option 1: Create Your Analogy Library

Write simple explanations for 3 technical concepts you use daily. For each: name the term, create an analogy, explain it in one simple sentence. Use at least 2 phrases from today. (150-200 words total)

Option 2: Rewrite Technical Documentation

Find a piece of technical documentation you wrote (README, API docs, wiki page) and rewrite one section to be understandable by a non-technical PM or stakeholder. (200-250 words)

Option 3: Prepare Your Next Stakeholder Update

Write a 2-minute script explaining your current project/sprint to a non-technical audience (CEO, client, or PM). Focus on business value, not technical details. Practice delivering it out loud.

Option 4: Create Your "Explain My Job" Script

Write a 100-150 word explanation of what you do for work that your grandmother would understand. Test it on a non-tech friend or family member. Iterate based on their feedback.

Quality Checklist:

At least 3-4 simplification phrases from today's class used naturally
Zero unexplained jargon (or jargon explained immediately with analogies)
Clear analogies that relate technical concepts to everyday experiences
Something you could actually use in your real work this week

💬 Fluency Class 5 – Explaining Tech to Non-Developers