A dimension larger than a supporting concept or tool
Entrainment, impedance and reactance, and fast loop and slow loop, outcomes over outputs and flow of value…. Outcomes over outputs and flow of value are both about what moves between vantages, value, information, a completed handoff. Entrainment, impedance and reactance, and fast loop and slow loop are not about what moves. They’re about the rhythm at which everything else happens. That’s an independent axis, not a supporting idea riding alongside the other two dimensions.
Vantage describes where you’re looking from. Altitude describes at what scope a question lives. Tempo describes at what pace a question needs to move, and whether that pace is being unilaterally imposed or mutually shared. All three are real, checkable properties of any organizational problem, and none of the three can substitute for either of the other two. A Craft-level problem can be addressed too fast or too slowly regardless of which altitude it sits at. A grand-strategic question can be rushed or dragged out independent of which vantage is doing the rushing or dragging.
What tempo actually contains
Entrainment describes how genuine coordination actually forms: not imposed from outside a system, but arrived at together, the way pendulum clocks on a shared wall or fireflies in a colony lock into a common rhythm with no conductor directing either. It carries its own real constraint, worth restating precisely: it only works within a system’s capture range. Push a change too far from the current rhythm and no added force closes the gap, which is why gradual ramps succeed where the identical end state, imposed all at once, fails.
Impedance and reactance, read as a pair, explain what happens when tempo gets pushed rather than shared. Electrically, reactance stores and shapes energy rather than dissipating it as waste, which is what a well-designed constraint does to organizational change, not blocking it, shaping its timing so it doesn’t arrive all at once. Psychologically, a perceived threat to autonomy produces its own reactance, a delayed, sometimes inverted counter-response, first described by Jack Brehm, where visible compliance in the room gives way to quiet reversion once the room empties. Both readings describe the same tempo failure: force applied against a system’s actual rhythm doesn’t close the gap, it just gets stored and released later, usually at a worse moment than the one it was applied at.
Fast loop and slow loop is the clearest tempo claim of the three, and it has a real, well-established academic home this framework hasn’t drawn on explicitly until now. Chris Argyris and Donald Schön’s distinction between single-loop and double-loop learning, developed across their work from the 1970s onward, traces back further still to cybernetic theorist W. Ross Ashby’s original example: a thermostat that turns heat on or off to hold a room near its set point is single-loop learning, correcting a gap between expected and actual results without questioning the setting itself. Someone walking over and changing the setting is double-loop learning, revising the governing structure that produced the gap in the first place. Fast loop is single-loop, tactical correction inside an existing structure. Slow loop is double-loop, the slower, harder question of whether the structure itself still deserves to stand. Argyris and Schön’s research found organizations reliably default to single-loop correction and avoid double-loop questioning, not from incapacity but because double-loop learning threatens the people who built the current structure, which is itself a tempo failure: a genuinely slow-loop question getting permanently deferred by the more comfortable, faster alternative.
The understanding Tempo offers that neither other dimension can
Altitude already establishes that a decision correct at one scope can be wrong at another. Tempo makes the parallel claim about pace: a response correct at one tempo can be wrong at another, independent of whether the vantage or the altitude was ever misjudged at all. A team can correctly identify a Systems-level, grand-strategic problem, and still fail entirely by trying to solve it with fast-loop urgency, or by leaving a tactical, technical-altitude fix stuck in a slow-loop review cycle it never needed. Neither failure is a vantage error or an altitude error. Both are pure tempo errors, and until now this framework had no clean way to name them as their own category.
Using tempo in practice
The same discipline altitude calls for applies here, just aimed at pace instead of scope: not picking a tempo and defending it, but staying alert to which tempo a given question actually needs, and not answering a slow-loop question with a fast-loop tool, or the reverse. A useful first check, alongside the two the practice section of this framework already runs: is this genuinely a fast-loop correction, or is it a double-loop question about whether the underlying structure itself still holds, and has it been given the tempo it actually needs, or just the tempo that was easiest to apply.
What’s still open
Treating tempo as a real, independent dimension rather than a subordinate idea opens real, specific questions this framework hasn’t answered yet: whether particular vantages have a native tempo of their own that gets violated when they’re forced to move faster or slower than their nature, whether altitude and tempo are correlated in some predictable way whose exceptions are where the most expensive failures hide, and whether capture range can become an actual measurable check rather than a description. Those are genuine open threads, not yet settled, and worth their own dedicated treatment rather than folding hastily into this piece.
References and further reading
- Ancona, Deborah, and Chee-Leong Chong. “Entrainment: Pace, Cycle, and Rhythm in Organizational Behavior,” Research in Organizational Behavior, 1996.
- Brehm, Jack W. A Theory of Psychological Reactance, 1966, Academic Press.
- Argyris, Chris, and Donald Schön. Organizational Learning: A Theory of Action Perspective, 1978, Addison-Wesley.
- Argyris, Chris. “Double Loop Learning in Organizations,” Harvard Business Review, September-October 1977.
- Ashby, W. Ross, source of the original single-loop/double-loop distinction via the thermostat example, later adopted into organizational learning theory by Argyris and Schön.