Quote: Tech Leadership as the 'Adult in the Room'

- A common framework for structuring executive updates is the Pyramid Principle, which advises leading with the main recommendation first, followed by a maximum of three supporting arguments, and then detailing the implications and next steps. - The Situation-Complication-Question-Answer (SCQA) framework is another popular narrative tool for presentations; it establishes a shared context (Situation), introduces a problem (Complication), poses a key question, and then delivers the solution (Answer). - When allocating engineering resources, some leaders use a 20/80 split as a baseline, dedicating 20% of team capacity to foundational work like tooling and infrastructure, and 80% to projects that directly serve business objectives. - A key mindset shift from Manager to Director involves changing focus from team execution and velocity to the broader business impact of your organization, such as cost efficiency, product time-to-market, or revenue expansion. - To demonstrate business alignment, engineering leaders can translate technical metrics into business outcomes; for example, framing on-time delivery as "engineering predictability" for sales and marketing or tracking lead time for change as a measure of business agility. - The transition to a director-level role typically requires 8-12 years of total experience, with the preceding Senior Manager level often taking 2-3 years to attain after first becoming a manager. - The Objectives and Key Results (OKR) framework is frequently used to align engineering teams with business goals by separating aspirational goals (Objectives) from measurable, concrete outcomes (Key Results). - For presenting engineering projects to non-technical leaders, a proven five-part structure includes: defining the business problem, presenting a key insight and recommendation, outlining the technical solution, quantifying the business impact, and stating the required next steps.