← Back to all posts

Building a Supply Chain OS: Nudges, Resonance, and Structure

I was unwinding with a cup of cacao this evening, thinking back on today’s store visits. They were billed as courtesy calls, but really, I was just trying to fix a broken pipeline. Truth be told, a simple text with the right protocol could’ve done the job—no need for the personal touch. And after seeing how Jerry set up automated prompts for his chief of staff, I’m realizing that text doesn’t even need to come from a human. It just needs to feel like it does—or maybe not even that.

That stings a bit, because so much of my time in the supply chain is spent doing just that—nudging people to keep things moving. Here’s the rundown of what I’m constantly reminding folks to do:

It’s not rocket science, just repetitive. But here’s the thing—a lot of these nudges get ignored. I’ve been telling myself the system holds together because of a deeper WHY, something I’ve been calling LOVE. It’s about planting trees for the next generation, building a legacy for those who come after. I think of Salvation Mountain, enduring long after Leonard Knight’s passing, with “God is Love” at its heart. That’s the purpose I thought was driving us.

But if love is the engine, why do so many let my prompts slide? I chewed on this with DeepSeek, and it flipped my perspective. Love isn’t enough to guarantee action. What I’ve been missing is resonance—finding the folks who don’t just offer warm words but actually follow through, especially when there’s no immediate gain for them. I’ve been pouring energy into people who mask transactional self-interest with politeness, and I’m done with that. So, I’m setting up a filter for resonance, and here’s how I’m approaching it:

At the same time, I’ve been running my reflections through LLMs to sniff out any hidden flaws in my reasoning, and it’s been a game-changer. The feedback cut through my loftier framing: supply chains don’t fail from complexity; they stall from latency and silence. My list of reminders? Just a queue of “unmoved states.” And while purpose—like love—can motivate, systems don’t run on goodwill alone. They need incentives, reliability, and accountability loops.

Here’s where my thinking got refined:

What I’m really building, I think, is a human coordination OS—nodes (farmers, processors, logistics, retailers), states (beans harvested to processed to shipped to sold to trees planted), triggers (reminders, confirmations), and a motivation layer (the mission, or “love”). The bottleneck isn’t my effort—it’s unreliable state transitions from mistimed or missing triggers.

Key observation: there’s a powerful—and risky—opportunity here. If I systematize this well, I’m not just automating reminders; I’m creating a self-propelling supply chain where humans only handle exceptions, not routine. But if I over-index on the “soul” framing, I risk underbuilding mechanical reliability, and the system gets shaky when goodwill dips.

Reflections for the evening: Filtering for resonance keeps my energy focused on the right people, while pressure-testing my ideas with LLMs uncovers hidden operational gems. I’m starting to see my role as balancing human connection with designing a deterministic system of feedback loops. Love might help me find who’s truly in, but structure keeps the chain alive. What about you—how do you balance filtering for the right people with building systems that don’t rely on constant nudging?