Why Fast Teams Still Lose
A company can correctly diagnose the bottleneck, own the constraint, and build real execution authority, and still lose. Not because the diagnosis was wrong. Because the parts of the organization that needed to move together didn’t.
The Strategy Isn’t Wrong. The Clock Is. argued that industries operate at different rates of change, and that value migrates to whichever constraint is binding at a given moment. This essay asks a narrower question, one that only shows up after a company has already gotten the market-level diagnosis right: why do organizations with the correct strategy, the correct constraint, and even the correct authority still fail to capture the value they correctly identified?
The answer isn’t speed. It’s coupling.
Why Speed Alone Isn’t the Problem
If engineering ships ten times faster than HR, nobody notices. The two functions barely touch. Speed mismatches only matter when the functions involved are tightly coupled, when one cannot act without the other’s output, sign off, or clearance. A company can run five, ten, twenty different clocks simultaneously without consequence, as long as most of those clocks operate independently.
The failure mode shows up specifically where two interdependent functions must clear each other on every cycle. The constraint isn’t the slowest function in the building. It’s the slowest dependency that every critical cycle has to cross.
Up to a point, faster engineering improves throughput. Beyond a certain synchronization gap, additional speed reduces throughput, because every new release creates more unresolved work for the coupled function downstream, more risk inventory, more exceptions stuck in a queue that was never built for this volume. That’s a testable claim, not just a plausible one. Track deployment frequency against governance approval frequency against channel update frequency in a real organization, and watch what happens to throughput as the variance between them widens.
Ford Model e and the Channel Clock
In 2022, Jim Farley split Ford into separate units, creating Model e to run the EV business at software speed while legacy combustion stayed under Ford Blue. The diagnosis was right. Competing with direct-to-consumer software platforms meant transparent pricing, digital purchasing, and real charging infrastructure.
Model e’s product and software teams moved fast. To match that on the commercial side, Ford introduced the Model e Certified dealer program that September, asking franchised dealers to invest up to $1.2 million for fast chargers, non-negotiable pricing, and digital sales workflows.
Here’s the coupling. Ford’s software team didn’t need dealers to ship code. But it did need every one of them to clear a state franchise law before the new pricing model could go live, and that clearance is the dependency this essay is about. The dealer channel clock was governed by decades of statute Ford could not rewrite on its own. Dealers in at least six states filed suits and administrative challenges arguing the mandates violated dealer-protection law. Because that clock ran on court schedules and statutory notice periods, Ford couldn’t force the model through. By November 2023 it rolled back the requirements. By July 2024 it scrapped the certified dealer program entirely.
Worth being honest about the full picture. EV demand was cooling industry-wide during this same window, and Ford pulled back roughly $12 billion in EV spending for reasons well beyond dealer friction. Ford doesn’t prove the law by itself. What it does is illustrate the mechanism cleanly, a fast function coupled to a slow one it could not bypass, with the slow one setting the outcome regardless of how good the fast one was.
GE Digital and the Coupled Sale
The same pattern shows up again in GE Digital’s Predix platform through the 2010s, through a sales dependency instead of a legal one, and the coupling here is almost textbook. GE correctly diagnosed that industrial equipment, turbines, jet engines, locomotives, was shifting toward software-driven predictive maintenance, and spent billions building the capability with real engineering autonomy behind it.
Engineering shipped on two-week cycles. But every dollar of that software had to pass through a sales force compensated on multi-million-dollar, multi-year capital deals. Engineering could not monetize its output without that function clearing it first. Asking a rep whose commission depended on a $100 million turbine contract to sell a $50,000 annual subscription wasn’t a parallel problem sitting next to engineering. It was the coupling point engineering’s output had to pass through to become revenue.
Worth being honest here too. GE Digital’s wind down was tangled, not clean. Business units that had already built competing tools resisted adoption, the strategy spread across too many verticals at once, and the platform had real technical shortcomings of its own. The sales coupling wasn’t the sole cause. It was a genuine, structural brake.
What This Costs
Large organizations run on more than a handful of clocks, product, governance, commercial channels, procurement, finance, regulation, and which ones matter varies by industry. The specific clocks aren’t the point. The coupling between them is, and every one of those coupling points is really an interface built for one clock speed and now being asked to serve another.
What asynchronous coupling costs rarely shows up on a quarterly report. It shows up as risk inventory nobody signed off building, capital held against decisions stuck in a queue, learning that arrives too late to change the next cycle. As execution compresses toward real time, advantage migrates away from the teams that move fastest and toward the organizations that synchronize their critical dependencies most effectively. The scarce capability is no longer building faster teams. It’s synchronizing the dependencies between them.
And Vijay Says... 