A Letter to the XBE Community

I wrote The Dionysus Program.

Eric Jorgenson—bestselling author of The Almanac of Naval Ravikant and the upcoming The Book of Elon—was kind enough to write the foreword. There's a line in it that I keep returning to: A great book doesn't just make you think. It changes who you are capable of being.

That's what I wanted to write. I don't know if I succeeded. But I know why I had to try.

· · ·

You've watched XBE change. You may not have had language for exactly what you were watching, but you felt it. We started by building a logistics system—software that actually moved trucks, balanced supply and demand, and coordinated the messy human machinery of heavy construction. Then we built visibility tools on top of that foundation to understand where the waste was actually coming from. And we kept hitting the same wall.

Here's what I mean. When we gave a superintendent a real-time view of his job—trucks, tons, idle time, dollars burning in the dark—something interesting happened. He didn't become more efficient. He became emotional. The dashboard told a more complicated story than the one he'd been telling himself. What he needed wasn't better data. He needed a system that made a different kind of honesty possible before the trucks were already backing up—because by the time the trucks are backing up, it is too late.

So we built planning tools. Job production plans. Supply-demand balancing. Ways to surface uncertainty before the fact, to make uncertainty socially admissible rather than something you quietly insured against by over-ordering trucks and hoping. Waste fell. Not because anyone became morally better, but because the structure made a different choice possible.

And then we built Game Plans—our version of OKRs. Clear goals. Measurable key results. That helped too, but insufficiently. We could see the goals. We still couldn't reliably metabolize the gap between where we were and where we said we'd go. The bottleneck wasn't the plan. It was the culture's capacity to tell the truth about the plan.

· · ·

Around this time, something else was happening. Artificial intelligence had started to change our work—and I could see that it was going to change everything, faster than almost anyone was acknowledging.

The half-life of expertise was shrinking. Skills that took years to build were becoming cheap in months. Roles that once required a team of specialists were becoming one-person jobs. And the people most affected weren't struggling with the technology itself. They were struggling with what the technology made them feel about themselves.

This is the thing I want you to understand precisely, because it changes what the right response looks like. When knowledge compounds this fast, it doesn't just update what people know. It dissolves the roles, rituals, and identities that gave people a reason to show up—and a story about why they were good at what they did. When those dissolve faster than new ones can form, you don't get orderly adaptation. You get numbness, theater, or someone to blame.

We were dealing with the melt. We were creating the melt. And it had only just begun.

· · ·

I've spent the last several years trying to figure out what was actually going to happen—to individuals, to teams, to organizations—and what a real solution might look like. Not a motivational solution. Not a productivity framework. A diagnosis and a prescription precise enough to be useful.

Most philosophy gets engaged from a safe distance. People read the important ideas, discuss them, admire them like paintings in a museum. They know the names. They can quote the lines. But they keep their hands in their pockets. The ideas stay separate from the daily life of the organization—from the moment a hard truth needs to be said, from the postmortem where everyone knows what went wrong but nobody says it.

I didn't want to write that kind of book.

· · ·

The Dionysus Program is my best attempt at the diagnosis and prescription for this moment. Its core claim is simple, though working it out took a long time: the bottleneck in any organization navigating rapid change is not technical capability. It is the rate at which the organization can metabolize error into new structure—new roles, new norms, new commitments—without burning the trust that makes honest work possible in the first place. I call this the epimetabolic rate. Everything else follows from trying to raise it.

The program distinguishes two modes of organizational time. Run Time is ordinary execution—forecasts, decisions, accountability to outcomes. Ritual Time is the dedicated container where critique is welcomed, meanings can melt safely, and new commitments are forged in public. Apollo governs the first. Dionysus governs the second. Both are necessary. Most organizations run Apollo almost exclusively, which is why they can improve their systems and metrics while quietly spending down the trust that makes any of it matter.

When you run only Apollo and the world changes fast enough, one of three things happens. Leaders ask people to shrink themselves so the change barely registers. At first, that feels like relief. It is not. Or they hold stability through force—align or be ostracized, agree or be sidelined. Or they look away entirely, letting competition and uncertainty do the work while pretending this is discipline. All three are ways of winning today by burning what you need to survive tomorrow.

The method, briefly: the program runs a single loop—critique, dissolution, reconstitution, renewal—at every scale, from a daily personal practice to a quarterly organizational reckoning. It uses Ritual Time containers to hold high heat without burning people, directing criticism at ideas and artifacts rather than at the people who held them. It gives that loop the governance rules, the aesthetic fuel, and the enforcement teeth it needs to be real rather than theater. The book is the full architecture. What I've described here is the skeleton.

The Dionysus Program is organizational alchemy that actually works. It is a field manual for leaders facing that bottleneck.

· · ·

I want to say something about how the book was built, because I think it matters. The frameworks here don't come from consulting engagements or business school theory. They are built on ideas that have survived centuries—Confucius on ritual and humaneness, Popper on error-correction, Durkheim on social facts, Turner on liminality, Nietzsche on Apollo and Dionysus, Ibn Khaldun on the binding force of groups. I went looking for old tools deliberately, not to escape modernity but to survive it. A good idea that has lasted five hundred years has already beaten most of the tests a new framework hasn't faced yet. I wanted the bones of this program strong enough to hold real heat.

· · ·

I'm releasing this now deliberately. This week we're also launching All-22—a full-field dispatch model for ready-mix operations that lets teams see, simulate, and act on the whole day before problems cascade—and Agent XBE, a superworkforce that can figure out and execute real work on demand, collapsing the division of labor that once required teams of specialists. These aren't separate bets. They are the melt, applied to our own industry. The work is changing faster than most organizations are ready for. The Dionysus Program is the companion to that change—not the technical manual, but the human one. The time to understand what's happening and how to thrive in it is now.

The eBook is free at dionysusprogram.com. If you want a physical copy—something to hold, annotate, or give to someone who needs it—the paperback is available on Amazon.

If you find errors in the logic, let me know. If you disagree with the diagnosis, say so in public. The program requires friction to stay honest. Criticism isn't a threat to these ideas—it's the mechanism by which they improve or die, which is exactly what the ideas themselves are about.

This is important work. I'd rather be wrong in public than right in private.

With respect and care for what we're building together,

Sean