In this episode of Tech Leadership with Fexingo, Lucas and Luna dive into the two-pizza team rule—Amazon's famous principle that a team should be small enough to be fed with two pizzas. They explore why this rule still matters in 2026, how it maps to cognitive load and team topology, and the trade-offs when teams grow or shrink. Using real-world examples from Amazon, Spotify's squad model, and a case of a misapplied two-pizza rule at a mid-size fintech, they unpack the practical nuances: when to split, when to merge, and how to keep teams aligned without falling into the trap of just counting pizza boxes. The conversation also touches on how the rule intersects with Conway's Law and platform teams, and why the right team size is less about a magic number and more about communication overhead and psychological safety. Perfect for engineering managers and CTOs looking to optimize their org structure for speed and clarity.