Introduction
- The Engineering Protocol Stack
- How this book is organized
- About the author
CPU
- Task manager
- RAM
- Process organization
- Loading new content
- Storage
Task Manager
- Multitasking
- Task Execution
- Task Prioritizing
- Key Ideas
RAM, Your Memory
- How Our Memory Works
- Your Memory Enemies
- Enjoy the process
- Select What to Add
- Method of Loci
- Key ideas
Process Organization
- A Gold Mine
- Before You Start Organizing Your Time
- Different Organization Systems
- Why analog
- Start your journal
- Planning and Review
- Key ideas
Loading New Content
- How Learning Works
- Choosing What to Learn
- Key ideas
Personal Knowledge Management
- Why capture beats memory
- The three kinds of notes
- Capture without friction
- Linking over filing
- Retrieval: the practice of review
- Applying it as an engineering leader
- Key ideas
LAN
- Identifying Team Status
- Team Roles
- Career Path
- People
- Team Management
Identifying Team Status
- Why labels matter in engineering teams
- What’s unique about software/tech teams
- The three lenses, in practice
- Building a simple status snapshot
- When to revisit the snapshot
- Common mistakes when reading team status
- Key ideas
Team roles
- Roles and Personality Traits in Engineering
- Skills and roles in cross-functional software teams
- Key ideas
Career Path
- What is a Career Path
- Main risks
- Effect on new joiners
- Why fast growth makes it worse
- Defining a Career Path
- Leveling your team members
- Recap
- Key Ideas
Onboarding
- Key ideas
Communication
- Key ideas
Team Management
- The five dysfunctions
- Team Topologies & Structure
- 1-on-1s & Feedback Loops
- Hiring & Onboarding
- Team Health Checks
- Key ideas
WAN
- Stakeholder Map & Expectations (inside + outside)
- Cross-Team Collaboration & Dependencies
- Customers & Users: Bringing the Outside In
- External Partners, Vendors & Platforms
- Upward Management, Org Change & Protecting the Team
Stakeholder Map & Expectations (inside + outside)
- Who Are Your Stakeholders, Really?
- Inside vs Outside: Two Types of Stakeholders
- Mapping Your Stakeholders: A Practical Approach
- Understanding and Managing Expectations
- Communication Patterns: Routing the Right Signal to the Right Node
- When Expectations Break: Recovering Stakeholder Trust
- Key ideas
Cross-Team Collaboration & Dependencies
- Why Cross-Team Work Gets Hard Fast
- Types of Dependencies: Technical, Process, Decision
- Mapping Dependencies: A Practical Approach
- Ownership, Handoffs, and Shared Timelines
- Communication Patterns: Routing the Right Signal Across Teams
- When Dependencies Slip: Recovering Without Drama
- Key ideas
Customers & Users - Bringing the Outside In
- Who Are Your Real Customers and Users?
- Practical Ways to Collect Ongoing Feedback
- Turning Raw Feedback into Actionable Narratives
- Keeping Customer Stories Visible Day to Day
- Balancing What Users Ask For with What Makes Sense
- Building an Outside-In Habit in the Team
- Key ideas
External Partners, Vendors & Platforms
- Identifying Critical Dependencies
- Evaluating Beyond Features
- Working Agreements
- Keeping Integrations Healthy
- When Partners Fail
- Operating Model
- Key ideas
Upward Management, Org Change & Protecting the Team
- Representing the Team Upwards
- Negotiating Priorities
- Making Change Digestible
- Protecting the Team
- Communication With Leadership
- Managing Your Own WAN Load
- Key ideas
Recap
- What each layer gave you
- The protocols, not the motivation
- Where to go from here