The Manager's Path

What the book is

The Manager's Path: A Guide for Tech Leaders Navigating Growth and Change was published by O'Reilly in 2017. Camille Fournier wrote it from experience as an engineer, manager and CTO. It has become one of the most recommended books for anyone moving into technical leadership.

How it is structured

The book follows the career ladder, one level per chapter:

• Management 101: what you should expect from your own manager.
• Mentoring: your first taste of responsibility for someone else.
• Tech lead: leading the technical work of a team while still coding.
• Managing people: one-to-ones, feedback, performance and career growth.
• Managing a team: staying technical, handling conflict, and shielding the team versus informing it.
• Managing multiple teams: delegation, prioritisation and staying close to the technology.
• Managing managers: hiring and developing managers and holding them accountable.
• The big leagues: senior leadership, strategy and working with the executive team.
• Bootstrapping culture: creating healthy engineering culture and processes.

Each chapter describes the job from the inside, what changes from the previous level, and the mistakes characteristic of it.

Why the structure works

Management advice is usually pitched at an unspecified audience, which makes much of it irrelevant to any particular reader. Organising by level means you read the chapter for the job you have and the one you are considering, and get a realistic preview of both.

The chapter most people need

Tech lead. It is the least well-defined role in engineering, frequently handed to people with no explanation, and this chapter is one of the clearest descriptions of it. It covers balancing coding with coordination, project management basics and communicating with stakeholders.

Is it worth it before you manage anyone?

Yes. The first chapters explain how to get the most from your own manager and mentors, which helps any engineer. Reading the tech lead and managing people chapters early helps you decide whether management appeals to you, before you are asked.

How to read it

• Read chapters 1 to 3 early in your career.
• Read the next level's chapter when a promotion or role change is near.
• Keep it on your desk as a reference when facing a specific situation, such as a difficult performance conversation or taking over a struggling team.
• Discuss chapters with a mentor or peers who are one step ahead.

Where it falls short

It reflects US technology company norms, especially fast-growing startups. Some advice needs adapting for smaller companies, service firms or different cultures. Remote and distributed teams receive less attention than they would in a book written today.

Common questions

Is it only for managers? No. It is equally useful for engineers deciding between the management and senior individual contributor tracks.

Is it technical? Not in a coding sense; it is about people, teams and organisations in technical contexts.

Best for: engineers considering management, new managers, and anyone who has just been made a tech lead and told to get on with it.