Decisions on the Record: Why Your Business Needs a Cable System | Lazy Leverage #98
No se pudo agregar al carrito
Add to Cart failed.
Error al Agregar a Lista de Deseos.
Error al eliminar de la lista de deseos.
Error al añadir a tu biblioteca
Error al seguir el podcast
Error al dejar de seguir el podcast
-
Narrado por:
-
De:
Most founders know the feeling. You write a careful company memo, send it to the team, feel good… and watch it vanish into the noise. Three weeks later a new hire joins who never saw it, a policy gets contradicted in Slack, and the left hand has no idea what the right hand is doing.
Peter and Jon tackle this head-on, and the solution comes from an unlikely place: the U.S. diplomatic cable system.
Jon, drawing on his government background, explains how embassies have solved institutional memory for decades. A cable isn't an email, but a formal, sequenced document that can only be released by authorized leaders.
He walks through how he built a version at Sagan. Urgency tiers, a sequential coordination chain requiring explicit sign-off, and tiered databases. What you get is a permanent, searchable, authoritative record new hires and LLMs alike can be pointed to.
Peter connects it to a real AI problem. That is, when you feed an LLM your Slack, Notion, and email simultaneously, it hits conflicting sources of truth with no way to weight them. Cables solve this by establishing information hierarchy by design.
Closing out the conversation, Peter explains why protecting the "space" matters more than filling the schedule.
KEY TOPICS: (03:00) The Disappearing Memo Problem (06:26) The Diplomatic Cable System: Origin and Inspiration (11:04) "A Cable Is a Decision on the Record" (16:04) Urgency Levels, Slack Notifications, and Tiered Databases (22:56) Crane Horizons: Tulum Debrief (25:49) Creating and Protecting the Space at Member Events (39:36) Tools Roundup: Claude's Native Connectors
Stay connected for more insights and strategies by following: Jon: @MatznerJon on X and at lazyleverage.beehiiv.com Peter: @pslohmann on X and at peterlohmann.com