Module 5: Technical Leadership & Strategy

Primary texts: Staff Engineer (Will Larson), The Manager's Path (Camille Fournier), High Output Management (Andrew Grove), Good Strategy/Bad Strategy (Richard Rumelt) Selective support: Fundamentals of Software Architecture Part 5 (leadership, negotiation, effective teams) for the architect-as-leader chapters

This guide is the primary teacher. You do not need to read the source books front-to-back to complete this module. Because leadership is mostly rehearsal, you will spend more time writing and speaking artifacts than reading.

Scope of This Module

This module is where you stop being only an implementer. You start operating across teams, writing strategy that other people use to make decisions, and influencing outcomes you do not control.

What it covers in depth:

the four Staff+ archetypes (tech lead, architect, solver, right-hand) and when each one is the job
working at the right altitude: code vs systems vs strategy, and when to change levels
leverage: where an IC's time multiplies, and what "high-leverage" actually looks like in a week
Rumelt's structure: diagnosis, guiding policy, coherent action, and why slogans are not strategy
engineering strategy documents: scope, anti-scope, tradeoffs, applicability
roadmaps at now/next/later with capacity honesty instead of wish-list theater
written-first culture: memos, design docs, RFCs, and the difference between broadcasting and aligning
stakeholder mapping: who must be informed, who must agree, who can veto
disagree-and-commit, managing up, and how to escalate without burning trust
audience-aware explanation: exec, peer, junior, customer
executive summaries that survive editing
architectural storytelling: the narrative arc of a design
mentorship vs sponsorship vs building a bench
giving and receiving feedback with the SBI (Situation-Behavior-Impact) model
personal strategy: career anchors, sustainable pace, visibility without self-promotion theater

What it deliberately does not try to finish here:

people management mechanics (hiring, firing, comp) beyond what ICs must know to partner with managers
organizational design at the VP+ altitude
executive politics for Director / VP roles
general soft-skills self-help; this module is about observable artifacts and rehearsed moves

This module sits last in Semester 8 because it governs how every earlier design, decision, and review ends up landing in an organization.

Before You Start

Answer these closed-book before starting the main path:

Name one engineering decision you have seen that was technically correct and organizationally disastrous. What was missing?
What is the difference between a manager and a Staff engineer? Where do their jobs overlap?
Rumelt defines a strategy as three things. What are they? What is a strategy missing if only the third is present?
Give one concrete example of "influence without authority." Who did the work, and why did it land?
Why is it a warning sign when every consequence in a design doc is positive?

Diagnostic Interpretation

4-5 solid answers

You have lived some of this material and can start on the concept sequence directly.

2-3 solid answers

Continue, but expect extra time in Cluster 2 (strategy) and Cluster 3 (influence). These are usually the weakest areas for strong ICs.

0-1 solid answers

This module will feel like a different language for the first week. That is normal. Plan for double the practice time in Clusters 3-5, and treat the practice labs as the real deliverable.

What This Module Is For

Most senior engineers are technically competent and organizationally invisible. The outcomes they cause are smaller than the outcomes they deserve, because the glue work of strategy, communication, and influence is missing.

This module builds the habits that turn technical competence into organizational outcomes:

writing a strategy document that directs other people's work
running a stakeholder conversation where the answer is not predetermined
giving feedback that the receiver can act on without defending
sponsoring an engineer into a role they did not know they could get
writing an executive summary that a tired VP reads once and makes the right decision on

By the end, you should be able to look at an ambiguous multi-team problem and produce (1) a diagnosis, (2) a guiding policy, (3) a set of coherent actions, and (4) a written artifact that an exec, a peer, and a junior all understand from their own angle.

Concept Map

How To Use This Module

Work in order. Clusters 1-2 set the frame for what Staff+ engineers do and why strategy matters. Clusters 3-4 build the communication and influence machinery. Cluster 5 keeps the work sustainable.

Cluster 1: The Staff+ Engineer's Work

Order	Concept	Type	Focus
1	Four Staff-Engineer Archetypes	PRIMARY	Tech Lead, Architect, Solver, Right-Hand - and when each one is the job
2	Working at the Right Altitude	PRIMARY	Code vs systems vs strategy; changing levels deliberately
3	Leverage: Where an IC's Time Multiplies	PRIMARY	High-leverage moves vs heroism; a week audited by leverage

Cluster mastery check: Can you name which archetype you are operating as this quarter, which altitude your calendar matches, and one move you should drop because its leverage is low?

Cluster 2: Engineering Strategy

Order	Concept	Type	Focus
4	Diagnosis, Guiding Policy, Coherent Action (Rumelt)	PRIMARY	Rumelt's three-part kernel and why most "strategy" is actually a wish list
5	Engineering Strategy Documents: Scope, Anti-Scope, Tradeoffs	PRIMARY	What belongs in a strategy doc and what explicitly does not
6	Roadmaps: Now/Next/Later, Capacity vs Wish-List	PRIMARY	Time-horizon roadmaps and honest capacity accounting

Cluster mastery check: Given a messy cross-team problem, can you produce a one-page strategy with a named diagnosis, two or three guiding policies, and at least three coherent actions that are on the roadmap and not on the wish list?

Cluster 3: Influence Without Authority

Order	Concept	Type	Focus
7	Written-First Culture: Memos, Design Docs, RFCs	PRIMARY	Writing to align, not to broadcast; the comment-first loop
8	Stakeholder Mapping and Alignment	PRIMARY	Who approves, who is consulted, who is informed; the alignment walk
9	Disagree-and-Commit, Managing Up	PRIMARY	Escalating without burning trust; the commit after the disagreement

Cluster mastery check: Can you take a decision you disagree with, name the stakeholders you talked to, state the strongest version of the other side's argument, and then commit to executing without sabotage?

