The Book
The Engineering Protocol Stack — A Layered Model for Engineering Leadership
What it’s about
We don’t have a processor in our head, but thinking of our brain and our teams as a layered system helps make visible a part of the job that’s rarely taught explicitly: managing attention, memory, teams, and organizations.
The Engineering Protocol Stack organizes engineering leadership into four layers, from the inside out:
- CPU — how you manage your own focus, tasks, and priorities.
- RAM — how you use your working memory and learn new things without overload.
- LAN — how you go from a group of people to an actual team.
- WAN — how your team connects to stakeholders, other teams, and the rest of the organization.
You don’t need to read the chapters in strict sequence — each one stands on its own — but reading them in this order shows why the layers depend on each other, and why fixing a problem at the wrong layer rarely works.
Table of contents
Introduction
- The Engineering Protocol Stack
- How this book is organized
- About the author
CPU
- Task Manager (multitasking, task execution, and prioritizing)
- RAM, Your Memory (how memory works, its enemies, the method of loci)
- Process Organization (organization systems, journaling, planning and review)
LAN
- Identifying Team Status
- Team Roles
- Career Path (defining it, leveling people)
- People (onboarding, communication)
- Team Management (the five dysfunctions, Team Topologies, 1-on-1s, hiring, team health checks)
WAN
- Stakeholder Map & Expectations
- Cross-Team Collaboration & Dependencies
- Customers & Users: Bringing the Outside In
- External Partners, Vendors & Platforms
- Upward Management, Org Change & Protecting the Team
Who this book is for
- Engineers making the jump to leading people for the first time.
- Tech leads and engineering managers who want a clear structure for the “soft” parts of the role.
- Heads of Engineering and directors who need to scale teams without losing culture.
- Any technical professional who wants to treat leadership skills with the same rigor as their code.
About the author
Written by Guillem Fernandez, Engineering Director and People Engineer with more than twenty-five years of experience across nearly every seat at the table: from developer to Head of Engineering, founder of two companies, and lecturer at the University of Barcelona. Read the full bio →