Every post-mortem on a brilliant flop blames bad timing, a comforting explanation because it treats timing like weather. The vision was right, the universe just didn’t show up on schedule.
Google Glass wasn’t wrong about head-mounted computing. It needed battery density, social norms, and form factor to mature at once, and Google owned none of them.
That’s a different disease than the one that killed Webvan, which didn’t fail waiting on someone else’s clock. It failed spending its own capital as if it already owned logistics infrastructure it hadn’t built yet. One company bet on clocks it didn’t control, the other burned cash pretending a clock didn’t exist. Both look like bad timing in hindsight. Only one of them was.
Timing is a lazy diagnosis. The real question is narrower, and answerable before the fact.
The Question Boards Never Ask
Almost every strategy framework tells executives how to choose a future. Almost none tell them how to survive while waiting for it. The question that actually matters:
How much of the future has to arrive, on someone else’s schedule, before this strategy pays for itself?
Every strategy pays a synchronization tax, determined by its Synchronization Load: the count of external conditions that must become true, none of which you control, before the strategy becomes viable. By viable, I mean the point where the business can fund its own next step instead of relying on fresh capital to survive. Every additional independent clock extends the period capital sits committed before it can compound. That delay is the tax, and every strategy with unowned dependencies pays it. Load is estimable before you write the check. Getting it wrong turns a payable tax into a fatal one.
Synchronization Load counts independent clocks, not mentions. Four dependencies that all unlock when a single enabling condition arrives are one clock wearing four disguises. The real count is how many separate parties, none reporting to each other, must move on their own schedule.
Same Prediction, Different Bill
In 2002, Bill Gates announced the Tablet PC and predicted pen computing would dominate within five years. He was right about the destination. Microsoft’s strategy required simultaneous leaps in stylus software, digitizer hardware, desktop OS changes, and mobile battery tech: four unowned clocks, expected to strike midnight together. Microsoft burned hundreds of millions waiting for an ecosystem that hadn’t formed.
Apple made the identical prediction and paid a different bill. Through the 2000s, it built high-margin MP3 players and phones while Samsung, Toshiba, and LG matured touchscreens, flash memory, and ARM chips on their own balance sheets. By the time the iPad shipped in 2010, someone else had already paid for most of the runway.
Apple didn’t forecast more accurately than Gates. It needed less of the future to arrive, and what little it did need, like the AT&T deal that got the first iPhone onto a network, it negotiated and owned outright rather than hoping for. That’s not an exception to the framework, it is the framework: the dependency didn’t disappear, it got internalized into a contract Apple controlled.
Engineering Viability on a Slice of the Vision
Netflix didn’t wait for broadband to become universal. It first built a DVD business that generated the cash to survive until broadband caught up. The DVD business wasn’t the vision. It financed the wait. They built something that got paid before the future arrived.
Amazon did the same with AWS: viable on plain storage and compute while developers built simple applications on top, long before enterprise cloud transformation was real. Same pattern, different infrastructure.
Skeptics will call this survivorship bias with better vocabulary, every winner reading as low load in hindsight and every loser as high load. Fair challenge, and it would sink the idea if the count only existed after the outcome. It doesn’t: Gates announced his four dependencies in the same press cycle as the prediction, and Apple’s AT&T dependency was visible the day the deal was signed. The count is available at the moment of the bet.
Three Moves, Ranked by Risk, Not Interchangeable
When a strategy depends on external clocks, leadership has exactly three moves, and they are not peers. Treating them as equally safe is how internalization turns into a second Webvan.
1. Exploit existing economics. Build on infrastructure that already exists while the rest matures on someone else’s balance sheet. Lowest risk, because you’re not funding anyone else’s clock.
2. Sequence the exposure. Take on one unowned clock at a time instead of four at once. SpaceX didn’t need Mars colonization or a satellite constellation to reach viability. A single NASA contract made Falcon 1 viable, and every dependency after was funded by the last one’s revenue.
3. Internalize the risk. Build the dependency yourself when no one else will move fast enough. Tesla built Superchargers and Gigafactories because utilities and automakers wouldn’t. This is the highest-variance move, not a shortcut around risk. You haven’t removed the clock, you’ve bet the company you can out-execute it. It only makes sense once the first two are ruled out.
All three assume the clock belongs to engineering or capital, something a balance sheet or contract can eventually own. Some clocks don’t work that way: a regulatory approval, a licensing regime, a standards body with members who don’t answer to each other. None bend to a bigger check or a faster team. You can’t exploit your way around an FDA review or internalize a spectrum auction.
The Test, Before You Write the Check
Skip the debate about how exciting the end-state is. Run the strategy through three questions instead:
- What external conditions have to go right before this becomes viable, and how many separate clocks does that reduce to?
- Which do we control today, through ownership, contract, or capital, and which can no amount of either move?
- For the rest: are we exploiting existing economics, sequencing one clock at a time, or internalizing deliberately, and can we afford that last option?
If the answer to the first question is four industries aligning on day one, and the answer to the third is “we’re hoping,” you’re not running a strategy. You’re holding a coordination bet dressed up as one.
The best strategists don’t predict the future more accurately than everyone else in the room.
They simply need less of it to arrive on time.
The companies that win aren’t the ones that see farther. They’re the ones whose businesses start working sooner.
The first job of strategy isn’t choosing the right future. It’s designing a business that can survive until that future arrives.
And Vijay Says... 