Cluster 4: Technical Communication

Order	Concept	Type	Focus
10	Audience-Aware Explanation	PRIMARY	Exec, peer, junior, customer: four audiences, four explanations
11	Writing an Executive Summary That Survives Editing	PRIMARY	BLUF, the 3-sentence test, and surviving the VP markup
12	Architectural Storytelling: The Narrative Arc of a Design	SUPPORTING	Problem, constraint, option, choice, consequence, open questions

Cluster mastery check: Can you take the same design and present it to (a) a VP in three sentences, (b) a peer architect in ten minutes, and (c) a new hire in an onboarding doc, without repeating yourself?

Cluster 5: Growing Others and Yourself

Order	Concept	Type	Focus
13	Mentorship, Sponsorship, and Building a Bench	PRIMARY	Mentor vs sponsor; creating the next Staff engineer, not being the only one
14	Feedback: Giving, Receiving, and the SBI Model	PRIMARY	Situation-Behavior-Impact; feedback as a practiced move
15	Personal Strategy: Career Anchors, Sustainable Pace, Visibility	SUPPORTING	What you want, how long you can sustain it, and how the right people learn you did it

Cluster mastery check: Can you name the engineer you are sponsoring (with a specific opportunity), the last time you received feedback without defending, and the next 18 months of your own career strategy in three sentences?

Then work these practice pages:

Order	Practice path	Focus
1	Strategy Memo Lab	Produce a real 2-page engineering strategy using Rumelt's structure
2	Design Review Workshop	Play reviewer and reviewee on the same design
3	Stakeholder Influence Clinic	Disagree-and-commit simulations; stakeholder map exercises
4	Leadership Katas	Outage exec summary, SBI feedback on a code review, roadmap tradeoff memo, 3-minute architectural story

Use Module Quiz after the concept and practice path. Use Reference and Selective Reading and Learning Resources only for targeted reinforcement.

Learning Objectives

By the end of this module you should be able to:

Identify your current Staff+ archetype and name the altitude your week is actually operating at.
Audit a week of calendar and Slack for leverage, and drop or delegate at least one low-leverage recurring commitment.
Write a one-page engineering strategy with a named diagnosis, two-or-three guiding policies, and coherent action.
Convert a strategy into a now/next/later roadmap with explicit capacity accounting.
Draft a design doc that survives async comment-based review and ends with a written decision, not a meeting.
Produce a stakeholder map for a cross-team initiative with RACI-style roles.
Disagree with a decision in writing, commit to executing it, and do both without sabotage.
Explain the same technical choice to an executive, a peer, a junior, and a customer, each in the form that audience actually reads.
Give SBI feedback on a real code review or decision, and receive feedback without collapsing into defense.
Name at least one engineer you are sponsoring (not mentoring) and the specific opportunity you are creating for them.

Outputs

one 2-page engineering strategy memo, Rumelt-structured, for a real or plausible problem
one design doc that received at least five written comments and ended with a decision section
one stakeholder map with RACI roles for a cross-team initiative
one written disagree-and-commit memo, with the strongest version of the other side's argument stated first
one executive summary of a real incident or decision, with a before/after rewrite
one architectural story (spoken aloud, 3 minutes) with a named problem-constraint-choice-consequence arc
one feedback log: three pieces of SBI feedback given, three received, each with the specific behavior and impact named
one personal strategy page: career anchor, 18-month goal, visibility plan, sustainable-pace rules
one mistake journal naming at least 10 specific leadership errors (e.g., "shipped without stakeholder alignment," "gave feedback about identity instead of behavior," "wrote a strategy that was just a wish list")

Completion Standard

You have completed Module 5 when all of these are true:

you can produce a Rumelt-structured strategy memo in under 2 hours from a problem statement
you can run a design review where the written decision is captured in the doc, not re-discussed next meeting
you have at least one engineer you have sponsored (not just mentored) into a concrete opportunity in the last 90 days
you can give SBI feedback with specific behavior and specific impact, without identity language
you can name the strongest version of an argument you disagree with before stating your own side
you know what altitude your calendar is actually operating at this week, and whether that matches the altitude the role requires

If you have opinions about strategy but have not written one, the module is not complete.

Reading Policy

Concept pages are the main path.
Book chunks are selective reinforcement. For Staff Engineer and High Output Management we do not have local chunks; validated external URLs stand in.
Read only if stuck means try the concept page, write the drill, and run the practice first.
See also (external) means the best external pointer when no local chunk exists; do not let it become the default reading.
Because this module is about producing artifacts, you should write more than you read. Each concept page ends with an artifact or rehearsed move you produce yourself.

Suggested Weekly Flow

Day	Work
1	Concepts 1-3, audit one week of your own calendar for altitude and leverage
2	Concepts 4-6, start the Strategy Memo Lab
3	Finish Strategy Memo Lab; Concepts 7-8
4	Concept 9; Stakeholder Influence Clinic
5	Concepts 10-12; start Leadership Katas (exec summary, architectural story)
6	Design Review Workshop
7	Concepts 13-15; finish Leadership Katas (SBI feedback, roadmap memo); quiz

Reference

If you need exact links into the local chunked books or validated external essays, use Reference and Selective Reading.

Rich Learning Pages

Scope of This Module​

Before You Start​

Diagnostic Interpretation​

What This Module Is For​

Concept Map​

How To Use This Module​

Cluster 1: The Staff+ Engineer's Work​

Cluster 2: Engineering Strategy​

Cluster 3: Influence Without Authority​

Cluster 4: Technical Communication​

Cluster 5: Growing Others and Yourself​

Learning Objectives​

Outputs​

Completion Standard​

Reading Policy​

Suggested Weekly Flow​

Reference​

Rich Learning Pages​