Mastering Tech Communication: Can You Explain What You Built?

Communication Is Part of the Build

In tech, we pride ourselves on building systems that scale, that perform, that solve real-world problems. But there’s one question we often avoid asking ourselves:

Can I clearly explain what I built — to anyone?

After our latest episode of MoloMolo African Tech Stories with Dr. Paulin Kantue featuring Prof. Klaus Bengler — an expert in ergonomics, human-machine interaction, and applied psychology — that question hit differently. Because communication isn’t a layer added on top. It’s part of the system. If we can’t explain it clearly, we haven’t built it well enough.

“The finest form of technical communication is the product itself.” Prof. Bengler

The Problem with Performance

In our industry, there’s a tendency to conflate complexity with competence. Technical jargon becomes armor — a performance that signals expertise but often conceals uncertainty.

As Prof. Bengler said:

“You don’t lose your competence when you simplify your language. You show how much you understand.” - Prof. Bengler

Clarity isn’t a downgrade — it’s an upgrade. It’s a signal of mastery. And if we’re serious about user-centric design, we need to communicate like we mean it.

Context, Culture, and Cognitive Load

Dr. Paulin and Prof. Bengler explored how even icons — the most “universal” form of communication — aren’t always universal. Take the snowflake symbol on car air conditioners. Common in Western markets, but in regions that have never experienced snow, the symbol creates friction. Tech that ignores context becomes inaccessible by default.

This is especially relevant in Africa, where too much tech is still built elsewhere and dropped in with the assumption that it will simply work. But users don’t adapt to tech. Tech must adapt to users. That’s not just design — that’s survival.

“When a product becomes global, communication must localize — or risk irrelevance.”- Prof. Klaus Bengler

Simplicity Is Strategic

Let’s be clear: simplification is not the same as oversimplification.

One gives users clarity and confidence, the other leads them to a false sense of security.

For example: if your collision avoidance system only works under perfect weather conditions, say that. Because leaving out the limitations doesn’t protect the user — it puts them at risk.

Whether it's interface copy, technical documentation, or UX design, our job is to inform, not impress.

“There’s a fine line between simplifying and oversimplifying. One invites trust. The other creates false confidence.”- Prof. Klaus Bengler

Tech That Makes Sense

This conversation is a call to every engineer, product manager, UX designer, and founder: we need to stop hiding behind the complexity we create. We need to start explaining like we actually want people to use what we’ve built.

That means building for people who won’t have a glossary in hand. For people who don’t live in beta. For people who just need the tech to work — and make sense while doing it.

“The goal of communication is not to impress — it’s to connect. Especially when building for people who weren’t in the design room.”

Communication Is a Core Feature

The best systems aren’t just functional. they’re humane, they’re accessible. They respect the user’s time, background, and capacity.

Clarity is not a “soft skill.” It’s infrastructure. Communication is not optional. It’s architecture and if we don’t design with communication in mind, we haven’t finished building.

Let’s write documentation that people can actually use. Let’s build onboarding that speaks their language. Let’s make tech that doesn’t need a translator.

Let’s build systems — and stories — that make sense.

🎧 Watch the full episode of “Mastering Tech Communication” on YouTube here below.