The Technical Program Manager's Guide: Navigating the Path to Success

Welcome to the Fourth Edition of the Technical Program Manager’s Guide to Success.

Writing this edition feels like coming full circle. When I published the first edition, the TPM role was still new and undefined in many organisations. Readers told me how the book gave them clarity, helped them prepare for interviews, and built their confidence as they stepped into the role. That feedback has driven every update since.

The world has changed, and so has the craft. Technical Program Management today still means tracking projects and applying frameworks, but the harder work is leading through ambiguity, building trust across very different teams, and connecting technology, product and strategy. The TPM of today is as much a strategist and leader as a program driver.

This Fourth Edition is written with that reality in mind, and it is organised differently from the ones before it.

• It is built on four pillars. Parts Three to Six follow the four courses I teach: Product Sense, System Design, Strategic Thinking and Execution Excellence. Each part takes one pillar from first principles to advanced practice.
• It uses one running case. Most chapters open with a short scenario from Larder, a fictional grocery-delivery company, and use its programs as the worked example throughout: an outage, a push for twenty-minute delivery, a monolith that cannot keep up, a festive-season launch and the incident nobody planned for. The company is invented; the situations are the ones every TPM meets. Each framework is run on Larder’s numbers, so you can see it working, and see where it stops working.
• It goes beyond one company. Part Seven, Field Cases, steps away from Larder to show three large cross-organisation programs in different worlds: building a streaming platform, running vulnerability management across a company, and making cloud cost everyone’s job.
• It gives you the artifacts. Part Nine, The Toolkit, follows one program from its first day to its closure and shows you the finished work at every step: the program brief, the strategy, the charter, the stakeholder map, the meeting cadence and agendas, WBRs and MBRs, risk registers, OKRs, roadmaps, Jira setups and automations, intake workflows, launch checklists and postmortems. Every sample comes with notes on why it is built the way it is.

You will still find what readers valued in earlier editions: guidance on applying and preparing for TPM roles, a complete bank of one hundred interview questions with answer outlines, a sample résumé, a 30-60-90 day plan, career ladders, and practical advice on growing from your first program to company-wide influence.

This book is for every stage of the profession:

• Developers and engineers exploring a move into program and product management.
• Program and product managers who want to step into the technical program side.
• TPMs preparing for interviews or new opportunities.
• Experienced TPMs sharpening their craft and widening their influence.

Don’t read it as a rigid manual. Use it as a companion: mark it up, come back to a chapter when a challenge arrives, and adapt the ideas to your own context. Technical Program Management is more than a job description. It is a craft, one that grows with reflection, practice and the drive to keep learning. My hope is that this edition does more than help you land the role. I hope it helps you lead with clarity, grow with purpose, and leave a lasting mark on the teams you work with.

Wishing you success and inspiration on the way.