Reference and Selective Reading
This module is less "book" reference and more "essay / blog" reference. Most canonical material for Staff+ engineering and engineering strategy lives in essays, not book chunks.
Use the concept pages first. Open these sources only when you need alternate exposition or more worked examples, and then read one source for one gap - not a reading list.
Source Roles
| Source | Role | Why it is here |
|---|---|---|
| Staff Engineer (Will Larson, free essays at staffeng.com) | Primary teaching source | Canonical archetypes, role shape, influence mechanics |
| Good Strategy/Bad Strategy (Rumelt) | Primary teaching source | Diagnosis / guiding policy / coherent action kernel |
| High Output Management (Grove) | Primary teaching source | Leverage mathematics and managerial output |
| The Manager's Path (Fournier) | Selective support | Managing up and 1:1 mechanics from the IC side |
| lethain.com | External essays | Sharpest short-form engineering-strategy essays |
| charity.wtf | External essays | Engineer/manager pendulum and career shape |
| larahogan.me | External essays | Influence without authority, stakeholder work |
| CCL | External reference | SBI feedback model; canonical source |
| Fundamentals of Software Architecture Part 5 (local chunks) | Light support | Architect-specific soft skills |
Read Only If Stuck
Cluster 1: The Staff+ Engineer's Work
- Staff archetypes - staffeng.com -- the canonical four archetypes, directly from Larson.
- Staff engineer archetypes - lethain.com -- the blog version with worked examples.
- What do Staff engineers actually do? - lethain.com -- the four-bucket view of the work.
- Fundamentals: Balancing architecture and hands-on coding -- altitude balance for architects.
- Fundamentals: Leveraging checklists -- one concrete force multiplier.
- Fundamentals: Leading teams by example -- non-heroic leverage patterns.
Cluster 2: Engineering Strategy
- Introduction for Engineering Strategy - lethain.com -- Rumelt's kernel adapted to engineering.
- Diagnosis in engineering strategy - lethain.com -- diagnosis step specifically.
- Setting policy for strategy - lethain.com -- guiding-policy step.
- Writing an engineering strategy - lethain.com -- full template with altitude check.
- Making engineering strategies more readable - lethain.com -- explore/diagnose/refine/policy/operation structure.
- When to write strategy, and how much? - lethain.com -- when the doc is worth writing.
- Why I Invented the Now-Next-Later Roadmap - ProdPad -- canonical roadmap source.
Cluster 3: Influence Without Authority
- The Anatomy of an Amazon 6-pager -- canonical long-form memo pattern.
- Intentional influence - LeadDev -- stakeholder-mapping exercise for engineers.
- Lara Hogan: Why can't they just...? -- curiosity-first stakeholder framing.
- Fundamentals: Architecture decision records -- decision-bearing artifact form.
- Fundamentals: Negotiation and facilitation -- architect-specific negotiation.
- Fundamentals: Negotiating with other architects -- peer-disagreement tactics.
- Fundamentals: Integrating with the development team -- alignment between architects and engineering.
- Disagree and commit - Wikipedia -- clean reference definition.
- The Hard Thing About Disagree and Commit -- trust-cost failure modes.
Cluster 4: Technical Communication
- Fundamentals: Diagramming and presenting architecture -- adapting presentation to audience.
- Fundamentals: Diagram guidelines -- diagram clarity per audience.
- Fundamentals: Case study - Going, Going, Gone -- worked design narrative.
- System Design Primer - Real-world architectures -- short production-architecture narratives.
- System Design Primer - System design interview questions -- the narrative arc under time pressure.
- The Ultimate Guide to Amazon's 6-Pager Memo Method -- annotated examples.
Cluster 5: Growing Others and Yourself
- Finding your Staff sponsor - lethain.com -- sponsorship mechanics from the receiving side.
- Fundamentals: Making teams effective -- distributed capability.
- Fundamentals: Developing a career path -- senior-IC trajectory.
- CCL - SBI Feedback Model -- canonical source.
- CCL - Use SBI to Inquire About Intent -- four-step SBI-I variant.
- charity.wtf - The Engineer/Manager Pendulum -- pendulum essay.
- charity.wtf - Twin Anxieties of the Engineer/Manager Pendulum -- worked framing for ambivalence.
- Schein's Career Anchors Inventory (PDF) -- 40-question self-assessment.
Optional Deep Dive
- Staff Engineer (Larson): the full book, for engineers considering a Staff+ track in depth. Free essay collection at staffeng.com/book.
- Good Strategy/Bad Strategy (Rumelt): Chapters 1-4 are essential; Chapters 5+ are case studies that reinforce the kernel.
- High Output Management (Grove): Chapter 3 (managerial leverage) is the load-bearing chapter; the rest is context.
- The Manager's Path (Fournier): Chapters on Tech Lead and Principal specifically; the manager track is not required here.
- lethain.com - Managing Staff-plus engineers -- what good management of Staff+ engineers looks like, useful mirror for self-understanding.
- lethain.com - Engineering management's foundational skills -- reference index across Larson's leadership essays.
Concept-to-Source Map
| Concept page | Best source if stuck | Why this source |
|---|---|---|
| Four Staff-Engineer Archetypes | staffeng.com/guides/staff-archetypes/ | Canonical source; short and definitive |
| Working at the Right Altitude | Fundamentals: Balancing architecture and hands-on coding | Concrete altitude-allocation guidance |
| Leverage: Where an IC's Time Multiplies | Fundamentals: Leveraging checklists | One force-multiplier pattern end-to-end |
| Diagnosis, Guiding Policy, Coherent Action | lethain.com - Diagnosis in engineering strategy | Sharpest diagnosis-step essay |
| Engineering Strategy Documents | lethain.com - Writing an engineering strategy | Full template with altitude check |
| Roadmaps: Now/Next/Later | ProdPad - Why I Invented the Now-Next-Later Roadmap | Canonical source |
| Written-First Culture | The Anatomy of an Amazon 6-pager | Canonical long-form memo pattern |
| Stakeholder Mapping and Alignment | Fundamentals: Negotiation and facilitation | Architect-specific negotiation patterns |
| Disagree-and-Commit, Managing Up | Management for Startups - The Hard Thing About Disagree and Commit | Trust-cost failure modes |
| Audience-Aware Explanation | Fundamentals: Diagramming and presenting architecture | Audience adaptation for presentations |
| Writing an Executive Summary | The Anatomy of an Amazon 6-pager | BLUF in the first paragraph |
| Architectural Storytelling | Fundamentals: Case study - Going, Going, Gone | Worked design-narrative example |
| Mentorship, Sponsorship, Bench | lethain.com - Finding your Staff sponsor | Sponsorship mechanics |
| Feedback and SBI | CCL - SBI Feedback Model | Canonical source |
| Personal Strategy | charity.wtf - The Engineer/Manager Pendulum | Pendulum essay anchoring career-anchor conversations |