Framework: Use 'Low-Context' Comms for Execs
For managers making the leap to director, a key piece of advice is to shift to "low-context" communication for executive audiences. This means being direct, concise, and impact-focused, tying all engineering updates to business ROI without technical jargon.
The concept of low- and high-context cultures was developed by anthropologist Edward T. Hall in his 1976 book *Beyond Culture*. In low-context cultures, like the United States and Germany, communication is expected to be explicit and direct, with meaning contained in the words themselves rather than in subtle, non-verbal cues. This direct, low-context style is the default for most C-suite interactions because it values efficiency and clarity, minimizing ambiguity for time-constrained leaders. Executives want the destination, not a step-by-step narration of your journey to get there. The goal is to quickly convey the business impact of engineering work, not the technical process behind it. A powerful framework for this is the Minto Pyramid Principle, developed at McKinsey by Barbara Minto in the 1970s. It inverts the typical storytelling structure by starting with the main conclusion or "answer first," a method also known as "Bottom Line Up Front" (BLUF). The pyramid structure requires you to lead with your single key takeaway, followed by three supporting arguments or key points. Each of these points is then backed by data and evidence at the base of the pyramid. This allows an executive to grasp the main idea immediately and then decide how deep into the details they need to go. When presenting engineering work, translate technical metrics into business-focused outcomes. Instead of discussing story points or commit counts, frame updates around engineering predictability, on-time delivery, and the balance between innovation and maintenance. This directly addresses executive priorities like cost efficiency and revenue acceleration. For structuring specific project updates or narrating past performance, the STAR method (Situation, Task, Action, Result) is highly effective. It provides a simple, logical flow that crisply defines the business context and your team's direct impact on the outcome, a format widely used and recommended by companies like Amazon.
