A Field Guide to the 22 Practice Systems: Which One to Build First

I have now written up all twenty-two practice areas as full lifecycles, stages, vitals, deadline logic, document categories, the works. People ask me a version of the same question after reading a few of them: fine, but which one do I actually build first? Not in the abstract, for my practice.

That question does not have one answer. It has a small number of honest ones, depending on what kind of practice you run. This is the decision guide I wish existed before I wrote the first one.

Start with what actually controls your calendar

The fastest way to sort twenty-two practice areas is by what actually drives the deadline pressure, because that is what a system earns its keep on first.

If your calendar is run by an external body, a court, an agency, a government queue, that is not yours to negotiate, start there. Immigration, tax, bankruptcy and insolvency, and regulatory compliance all share this shape. The deadline logic in each of those lifecycles exists specifically because a human being cannot reliably track a queue they do not control across more than a handful of matters at once. If this describes your docket, the system pays for itself in the first month, because it is replacing a spreadsheet or a sticky note that was already failing.

If your calendar is run by litigation procedure, statutes of limitation, discovery cutoffs, filing deadlines that move when a court reschedules, that is a different shape of pressure. Personal injury, medical malpractice, employment, civil rights, and criminal defense all live here. These systems earn their keep on missed-deadline risk more than on volume.

Then sort by what actually breaks under volume

A second, separate axis: does your practice area break under volume, or under complexity?

Landlord-tenant, insurance defense, and workers' compensation are volume practices. The individual matter is not usually complicated, it is that there are dozens of them moving at once, each at a different stage, each with its own small deadline. A system here earns its keep by making the dashboard, not the matter, the unit of work. You stop asking "where is this one file" and start asking "which files need me today," and that shift alone changes how much docket one person can actually carry.

Corporate transactional, IP prosecution, IP litigation, estate planning and probate, and franchise law are complexity practices. The volume is manageable, but a single matter has enough moving parts, parties, documents, dependent milestones, that tracking it in your head or in email threads eventually drops something. A system here earns its keep on completeness, not throughput.

If you cannot tell which axis you are on, start with intake

A fair number of people reading a practice-area lifecycle post are not actually sure yet which practice area is costing them the most, because they never captured where the work was coming from or how it was actually behaving once it arrived. If that is you, do not start with a practice-area system at all. Start with intake and referral tracking, because it will tell you, with real numbers instead of a hunch, which practice area in your own docket is actually the highest-leverage one to systematise next. I wrote about why this is usually the first leak worth plugging in why client intake is where law firms leak the most revenue.

The honest exception: build around your revenue concentration, not your interest

Every lawyer has a practice area they find intellectually interesting and a practice area that actually pays the mortgage, and they are not always the same one. Build the system for the one that pays the mortgage first. The interesting one can wait. I have watched more than one build stall because someone spent the first month perfecting the system for a matter type that represented ten percent of their docket, while the matter type carrying the other ninety percent kept running on memory and good intentions.

What the twenty-two actually share, underneath the differences

Here is the part that matters more than the sorting logic above: every one of the twenty-two lifecycles is built on the same six primitives underneath. Matters, actions, time, evidence, results. What changes practice to practice is not the structure, it is which primitive carries the weight. In immigration, time carries the weight because of the queue. In IP prosecution, evidence and results carry the weight because a portfolio is a collection of assets, not a single dispute. In personal injury, all six primitives are load-bearing at once, which is part of why that lifecycle reads as the most involved of the set.

This is not an accident, it is the point of building on one method instead of twenty-two unrelated templates. Once you have installed the structure for your highest-leverage practice area, extending it to a second one is fast, because you are not designing from a blank page again, you are re-weighting the same six primitives for a different set of stages.

The actual answer, if you want one sentence

Build the system for the practice area where a missed deadline or a lost file costs you the most, this month, not eventually. Everything else on this list is a tiebreaker for when two practice areas are close.

The Practice Pack Blueprints cover all twenty-two, stages, vitals, deadline logic and document categories already worked out for each, so once you know which one to start with, you are installing it rather than designing it from nothing.