Skip to content
    AppendicesChapter 139

    The Engineering Executive's Primer

    A practical reading of Will Larson's guidance for engineering executives: the first ninety days, strategy, planning, values, metrics, mergers and acquisitions, leadership styles, and personal energy.

    Book summaryworking15 minevergreen · reviewed Aug 12, 2026
    Chapter outline

    The Engineering Executive's Primer

    Authors: Will Larson
    Publisher: lethain.com
    Length:

    Primary source: the work itself

    A practical reading of Will Larson's guidance for engineering executives: the first ninety days, strategy, planning, values, metrics, mergers and acquisitions, leadership styles, and personal energy.

    The Engineering Executive's Primer — original coverOriginal

    Brief

    The essential idea

    Will Larson frames engineering-executive work as a discipline of context, priorities, and organizational dynamics rather than a series of heroic decisions. Entering the role requires evaluating why to take it, navigating internal or external transitions, understanding a sometimes chaotic hiring process, and assessing the actual mandate behind an offer.

    The first ninety days should emphasize diagnosis of the business model, culture, stakeholders, delivery, platform quality, incidents, and team health while limiting premature change. Strategy then provides explicit choices and exclusions, and planning connects financial cycles, quarterly or half-year horizons, team delivery, and regular business reviews.

    Useful values must be reversible, applicable, and honest enough to guide real trade-offs. Metrics should support decisions rather than replace trust, and M&A work needs engineering due diligence across integration complexity, security, scale, cost, and culture. Leaders switch deliberately among policy, consensus, and conviction while managing their own energy for long-term effectiveness.

    Decision lens

    Key takeaways

    The first ninety days are for learning the system and earning trust before broad intervention.

    Engineering strategy is a set of choices, constraints, and explicit refusals connected to business goals.

    Planning must link financial, strategic, delivery, and review horizons.

    Organizational values are useful only when they resolve real trade-offs and affect operating mechanisms.

    Metrics should be introduced gradually and tied to decisions, not used to compensate for missing trust.

    Engineering leaders need a consistent due-diligence frame for mergers and acquisitions.

    Policy, consensus, and conviction are context-dependent leadership modes rather than fixed personalities.

    Personal energy is a strategic resource, not an afterthought to company and team priorities.

    Workplace experiment

    Apply it at work

    1. 1

      Build a first-ninety-days diagnostic covering business, delivery, quality, incidents, stakeholders, and team health.

    2. 2

      Add explicit non-goals to the next engineering strategy cycle.

    3. 3

      Introduce no metric without naming the decision it supports and the misuse it might invite.

    4. 4

      Translate one stated value into hiring, onboarding, performance, or promotion behavior.

    5. 5

      Choose policy, consensus, or conviction deliberately for an upcoming consequential decision and explain why.

    Choose one action, define the observable effect, and keep the first test small enough to reverse.

    Evidence

    Sources and further reading

    Previous chapterThe Laws of SimplicityNext chapterHypothesis Map