Spot The Loop Before It Spots You
This will take five minutes and ruin how you see every problem you've ever had.
For most of my life, I thought I was just unlucky.
Different situations, same problems. Different years. Same slow collapsing. I would fix something obvious, feel briefly competent, maybe even tell someone about it, and then watch the whole thing rebuild itself six months later like I had done nothing at all.
It was not a case of bad luck. I was just completely blind to what was causing every problem I was supposed to be managing.
I also have quite a few project management certifications. Framed. On a wall. In my house. But none of them taught me this, because project management and systems thinking are two different beasts, although very closely related.
This is the five-minute method I wish someone had handed me before I spent several years confidently solving the wrong things.
What you are actually looking for
A reinforcing loop has one defining feature: the output feeds back into the input. The effect becomes its own cause. The cycle multiplies itself in whatever direction it is already moving.
Good things become better. Bad things become hell. The loop has no conscience, no preference, and absolutely no interest in your feelings about it.
Most people miss reinforcing loops because they look for events. A thing happened. Maybe a person dropped the ball. The idiot COO made a poor decision. They find a culprit, fix the obvious part, dust their hands off, and then wonder why the same problem shows up again seven weeks later wearing a slightly different hat.
You know what they say, a pig in makeup is still a pig.
The loop was never about the event. It was about the structure underneath it. The event was just the part you could see, and the structure remains untouched.
Spot the loop in 5 minutes
With five minutes and a reasonable tolerance for mild existential discomfort when the loop becomes visible, you realize it has been there lurking for two years.
Step 1 - Name the symptom you keep seeing
Pick one recurring problem. Something annoying (or disastrous) that comes back reliably, like a bad habit or a status update request from someone who has never once read the status update.
Write it in the center of the page. Be specific. “We keep missing deadlines” is a feeling. “Client delivery slips one to two weeks every time” is something you can actually work with.
Step 2 - Follow the chain in both directions
From your symptom, trace two paths.
Forward: what does this symptom produce as a consequence? Then what does that produce? Keep going three steps.
Backward: what feeds this symptom in the first place? What feeds that? Three steps back.
Keep the language plain. You are following a thread, not building a consulting framework to post on LinkedIn. That comes later and you can even start with “I’m thrilled to announce…”.
A real example from my own life: Starting from “delivery keeps slipping”, the slip creates client pressure, pressure generates urgent check-in calls, calls interrupt focused work, interrupted work slows delivery further, delivery slips more. Going backward: delivery slips because estimates were optimistic, estimates were optimistic because the team felt pressure to commit fast, that pressure came from the last time delivery slipped and leadership stopped trusting anyone.
Step 3 - Check if the chain closes
Look at what you drew. Does the final consequence eventually connect back to your original symptom?
If yes, you have a reinforcing loop. The system is feeding itself and has probably been doing so since before you arrived.
If no, you have a cause-and-effect chain, which is still useful, but that is a different conversation for a different Wednesday.
Three signs you are definitely in a loop
The problem keeps returning after you fix the obvious part. You addressed the symptom, felt good about it, mentioned it in a meeting. The loop kept running underneath and rebuilt the exact same conditions while you were busy feeling relieved.
Each cycle feels slightly worse than the last. The amplitude is increasing. That is reinforcement doing precisely what it is designed to do, just not for you.
Everyone is trying hard and nothing is improving. This one is counterintuitive but remarkably consistent. Reinforcing loops often run hardest in high-effort teams, because all that energy gets redirected into the loop rather than out of it. The gap between how hard people are working and how little is actually moving forward - that gap is the loop waving at you.
A personal example I have fully come to terms with
A few years back I was managing a project where the team was permanently underwater.
More tasks kept appearing than were being completed. Leadership, reasonably concerned, asked for more information to understand the situation. Reporting consumed time, which left us all less time went to actual work. More tasks fell behind. Leadership, now more concerned, added more reporting.
I spent half a year running motivation workshops with the team, sending encouraging messages and offering support, and having one-on-ones where I said things like “I really believe in this team” while the backlog doubled.
I should have just spent a few hours mapping loops on a piece of paper instead.
When we finally challenged the approach and cut the reporting cadence in half, output improved in less than a month. Because we had stopped feeding the monster that was eating them alive.
I tell this story with the confidence of someone who has processed it thoroughly and not at all with the energy of someone who still thinks about it at 2am sometimes.
Four loops that show up everywhere
These appear across industries and team sizes with the kind of regularity that suggests they are less about individual management failures and more about basic human structure.
Which is either comforting or deeply alarming depending on the day.
The confidence loop
Good results build confidence, confidence improves decisions, better decisions produce better results. Run this upward and you get a team that seems to operate on a different plane entirely. Run it downward and you get a team that has learned to solve their own problems because raising problems has historically led to a longer meeting and no actual change.
The documentation loop
Poor documentation creates confusion, confusion generates questions, answering questions pulls time away from writing documentation, documentation stays poor indefinitely. Most knowledge management initiatives (and I mean probably like 75% of all attempts to document something) die inside this loop without ever knowing what ended them.
The hiring loop
Under-resourced teams cut corners, cutting corners create debt and quality problems, quality problems generate extra unplanned work, extra work keeps the team under-resourced. Companies try to hire their way out but the loop absorbs the new hires like an organisational Venus flytrap on steroids and carries on as before.
The trust loop
Leaders micromanage because they do not trust the output, micromanagement signals distrust to the team, the team stops taking ownership, output quality drops, leaders micromanage more intensely. This one ends careers. It also tends to take entire departments with it on the way out, which is a generous parting gift.
What to do once you find one
Two options. Only one works long-term.
Option one is to break the chain at its weakest point. Find the single connection that is most accessible and interrupt it. Faster to implement. Sometimes genuinely all you need.
Option two is to reverse the direction entirely. Find the input that would start the loop running the other way. Takes longer to design but it’s pedal to the metal in your favour once it starts moving.
Whatever you do, resist the urge to fix every link at the same time. That is how you end up making everything measurably worse before producing a modest improvement that nobody remembers was the original goal. Ask me how I know.
Pick one link. Move it. Watch what the loop does next, and wait for the delay before doing anything else.
Your exercise for this week
Take the most persistent frustration you are carrying right now. The one you have addressed at least twice and somehow still wake up to.
Run it through the three steps. On paper if you can, because drawing ugly arrows by hand does something that typing on a screen does not. I do not know why. I am a project manager, not a neuroscientist. I just know it works.
If you find a closed loop, you have found the shape of the problem. That is the first moment you are actually in a position to change it rather than just react to it and then write a very thorough retrospective about it.
Do not fix the loop today. Name it dead center in your page.
Write one sentence: there is a reinforcing loop where X produces Y, Y produces Z, and Z feeds back into X.
Naming it is the moment it loses some of its grip on you. It was running invisibly, now it is not. That is you reclaiming control.
Happy building,
— R.