Feeling behind? You probably are. But not the way you think.
Why Smart People Keep Failing at the Same Problems: Delays, Feedback Loops and Late Reaction
Most people blame bad outcomes on bad effort.
Before I started learning Systems Thinking, I spent years doing this. Every failed project, every missed deadline, every strategy that collapsed halfway through execution, I assumed someone had not tried hard enough. Usually me.
I was dead wrong.
That was Jay W. Forrester’s central point when he built system dynamics in the 1950s. Organizations do not behave according to intention. They behave according to feedback, delays, and internal structure. You can have smart people, genuine effort, clear goals, and still produce failure if the loop is wrong.
I found this both illuminating and deeply inconvenient.
First, understand what a loop actually is
A system reacts to its own output. That reaction creates a loop. There are two types:
Reinforcing loops: the ones that spiral
A reinforcing loop amplifies whatever is already happening, good or bad.
Balancing loops: the ones that try to correct
A balancing loop tries to push things back toward a target.
You can find a more detailed explanation here:
Delay is where systems become dangerous
A delay means the system reacts after reality has already changed.
In practice: You launch a process change today. The real consequences appear three months later.
By then, you have already layered three more fixes on top of the original one. The first signal is buried. Nobody knows what caused what anymore.
Forrester showed that long delays push managers to overcorrect, undercorrect, or react to conditions that no longer exist. They are not steering the current system. They are steering an outdated picture of it, with confidence.
I have done this. I have also been the person confidently presenting a slide deck about a problem that had already solved itself two weeks earlier. Nobody told me. I just kept presenting.
This is why companies can look completely irrational from the outside while every individual decision seemed reasonable at the time it was made. The decisions were not wrong, but the timing was completely off.
A real example: Teradata
In late 2025 and early 2026, Teradata publicly changed its planning and governance model because long planning cycles were making transformation almost impossible.
They had been running on three-to-five-year (!!!!) roadmaps. That created a structural trap: strategy stayed fixed while the market kept moving, customer feedback arrived too late to affect priorities, and funding decisions happened so rarely that dead initiatives survived long past their expiry date, absorbing attention and budget like organizational zombies.
All that not to mention that nowadays an employee normally stays with a company somewhere between 22 and 30 months on average, meaning the majority of the people involved in the process start were no longer there to see the strategy through.
Leadership did not frame this as a people problem or an execution problem. They rightfully called it what it was: a system design problem.
They replaced the long roadmap with rolling 12-to-18-month planning, added quarterly portfolio resets and started using OKR-style reviews to reallocate attention faster.
The result: less time between a signal appearing and a decision responding to it. Fewer dead projects kept on life support and healthier loops overall, with more current and relevant information.
Forrester would have nodded.
Most organizations still get this wrong
And this happens across the board, from enterprise sized orgs to startups and even solopreneurs.
They keep asking “why are teams not executing?”, when the better question is: “what delay is hiding the truth from me?”
Teams usually execute exactly as the structure tells them to.
But monthly reporting hides weekly failure. Quarterly budgeting protects initiatives that stopped making sense in month two. Annual planning freezes assumptions that expired before the ink dried.
The visible symptom is slow execution, while the actual cause is a correction that arrives too late to matter.
This happens at home too
You have been tired for three weeks. You know you should sleep more. You keep postponing it because work is heavy right now, and you will recover on the weekend.
But the weekend comes and two nights of decent sleep do not fix three weeks of deficit. You conclude that “sleeping more doesn’t really work for you”, a sentence I have genuinely said out loud, and return to the same pattern.
The loop continues because the correction arrived too late and was too small to close the gap that had already opened.
That is a systems problem right there sitting at your own dinner table.
What to do with this
Take one frustration you are carrying right now, at work or at home, and ask three questions:
What is feeding itself here? What is trying to correct it? Where is the delay between cause and consequence?
If you cannot find the delay yet, you are probably still looking at symptoms. Keep pulling the thread.
One next move
Do not try to redesign the whole system. That way lies a very long weekend and a whiteboard covered in arrows that makes sense to nobody, including you.
Shorten one feedback cycle. All you need is one earlier correction point. That single change is often enough to shift the direction of everything connected to it.
Next Monday: Why the highest-leverage points in a system are almost never where you first look.
Happy Building,
— R.