This book is written for Project Managers within software delivery organizations. The stakeholder dynamics you face, both at the client and within your own organization, are complex because they sit within a commercial relationship where interests don't always align.

Whether your company operates as SaaS or another model matters less than the nature of your projects. The dynamics described here are most relevant for high-touch, change-heavy initiatives. Projects that require deep commitment from both your client and your organization. Significant complexity, significant stakes.

These days there are many titles for this role on the vendor side. Program Manager, Project Manager, Delivery Manager, Implementation Lead. The title doesn't matter. If you are responsible for delivering software solutions to corporate clients, or managing people who do, this book is for you.

If you operate as a Project Manager on the client side, the principles still apply. However, the complexity is different. Buying power sits with you, and many vendor-related stakeholder issues can be resolved by applying it.

No hard rule. But broader experience helps you recognize that formal project education alone doesn't create project success. Real projects mean dealing with individuals who have different backgrounds, maturity levels, mandates, and incentives. With more experience, you're more likely to have reached the point where you think "there must be more out there than this." That said, if you're open-minded and realize that going from good to great as a PM means developing people skills, you will benefit from this book.

Yes and no. This book doesn't offer a fixed set of techniques to magically resolve all stakeholder issues. But if you're reading this, that's probably not what you're after anyway. Applying techniques and templatizing stakeholder interactions is a fast way to lose credibility.

What the book does address is what you can bring to a project reality: emotional clarity, mental clarity, care, and appropriate relationships. These are underlying skills that allow you to become more deliberate and successful in how you manage a stakeholder landscape and build influence. Not as a technique or tactic, but as a skill that others perceive as genuine.

No. If that's what you're after, this book won't help. I believe templates and scripts work counterproductively. They amplify stakeholder issues rather than solve them. This is not a quick-fix problem area.

No. Project management methodology is a different dimension. Stakeholders exist regardless of which methodology you apply. Each methodology does bring its own opportunities and challenges in dealing with them. For instance, there are few cross-organizational trust-building mechanisms as effective as delivery. Delivering often and early, following Agile principles, supports that. On the other hand, more traditional methodologies tend to be more elaborate on governance. Most important, and briefly addressed in the book: aligning and integrating customer and vendor delivery methodologies is essential for efficient delivery. Often more important than the actual methodology you operate under.

Around 130 pages. I don't hold back on my views about what matters in managing stakeholders. I intentionally share everything I have to offer in this area. Why is it free? Because I choose to collaborate on the application of this material, while making the material itself available to anyone interested.

Yes. The book provides skills and insights you can directly translate into how you approach specific situations. However, it's not a prescriptive playbook to magically resolve your problems. This material requires your interpretation and integration to make it valuable in your project situation.

Don’t they all? Politics has a negative ring to it, but the reality of software-driven improvement projects is that opposing interests are always present. That's not always a bad thing, and it's certainly logical. The goal is not to eliminate this. The goal is to recognize it and address it in a non-offensive way that benefits the project. This book provides the skills to do that.

Yes. It provides insights on how to deal with this. Not just "create a scope description and apply change control." That's a mechanical solution for a people problem. It may create some clarity but won't resolve the issue. This book helps you develop the skill to address this with the client, uncover why it's happening, and define a joint approach that either allows for change or reduces its impact on timeline, budget, and quality.

Yes. It will help you not be the bad guy. You'll be the clarity guy. The book gives you insights to share that clarity in a constructive manner. Others may not like it, but they will respect and understand it. And let me say it out loud: scope creep is not an issue. Having a project that operates with a lack of clarity about scope creep, specifically around what the impact is and who owns that impact, that is the issue.

Yes. They are key stakeholders in the SaaS vendor reality. Learning skills how to work with them successfully is a core part of the book.

Yes. They are key stakeholders in the SaaS vendor reality. Learning skills how to work with them successfully is a core part of the book.

That's up to you to decide. But PMI calls them power skills rather than soft skills for a reason. They recognize that interpersonal skills make the difference between a capable Project Manager and one that creates project success in real life. If you ask me, it's as practical as it gets. And it's not limited to your Project Management context. These skills are valuable further in your career and in your personal life. I've never made a bigger positive jump in my professional career than as a result of developing these skills.