But a nagging doubt builds. The team is moving slowly. The views never change. Doubt grows. Or maybe a new strategy is emerging. Execs stop paying attention to these views. Meetings missed, etc. You learn that there's back-channeling, and other meetings set up to get the "real story." OKR cycles get missed or are rushed. Suddenly, you learn about new views emerging like the "just the tier 1 launches," or "the engineering roadmap," or ___________.
One thing I kept thinking these modes don’t usually feel like intentional choices teams make. Instead, it’s more like a pendulum that swings depending on context, circumstances, culture, and how developed certain organizational muscles are.
Idealized Discipline often requires constant effort and can become prohibitively expensive or rigid if the surrounding conditions don’t justify or allow that level of structure.
Lightweight (but Effective) Constraints is the sweet spot everyone *wants* to be in, but it's deceptively hard to maintain. It relies on deep transparency and shared context, which can be cognitively overwhelming for individual contributors, leading to “oh shit” moments when things fall through the cracks.
Reactive Mode isn’t something people choose—it’s where you land when things keep breaking and the org is stretched thin. And yet, it’s often the place where teams are forced to learn the most (painfully).
What I’m taking away is that organizations *will* cycle through these modes—and the real work is being aware of that motion and responding with intention, not just inertia.
One thing I kept thinking these modes don’t usually feel like intentional choices teams make. Instead, it’s more like a pendulum that swings depending on context, circumstances, culture, and how developed certain organizational muscles are.
Idealized Discipline often requires constant effort and can become prohibitively expensive or rigid if the surrounding conditions don’t justify or allow that level of structure.
Lightweight (but Effective) Constraints is the sweet spot everyone *wants* to be in, but it's deceptively hard to maintain. It relies on deep transparency and shared context, which can be cognitively overwhelming for individual contributors, leading to “oh shit” moments when things fall through the cracks.
Reactive Mode isn’t something people choose—it’s where you land when things keep breaking and the org is stretched thin. And yet, it’s often the place where teams are forced to learn the most (painfully).
What I’m taking away is that organizations *will* cycle through these modes—and the real work is being aware of that motion and responding with intention, not just inertia.
So well put!
I can’t help feeling we have worked in the same companies :)
if i could ever get my bank account in order i eould love to upgrade to paid