Learning Resources
This module is practice-heavy and external-URL heavy. Most of the canonical material for Staff+ engineering and engineering strategy lives in essays and books that do not appear as local chunks in this repo. Use this page as the source map.
Source Stack
| Source | Role | How to use it in this module |
|---|---|---|
| Staff Engineer (Will Larson) | Primary teaching source | Archetypes, role scope, influence mechanics. Available free as essays on staffeng.com |
| Good Strategy/Bad Strategy (Richard Rumelt) | Primary teaching source | Diagnosis / guiding policy / coherent action. Read the first 4 chapters, skim the rest |
| The Manager's Path (Camille Fournier) | Selective support | Managing up, 1:1s, organizational dynamics from the IC side |
| High Output Management (Andrew Grove) | Selective support | Leverage math, task-relevant maturity, operational rhythm |
| Fundamentals of Software Architecture Part 5 | Local book chunks | Soft skills of architecture - negotiation, leadership, presenting |
| lethain.com (Will Larson's blog) | External essays | Engineering strategy, altitude, sponsorship - the sharpest short-form essays on this material |
| staffeng.com | External essays | Canonical archetypes and role-scope material; book essays available free |
Resource Map by Cluster
Cluster 1: The Staff+ Engineer's Work
| Need | Best source | Why |
|---|---|---|
| the four archetypes, canonical form | Staff archetypes - staffeng.com | Larson's own framing; short and definitive |
| worked examples of the archetypes | Staff engineer archetypes - lethain.com | Blog version with concrete examples and edge cases |
| what Staff engineers actually do | lethain.com - What do Staff engineers actually do? | Four-bucket framing for the work |
| altitude and balance between IC and architecture work | Fundamentals: Balancing architecture and hands-on coding | Local chunk; concrete altitude-allocation guidance |
| leverage and force multipliers | Fundamentals: Leveraging checklists | One force-multiplier pattern worked end-to-end |
Cluster 2: Engineering Strategy
| Need | Best source | Why |
|---|---|---|
| Rumelt's kernel in engineering context | lethain.com - Introduction for Engineering Strategy | Explicit adaptation of Rumelt's three-part kernel |
| diagnosis - the sharpest treatment | lethain.com - Diagnosis in engineering strategy | Best short essay on the diagnosis step specifically |
| guiding policy in practice | lethain.com - Setting policy for strategy | Policy step with engineering examples |
| strategy document shape | lethain.com - Writing an engineering strategy | Template + worked example + altitude check |
| readable strategy documents | lethain.com - Making engineering strategies more readable | Five-component structure for long-form docs |
| when to write strategy at all | lethain.com - When to write strategy, and how much? | Decision guide for whether the doc is worth it |
| now/next/later roadmaps | ProdPad - Why I Invented the Now-Next-Later Roadmap | Canonical source |
| converting Gantt to now/next/later | ProdPad - Convert a Timeline Roadmap to Now-Next-Later | Migration guide |
Cluster 3: Influence Without Authority
| Need | Best source | Why |
|---|---|---|
| written-first culture and memos | The Anatomy of an Amazon 6-pager | Canonical long-form memo pattern |
| 6-pager worked examples | Medium - The Ultimate Guide to Amazon's 6-Pager Memo Method | Annotated examples |
| stakeholder mapping and influence | LeadDev - Intentional influence (Lara Hogan) | Explicit stakeholder-mapping exercise |
| curiosity-first influence framing | Lara Hogan - Why can't they just...? | Influence without authority as curiosity-based |
| negotiation in architecture context | Fundamentals: Negotiation and facilitation | Local chunk; architect-specific negotiation patterns |
| negotiating with other architects | Fundamentals: Negotiating with other architects | Concrete peer-disagreement tactics |
| disagree-and-commit origin and definition | Wikipedia - Disagree and commit | Clean reference definition |
| disagree-and-commit failure modes | Management for Startups - The Hard Thing About Disagree and Commit | Trust-cost analysis |
Cluster 4: Technical Communication
| Need | Best source | Why |
|---|---|---|
| presenting architecture | Fundamentals: Diagramming and presenting architecture | Local chunk; adapting presentation to audience |
| diagram clarity | Fundamentals: Diagram guidelines | Concrete guidelines per audience |
| decision-bearing documents | Fundamentals: Architecture decision records | ADR form as a vehicle for written-first decisions |
| design case study | Fundamentals: Case study - Going, Going, Gone | Worked example of a design narrative |
| real-world architecture narratives | System Design Primer - Real-world architectures | Short production-architecture narratives |
| interview communication patterns | System Design Primer - System design interview questions | The narrative arc applied under time pressure |
Cluster 5: Growing Others and Yourself
| Need | Best source | Why |
|---|---|---|
| mentorship and sponsorship buckets | lethain.com - What do Staff engineers actually do? | Names mentorship + sponsorship as a load-bearing activity |
| finding and activating sponsors | lethain.com - Finding your Staff sponsor | Mechanics from the receiving side |
| leading by example, architect as leader | Fundamentals: Leading teams by example | Local chunk; non-heroic leadership patterns |
| what makes teams effective | Fundamentals: Making teams effective | Local chunk; distributed capability over single strong IC |
| SBI feedback - canonical source | CCL - SBI Feedback Model | Center for Creative Leadership's original material |
| SBI with intent-inquiry (SBI-I) | CCL - Use SBI to Inquire About Intent | The four-step variant with intent-asking |
| career anchors self-assessment | World of Work - Career Anchors Inventory (PDF) | 40-question Schein self-assessment |
| engineering career path | Fundamentals: Developing a career path | Local chunk; senior-IC trajectory and the 20-minute rule |
| engineer / manager pendulum | charity.wtf - The Engineer/Manager Pendulum | Sharpest essay on the manager/IC career choice |
| twin anxieties of the pendulum | charity.wtf - Twin Anxieties of the Engineer/Manager Pendulum | Worked framing for ambivalence |
| foundational engineering leadership skills | lethain.com - Engineering management's foundational skills | Reference index across Larson's essays |
Books (Deep Dive)
Read these in order of highest return on reading time:
- Staff Engineer (Larson) - or read the free essays at staffeng.com/book. Cluster 1 + Cluster 5 primary.
- Good Strategy/Bad Strategy (Rumelt) - first 4 chapters define the kernel; the rest are case studies. Cluster 2 primary.
- The Manager's Path (Fournier) - for the IC chapters (Tech Lead, Principal), not the full manager track. Cluster 3 support.
- High Output Management (Grove) - the leverage math in Chapter 3 alone is worth the purchase. Cluster 1 primary.
Use Rules
- If you are stuck on strategy structure, go to lethain.com first - Rumelt's book explains why the kernel is right; Larson's essays show how to write one in engineering.
- If you are stuck on archetypes or Staff+ role definition, go to staffeng.com.
- If you are stuck on influence, try writing the artifact before reading; the write-first loop usually surfaces the gap.
- If you are stuck on feedback mechanics, go straight to the CCL sources - they are short.
- Do not try to read everything on this page. Pick the 3-5 essays that match your weakest cluster and write the artifact.
Leadership decision extension
Complete the 18–26-hour integrated decision package and TL1–TL6 assessment. Reuse the original memo, two pre-reads, roadmap, delegation retrospective and ethical-impact record. Selective free readings: DORA metric context and Google SRE on toil. No extra book purchase is required.