Every profession has its folklore of heroics. In law, it is the late night before a filing deadline, the brief finished at the last possible minute, the lawyer who caught the critical detail through sheer force of attention. These stories are told with admiration, and some of them deserve it.
I have come to see them differently. Most of the time, a heroic save is evidence that something upstream went wrong. A practice that depends on heroics is a practice that depends on luck, and luck does not scale.
Heroic effort has a ceiling
Effort is finite. A person can work harder for a week, perhaps for a month, but not indefinitely. Attention is finite too. The sharpest professional in the world will eventually miss something on a tired afternoon, because that is what human attention does.
When the quality of the work depends on one person being at their best every day, the quality of the work will vary with that person's day. Clients should not have to hope that their lawyer slept well. They should be able to rely on a practice that produces the same careful result whether the day was good or bad.
That is what a system provides. It moves quality out of the realm of mood and memory and into the realm of structure.
What a system actually looks like
In my practice, the system is not a single thing. It is a set of ordinary tools, each modest on its own, that together carry most of the weight.
- Checklists. Before a document leaves the office, it goes through the same review every time. The checklist does not care whether the matter is routine or significant. It asks the same questions either way, and that consistency is the point.
- Written procedures. How a new matter is opened, how a deadline is recorded, how a client document is stored, how a payment is posted. Each of these is written down, so that it is done the same way regardless of who is doing it or how busy the week has been.
- Automated reminders. Deadlines, follow-ups, and outstanding items surface on their own schedule. I do not rely on remembering that something is due. The system tells me.
- Gates. Certain steps cannot proceed until a prior condition is met. A document is not sent until it has been checked against the right template. A matter does not advance until the necessary information is in hand. A gate catches the mistake before it reaches the client, which is the only place a mistake can be caught cheaply.
None of this is glamorous. None of it makes for a good story. All of it protects clients from errors that would otherwise be inevitable.
Every recurring error becomes a rule
The most valuable habit I have developed is simple to state and harder to practice: when a mistake happens twice, it becomes a rule.
A single error may be a fluke. A repeated error is information. It tells me that the system has a gap, and that the gap will keep producing the same error until it is closed. The response is not to resolve to be more careful next time. Resolutions fade. The response is to change the system so the error cannot recur, or so that it is caught automatically when it does.
Over the years, this habit has turned many of the practice's past mistakes into its present safeguards. Each rule represents a lesson that no longer has to be relearned. The practice gets a little more reliable with every correction, and that improvement compounds.
This is also why I try not to treat errors as occasions for blame. Blame focuses on the person. Improvement focuses on the system. A practice that punishes mistakes teaches people to hide them. A practice that turns mistakes into rules teaches people to surface them.
The leader designs the system
In an earlier essay on systems as the path to success, I wrote that goals describe a destination while systems describe what you do every Tuesday morning regardless of how you feel. That idea has a leadership corollary.
The leader's most important job is not to be the hero. It is to design the system that makes heroics unnecessary. That means thinking carefully about where errors tend to occur, what information people need at each step, and which decisions should be made once and then standardized rather than made fresh every time.
Good system design asks a few questions:
- Where does this process depend on someone remembering? That is where a reminder or a checklist belongs.
- Where could a mistake reach the client before anyone notices? That is where a gate belongs.
- What do we keep explaining? That is where a written procedure belongs.
- What went wrong last month? That is where the next rule comes from.
Then hold to it
Designing the system is half the work. The other half is holding to it, and this is where many leaders falter.
The temptation to skip a step is strongest exactly when the system matters most: when a deadline is close, when a matter seems simple, when everyone is confident they already know the answer. A checklist that is skipped under pressure is not a checklist. It is a suggestion.
Holding to the system means running it on the routine matter and the urgent one alike. It means following the procedure even when I wrote it and think I know it by heart. It means treating the gate as a gate, not as a formality to be waved through when it is inconvenient.
This requires a kind of humility. The system exists precisely because I am fallible. Overriding it because I feel confident is a way of pretending I am not.
Quiet reliability
A well-run practice does not produce many dramatic stories. Deadlines are met without fanfare. Documents go out correct the first time. Clients receive what they were told they would receive, when they were told they would receive it.
That quiet is the goal. It means the system is doing its job, and it frees the people inside it to spend their attention on judgment, strategy, and care, which is where human attention is most valuable.
If you are building or rebuilding the systems behind your own practice or organization and would like a candid outside perspective, request a private introduction.
The best measure of a system is how little anyone has to rescue it.