In 2013, neuroscientist Mark Blumberg and colleagues published a paper with a title that sounds almost whimsical: “Twitching in Sensorimotor Development from Sleeping Rats to Robots.” The premise was deceptively simple. When rats sleep, their bodies twitch, not randomly, and not uselessly. These tiny, low-force movements help the brain build an internal map of the body: what moves, how far, under what constraints, and with what consequences.
Blumberg asked whether these twitches, a special form of self-generated movement, could help robots learn their own mechanics before being asked to do anything meaningful. The question itself was more interesting than the answer, because it challenged the assumption that learning follows performance. Instead, it suggested that learning might need to precede it.
What struck me wasn’t the neuroscience or the robotics. It was how familiar the problem felt in a business context. Most organizations do the exact opposite of what those sleeping rats are doing. We ask them to sprint before they know where their joints are.
We reorganize, launch, migrate, scale, and commit, then act surprised when things break in ways no one anticipated. We demand certainty up front and learning afterward, as if understanding were something that naturally emerges once enough pressure is applied. Blumberg’s rats suggest a different order of operations, one that feels almost subversive in a corporate setting: learn first, perform later.
What Twitching Really Is
The word “twitching” sounds accidental, even sloppy, but in Blumberg’s work it is neither. Twitching has a few defining characteristics that matter far more than the movement itself. It is low-stakes, frequent, self-initiated, and deeply information-rich in ways that intentional performance rarely is.
A twitch does not try to achieve an outcome. It exists to generate feedback about the system itself. Performance-driven movement optimizes for results, while learning-driven movement optimizes for understanding, and those two goals often pull in opposite directions.
Most businesses are deeply uncomfortable with activity that is not obviously productive. We prefer plans, milestones, roadmaps, and metrics that point in a straight line toward a declared goal. Twitching doesn’t look like progress in that sense. It looks like motion without ambition, which is precisely why it works.
In organizational terms, twitching is not chaos or lack of discipline. It is disciplined, bounded exploration designed to teach the system about itself before the system is put under load. It is motion with intent, even if that intent is learning rather than winning.
Learning Faster Than Your Competitors
Every company talks about learning, but far fewer design for it in any serious way. Learning is often treated as a byproduct of execution rather than a first-class objective. In practice, many organizations learn only after commitment has already been made.
They learn after the launch, after the reorg, after the acquisition, or after the migration. Learning becomes a postmortem activity, something conducted when the cost of being wrong is already locked in and the options for correction are limited. At that point, insight is expensive and humility is painful.
That approach is equivalent to discovering how your knees work halfway through a marathon. You may learn something important, but the timing guarantees unnecessary damage. Twitching flips this sequence by allowing organizations to observe consequences before committing fully.
Instead of betting everything at once, teams run small pilots, create parallel paths, and test assumptions in constrained environments. They let parts of the organization probe ideas without the burden of success attached. What emerges is not just data, but understanding.
The competitive advantage here is not speed alone. It is learning velocity, the rate at which an organization updates its mental model of reality. Twitching increases that rate without increasing existential risk, which is a rare and valuable combination.
Product Development: Twitch Before You Ship
Nowhere is this pattern clearer than in product development. Strong product teams rarely start with scale, even when they talk as if they do. What they actually start with is signal, because signal tells them where reality diverges from expectation.
They want to know where users stumble, where workflows bend, and where incentives quietly distort behavior. Twitching shows up here as prototypes, feature flags, fake doors, concierge MVPs, and intentionally manual processes that feel almost regressive on the surface.
What these approaches have in common is not thrift or speed. They are expressions of humility. They assume the team’s understanding is incomplete and that the product is not a solution yet, but a question posed to the world.
Each small release becomes a twitch, an opportunity to feel resistance and discover constraints before those constraints are locked into architecture. Teams that skip this phase often mistake momentum for progress. The dashboard looks great right up until reality asserts itself, at which point the system is too heavy to change gracefully.
Twitching keeps products light long enough to learn what they actually are.
Organizational Design: Feeling the Body of the Company
Reorganizations fail for the same reason big launches fail: leaders assume they understand the system they are changing. They draw boxes, redefine roles, and announce clarity, expecting behavior to follow structure. What they discover instead is that communication paths, informal power, and trust networks ignore org charts entirely.
The company moves, but not in the way anyone expected. Decisions slow down, accountability blurs, and the intended benefits of the change never quite materialize. At that point, leaders often double down, mistaking resistance for stubbornness rather than information.
Organizational twitching offers a different approach. Instead of wholesale change, it relies on temporary structures, trial operating models, time-boxed experiments, and limited-scope governance shifts. These moves are not meant to last; they are meant to teach.
When leaders allow the organization to twitch, they gain insight into where friction actually lives, where authority truly sits, and which assumptions about behavior collapse under real conditions. The organization reveals its body map, and leaders make better decisions because of it.
Strategy as Safe Motion, Not Declarations
Strategy is where twitching feels most counterintuitive. We tend to think of strategy as a declaration, a bet that signals confidence to the market and alignment internally. In many organizations, ambiguity is treated as weakness and exploration as indecision.
Confidence without understanding, however, is bravado rather than leadership. Strategic twitching treats strategy as a hypothesis instead of a proclamation. It allows exploration at the edges without forcing premature coherence across the entire organization.
This approach encourages small parallel bets rather than singular, monolithic ones. It creates space for internal contradiction long enough for signal to emerge, even if that signal challenges the original narrative. Many successful pivots did not begin as bold moves; they began as side projects, internal tools, or experiments no one was quite sure about.
The leaders who recognized their value were not necessarily more visionary than their peers. They were simply better listeners, paying attention to the twitches instead of dismissing them as noise.
Leadership and the Discipline of Not Knowing
At its core, twitching is a leadership posture. It requires admitting uncertainty and resisting the urge to appear decisive before the system has taught you what decisiveness should look like. It favors questions over pronouncements and probes over mandates.
This stance is uncomfortable, especially for senior leaders conditioned to equate authority with answers. Yet the paradox is that leaders who allow twitching often earn more trust, not less. They signal respect for complexity and confidence in learning, which tends to resonate more deeply than forced certainty.
They also avoid the trap of overcorrection. When organizations do not twitch, they swing. Big decisions are followed by big reversals, and learning happens in painful spikes rather than steady accumulation. Twitching smooths that curve and makes adaptation less traumatic.
The Lesson Sleeping Rats Are Teaching Us
Blumberg’s sleeping rats are not trying to optimize anything. They are not chasing outcomes or maximizing efficiency. They are doing something far more foundational by learning who they are and how they work.
The best organizations behave the same way. They move before they commit, test before they scale, and listen before they declare. They treat motion as a source of knowledge, not just progress, and they build systems that can absorb what they learn.
The alternative is familiar and costly. Big launches lead to big reorganizations, which lead to big regrets. We mistake certainty for competence and decisiveness for wisdom, only to discover that complex systems do not respond to confidence. They respond to curiosity.
Twitching is not inefficiency or hesitation. It is foresight. It is how smart systems avoid catastrophic learning later by investing in gentle learning early. As you look at your next roadmap, reorg, or strategic bet, it is worth asking what small, safe movement could teach you who you really are before you ask the system to perform.
That question does not slow progress. It changes its direction in ways that matter.