Most business owners think about margin as an output. Revenue minus cost equals profit. If margin shrinks, you either raise prices or cut costs. Simple math.
Except it isn't. Margin erosion almost never shows up as a single line item you can point to and fix. It shows up as a pattern. A reinforcing cycle where one problem feeds another, which feeds another, which circles back and makes the original problem worse. Systems thinkers call these reinforcing cycles feedback loops. I call them the silent killers of otherwise healthy businesses.
The Loop You Don't See
Here's a scenario I've watched play out at multiple companies, including some I've invested in.
A services business starts losing a few experienced team members. Not a crisis, just normal attrition. But the remaining team picks up the slack, which means they're stretched thinner. Response times slip. Quality dips just enough that a couple of clients notice. One leaves. Revenue drops slightly, so leadership tightens the budget, which means fewer resources for training and hiring. The remaining team gets stretched even more. Another good person leaves because the workload is unsustainable. The loop tightens.
Nobody made a catastrophic decision. Every individual choice along the way was rational. But the system produced an irrational outcome because nobody was watching the loop.
This is what Donella Meadows described in her foundational systems thinking work: reinforcing loops don't require malice or incompetence. They just require inattention. The same structure that creates compound growth creates compound decline. The direction depends on whether you're feeding a virtuous cycle or a vicious one.
Three Reinforcing Loops That Kill Margin
Here are three all too common death loops:
The Discount Spiral
A sales team offers discounts to hit quarterly targets. Gross revenue comes in, but margin drops. Next quarter, the target is based on the discounted revenue number, so they discount again to show growth. Customers are trained to wait for discounts. Full-price purchases decline. Marketing spends more to generate leads that sales will discount anyway. Customer acquisition cost rises. Margin compresses further. The team asks for bigger discount authority to stay competitive.
Every step in this loop has a reasonable justification in the micro, but the loop itself is destructive in the macro.
The Complexity Tax
A product team adds a one-off feature to win a deal. Each feature adds maintenance cost and increases the surface area for bugs. Support tickets rise. Engineers get pulled from new development to fix existing problems. The product falls behind competitors, so the team adds more features to catch up. More complexity, more bugs, more support load. The cost of running the product grows faster than revenue from the features that were supposed to drive growth.
I've seen this one at scale. Procter & Gamble, before their procurement overhaul, had so many disconnected legacy systems that matching invoices to purchase orders took days. That complexity tax was costing them real money across the entire organization until they broke the loop.
The Talent Drain
This one is the most common in service businesses. At WorldVia, where we have roughly 6,000 travel advisors in our network, I think about this constantly. If advisor support quality drops, advisors would leave for networks that serve them better. Their departure reduces the overall revenue, and eventually the overall capability of the network, which makes it harder to attract strong new advisors. The average quality would decline over time. Revenue per advisor would drop. There would be less to invest in support and the loop would not only continue, it would accelerate.
The only way to fight this one is to invest in support and tooling based on capacity planning metrics. Stay ahead of the curve. If you wait to hear a groundswell of upset customers and then react, the loop is already spinning. You're too late.
How to Spot a Loop Before It Eats You
The tricky thing about reinforcing loops is that they're invisible at the individual-decision level. Each choice looks fine in isolation, but the damage is structural.
Three practices help.
Ask "Then What?". This one sounds simple, and it is, but don't let the simplicity fool you on the value it delivers. Mapping the chain of consequences past the first order is a cheat code to better decision making. When you make a decision, ask what the second and third effects will be. If you cut the training budget, then what? What happens six months later to retention? If retention drops, then what? What happens to client satisfaction? If satisfaction drops, then what? What happens to revenue? Keep asking "then what?" and follow the chain to see if it circles back. If it does, you've found a loop.
Watch for delayed signals. Reinforcing loops are dangerous precisely because the feedback is delayed. The decision to underinvest in quality doesn't show up in this quarter's numbers. It shows up in next year's churn rate. Build leading indicators that catch the problem before the lagging indicators confirm it. Employee engagement scores. Time-to-resolution metrics. Customer health scores. These are your early-warning system.
Stress test your balancing loops. Every healthy system has balancing loops that counteract the reinforcing ones. A thermostat keeps a room at a set temperature. Quality standards keep a product from degrading. But balancing loops break down under pressure. When budgets get tight, the first things cut are often the balancing mechanisms: QA processes, training programs, customer success teams. That's when reinforcing loops run unchecked.
Systems Over Hustle
Hustle-mode operators see each problem as a thing to be solved individually. Attrition problem? Hire faster. Discount problem? Set stricter approval rules. Complexity problem? Add more engineers. These are first-order fixes that don't address the structure producing the problems.
Systems-mode operators look for the loops. They ask why the problem keeps recurring. They invest in the balancing mechanisms that prevent reinforcing loops from spinning up in the first place. They build structure that makes the right outcome the default outcome, not the heroic outcome.
You can't outwork a reinforcing feedback loop. You have to redesign the system around it.
Keep building,
— JW
