This interview is about the deep logic behind business success. Guest Zack Kanter argues Amazon's greatness isn't any single move but its 'constitutional' system that makes it faster as it grows, defying the 'big companies slow down' myth. Key examples: Amazon (uses 'six-page memos' and 'two-pizza teams' to evolve itself), Walmart (impressive but limited by physical stores), and Stripe (a payment company you pay per use, like having a 'shadow army' working for you).
This episode features Zack Kanter, founder and CEO of Stedi. He and host Patrick O'Shaughnessy delve into the success models of Walmart and Amazon and their transferability, extending to underlying business logic such as the OODA loop, network health, team size, and leverage. The most weighty judgment in the entire episode is: Amazon's success does not stem from a single strategy, but from its construction of a self-reinforcing system akin to a "constitution," which allows it to accelerate as it scales, overturning the conventional wisdom that "large companies inevitably slow down."
Zack Kanter argues that Walmart and Amazon are essentially the same type of "optimization problem," but with vastly different constraints.
Zack Kanter proposes that Amazon's success stems from its unique system that merges "intelligent design" with "evolutionary" mechanisms, making it a self-reinforcing "autonomic nervous system" that does not rely on a single hero.
Zack Kanter reinterprets John Boyd's OODA loop, arguing its essence lies in "Orientation," while observing, deciding, and acting are implicit in high-performing teams.
Zack Kanter argues that modern companies should aspire to be "Navy SEALs" rather than an "Army," with the key being the use of a "shadow workforce"—third-party services that charge per transaction and are continuously optimized.
Zack Kanter believes the best question a VC can ask is "How do you measure network health?" because it reveals the true state beneath surface growth data.
| Position | Guest Attitude | Key Data |
|---|---|---|
| Walmart | Highly appreciates its achievements, but believes its model has a physical ceiling | Logistics fleet of 7,000 tractors; approximately 100,000 SKUs |
| Amazon | Views it as a model of "constitutional" organization, bullish on its self-reinforcing ability | 488 million SKUs (at time of interview); 17 leadership principles; AWS is the "first and best customer" |
| Stripe | Views it as a model of "high leverage" tools, a case for "buy" in the build vs. buy decision | 1,800 engineers; focused on the single, deep business of payments |
| NetSuite | Views it as an example of "we can no longer do hard things," believes it is the best in its industry but has fallen behind | Founded in 1998; acquired by Oracle for $11.5 billion; outdated API, running on its own data centers |
| Tesla | Views it as an example of the "more for less" value proposition of "more value, lower price" | Outperforms peers, lower price |
| Slack | Views it as an example of success through "depth" rather than "breadth" | Focused on the single function of messaging |
| Flexport | Mentioned as an early investor, but no in-depth business analysis provided | Received $1 billion in funding from SoftBank |
1. "Amazon is the only company that gets faster as it gets bigger." — Zack Kanter. Its "constitutional" architecture (six-page memos + two-pizza teams + customer value fitness function) combines "evolution" with "intelligent design," achieving self-acceleration.
2. "The core of the OODA loop is 'Orientation,' not 'Observe-Decide-Act.'" — Zack Kanter. In high-performing teams, observing, deciding, and acting are implicit; the real tempo is continuous, rapid "orientation"—constantly updating the cognitive model of a complex environment.
3. "Trust is not a cause, but a result. It comes from everyone in the team having 'Fingerspitzengefühl' (fingertip feel) for their own work." — Zack Kanter. Citing German Blitzkrieg theory, he points out that trust is an emergent property of the fact that "everyone is good at their job," not something built through team-building activities.
4. "The decision criterion for build vs. buy is: Is there an external company that can 'compound' this component faster than you can? If not, build it yourself, or don't do it at all." — Zack Kanter. This "don't do it" option is key to preventing system bloat and maintaining focus.
5. "The best question a VC can ask is: 'How do you measure network health?'" — Zack Kanter. GMV is an outcome; network health (e.g., Uber's "number of zeros," Airbnb's "percentage of never-booked listings") is a leading indicator that reveals real problems beneath surface growth.
6. "Most common business advice is wrong because it's backward-looking." — Zack Kanter. Using "Blitzscaling" as an example, it was the right answer for the past decade, but once it becomes common knowledge, it's no longer an advantage. Companies need to "weave the right strategic puzzle," not copy popular theories.
7. "Software is a 'multi-dimensional puzzle'; being off by one degree leads to complete failure. A physical product (like a coffee mug) can still hold water even if slightly misaligned." — Zack Kanter. This explains why "orientation" and "shared consciousness" are more critical in the software industry than any other.
8. "The best question is: 'What words are not being spoken?'" — Zack Kanter. As a founder, his job is to "harvest the collective unconscious of the team," bringing unspoken concerns, doubts, or conflicts to the surface, thereby dismantling "systemic paranoia."