How Engineers Communicate

Key Concepts

• Mechanism-First Thinking: A problem-solving approach prioritizing understanding how something works, its components, and potential failure points. Common among engineers.
• Decision-First Thinking: A problem-solving approach prioritizing understanding why a decision is being made, its impact, and required resources. Common among executives and managers.
• Communication Gap: The disconnect arising from these differing thinking styles, leading to friction in the workplace.

The Collision of Thinking Styles in the Workplace

The core issue discussed is the frequent clash between two distinct approaches to problem-solving and communication commonly observed in professional environments: a “mechanism-first” style, typically exhibited by engineers, and a “decision-first” style, prevalent among executives and managers. This isn’t presented as a value judgement, but rather as a fundamental difference in cognitive focus.

Engineers and Mechanism-First Thinking:

Engineers, according to the speaker, fundamentally approach challenges by dissecting how things function. Their inquiries center around technical details: “How does this work?” This isn’t simply curiosity; it’s a crucial step in ensuring robustness and reliability. Specific questions engineers pose include identifying “dependencies” – what other systems or components rely on this one? – and exploring “edge cases” – unusual or extreme scenarios that could cause failure. A key characteristic is a need for verification: “Is this statement true?” This reflects a commitment to factual accuracy and a desire to avoid assumptions. The emphasis is on a thorough understanding of the underlying system before any action is taken.

Executives/Managers and Decision-First Thinking:

In contrast, executives and managers prioritize understanding the impact of information and the need for action. Their questions are geared towards the bigger picture and the consequences of choices. They focus on “What are the changes?” – what is different now compared to before? – and “Why does this matter?” – what is the significance of this information? Risk assessment is paramount: “What’s the risk?” Crucially, they need to know what support they require: “What do you need from me?” This demonstrates a focus on resource allocation and enabling progress. The emphasis is on making informed decisions and driving outcomes.

The Nature of the Disconnect:

The speaker highlights that this isn’t a matter of one style being “better” than the other. Rather, it’s a difference in priorities. The collision arises because each style assumes the other shares its priorities. An engineer providing detailed technical explanations may be met with impatience by a manager seeking a concise answer to “What’s the impact?” Conversely, a manager asking “Why does this matter?” may be frustrated by an engineer’s detailed explanation of the underlying mechanism without a clear statement of consequences. This mismatch can lead to miscommunication, frustration, and ultimately, slower progress.

No Specific Data or Case Studies:

The discussion is largely conceptual and doesn’t rely on specific data, research findings, or detailed case studies. It’s presented as a common observation based on experience within workplace dynamics.

Synthesis:

The primary takeaway is the importance of recognizing these differing thinking styles. Effective communication requires adapting one’s approach to the audience. Engineers need to translate technical details into business implications for managers, while managers need to allow engineers the space to explore the “how” before demanding immediate decisions. Acknowledging this fundamental difference is the first step towards bridging the communication gap and fostering more productive collaboration.