There is a moment in the life of every small firm when the founder realizes that the firm cannot grow past her. The signs are subtle for a long time and then suddenly obvious. The work that depends on her judgment keeps showing up faster than she can train others to handle it. The senior people get frustrated because she will not let go. The clients are loyal to her, not to the firm. Whenever she takes a vacation, the work piles up in a way that takes two weeks to dig out of. The firm is, in effect, a personality projected onto a payroll. It is a wonderful personality and a fragile firm, and the founder is too busy being the personality to notice that the firm under her has stopped scaling.
This is the moment process design becomes the most important investment the firm can make. It is also, in our experience, the moment the firm is least equipped to make it. The same things that made the founder good at running the firm by heroics — her judgment, her speed, her unwillingness to delegate the parts she cares about — make her bad at writing down how the firm works. The founder has to learn a new skill, late in her career, to do the thing that will determine whether the firm outlives her. Most founders never get there. The firms that do are the ones that, in retrospect, were able to compound.
You cannot automate a process that does not exist. This sounds obvious until you walk into a small professional services firm and try to figure out how it actually does its work. The work gets done — the documents go out, the clients get served, the bills get paid — but if you ask three people in the firm how the work happens, you will get three different answers, each only partly true. The firm does not have a process. The firm has heroics.
Most small firms are run on heroics. A senior person knows how to do something. She does it. When she is busy, she trains a junior person by doing it together a few times. Eventually the junior person can do it on her own, mostly. When something unusual happens, the senior person handles it. When the senior person leaves, the institutional knowledge leaves with her. This is fine until the firm needs to scale, at which point it becomes a wall.
From Heroics to Process
Process design in a professional services firm is not about turning the work into a factory. It is about making the work repeatable enough that it does not depend on any one person knowing the answer. The senior person’s job changes from “do the work” to “design the work so that other people can do it correctly without me.” This is a different job. It uses different muscles. It requires the senior practitioner to translate twenty years of tacit knowledge into explicit instructions, and then to accept that the explicit instructions, executed by a less experienced person, will produce work that is ninety percent as good as her own — which is the right trade, because the firm can run ten parallel instances of ninety percent and only one instance of one hundred percent, and ten times ninety is nine hundred percent.
The smallest unit of process design is the checklist. A real checklist, not a wishlist — a sequence of steps that, when followed, produces a reliable outcome. For probate intake, the checklist might have forty items. For drafting a particular kind of trust, eighty. For an offer in compromise, two hundred. The checklist is not a substitute for judgment. It is a way to free up the practitioner’s judgment for the parts of the work that actually require it.
The genius of the checklist, which Atul Gawande wrote a whole book about and which professional services firms have mostly failed to learn from, is that it does not lower the ceiling of performance — it raises the floor. The best practitioner with a checklist is at least as good as the best practitioner without one, because she can simply ignore the items she already has internalized. The mediocre practitioner with a checklist is substantially better than the mediocre practitioner without one, because the checklist catches the items she would otherwise have forgotten. The variance of the firm’s output narrows. The narrow variance is what clients are actually buying when they hire a “good firm.” They are not buying the peak performance. They are buying the predictability.
Document Before You Automate
The first rule of automation is that you cannot automate what you have not first documented. The temptation to skip the documentation step and go straight to the software is enormous, because documentation is boring and software is exciting. The teams that skip the documentation step end up with software that automates the wrong thing, or that requires more manual work than the process it replaced.
We document everything before we automate anything. The process documentation lives in plain text, edited by the practitioners who actually do the work, reviewed by the firm leader, and updated whenever the process changes. It is not glamorous. It is the most valuable artifact in the firm. The documentation, taken together, is the firm’s operating system — and a firm with a written operating system is qualitatively different from a firm without one. The first kind of firm can be taught to a new partner. The second kind of firm can only be lived through, which means it cannot be replicated, transferred, or sold.
The order matters: document first, then automate. Most firms that get this order wrong end up with a tangle of automations that nobody fully understands, each one solving a small problem in a way that creates a larger one. The right sequence is to write down the process as it is currently being executed, in enough detail that a thoughtful new hire could follow it. Then improve the process on paper — most processes have at least one or two obvious improvements that surface only when they are written down. Then, and only then, look at what parts of the improved process are mechanical enough to automate. The mechanical parts get automated. The judgment parts stay with humans. The result is a firm that uses software as a force multiplier, not as a substitute for understanding its own work.
Process Owners
A process without an owner decays. Every process in the firm has an owner — a specific person whose job includes keeping that process current, identifying where it is breaking, and fixing it. The owner is not necessarily the senior practitioner. Often the best process owner is the senior paralegal or the office manager, because she is the one who watches the process get executed every day and notices when it is not working.
Process owners are paid for the role. It is not extra duties on top of a full-time job. We carve out real time and real authority for the people who own processes, because the alternative is processes that look great on paper and that nobody actually follows.
The pathology of process ownership without authority is one of the most common patterns in professional services firms. Someone is named “process owner” but has no power to change the process, no time to maintain it, and no audience for raising the alarm when it is failing. The process stays on paper. The work happens however the practitioners decide it happens. Six months later, the documented process and the actual process have diverged so far that the documentation is worse than useless — it is misleading. New hires are trained on the documentation and then quietly learn from senior peers that the real way to do things is different. The firm now has two operating systems, one written and one oral, and the oral one wins. The cure is not better documentation. The cure is process owners with authority commensurate with the responsibility.
When to Break the Process
Process discipline is a tool, not a religion. Every process should have an explicit exception path. The exception path is what the practitioner does when the fact pattern is novel, the client is unusual, the deadline is unusual, or something else is unusual. The exception path requires more judgment than the standard path. That is the entire point.
A firm that follows its processes ninety-five percent of the time and uses good judgment for the other five percent is much better off than a firm that has perfect adherence to a process that does not actually fit reality. Process exists to make the routine work routine, so that the unusual work can get the attention it deserves.
The cultural failure mode in mature-process firms is process worship — the belief that the process is the work, rather than a scaffolding for the work. Process worship produces firms that follow the documented steps even when the steps are clearly wrong for the situation in front of them. The signs of process worship are easy to spot once you know what to look for: practitioners who escalate trivial decisions to managers because “the process does not cover this,” documentation that has not changed in three years even though the firm has, and a steady erosion of judgment among the people who used to have it. The cure is to make the exception path as legitimate, as documented, and as celebrated as the standard path. The exception path is not a failure of the process. It is part of the process, and the practitioners who use it well are doing the highest-value work in the firm.
The Documentation Discipline
Documentation rots if it is not maintained. The discipline of keeping it current is harder than the discipline of writing it in the first place, because the urgency that drove the original effort fades, and the maintenance work is invisible until the documentation is wrong. The firms that maintain their documentation well do so because they have built maintenance into the regular operating rhythm — not as a quarterly project but as a continuous practice. Every time a process is executed in a way that differs from the documentation, the documentation gets updated. Every time a new edge case is encountered, the documentation absorbs it. The documentation is a living artifact, not a published one.
The format matters less than the discipline. We have seen firms run perfectly good documentation systems in plain text files, in Notion, in Google Docs, in dedicated process-management software, and in old-fashioned binders. We have also seen firms with expensive process-management platforms whose documentation is stale and useless. The platform does not create the discipline. The discipline is what makes the platform worth anything. A firm with a discipline and no platform will have better documentation than a firm with a platform and no discipline, every time.
What Good Process Design Feels Like
In a firm with mature processes, a new hire can be doing real client work in weeks instead of months. A long-term associate can leave for two weeks of vacation and the firm does not freeze. The firm leader can sleep on Sunday night without lying awake wondering which deadline is going to be missed on Monday. The work product is consistent. The clients notice that the firm feels organized.
The reason most small firms do not invest in process design is that the payoff is invisible. You cannot point at a particular client win and credit the process for it. You can only point at the absence of failures, which is the hardest thing in the world to point at. We do this work anyway, because the absence of failures is what compounds into a durable firm.
There is also a more subtle, and ultimately more important, effect of mature processes. The firm starts to be able to think about itself. Not in the vague, retrospective way that all firms can — “I think we are getting better at X” — but in the specific, prospective way that only systematized firms can. The leadership can look at a documented process, see that it produces a particular kind of result, and ask whether a different version of the process would produce a better result. The firm becomes capable of experimentation, because there is a baseline to experiment against. Pre-process firms cannot really experiment, because they cannot measure the difference between the experiment and the control. The maturity of the process is the prerequisite for the maturity of the firm’s self-understanding, and the self-understanding is the prerequisite for everything that compounds beyond it.
What to Do Monday Morning
Pick the three processes that the firm runs most often and write them down. Not in a slide. In plain text. Start with the most ordinary, most repeatable processes — intake, billing, file opening — because these are the ones where the gap between “documented” and “actually executed” is widest and where the wins from closing the gap are largest. Resist the urge to start with the glamorous, complicated processes. Start with the ones that should be boring and have somehow become hard.
Assign an owner to each process. Give the owner real time and real authority. If you cannot give the owner real time, the process is not important enough to have an owner. If you cannot give the owner real authority, the documentation will diverge from the practice within a quarter. The owner-with-power is what makes process work compound rather than decay.
And finally, write down the exception path for each process. Not in the abstract. With examples. The exception path is the proof that the process respects judgment, and the explicit acknowledgment of the exception path is what keeps the standard path from becoming a religion. A firm that has both — a clean standard path and a legitimate exception path — has built the operating system that will let it scale beyond the senior people who currently hold it together. The rest is execution, and execution is easier than building the operating system in the first place.