The team meets Monday mornings at 9:00am for their weekly standup. One week, Johnny arrives five minutes late and cites traffic. He apologizes and it’s a non-issue. Next Monday, two others are five minutes late. Fast forward six months and the 9:00am standup begins at 9:12am. Julie, who consistently shows up on time, sits alone with her coffee.
Nobody changed the meeting time. The loop did.
The Loop Nobody Designed
Last week’s article argued that behavior is conditional and that the conditions a team creates are shaping more of the behavior than the people who are often diagnosed and pathologized. So, what are these conditions doing that makes them so powerful? They’re looping, reinforcing themselves, producing tomorrow’s version of yesterday’s pattern with the quiet consistency of a meeting that has been consistently starting at least 10 minutes late.
In its colloquial use, a ‘feedback loop’ might refer to a formal or informal feedback process. Think of a post-project debrief, or an annual performance review. In complexity science, it refers to processes where the output becomes its own input. Positive loops amplify the process, and negative loops dampen them. Together, they produce most of what we experience as team behavior – one kind word produces another, or a new initiative meets the gravitational pull of ‘we already tried that.’ Loops don’t ask permission. They don’t appear on the org chart, but they form anyway, from the small interactions nobody notices. Once they do, they become an important part of the team’s operating system.
Most teams don’t have a culture problem. They have a culture loop.
The loop isn’t optimizing, it’s accumulating. Tiny gravitational nudges, multiplied by ten thousand meetings, become a structure as load-bearing as the building itself.
The Loop That Eats Feedback
It could be argued that the most consequential loop in organizations is the one that keeps the feedback that matters from reaching the people who could act on it.
Elizabeth Morrison and Frances Milliken called this organizational silence in their 2000 paper in the Academy of Management Review, and they argued it isn’t shyness or laziness – it’s a self-reinforcing system. Employees withhold concerns, managers infer there are none to raise, and the absence of bad news is read as evidence of good performance. Each act of silence teaches the next person that silence is the correct move. The authors traced the pattern through large-scale organizational failures – the Columbia shuttle, Enron – where the relevant warning was, technically, available. Just not upward.
It could be assumed that a loop like this would need some sort of punishment to keep running – speak up, get burned, learn to stop. James Detert and Amy Edmondson, in 2011, found the burn isn’t necessary. Individuals imagine the simulation. They anticipate how speaking up would land – the boss’s defensiveness, the colleagues’ eye-rolls, the quiet career cost – and self-silence against the imagined simulation. Detert and Edmondson called these implicit voice theories: taken-for-granted rules about when speaking up is risky. The imagined simulation doesn’t have to be accurate to be effective.
The strongest feedback loop in most organizations is the one preventing feedback from looping.
Your team’s strategy may not be ineffective because the strategy is wrong, but because the loop is stronger than the strategy. In another scenario, the stated values don’t predict the room’s behavior because the loop reinforced different values long before the values were drafted at the workshop. Loops eat strategies for breakfast.
Loops Don’t Argue. They Just Win.
Part of what makes loops so durable is that they don’t announce themselves. In the absence of negative feedback, a team will see itself as high performing. The leader who asks ‘any questions?’ at the end of every presentation and never gets any doesn’t think they’re suppressing voices, they think they’re efficient. The team that always agrees doesn’t think it’s suppressed, it thinks it’s aligned.
What’s more, the team’s memory of its own past (hysteresis, in complexity science terms) keeps these patterns stable long after the original conditions are gone. You can replace every person on the team, and the loop will calmly absorb the new arrivals and continue.
Diagnose the Loop
A few questions for any team that suspects its loops are running the show:
– What happens the instant someone disagrees? The micro-reaction is the loop.
– What kinds of feedback never seem to land? The loop has chosen its filter.
– What questions has the team learned not to ask? The loop has marked certain topics as radioactive.
– What does “we’ve tried that” mean here? Sometimes, a useful historical note. Often, the loop’s immune response in action.
Notice none of these are about strategy.
Strategy is what you say. Loops are what you get.
As long as the loop is running, new strategies get absorbed into the old pattern. The fix isn’t a better message, it’s working at the loop level: the micro-reactions that meet dissent, the filters that drop certain kinds of input, the questions the team has learned not to ask. Strategy can’t outrun structure. Otherwise, the standup starts at 9:12. Then 9:20. And the person who still shows up at 9:00 is still sitting alone with their coffee.
–––
References
Morrison, E. W., & Milliken, F. J. (2000). Organizational silence: A barrier to change and development in a pluralistic world. Academy of Management Review, 25(4), 706–725.
Detert, J. R., & Edmondson, A. C. (2011). Implicit voice theories: Taken-for-granted rules of self-censorship at work. Academy of Management Journal, 54(3), 461–488.