How to Explain Technical Concepts to your Non-technical Colleagues

Have you ever watched your colleagues’ eyes glaze over as you try to explain something technical?
You’re mid-sentence talking about API endpoints or load-bearing capacity, and the person across the table has clearly switched off. It’s a frustrating experience — and a common one for engineers and technical professionals working in the UK.

The good news is that communicating technical ideas clearly is a skill you can develop. In this post, I’ll share a practical framework with four principles that will help you explain complex concepts to a non-technical audience in a way that’s accessible, engaging, and actually useful to them

When faced with explaining something technical, many professionals assume that a good explanation means covering every detail. They aim to be as accurate and precise as possible, because that’s what’s valued in technical fields.

However, the problem is that the person listening can get overwhelmed with too much information, especially when you are explaining something they don’t have much background knowledge in. They stop following, and your key point is lost entirely.

When speaking to a non-technical audience, accuracy isn’t the most important thing. Clarity is.
Your goal isn’t to turn them into technical experts; it’s to give them just enough information to understand what they need to know, and to deliver it in a way that makes sense for them.

Before explaining how something works, explain what it is and why it matters to them, and to the project. What problem does it solve? What change will it create?

This gives people a reason to listen, which is crucial. We pay attention when we understand why something is relevant to us.

Compare these two openers:

Without big picture: “We need to refactor the code base to reduce technical debt and improve scalability.”

With big picture: “I want to show you how we can save the team three hours a day by connecting these two systems.”

The second immediately answers: “Why should I care?” It creates a foundation you can build on if they want more detail, and it respects their time if they don’t.

This sounds obvious, but it’s harder than you’d think. When you work in a technical field, jargon 9words specific to your field of work) becomes automatic. You use it every day with colleagues who understand it instantly. Over time, you stop noticing which words are confusing to anyone outside your field.

The impact of language on how you’re perceived is significant. Use jargon-heavy language with a non-technical audience and you create distance, as they feel like outsiders looking in.

Use clear, accessible language and you create connection. You bring them into the conversation.

You have two options when technical language comes up:

1. Replace it with simpler language. Instead of “we need to improve the thermal efficiency of the system,” say “we need to stop the system from losing so much heat.”
2. Explain it simply if you must use the term. For example: “We need to add redundancy to the system — that means we’ll have a backup component that automatically takes over if the main one fails.” Then pause and check in: “Does that make sense?”

That final check-in matters. Don’t rush past a new term. Give people time to process and confirm their understanding before moving on.

For longer or more abstract explanations, analogies are one of your most powerful tools. They work by connecting something unfamiliar to something your audience already understands. This helps them to visualise a concept rather than just hear about it.

For example, a feedback control system in engineering can be explained like this: “It’s like the thermostat in your home. You set the temperature you want. When it drops below that level, the heating switches on. When it rises above it, the heating switches off. The system constantly monitors and adjusts to keep things stable.” Everyone who has a central heating system immediately understands the principle.

A few tips when using analogies:

1. Keep them simple and relatable.
2. Don’t worry about making them perfect — they don’t need to capture every detail, just the general idea.
3. Use them sparingly — save them for genuinely complicated concepts where they’ll add the most value.

Your voice is a powerful tool, and how you deliver your explanation matters as much as what you say. When you know a topic well, it’s natural to speak quickly because the material is comfortable and familiar. But your audience may be hearing it for the first time, and they need time to process.

Deliberately slow your pace. Add pauses after key points, definitions, and analogies. Silence isn’t awkward in these moments; it’s necessary. It’s the space where understanding happens.

Where helpful, use gestures to illustrate your points. For example, if you’re describing something increasing or decreasing, a simple hand movement reinforces the meaning.

Finally, actively invite questions throughout, not just at the end.
Create natural moments to check in:

1. “Does that make sense so far?”
2. “Is there anything you’d like me to explain in more detail?”
3. “Any questions before I move on?”

When someone does ask a question, treat it as a good sign. It means they’re engaged and following along well enough to ask.
Take time to answer clearly and with genuine interest in their understanding, as this will build connection and trust.

If you can put these four principles into practice, your conversations, meetings, and presentations with non-technical colleagues will become noticeably easier,  and far more productive!

Remember: your goal is never to turn them into technical experts. It’s to give them exactly what they need to make decisions, understand the project, and have a productive conversation with you.

If you’re looking for support with developing your English communication skills for the UK workplace, check out my one-to-one coaching programmes. All programmes are tailored 100% to your needs, so you’ll make progress more quickly than regular English programmes.

You can find out more and book your free trial session here:   One-to-one Coaching