About the Book

About the Case Studies

The case studies throughout this book are loosely based on tricky, real scenarios encountered over years of both teaching and mentoring people across the industry. Some of the situations reflected in these cases draw on challenges that mentees and colleagues have genuinely faced in their own organizations, reshaped here into stories that protect the people and companies involved while keeping the underlying dilemma intact.

The intent behind these case studies is to create a safe space where you can explore difficult, ambiguous situations without the stakes that come with facing them for real. In an actual workplace, a wrong call in a tense moment can cost trust, credibility, or even a job. In this classroom, it costs nothing but the discomfort of being wrong in front of your peers, which is exactly where that discomfort is most useful and least expensive.

You'll also notice that these case studies come without an answer key, and that omission is deliberate rather than an oversight. Project management and Agile leadership rarely offer a single correct answer that applies cleanly to every context. What works well in one organization, with one team, under one set of constraints, may not work at all somewhere else. The goal of each case study is for you to think it through carefully, talk it over with your classmates, and decide for yourself what a good solution might look like given your own style and the particular organizational context you're imagining. That process of reasoning and discussion is the actual skill this book is trying to build, far more than any single "right" answer ever could be.

Knowing Yourself, and Everyone Around You

Real success as a project manager, program manager, portfolio manager, or Agile practitioner was never just a matter of mastering frameworks, ceremonies, and terminology. Certifications can teach you the vocabulary of the discipline, but they can't teach you how to read a room, how to sense when a stakeholder's silence means agreement or fear, or how to notice your own frustration rising before it shapes a decision you'll later regret. That deeper capability comes from somewhere else entirely: from knowing yourself, knowing the people above you, knowing the people around you, and knowing the people below you.

This matters especially for program management, where the real work is converting strategy into reality. A program manager sits at the point where a boardroom's vision has to become something tangible that multiple teams, projects, and stakeholders can actually deliver, and that translation rarely happens through process alone. It takes a high level of emotional intelligence and a genuine willingness to keep evolving as a leader, since the gap between strategic intent and operational reality is almost always a human gap before it's a technical one. Reading the politics behind a strategic priority, sensing where a sponsor's confidence is thinner than it appears, and knowing when to push a project team versus when to shield them, all of this depends on emotional intelligence that no methodology can substitute for. Strategy is a sentence on a slide until a program manager turns it into work people actually do.

Managing up, managing across, and managing down are not separate skills to be checked off a list one at a time. They're woven together, and none of them means much in isolation from the others or from the self-awareness that has to sit underneath all three. A practitioner who can read every stakeholder in the room perfectly, but has never paused to examine their own reactions under pressure, will eventually be undone by that blind spot no matter how sharp their stakeholder management looks on the surface. And a practitioner who has done the deep, quiet work of understanding themselves, but has never learned to genuinely read the people they depend on, will find that self-knowledge alone doesn't move a team or win a stakeholder's trust. It's the combination, self and others, up and across and down, that actually holds under real pressure, and it's what ultimately allows strategy to survive the journey from a slide deck into something real.

If this book manages to accomplish only one thing beyond teaching its concepts, let it be this: that it nudges you toward becoming a more complete version of yourself, someone capable of holding all of these relationships at once with the judgment, humility, and hard-won self-awareness this work has always genuinely demanded.