What this covers
Zack Kanter, founder of an EDI company called Stedi, talks with host Patrick about why some businesses keep their pace as they grow. The conversation ranges across Amazon's structure, military strategy, and Kanter's own choices as a founder. John Boyd supplies the main framework. In Kanter's reading of the OODA loop, observing, deciding, and acting become largely implicit with good instincts, so the real work is orientation. He draws on Chet Richards' fuller diagram and on Boyd's energy-maneuverability equations for fighter jets. He also argues that Toyota's just-in-time system emerged in parallel with Boyd's ideas rather than from them.
Amazon is the extended case study. Kanter describes it as Walmart's playbook moved online, with the floor-space constraint removed. Marketplace then let it own demand while outsourcing supply. He points to the six-page memo, where most ideas die in drafting. He contrasts this with companies that depend on a succession of heroic founders, naming Musk's firms and Stripe under the Collisons, where succession is nearly impossible to get right.
The more contested turns concern advice to founders. Kanter calls blitzscaling attrition warfare, once correct but poor now that it is common, and he treats consumer startups as lottery tickets. He favors B2B businesses where the founder has real domain edge, citing Ed Thorp. He also bets on what will not change, such as purchase orders and invoices. He argues that leading indicators of network health, such as Airbnb's never-booked listings or Uber's zero-supply app opens, matter more than GMV or take rate. Shorter detours cover how trust forms in teams, why society now builds slowly (the Empire State Building against a highway interchange), and how shared delusions trap relationships and companies.
Kanter argues that durable business advantage comes from self-reinforcing, non-rent-seeking systems and from orientation speed, which lets a firm sustain tempo as it grows, and that most conventional startup advice is backward-looking and should be replaced by deliberate edge-based choices.
- Amazon's tempo increases with size because it builds self-reinforcing systems (marketplace, AWS, memo selection) rather than relying on heroic founders
- Boyd's OODA loop reframed as continuous orientation, which in software is the key skill and more complex than in other businesses
- Build-versus-buy and business-model choices should follow an honest edge, since popular advice like blitzscaling reflects past conditions
Being trapped inside a system's reality and failing to act on hard conversations both reflect a gap between seeing options and acting.
- Patrick's reading of the Obvious Adams parable suggests that people inside a system gradually lose the ability to see outside it, so the observe step of OODA is mainly about not being trapped by the system's reality and realizing alternatives exist.
“maybe the observe for business people out there is really just making sure that you're not suckered into the realities of the system”
- People find it easy to name the hardest conversation they have not had yet, but difficult to actually initiate it, which is simple but not easy.
“one it's interesting how easy it is often for people to answer that question and how hard it is to then go and do it simple but not easy.”