929 (Tanakh)
II Samuel 6
In another voice
Hook
You’ve just secured your Series A. You’re scaling fast, delegating core functions to "new carts"—automated systems, outsourced ops, and slick software—to move your "Ark" (your product/mission) forward. It feels efficient. Until the oxen stumble, the system breaks, and you realize you’ve outsourced your core responsibility.
Listen to this lesson. Ask it questions.
Audio, a chevruta that cites its sources, Hebrew tools, and every daily cycle, in the app.
Text Snapshot
"They loaded the Ark of God onto a new cart... But when they came to the threshing floor of Nacon, Uzzah reached out for the Ark of God and grasped it, for the oxen had stumbled. G-OD was incensed at Uzzah. And God struck him down on the spot for his indiscretion." II Samuel 6:3-7
Analysis
Insight 1: The Fallacy of "New Carts"
David tried to modernize the transport of the Ark using a "new cart" II Samuel 6:3. It was efficient and innovative, but it bypassed the established protocol of human, conscious carriage. In startups, "new carts" (automation, AI-driven ops) are dangerous when they replace the deliberate, "skin-in-the-game" stewardship required for your core value proposition.
Insight 2: The Proximity Trap
Uzzah died because he treated the Ark as a commodity to be stabilized rather than a sacred charge to be carried II Samuel 6:6-7. When you delegate the "spirit" of your company to automated processes, you distance your team from the mission. Metrics don’t feel the "stumble"—people do.
Insight 3: The Cost of Disconnection
David’s initial failure to honor the process led to a "breach" (Perez-uzzah) II Samuel 6:8. If your internal culture is disconnected from your core values, your growth will be interrupted by "breaches" that no amount of capital can fix.
Policy Move
The "Manual Override" Audit: Identify your company’s "Ark"—the one thing you cannot afford to automate. Implement a policy where any "new cart" (new automated process or outsourced department) must have a mandatory monthly "Human-in-the-Loop" review session to ensure the mission hasn't been abstracted away.
Board-Level Question
"Where are we optimizing for efficiency at the expense of ownership, and which of our current systems would fail if we removed the 'auto-pilot'?"
Takeaway
Scaling requires systems, but leadership requires presence. Don’t let your "new carts" drive the company off a cliff while you’re busy dancing in the front.
Tomorrow's lesson, already explained.
Today's is done. Tomorrow morning's arrives the same way: one short, source-cited email on the day's page. Every day of the cycle has one.
derekhlearning.com