You don’t have to be a CIO to know that a great IT department is crucial to the success of any large organization. With the rise of big data, artificial intelligence, and the Internet of Things, technology promises to become an even more fundamental part of competitive corporate strategies in every industry.
But even as technology becomes more critical to success, technical knowledge remains limited. Many people, including powerful executives, consider software programming, network design, and other key competencies to be reserved for “technical people.” In other words, a CEO who pays very close attention to finance, sales, marketing, and other departments might gloss over cybersecurity, because they assume they won’t understand much of what happens.
When you’re responsible for your company’s technology and/or cybersecurity program, you have to be able to communicate your department’s needs to the executive team. Unfortunately, the perceived divide between “technical people” and the rest of the company can result in poor communication, especially in the boardroom.
Thankfully, explaining technical things in simple terms doesn’t have to be that challenging. Below are three best practices for communicating technical topics in ways any board member will understand.
1. Don’t Assume Baseline Knowledge
Normally when we speak to people, we subconsciously analyze just how much they know about whatever we’re talking about. This allows us to skip past the basics and get to the interesting stuff faster. This is a vital part of human communication — without this we would need to start every chicken soup recipe with instructions for turning on the stove.
However, our assumption is not always accurate, especially when it comes to technical topics. Assuming your audience knows too much can lead to frustration on both sides and impede important decisions from being made.
One example is technical jargon. Sure, it’s easier to say “VPN” than “virtual private network,” but if the people in the room don’t have an understanding of what those letters stand for, they will begin to tune out. Terms that seem very basic to you (e.g. SaaS or API) might cause confusion among your audience.
On the other hand, explaining every detail of a technical subject can be a tedious way of doing business, and might lead to executives feeling embarrassed about what you assume they don’t know. One workaround is to print a cheat sheet of technical acronyms and terms with their definitions and leave it in front of every seat before you start a presentation.
2. Talk About Impact, Not Process
When you’re discussing technical information as someone who likes working with technology, it can be tempting to talk in detail about how things work. While something like the ins and outs of hyper-converged network infrastructure might make for engaging conversation with your IT team, it won’t be as stimulating for members of the C-suite.