The Noren Loop Map
Run any recurring problem through five moves and find the one change actually worth making.
- A 20-minute diagnostic you can run on any problem that keeps coming back — missed deadlines, churn, the same argument every sprint.
- A one-page map of the stock, feedback loops, and delays that keep producing the pattern.
- One defensible answer to "what single change is actually worth making?" — instead of another round of symptom-fixing.
The problems that keep coming back aren't bad luck — they're the output of a structure. Push on the symptom and the structure pushes right back. Systems thinking is the discipline of seeing that structure: the stocks, the loops, and the delays that produce the same outcome no matter how hard you work on the surface.
A recurring problem is a structure, not an event. Fix the event and it returns; change the structure and it can't. The Loop Map is a repeatable way to find the structure in twenty minutes.
Five moves, always in order
Each move ends with a gate — a check that tells you whether you've actually seen the system, or just renamed the symptom.
- 1Name the stock. What is accumulating or draining that you actually care about — customers, trust, cash, morale? State it in one noun.GateIf you can't name it in a single noun, you're still describing events. A system has a stock; a complaint doesn't.
- 2Find the loops. What reinforcing loop is amplifying it, and what balancing loop is resisting your fixes? Sketch them — nouns and arrows.GateIf no arrow in your sketch circles back to where it started, you've drawn a to-do list, not a loop. Keep looking.
- 3Mark the delays. Where does action take time to show up? Those are the places you'll be tempted to overreact.GateIf you found no delays, look again — every real system has one, and it's exactly where the overcorrection lives.
- 4Drop down the iceberg. Past the event to the pattern, the structure, and the belief that makes the structure seem reasonable.GateIf you can't state the belief holding the structure in place, you'll rebuild the same structure with new parts.
- 5Find the leverage. Sort every attempted fix into parameter / rule / goal. The real lever is almost never the parameter everyone is arguing about.All five done?You have one change worth making. Make it — then let it run long enough to outlast the delay you marked in move 3.
Most people act at the surface
Every recurring problem can be read at four depths. Each level down is harder to see — and far more powerful to change.
The Atlantic cod that vanished overnight
For centuries the cod off Newfoundland seemed inexhaustible. Then, in 1992, the fishery collapsed almost overnight and — decades later — still hasn't recovered. Read as a system: the fish were a stock; reproduction the inflow, fishing the outflow. Better technology pushed the outflow far above the inflow for years.
Because the stock was huge, nothing looked wrong — the buffer hid the danger — until it crossed a threshold and collapsed nonlinearly. The most dangerous systems are the ones that look fine right up until they don't. When something important is being drawn down faster than it refills, the absence of an alarm isn't safety. It's the buffer, quietly running out.
Stock: the team's unfinished work. Reinforcing loop: missed deadlines → pressure → shortcuts → rework → more unfinished work. Balancing loop: every "crunch week" quietly drains morale, so each crunch buys less than the last. Delay: rework surfaces weeks after the shortcut that caused it. The belief underneath: "urgency makes us faster." Leverage: not another deadline (the parameter everyone argues about) — a rule change: nothing new starts until something ships.
Same five moves, run on a Tuesday-afternoon problem. The map doesn't care how big the system is — that's the point.
Go deeper with the full playbook
The Loop Map is the one-page version. The Systems Lens teaches you to see every structure behind the noise.
A complete field guide to seeing the stocks, loops, and leverage points behind every recurring problem.