How to Explain Complex Ideas Simply: Turn Your Expertise Into a Model

Picture someone who knows their field better than anyone in the room. They explain it carefully, in full, with every caveat. The team nods. Leadership nods. And a week later nobody is doing anything differently.

It's tempting to decide the listeners weren't smart enough, or that the subject is just too complex. Often neither is the real issue. What's missing is a shape. When you give what you know a simple visual form, a triangle, a ladder, a graph, two things happen at once. The listener hears "this is simple." And they see where to start.

That's what this article is about: how to turn expertise into a model people can actually use.

Why Expert Knowledge Gets Stuck Before It Reaches the Team

A good model is supposed to help people learn faster and go deeper. So it's worth asking what gets in the way of that.

Ask what could stop a person from using a method they were handed, and the answers worth noticing are ordinary ones. The sense that the thing is complicated. The experience that it's hard. The feeling of "this is bigger than me."

Notice that none of those are facts about the content. They're feelings about it. Which means you can design against them.

A List of Principles Is Not a Model

Look around and you'll find models everywhere. People take communication styles, something humans have been doing forever, and draw it as a disc, a star, or some other shape, each one with a copyright line at the bottom.

I don't think that's bad at all. It means people have noticed that a picture teaches faster than a paragraph.

But there's a line worth drawing. If you've ever mapped out how you do what you do, you may already have some structure: six steps to this, four principles of that. A numbered list only becomes a model when the shape adds something the list didn't have.

It also helps to know what kind of model you're building. One kind is academic. It's validated through research, across many questionnaires and many people, and it's heavy, serious work. If that interests you professionally, go for it. Most managers don't need it.

The other kind is a conceptual model. It doesn't claim to be scientifically exact. It's a frame for looking at a situation, not a list of actions to perform. Its job is to make reality easier to see. So if your model is complicated, in most cases it's already failing at the one thing it was for.

The Shape Does Half the Explaining

Here's the part most people skip. The visual form of a model isn't decoration. It carries instructions.

Take a model from the NLP world that's drawn as a triangle. The way it's drawn tells you, without a word, that when you don't know where to begin, you start at its center. Later, when you want to be thorough, you often go through the whole thing starting from the bottom. It could just as easily have been a ladder. What matters is that the picture directs you.

Now take a graph. When I teach the stages a business goes through, I draw them as a graph on purpose, because a graph carries the feel of math. Nobody argues with the order of points on an axis. The shape itself announces a process with a fixed sequence.

That matters more than it sounds. Hand people a set of principles and they shop. They keep the ones that feel relevant and quietly drop the rest. A graph doesn't allow that kind of shopping. It's a package deal: accept it or reject it, but you can't cherry-pick.

A graph also makes a promise about time. Stages spread across a line tell people this is a journey, not an afternoon. And I deliberately draw three lines where one would do. I never have to say "this is several things happening in parallel." The drawing says it for me.

That's the real power of the drawing. It lets me pass my unspoken guidance for how to use the model straight to the person who has to apply it. And the message underneath it all is: this is simple.

There's a practical bonus for the person explaining, too. A single picture holds a lot of information at once. When someone interrupts with a question and pulls you off track, a speaker who has the whole picture in their head can go to another corner of it and come back. Without that picture, it's easy to lose the thread for good.

How to Turn What You Know Into a Simple Model

Define where people start and where they end up

Before you draw anything, answer two questions. What state is the person in when they meet this idea? What state should they be in when they're done? Everything in the model lives between those two points.

Collect, then put it in order

First gather everything that matters. Then ask whether it has a sequence, meaning some things have to happen before others. With actions that's usually obvious: you build the page before you send people to it. With ideas it takes more thought, and that thinking is often where the insight is.

Design against the obstacle

Go back to the feelings that stop people. Complicated. Hard. Too big for me. Then ask how the shape can answer them.

I often make worksheets so simple that people look at them and feel almost silly printing them. That's deliberate. The simplicity plants the belief that the task is easy, and easy tasks get done.

Give the what before the how

If people need a piece of knowledge to use a tool, give them that knowledge first. Talk about using your strengths to people who don't know what their strengths are, and they'll tell you it isn't practical. When the what is already in their hands, the how feels practical almost by itself, and a clear model is what puts it there.

And the more complex the thing you're asking for, the more ways you'll need to deliver it. Some people can do it from an explanation. Many need to see it demonstrated or feel it through practice.

Decide What the Model Is For

A model on a whiteboard still has to reach someone's real week. Before any important explanation, I set a goal on three levels. What should they grasp when I'm done? How should they feel about it? And what should they actually go and do? Sometimes one of the three is enough. Zero is never enough.

Then choose your examples as evidence. Ask which examples, stories and illustrations prove the belief you want the listener to hold. An example isn't there to fill time. It's there to prove the belief you want them to walk away with.

One more thing experts should know about themselves. You often see a bigger problem that the average person can't see yet. Don't lead with it. Solve the first problem they can see, and that's what lets them see the second one.

Packaging Is Not a Model

A warning, because I've watched this backfire. In recent years the "seven steps to anything" format got pushed hard, since showing a method from the outside makes people feel safe. Too often there was nothing behind the number, just a loose collection of ideas dressed up as a formula, and people learned to expect disappointment.

So don't reach for the packaging first. Reach for the substance, and let the shape come out of how the thing actually works.

Where Storytelling Comes In

A model gives an idea its structure. A story gives it a life. Managers need both, because the goal is the same: a message people understand, remember and act on.

That's the focus of my Authentic Storytelling workshop. A lot of storytelling training chases literary craft. This one is about the message: how to pick a short story that makes one point clearly, how to get people wanting to listen, how to check that your main idea really got through, and what to do when someone in the room disagrees. For managers and experts who explain things for a living, it's a natural next step after learning to give their knowledge a shape.