Books / Inflicting Change
Inflicting Change
A Field Guide
By Walter Meyer · ThatWaltGuy
Get the book
The title is a wink. Nobody sets out to inflict anything. But anyone who has tried to change how a large organization works knows the feeling: the steering committee approved the deck, the vendor demo promised the moon, and the people who have to live with the result never asked for any of it. Change at that scale happens because a team shows up every day and makes it happen, sometimes over the objections of the people who asked for it. Approval is where it starts, not where it ends.
Inflicting Change is a field guide to that work: the people, the politics, and the delivery discipline it takes to get a stalled program moving again. Twenty-three short chapters, built from years of walking into projects that were on fire and figuring out what to do next. The chapters follow the arc most programs travel, from kickoff euphoria through the valley where projects go to die or be reborn, up the climb to delivery, and on to the quiet pride that arrives a few weeks after launch.
It is written for delivery leads, consultants, architects, and project managers who are in the weeds right now, and for the leaders who wanted the change and are wondering why their own organization is making it so hard. No methodology. No framework. No quadrant diagrams.
Book 1 of the Inflicting Change series. The author's second book, Agents Decide, Tools Do, Gates Prove, carries the same insistence on proof over promises into building agentic AI systems.
"Short chapters. Strong opinions. Built from years of walking into projects that were on fire and figuring out how to get things moving again."
Key takeaways
- 01 The technology is the easy part. Projects fail because of people, politics, and fear, and none of that comes with documentation.
- 02 Resistance rarely announces itself. It looks like a room that went quiet, decisions that get reopened, and the stakeholder who can never make the meeting. You cannot work with resistance you cannot see.
- 03 Every program travels the same arc: euphoria, reality, the valley, the climb, delivery, relief. Your client is living it for the first time, so hand them the map.
- 04 "Is this moving us toward our goal?" is the most useful question on a project. It is annoying until it saves the project.
- 05 Everything you write down is a promise. Tag scope as now versus later from day one, or the perception gap grows every sprint until someone closes it with a chainsaw.
- 06 "Can we?" is a technical question, and the answer is almost always yes. "Should we?" is the question that separates senior leaders from junior ones.
- 07 Have the tough conversation before lunch. Bad news does not age well, and every day of delay grows the blast radius.
Reader questions
Is this a change management methodology?
No. There are no frameworks, no certification programs, and no maturity models. It is a field guide: the things the author wishes someone had told him before his first project went sideways, in twenty-three short chapters that can be read in a sitting and returned to mid-project.
Who is it for?
Delivery leads, consultants, architects, and project managers who are on a hard project right now. Leaders who actually want the change and are wondering why their own organization is making it so difficult. And the executive who sponsored the thing and wants to see how the people delivering it see the world. "Client" means whoever you deliver for, including the internal business your own team serves.
Are the stories real?
The stories are true, but the names are not. Details have been changed, timelines shifted, and some of the people and projects are composites of the same mistake made in several places. Nothing draws on any client's or employer's confidential information. And the mistakes were not confined to one side of the table.
Do I need to read this before Agents Decide, Tools Do, Gates Prove?
No. The books stand alone. Inflicting Change is about delivering change through people and politics. Agents Decide, Tools Do, Gates Prove is about building agentic AI systems you can prove work. Both are written for people who have to stand behind a result.
About the author
Walter Meyer leads enterprise transformation programs and builds agentic systems. His career began in the U.S. Navy Nuclear Power Program, where "done" meant demonstrated, and has run through a startup he took to profitability and acquisition and senior roles at two creative digital consultancies. He is the author of Inflicting Change and Agents Decide, Tools Do, Gates Prove. More →
Also by Walter Meyer
Agents Decide, Tools Do, Gates ProveA Field Guide to Building Agentic Applications