Communicate effectively with executives and senior decision-makers. Frame engineering reality in business consequence without dumbing it down or burying it. Walk out of the meeting with a decision. A pitch is constraint propagation: the decision-maker has a model of "what's worth funding" with hidden weights, and your job is to surface the highest-weight features in the first two minutes — the same shape as designing a query for a known access pattern. Anchoring is optimizer initialization: the first number sets the starting point everyone else solves from, which is why whoever states the first number is choosing the search space. And a good pitch has the property a good API has: a coherent type signature. The decision-maker should know after the first sentence what kind of thing they're evaluating — a cost-avoidance case? a growth bet? a risk mitigation? Pitches fail when the type is ambiguous until slide six, by which point evaluation has stopped. One more compression test, borrowed from how the best framework authors name their philosophies: find your proposal's three-word version — "pay down auth," "migrate the read side," "fund observability." The three-word version is what the exec carries into the next meeting without you. Make sure it's right.
This course unlocks once you've finished its prerequisite. Open prerequisite →
A flag before anything else, because it matters more here than anywhere else in the curriculum: I have never been in an executive meeting. I have not had a CEO check their phone w…
Up-the-stack communication inverts every habit the earlier modules built: less context, more conclusion; one-shot opportunities, no iteration; an audience that cares about almost …
Approach: Essential
Approach: Important
Approach: Important
Approach: Important
Approach: Important
Approach: Reference
Approach: Reference
1. Write a 1-pager for one technical case you actually want to make — debt paydown, an infrastructure investment, a hire, an architectural change. Full structure, two-hour time-bo…
10 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.