In this article I reframe stakeholder management: most stakeholder problems are not bad outcomes to fix one at a time, but reinforcing loops that keep regenerating them, and the fix is to find the single link in the cycle you can cut.
Most stakeholder problems get treated as outcomes to fix. A launch slips, sales goes off-script on the messaging, product quietly reprioritizes your feature out of the release, and engineering decides marketing overpromised again. You chase each one down, smooth it over, and move on, and then the same fight shows up next quarter wearing a different name.
That is the tell. When a problem keeps coming back, you are not looking at a bad outcome. You are looking at a system that keeps producing it.
This is the difference between thinking in outcomes and thinking in systems. Outcomes are the events you react to, while the system is the set of forces that makes those events likely in the first place. Fix an outcome and you feel productive for a week. Fix the system and the outcome stops happening on its own.
The most useful piece of systems thinking for stakeholder work is the reinforcing loop, a term I am borrowing from Donella Meadows, whose book “Thinking in Systems” is still the clearest primer on this. A reinforcing loop is a cycle that feeds itself, where each turn makes the next turn stronger, compounding in one direction until something interrupts it. Most stakeholder dysfunction is a reinforcing loop running in the wrong direction, and nobody at the table can see it because everyone is busy reacting to its latest output.
The vicious loop nobody names
Here is the shape of it. Trust drops a little, maybe after a missed handoff. So people share less information, because why expose yourself to a team that just burned you. Less information means more surprises down the line. Surprises make people defensive, so they grab for more control and more sign-off gates. The control reads as distrust to everyone else, so trust drops further. Now you are one full turn into the loop, and the next turn is faster than the last.
From inside, it does not look like a loop. It looks like a series of separate problems: a bad handoff, then a territorial PM, then a sales team that stopped reading the enablement docs. You fix each one in isolation and feel like you are losing ground, because you are. You are bailing water out of a boat while the loop drills new holes.
The leverage is not in any single hole. It is in finding the loop and cutting it. Jaime Rodríguez de Santiago makes the same point with the broken windows theory in “La realidad no existe”: the fix is not chasing each new act of vandalism, it is breaking the reinforcing loop that tells everyone the building is abandoned.
A real one: the launch that kept slipping
Here is a version I have watched play out more than once, drawn to its common shape: a flagship launch that slipped three times before anyone admitted why.
Product Marketing owned the launch date, product owned the build, and sales owned the number. Early on, the date moved once for a legitimate reason, a dependency that slipped, which was fair enough. But watch what that one slip set in motion.
Sales saw the date move, so they quietly stopped building pipeline around it. No point lining up customers for a date that walks. Product saw sales disengage, so the launch felt less urgent internally, which made it easier to let the next dependency slip too. PMM, caught in the middle, responded by adding process: more status meetings, more sign-off checkpoints, a tighter brief. All of it was meant to create certainty, but what it actually signaled was that nobody trusted the date either, so everyone hedged a little harder.
Three turns of that cycle and the launch was six weeks late, the messaging was mush because it had been written for a date that kept moving, and the post-mortem blamed “communication.” It was never communication. It was a reinforcing loop where every slip made the next slip more likely, and every defensive response made the slips worse.
You could fix the outcome easily enough: pick a new date, crack the whip, and ship the thing. But the spiral would just re-form on the next launch, because nothing about the system actually changed.
How to cut a loop instead of chasing its output
Cutting a loop is not about working harder on the symptoms. It is about finding the one link in the cycle you can break, then breaking it so the cycle cannot complete.
Name the loop out loud. Half the power of a reinforcing loop is that it stays invisible. Everyone sees their own slice. When you draw the full circle on a whiteboard, “slip leads to disengagement leads to less urgency leads to more slip,” the room stops blaming each other and starts looking at the cycle. That shift, from “who messed up” to “what is the loop,” is most of the work. People defend themselves against blame. They do not defend themselves against a diagram.
Find the weakest link, not the loudest symptom. The loudest symptom in the launch story was the slipping date. The weakest link, the one easiest to cut, was sales quietly disengaging. If sales stays committed, product feels the urgency and PMM does not need to pile on process, so that is where you intervene.
Here is the part most advice skips: by the time you notice, sales has already checked out, and you cannot just ask them to care again. Asking a disengaged stakeholder to recommit to the same thing they already gave up on does nothing. You have to change what they are committing to. Three moves do most of the work. First, shrink the ask to something they can believe in, a narrower scope and a date they help set rather than one handed to them, because people defend plans they had a hand in building. Second, make the commitment mutual and visible: product commits to protecting the dependency in the same meeting sales commits to building pipeline, so neither is exposed alone. Third, give them an early proof point, a small win in the first two weeks that shows the date is holding this time, because nothing rebuilds a stakeholder’s confidence faster than being right to trust you once. Land those three and the link is cut. Sales stays in, and the cycle cannot close.
Change the structure, not the mood. Telling people to “communicate better” or “rebuild trust” is asking the loop to fix itself through goodwill. Goodwill evaporates under the next deadline. Structure does not. Change who owns the date. Change what gets committed and when. Change the order in which decisions get made. A reinforcing loop is held together by structure, so structure is the only thing that reliably breaks it.
Then point the loop the other way. Reinforcing loops do not only run vicious, and the same compounding works in your favor once you flip the direction. A date that holds builds confidence, which makes sales lean in, which makes the launch feel real to product, so the next dependency gets protected instead of dropped. Cut the bad loop and seed the good one, and alignment stops being something you fight for in every meeting. It becomes the default the system produces.
Sometimes it really is just a bad process
A caveat, because the systems lens is easy to overuse. Not every recurring problem is a loop. Sometimes a launch slips because one person is in over their head, and the fix is a direct conversation, not a diagram. Sometimes a process is simply broken and needs rewriting, full stop. The test is whether the problem regenerates after you fix it. Solve it cleanly and it stays solved, and it was a one-off, so treat it as one. Solve it and watch it reassemble itself out of new parts, and that is your signal to stop fixing instances and go find the cycle feeding them. Forcing a systems story onto a simple problem is its own kind of overthinking, and it wastes the very sightline that makes the lens valuable when you actually need it.
Why stakeholder management is the PMM’s job specifically
Product Marketing sits at the one seat that touches product, sales, customer success, and leadership at the same time. That position is usually framed as a curse, the person with all the dependencies and none of the authority. Systems thinking flips it into the advantage. You are the only one who can see the whole cycle, because you are the only one standing in every part of it.
Engineering sees its dependencies. Sales sees its number. Leadership sees the dashboard. You see the cycle connecting all of them. That is what makes stakeholder management a systems problem rather than a soft skill, and that sightline is leverage almost nobody else in the building has. It is wasted if you spend it reacting to outputs one at a time.
So the next time the same stakeholder fight shows up wearing a new name, do not fix it again. Step back far enough to see the circle it is part of. Find the link you can cut. Then cut it, and watch how many “separate” problems were really one loop the whole time.
Frequently asked questions
How do I tell a reinforcing loop from a one-off problem?
Watch whether it regenerates. Fix it cleanly and it stays fixed, and it was a one-off, so treat it as one. Fix it and watch the same fight reassemble itself out of new parts a quarter later, and you are looking at a loop. The recurrence is the signal, not the size of any single incident.
What if I can see the loop but I do not own the people in it?
That is the normal case for product marketing, and it is also the advantage. You rarely have authority over product, sales, or leadership, but you are the only one standing in every part of the cycle, so you are the only one who can name it. Drawing the full loop on a whiteboard shifts the room from blaming each other to looking at the structure, and that shift does most of the work without needing any authority at all.
Where do I intervene if I only get one move?
Find the weakest link, not the loudest symptom. The loudest symptom is usually the thing everyone is already arguing about. The weakest link is the quiet one that, if it holds, stops the cycle from closing. In a slipping launch the loud symptom is the date, but the weakest link is sales quietly disengaging, so that is where one move buys the most.
Is this just a fancy way of saying communicate better?
No, and that is the point. Treating stakeholder management as a communication problem is exactly the trap. Telling people to communicate better or rebuild trust asks the loop to fix itself through goodwill, and goodwill evaporates under the next deadline. Loops are held together by structure: who owns the date, what gets committed and when, the order decisions get made in. Change the structure and the loop breaks whether or not anyone feels more warmly toward each other.
Sources
- Donella H. Meadows, “Leverage Points: Places to Intervene in a System” and Thinking in Systems: A Primer (Chelsea Green, 2008). The source for reinforcing and balancing loops, and for leverage points, the places in a system where a small change produces an outsized shift.
- Jaime Rodríguez de Santiago, La realidad no existe (Líneas Desaparecidas, 2023), chapter 15, “Cuando todo se conecta con todo.” Frames systems thinking as moving from linear cause and effect to spotting the loops, and uses broken windows theory to show why you break the reinforcing loop rather than chase its symptoms.
I help B2B SaaS companies fix their go-to-market when positioning is unclear, launches don’t land, and sales can’t explain what makes them different. Ten years doing exactly this, scale-up to enterprise. Contact me at zackalami.com/#contact.
