How to explain complex ideas

The more you know about something, the harder it becomes to explain it simply.

This is the curse of expertise. You've spent years learning your product, you know every detail, every nuance, every technical specification.

And that tends to make you terrible at explaining it to someone who doesn't.

Most technical founders and marketers lose people in the first paragraph. They use jargon because it feels professional. They include every detail because they think it adds credibility. They assume people have the same baseline knowledge they do. (The curious part is that this mostly happens when writing, not so much when explaining it in person)

The result? Confusion. Glazed eyes. People nodding but not actually understanding.

So today, I'm going to show you the 10-year-old method for breaking down complex ideas so clearly that anyone can understand them.

Let's dig in.

Here's what I think happens when experts try to explain their work.

They use “jargon” because it feels professional. Saying "we leverage machine learning algorithms" sounds smarter than "our software learns patterns and makes predictions." But one is clear, and the other isn't.

They include every detail because they think it adds credibility. they assume that more information equals more trust. But often, more information just creates more confusion.

They assume people have context they don't have. they forget what it was like not to know this stuff. They skip the foundational steps because they seem obvious to them.

The result is content and conversations that may technically be accurate but practically useless. Because if people don't understand what you're saying, it doesn't matter how correct you are.

If you can explain your product or idea to a 10-year-old, you can explain it to anyone.

This doesn't mean dumbing it down. It means stripping away everything that doesn't need to be there and focusing on clarity.

Here's the framework:

Step 1: Strip out all the complex words

Replace technical terms with everyday words. If you can't replace a term, you need to define it first in plain language.

The test is simple: Would a 10-year-old know this word? If not, find a different word or explain it.

For example, instead of "API integration," you might say "connection between two systems." Instead of "predictive analytics," you might say "using patterns to guess what will happen next."

I think this step is the hardest because jargon feels like shorthand. It is shorthand, but only for people who already know what you're talking about. For everyone else, it's a wall.

Step 2: Start with what they already know

Connect your new concept to something familiar. Use analogies from daily life. Build from the known to the unknown.

A 10-year-old doesn't know how software works, but they know how Netflix recommends shows based on what they've watched. They don't know what machine learning is, but they understand that the more you use something, the better it gets at knowing what you like.

Start there. Then build.

This is how you bridge the gap between their world and yours. You're not asking them to learn an entirely new language. You're translating yours into theirs.

Step 3: Focus on the "what" and "why," not the "how"

A 10-year-old doesn't need to know how something works mechanically. They need to understand what it does and why it matters.

The same is true for most of your prospects.

They don't need to know the technical architecture of your platform. They need to know it saves them time. They don't need to understand the algorithm. They need to know it helps them make better decisions.

Save the technical details for later, or for the people who specifically ask. Lead with the outcome.

Step 4: Use concrete examples, not abstract concepts

Show, don't tell. Use specific scenarios people can visualize. Turn data into stories.

Instead of saying "Our solution increases operational efficiency by 30%," say "A farm using our system saved 15 hours a week on data entry and caught a soil issue three weeks earlier than they would have with their old process."

One is a number. The other is a picture.

I think concrete examples work because they let people imagine themselves in the scenario. Abstract concepts require too much mental translation.

Step 5: Break it into the smallest possible pieces

One idea per sentence. One concept per paragraph. Build complexity slowly.

Don't try to explain your entire product in one paragraph. Explain one piece. Then the next piece. Then how those pieces connect.

This may feel painfully slow to you because you already understand it. But for someone learning it for the first time, this pacing is what makes it actually land.

Let me show you what this may look like in practice.

Example 1: Explaining a technical product feature

Complex version: "Our API leverages machine learning algorithms to optimize resource allocation through predictive analytics."

10-year-old version: "Our software watches how you use your equipment and tells you the best time to use each piece, so nothing sits idle and nothing gets overworked."

Same concept. One is clear, one isn't.

Example 2: Explaining a business model

Complex version: "We operate on a SaaS revenue model with tiered pricing based on usage metrics."

10-year-old version: "You pay us monthly, like Netflix. The more you use it, the more you pay, but you can start small."

Everyone understands Netflix. Not everyone understands SaaS revenue models.

Example 3: Explaining ROI

Complex version: "Our solution delivers a 3:1 ROI within 18 months based on operational efficiency gains."

10-year-old version: "For every dollar you spend with us, you'll save three dollars within a year and a half, mostly by wasting less time and materials."

The second version tells them exactly what happens. The first version requires translation.

I think the 10-year-old method should be your default. But there are times when you can add complexity back in.

Use the simple version when:

You can add complexity when:

The key is to start simple. You can always add layers. But if you start complex, you may lose people before they ever ask for more.

Pick your most complex product feature or concept. The one you struggle to explain. The one where people's eyes glaze over.

Write down how you currently explain it. Then rewrite it as if you're explaining it to a 10-year-old.

Strip the jargon. Start with something familiar. Focus on what it does and why it matters. Use a concrete example. Break it into small pieces.

Then test it on someone outside your industry. A friend, a partner, someone who has no context for what you do.

If they understand it, you've got it. If they don't, simplify it more.

Use that simple version as your default explanation. You'll be surprised how much clearer your conversations become.