Insight: Great EMs Build Systems, Not Answers
A trending leadership take suggests that scaling engineering leadership isn't about having all the answers. Instead, it's about creating systems where answers emerge from the team autonomously, allowing leaders to scale themselves by empowering others.
A core framework for executive updates is the brief, quantitative summary: start with a feeling ("I'm worried about...") and immediately ground it in a number ("...we are two weeks behind schedule"). This structure respects executive time by delivering the most critical information—the project's status against its goals—upfront and without jargon. When presenting to senior leadership, structure the narrative around a solution, not just a problem. A recommended 5-part story structure includes: the Problem your audience resonates with, your unique Insight or Recommendation, the engineering Solution, its business Impact with tangible evidence, and the specific Next Steps you need from them. This flips the script from a technical report to a business case. For high-stakes decisions, Amazon's "one-way vs. two-way door" model provides a system for scaling judgment. Decisions that are hard to reverse (one-way doors, like a platform choice) require deep review and slower, more deliberate processes. Reversible decisions (two-way doors, like internal tooling) should be made quickly by the team, empowering autonomy and speed. A director's time allocation can be modeled by the 70/20/10 framework: 70% of time should be spent enabling others through coaching and unblocking, 20% on strategic work like roadmaps and architecture, and only 10% on hands-on technical work for the most critical paths. This system forces a shift from individual contribution to scaling the organization. Executive project status reports should be standardized to a single page or five slides maximum. The format should consistently include an overall status (On Track, At Risk, Off Track), key accomplishments in the reporting period, a summary of risks that require executive action, and a clear outline of upcoming milestones. To connect engineering initiatives to business outcomes, leaders can use the Objectives and Key Results (OKR) framework. This system separates aspirational goals (Objectives) from measurable outcomes (Key Results), ensuring that every technical investment and architectural decision is explicitly tied to the company's broader strategic goals. For running leadership reviews and navigating technical debates, the "Disagree and Commit" principle is a key cultural system. It encourages vigorous debate and dissent based on data during the decision-making process. However, once a decision is made, the leader's role is to enforce full alignment and commitment from the entire team, eliminating re-litigation.
