When Systems Fail is the working title of a book I have been thinking about writing.
I am not ready to say that I am writing it. I do not have a manuscript, a publishing plan, or even a settled understanding of what the finished book would be. At this point, I have a title, a growing collection of notes, and the sense that some experiences should be documented before time reshapes them.
The idea emerged from my experience moving through a legal system I had never expected to encounter so closely.
There is much about that experience that I cannot responsibly write about yet. Some matters remain unresolved. Some details belong in legal filings rather than a public journal. Other parts require distance, documentation, and judgment that I may not yet have.
But I can write about one of the broader realizations that has stayed with me.
Systems rarely experience a person’s life as that person experiences it.
They work through categories, procedures, deadlines, professional roles, and limited sets of information. Facts are selected because they are considered relevant to a particular question. Events are placed into narratives that allow decisions to be made. Once those narratives become established, later information may be interpreted through what has already been decided.
This is not limited to the legal system. It happens in businesses, institutions, technologies, families, and communities. Every system reduces complexity in some way. It has to because no organization can examine every detail from every possible perspective.
The question is what happens when the reduction leaves out something important.
Over the past several years, I have repeatedly struggled with the feeling that the full truth of my experience had no natural place to go. There were formal processes, but each process had its own purpose and limitations. There were moments when I believed the larger story would finally be examined, only to realize that the system was seeking a narrower answer.
Just like any small business owner, I made mistakes and decisions I would approach differently today. Still, there is a difference between acknowledging personal responsibility and accepting that an incomplete narrative is the only narrative that should remain.
That tension may be where this book begins.
I can imagine When Systems Fail becoming part personal account and part examination of the systems and structures surrounding that account. It might explore how institutional incentives, professional responsibilities, resources, and procedural momentum influence what a system is capable of seeing.
It might also examine the systems inside small businesses.
Many small business owners build operations gradually. They rely on contractors, service providers, software, automation, employees, and informal procedures. They often do not have legal departments or compliance teams reviewing every process. A system that appears workable from inside the business may look very different when reconstructed later by someone outside it.
One possible purpose of the book would be to help business owners examine their own systems before someone else does it for them. Where is authority unclear? What is happening without adequate oversight? Which assumptions have never been written down? What could be misunderstood if it were separated from its original context? Where has convenience replaced careful design?
I do not yet know how much of the book would be personal narrative, how much would be systems analysis, or how much would be practical guidance. It may be all three, or it may eventually become something narrower.
Part of what has made the idea feel possible is that I now know several people who have written books. One of them is my friend Steve Keller, whose book Pay to Play grew from his own experience with the justice system. In fact, there are more than three other authors in my Bible study.
Being around them has made writing a book seem less like something done by a distant class of people and more like a long process undertaken one page at a time.
There may also be a responsibility in documenting an experience while acknowledging that it is still unfolding.
I have often imagined that I would write only after everything was resolved, when the complete meaning of the story was finally clear. I am beginning to question whether stories ever become that complete. Outcomes may settle certain questions, but they do not necessarily explain everything that happened or what should be learned from it.
Perhaps the work now is not to write the final account.
Perhaps it is to preserve the record, collect the questions, and pay attention to the systems that normally remain invisible until something goes wrong.
I do not know whether When Systems Fail will become a published book. I know only that the idea has remained with me, and that I have begun making room for it.
For now, that may be enough.