For the technical leader deciding whether communication training is worth their engineers’ time: what changes when decision makers understand what they are signing.
An engineer leading a project needed approval from several decision makers. He got every sign-off, so he believed everyone understood and agreed to what the project would deliver. Then, when it came time to deliver the product, one of those decision makers told him, “This isn’t what I signed off on at all.”
He pointed out that the person had signed the approval documents. The signature, it turned out, had never carried understanding, and nobody found that out until the end.
The gap between a signature and an understanding is common enough to show up in the numbers. In the 2024 State of Business Communication report from Grammarly and The Harris Poll, about one in five business leaders said they had lost business because of poor communication.
The engineer told that story as a guest on Neil Thompson’s podcast, and Neil draws the lesson plainly: “obtaining someone’s approval does not necessarily mean that person understands what they are approving.” Closing that gap is what his company does. Teach the Geek, which he founded in San Diego in 2017, works with technical professionals so they can present more effectively, especially in front of non-technical audiences, mainly by developing speaker training programs for organizations with technical staff. Neil is an engineer himself, a licensed Professional Engineer in California with a master’s in biomedical engineering from Columbia, and he spent years presenting to management in the medical device industry. “I was terrible at it at first, but improved significantly over time,” as he puts it on his profile.
The Question He Asks First
Neil’s answer to the problem starts before the slides. An engineer who served on the board of a technical association came to him with a structural problem. “She had difficulty structuring her presentations so that the other board members could easily follow what she was saying,” he says.
“We started by identifying the call to action for her presentations. I asked her, ‘What do you want people to think or do after hearing you speak?’”
“Once we had an answer to that question, we worked backward to identify the key points she needed to communicate to achieve it. This removed information that did not answer the question.” The effect, in his account, was that she was giving the board members the information they needed to make decisions rather than overwhelming them with details that weren’t relevant to those decisions. “The improvement was noticeable. Her presentations became easier to follow, and the other board members could better understand what she was communicating.”
It’s the same instruction he gives in his latest article for Inc., where he’s a contributor. Technical professionals, he wrote, often try to give everyone in a presentation everything they might want to know, and executives get buried in details. His alternative is a single question: “What information could change the decision?”
He has a larger argument about why that question matters, and he makes it to clients in plain terms.
Communication as Technical Infrastructure
“Communication should not be treated as a soft skill that is optional or secondary to technical expertise,” Neil says. “It should be treated as essential to getting work done.”
“A technical professional can be talented, but that expertise has limited impact if the people responsible for making decisions cannot understand or act on what the technical professional is saying.”
Neil Thompson, Founder, Teach the Geek
When communication fails, he says, “decision makers may misunderstand a recommendation, overlook an important consideration, or make a poor decision because they did not fully understand the information presented to them.” That’s why he calls communication critical technical infrastructure: “It enables technical knowledge to be understood and used. Just as organizations need reliable systems and processes to carry out their work, they need technical professionals who can explain complex information clearly enough for others to make informed decisions.”
He has made the same case to the pharmaceutical industry in an article for ISPE, “Communication as Technical Infrastructure in Pharmaceutical Manufacturing,” arguing that communication deserves the same strategic attention as the technical systems that support pharmaceutical operations.
He didn’t start out holding that view. He arrived at it in a project status meeting.
The Meeting Where the Project Was Canceled
Neil worked as a product development engineer in the medical device industry for several years. The first turn in his career came from his boss, who wanted the engineers to become patent agents so the company could handle patent drafting and prosecution internally rather than outsourcing that work to outside counsel. “I became a patent agent for that reason,” he says. “Interestingly, my boss continued outsourcing the work even after I became a patent agent, leaving me with patent agent skills but little opportunity to use them.” He eventually joined a boutique patent firm where he could use them, Torrey Pines Law Group, which specializes in life sciences IP as it relates to artificial intelligence and machine learning. There he drafted and prosecuted patent applications from 2019 to 2023. Alongside, he wrote for medical device companies as a freelancer: marketing collateral, quality documents and clinical papers.
The second turn was the one that led to Teach the Geek. As an engineer he had to give presentations to management, “and I was not particularly good at them,” he says. Then the project he was hired on for was canceled, abruptly, during a project status meeting. He was reassigned to other projects, but the experience made him question whether his communication had contributed to the cancellation.
“I did not want to find myself in that position again, wondering whether my inability to communicate effectively had affected the outcome of my work.”
Neil, Founder, Teach the Geek
He joined Toastmasters, an international organization that gives people opportunities to practice public speaking (his profile records an Advanced Communicator Bronze from 2013), and improved. He also noticed something: “many of the engineers I worked with struggled with presentations just as I had.” He calls that observation an opportunity “to help other technical professionals develop skills I had worked hard to acquire myself.”
The third turn was turning that opportunity into a company. “Teach the Geek grew out of my engineering experience and my recognition that technical professionals needed help communicating their expertise,” he says. “I wanted to work with people like myself so they could present more effectively, particularly to non-technical audiences, and help decision-makers make more informed decisions.”
One person helped him say what the company was.
Useful Beats Entertaining
Lois Creamer introduced him to the idea of the positioning statement. “A short and clear statement on what you do and who you work with, a positioning statement helped me better talk about Teach the Geek,” Neil says. His own now reads: working with technical professionals so they can present more effectively, especially in front of non-technical audiences.
He applies the same precision to the advice he hears about speaking. “To be an effective speaker, you need to be engaging,” he wrote in a recent post. “I hear this advice all the time. But I think we need to be more precise about what ‘engaging’ means.” His definition doesn’t require a laugh, a dramatic story or getting the audience out of their seats. “You need to give me a reason to keep listening.” A speaker can be entertaining without being useful, or useful without being particularly entertaining, and he’s clear which he’d take: “I’ll take the second one.”
He holds the same line on generative AI. “Generic information is a dime a dozen. Information itself isn’t,” he wrote. A speaker who has spent twenty years in a field and reached a conclusion that runs counter to conventional wisdom has something, he argues, that an AI wouldn’t give you unless you knew to ask the right question in the first place.
“I don’t necessarily want a speaker to give me information I could have gotten from AI. I want them to give me information I didn’t know I needed.”
Neil, Founder, Teach the Geek
Much of that thinking comes out of the Teach the Geek podcast, which he has hosted since 2017, interviewing engineers, scientists and others with STEM backgrounds about public speaking, with a new episode every Wednesday. He has also published The State of Technical Communication Report, which draws on nearly one million words of interviews and looks at how communication drives performance, alignment and leadership in engineering organizations.
That work continues this year, and he has a specific reader in mind for it.
Where Neil Is Now
This year Neil is writing as much as he’s speaking. His articles for Inc. and ISPE carry the infrastructure argument to business and pharmaceutical readers, and his newsletter carries it to his own list, each issue built around a main insight and an interview. His children’s book, Ask Uncle Neil: why is my hair curly?, from 2018, answers his nephew Anthony’s question with science. He wrote it, he says, to foster curiosity in children so they “see themselves as members of the innovation economy.”
The reader he most wants this piece to reach is specific. “My goal is to get Teach the Geek in front of technical leaders within organizations who can determine whether communication training for technical professionals benefits their technical staff,” he says. What he’s offering them is the speaker training program, and he is direct about its limits: in a talk on developing speaker training for technical staff, he says training alone isn’t enough, and that repeated, hands-on practice is what lets participants internalize techniques and gain confidence.
Asked for one thing outside work that belongs in the piece, he gave a habit. “I like routines. For example, I always keep my phone, keys, and wallet in the same place so I do not have to waste time looking for them. I think presentations benefit from a similar kind of structure, namely always preparing presentations by having a call to action and working backwards to develop the presentation’s points.”
Asked for the one line he wants readers to take away, he pointed to his own: “Your CEO doesn’t need more information. They need the right information.”
Five Lines from Neil’s Diary
- “What do you want people to think or do after hearing you speak?”
- “Attention is getting me to listen. Engagement is giving me a reason to keep listening.”
- “Generic information is a dime a dozen. Information itself isn’t.”
- “Obtaining someone’s approval does not necessarily mean that person understands what they are approving.”
- “I want them to give me information I didn’t know I needed.”
From the Diary of Neil Thompson
Neil Thompson is a San Diego-based engineer and the founder of Teach the Geek.
| Role | Founder, Teach the Geek; presentation skills speaker and trainer; host of the Teach the Geek podcast |
| Based in | San Diego, California |
| Previously with | Torrey Pines Law Group, PC (2019 to 2023) |
“Your CEO doesn’t need more information. They need the right information.”
Editor’s note
Executives Diary features Neil Thompson because his argument comes with a mechanism. He starts a presentation at the decision it has to produce and works backward, and the case he gives shows exactly what that removes. He arrived at the work through a project of his own that was canceled in a status meeting, and he says so. The feature is written for the technical leader deciding whether communication training is worth their staff’s time.
Executives Diary, Editorial



