Communicating up

• Lead with the answer, then the reasoning — executives will interrupt a build‑up; they won't interrupt a conclusion
• Every slide or sentence should survive the "so what" test — if it doesn't change a decision, cut it
• Translate technical risk into business risk in the same sentence: not "the API has a rate limit" but "at your projected volume, this constraint would delay the Q3 rollout by roughly six weeks unless we address it now"
• Silence is a tool — a confident pause after stating the key number lands harder than filling the space

Length is a signal

Deep technical people lose senior rooms on length far more often than on content. A complete answer in ninety seconds, followed by a full stop and "do you want more detail on any of that?", outperforms a thorough four‑minute version — for two reasons that have nothing to do with attention span. It hands control of the conversation back to the most senior person in the room, which is where they expect it to be. And it demonstrates the thing you are actually being assessed on: that you can tell what matters from what is merely true.

Apologising for the length is worse than the length. It tells the room you knew it was too long and did it anyway. The discipline to practise is the ending: finish, then stop, and let the silence sit. Filling it is a habit; not filling it reads as confidence.

Mapping the committee

At enterprise scale the buying committee isn't a list, it's a map: each stakeholder plotted by power (can they approve or block?) and interest (do they care about this deal at all?). High power / low interest stakeholders (often the CFO on a mid‑size deal) need brief, infrequent, numbers‑first contact. High interest / low power stakeholders — the people who will use the thing daily, and sometimes a well‑regarded internal advocate with no formal authority — need the most frequent contact and the most support material. (A true champion, by the definition in Module 06, has power as well as motivation and belongs in the first quadrant; an enthusiast without power is a coach, not a champion.) Getting this map wrong — over‑investing in someone who was never going to block the deal while ignoring the one who quietly can — is one of the most common reasons technically‑won enterprise deals stall. Full template at Template 9.