Why Engineers Are Terrible Communicators

Understanding & Overcoming the “Concept Tax” in Technical Communication

Key Concepts:

• Concept Tax: The extra mental effort required by listeners to understand technical explanations.
• Mechanism-First Thinking: A detailed, internally-focused approach to problem-solving common among engineers.
• Decision-First Thinking: A results-oriented, externally-focused approach to problem-solving common among executives and managers.
• Verbal Orange Cones: Technical jargon or complex concepts that disrupt listener comprehension.
• Cone Translation: The process of explaining technical terms in simple language, followed by the consequence or impact ("Why it matters").
• Failure Movie: A brief, vivid mental picture of the negative consequences if a technical issue occurs.

I. The Cognitive Burden of Technical Communication

The speaker begins by highlighting a significant issue: engineers are often difficult to listen to. Software measuring cognitive tension reveals that technical explanations demand more mental energy from listeners than communication from managers or CEOs. This isn’t due to a lack of intelligence on the part of the audience, but rather a mismatch in communication styles. Engineers naturally operate in a “mechanism-first” mindset, focusing on how things work, dependencies, and edge cases. Conversely, executives and managers prioritize “decision-first” thinking, asking what changes, why they matter, what the risks are, and what they need from the speaker.

This difference creates a “concept tax” – the extra mental work listeners must do to extract value from an engineer’s explanation. An example is given: stating “we refactored the pipeline, updated the schema, and improved concurrency” forces the listener to decode three concepts before understanding the overall point. Reducing this concept tax is crucial for career advancement.

II. The Danger of “Verbal Orange Cones”

The speaker introduces the analogy of “verbal orange cones” to illustrate how technical jargon hinders communication. Just as physical cones on a road force a driver to slow down and focus intensely, technical terms like “latency,” “schema,” and “rate limiting” disrupt mental processing and cause disengagement. The speaker establishes a rule of thumb: two “orange cones” (technical terms) within a 10-second window will likely cause the listener to disengage. This isn’t due to the listener’s lack of intelligence, but because their brain is overloaded with decoding and questioning the unfamiliar terminology. The speaker cites a personal anecdote with a powerlifting coach (“Joseph, your mitochondria is showing signs of implosion”) as an example of how even credible sources can lose their audience through overly complex language.

III. The “Cone Translation” Framework

To combat the concept tax and verbal orange cones, the speaker presents a structured approach called “Cone Translation.” This framework consists of three components:

1. Cone: The technical term itself.
2. Translation: The simplest explanation of the term in everyday language.
3. Why it Matters: The consequence, decision, or risk associated with the term.

For example, explaining “latency” becomes: “Latency, meaning the delay after you click, is why the app feels slow.” This structure connects technical details to tangible outcomes, making the information accessible to a non-technical audience. The speaker emphasizes the power of the word “why” as a gateway to the decision-first world of executives.

IV. Activating the Right Brain: The “Failure Movie” Technique

The speaker acknowledges that many engineers are predominantly left-brain thinkers (logical and detailed) and struggle with activating the right brain (visionary and creative). Instead of focusing on metaphors or poetic language, the speaker recommends an exercise called the “Failure Movie.” This involves creating a 5-10 second mental picture of what happens when something goes wrong.

The key insight is that executives and managers are highly attuned to consequences. Instead of stating “This improves reliability,” an engineer should say, “If this breaks, what it looks like is checkout getting stuck during our busiest time of day.” This transforms abstract technical language into a vivid, relatable scenario.

V. The “Failure Movie” Template & Its Benefits

The speaker provides a specific template for constructing a “Failure Movie” sentence: “If this breaks, who sees what and it causes cost?” Examples include: “If this breaks, users see payment failures and it causes abandoned carts.”

Using this technique demonstrates an engineer’s ability to think ahead and anticipate potential problems – a quality highly valued in leadership positions. It allows engineers to leverage their analytical skills to create compelling, visual communication that resonates with decision-makers. The speaker concludes by emphasizing that engineers are uniquely positioned to bridge the gap between technical expertise and effective communication, becoming invaluable “translators” within their organizations.

Data & Statistics:

• Software measuring cognitive tension demonstrates that listening to engineers requires more mental energy than listening to managers or CEOs.
• The speaker states that two “verbal orange cones” within a 10-second window will likely cause listener disengagement.

Notable Quote:

“If you can reduce or lessen significantly your concept tax, you will rise significantly in the communication ladder.” – The Speaker.

This summary aims to provide a detailed and specific account of the video’s content, preserving the original language and technical precision. It focuses on actionable insights and specific examples, rather than broad generalizations.