Why We Must Learn to Speak
Most technical professionals harbour a quiet belief that good work speaks for itself. We assume that if the code is elegant, the architecture sound, or the research data conclusive, stakeholders will naturally recognise its value.
They will not. In the reality of enterprise technology and academia, a poorly communicated architecture proposal is functionally indistinguishable from a bad architecture proposal. Brilliant engineering dies in conference rooms every day simply because the people presenting it treat communication as an afterthought rather than a core competency.
Patrick Winston, the late artificial intelligence pioneer and longtime MIT professor, understood this structural failure perfectly. For over forty years, he delivered an annual lecture titled “How to Speak.”[^1] It was never a seminar on charisma or stage presence. It was a rigorous, engineering-minded approach to cognitive engagement.
Winston operated on a specific premise: your career trajectory and the survival of your work depend on three variables, strictly in this order: your ability to speak, your ability to write, and the quality of your ideas. He formulated this into a straightforward equation where Impact equals Knowledge plus Practice plus Talent. Talent is the smallest variable. Knowledge of how human attention works, paired with deliberate practice, dictates whether your ideas are accepted or ignored. You have a fundamental duty to advocate for your work.
How to Engineer Cognitive Engagement
Accepting that your ideas require a deliberate defense is the foundation. The methodology involves working within the strict biological constraints of your audience. The human brain possesses only one language processor. It is incapable of reading complex text and listening to complex speech simultaneously. When you present, you are fighting a constant battle against cognitive overload and natural distraction. Winston estimated that up to 20 percent of any room is mentally absent at any given moment.
To mitigate this, you must build cognitive scaffolding into your delivery.
The First Sixty Seconds
Audiences are highly critical in the opening minute of a presentation. They are adjusting to your cadence and deciding whether you are worth their attention. Never open with a joke. The audience is not calibrated to your humour yet, and technical professionals rarely deliver stand-up comedy effectively.
Instead, deliver an empowerment promise. Tell the room exactly what capability or insight they will possess at the end of the session that they lack right now. If you are defending a system migration, state clearly: “By the end of this hour, you will understand the specific latency bottlenecks in our current monolithic setup, and how this proposed microservices framework will resolve them.” Give their limbic system a reason to trust that the next hour is a valuable investment of their time.
The Big Four Heuristics
Because attention naturally degrades, Winston insisted on four structural habits to repeatedly pull the audience back into the narrative:
Cycling: Never state a critical concept only once. Introduce the idea briefly, cycle back to explain it in depth, and then summarise the exact takeaway you want them to remember.
Building Fences: Technical audiences naturally attempt to pattern-match your idea against things they already know. Control this process. Clearly define what your idea is not. If you are proposing a new caching strategy, state explicitly: “This looks similar to our Redis implementation, but the invalidation logic here is completely different.” Build a fence around your concept so it isn’t confused with legacy work.
Verbal Punctuation: People zone out. When they tune back in, they need a landmark to understand where they are in the narrative. Provide explicit transitions. Phrases like, “We have established the historical failure rates. Now, we will examine the proposed architectural fix,” act as cognitive seams.
Asking Questions: Introduce manageable silence. Ask a highly specific question and wait for a full seven seconds. It forces the room to actively process the material rather than passively consuming it.
Packaging the Output
If you want an idea to survive long after the meeting concludes, it must be easily transmittable. Winston advocated for the “Five S’s” when looking to gain broad traction for a concept: a visual Symbol, a memorable Slogan, an element of Surprise that challenges industry assumptions, a Salient idea that anchors the logic, and a Story that explains the genesis of the work.
What to Execute in the Room
The physical environment and the tools you choose dictate how your message is received. We routinely default to slide decks out of habit, often to the detriment of the presentation.
Controlling the Medium
Slides are excellent for exposing ideas—showing a network topology diagram or a data graph—but they are terrible for teaching. If your goal is to explain a complex mechanism, use a physical board or a prop. Watching someone draw a system architecture or manipulate an object triggers empathetic mirroring. The audience’s mirror neurons fire, and they cognitively participate in the creation of the idea alongside you.
If you must use a presentation deck, ruthlessly edit it. Strip away background graphics, company logos, and unnecessary text. If your slide contains a paragraph, the audience will read it and ignore your voice. Rely on a minimum 40-point font. Discard the laser pointer, which only serves to highlight natural hand tremors and breaks eye contact; draw arrows directly on your slides instead.
Environment and Closure
Context matters. A dark room signals the brain to sleep. Instruct the AV staff to keep the house lights up; it is far easier to see a bright screen with open eyes than closed ones. Time of day is equally critical. Post-lunch sessions battle physiological fatigue. If you control the scheduling of an internal review, prepone it to 11:00 AM when baseline alertness is optimal.
Finally, consider your exit. The standard industry practice is to end on a blank slide or a generic “Thank You” screen. This wastes the most potent moment of the presentation. Your final visual should be a ‘Contributions’ slide—a concise summary of the specific value you just delivered. Leave that slide up as you take questions and as you walk off. Let your core thesis be the final image burned into the room’s memory.
You do not need innate charisma to be a highly effective technical speaker. You only need to respect the mechanics of human attention and practice the discipline of structural clarity.
Footnotes:
[^1]: MIT OpenCourseWare. “How to Speak by Patrick Winston.” https://ocw.mit.edu/resources/res-tll-005-how-to-speak-january-iap-2018/how-to-speak/
