Get your firm's free AI report card
BLOG POST · SOLO & SMALL FIRM PRACTICE

Lawyers, Map the Process Before You Automate It

TL;DR
  • A lawyer can't hand a process to an AI agent, or a new hire, if it only exists in the lawyer's head.
  • Map the process as it actually runs today, with every step, delay and hand-off, not as you wish it ran.
  • Start with the business side of the practice, like intake and billing, and keep your own thinking on the legal work.

Every AI workflow in a law firm starts as a process map, whether anyone drew it or not. An agent can only follow steps that someone has written down, and most solo practices run on steps that live in one lawyer's head. Before you automate intake, billing or anything else, draw it. A course in the Solo Practice University archive, recorded years before large language models, explains how.

Your AI is only as good as the process you give it

John O'Connor, founder of Associate and SPU's Professor of AI Fluency, sees the shift this way:

"AI is shaped by code and context, which gives lawyers an opportunity to build their own AI."

Context is the part lawyers control. It's your intake questions, your conflict check, your billing routine, the order you do things in and the reasons why. A generic chatbot has none of that. Your firm's AI is the version that does.

"Opinionated, agentic process informed by deep subject matter expertise will be a feature of the AI future."

Note the word "process." An agent that runs your intake needs to know where intake starts, what happens next, who decides what, and when it's finished. If you can't say those things out loud, you can't hand them to software. You can't hand them to a paralegal either, which is the older version of the same problem.

"If it's a process, it can be mapped"

The course is Lean Six Sigma for Solos, recorded for SPU between 2013 and 2015 and taught by Nora Riva Bergman and Liz Lamar. Its class on process mapping opens with a line from W. Edwards Deming that the course returned to more than once:

"If you can't describe what you are doing as a process, you don't know what you are doing."

The course's diagnosis of the typical firm hasn't aged a day:

"The processes that run your firm, however, all too often are just in your head. They are not written out anywhere."

A process map, as the course defined it, is "a pictorial sequence of actions" that make up a complete process. If you've drawn a flowchart, you've drawn one. The difference is what you do with it: a flowchart describes the work, while a map is a tool for improving it.

The course made a point that matters more now that AI is in the office. In a law firm, the work is mostly knowledge, and knowledge doesn't move down an assembly line where you can watch it:

"That work in your office is often invisible. It's knowledge, it's time, it's thinking, mapping the process makes that work visible."

Invisible work is also invisible waste. If you can't see the steps, you can't see the ones that repeat, stall or don't need to exist. And you can't tell an agent which ones to skip. (The course quoted David Allen's Getting Things Done on this: "your mind is for having ideas, not holding them." SPU has written before about getting that thing done the same way.)

How the course said to draw the map

The method is deliberately low tech. Sheets of paper on a wall, a sticky note for every step, then a photo of the finished wall so you keep a record. The rules around it are what make it work.

Pick one process. Client intake, conflict checking, billing, preparing for a deposition. One at a time.

Include everyone who touches it. If it's just you, that's fine. If a paralegal does half the steps, the paralegal is in the room, because they know things about the process you don't.

Map what happens now. This was the rule the course leaned on hardest:

"Map exactly what happens. Every single step, every single delay, every single person that touches the work as it moves through the process…"

The temptation is to draw the process you'd like to have. Don't. Without an honest current state, you have nothing to improve from. A guest session in the mapping class put it bluntly: "You'll be surprised when you see what really happens, not what you think happens."

Agree where it starts and ends. Does intake begin with a phone call, a web form or a referral from another lawyer? Often all three, and each is its own starting point with its own next step.

From there, the course laid out four steps: map the current process, analyze it, design a better one, and document the new process.

From your head to a process anyone can run

1Map the current stateEvery step, delay and hand-off
2Analyze itStalls, delays, duplicate work
3Design a better oneOften one small tweak
4Document itReady for staff, or an agent
The four steps are the course's. Handing the documented process to an AI agent is the modern addition.

What the map shows you

Once the wall is full, you read it for trouble. Where do potential clients get stuck waiting for a call back? Which steps take the longest? Is anyone doing work someone else already did? The course described mapping sessions where one person says "I do that" and another says "I do that too," and nobody had known.

The guest session gave a measurement worth stealing: the difference between process time, the time someone actually spends working, and lead time, which adds all the waiting. Their example:

"…the simple step of having a lawyer open an email and review a short draft reporting letter to clients has a process time of less than five minutes, but a lead time of somewhere between two to four weeks, depending on the attorney."

Five minutes of work, weeks of waiting. No AI tool fixes that if nobody can see it. Automate the drafting and the letter still sits in the same inbox.

The course also reminded lawyers that the "we don't make widgets" objection misses the point. Law has art in it, and the course called that art "really our greatest value add." But the art sits on top of routine, and "a process is like a recipe. It's all of the essential steps that you have to follow." Map the recipe so you have more time for the art.

Start with the business side

Which process should you map first? O'Connor's advice on adopting AI points in one direction:

"Use AI to delegate everything around the practice, the business side."

That means intake admin, scheduling, billing, file opening and the documents about the practice rather than the legal work itself. These are the processes the course called administrative, and they are the easiest to map because they repeat. They are also the ones SPU has long argued solos neglect when managing the business side of the firm. The legal work, the thinking and the judgment, stays with you.

Intake is the classic first map, and it's a good one. It has clear starting points, it repeats every week, and the hand-offs are where leads fall through. If your intake starts with a web form, follow that thread back to the source. SPU offers a free law firm website review if you want a second pair of eyes on where your inquiries begin. And if you already use a standardized intake form, the form is half your map.

From map to agent

Here's where the old course meets the new tools. Anthropic's guide to building effective agents separates two kinds of systems. Workflows are "systems where LLMs and tools are orchestrated through predefined code paths." Agents are "systems where LLMs dynamically direct their own processes and tool usage." Either way, someone has to know the process first: you either write the path, or you give the agent enough of it to direct itself. The same guide recommends "finding the simplest solution possible, and only increasing complexity when needed."

Anthropic's Agent Skills for Claude make the connection even plainer. Anthropic describes them as "organized folders of instructions, scripts, and resources," and its documentation says they're organized "like an onboarding guide you'd create for a new team member."

That's a documented process map. The course pitched maps for exactly this use years ago, as a training tool for a new assistant, and as a way to capture what one guest called "the knowledge that is locked in the brains of your colleagues." The reader has changed. The document hasn't.

One line from the course explains why this doesn't hand your practice to a machine:

"…you're not going to actually do everything associated with the work in your office but you're going to know how it should be done and how you want it to be done. Those are two very very different things."

That's the role of a lawyer running agents: knowing how the work should be done, and checking that it was. It's the same skill as delegating to people. Before you put client information into any tool, check your own jurisdiction's rules on confidentiality and supervision.

Before you hand a process to AI

  • It's on paper. Not just in your head.
  • It's the real process. Current state, not the wish list.
  • It has clear start and end points. One per way in.
  • Delays are marked. Lead time, not just work time.
  • It's business-side work. Your judgment stays with you.
Drawn from the course's mapping rules and John O'Connor's advice to delegate the business side first.

Build the infrastructure now

None of this needs to be a big project. The course's advice was to start with one simple process, and to remember that "it might just be one little tweak" that makes the difference. One map a month is twelve processes a year that your staff, your future hires and your AI tools can follow. It's also the clearest picture you'll ever have of what your knowledge work really is.

O'Connor sees BigLaw's AI push sending a new kind of lawyer into the practice areas solos have long owned, and that makes the timing plain:

"It changes the landscape, and makes it more important to build infrastructure now."

A process map is infrastructure. It's cheap, it's yours, and every AI tool you adopt later will run better on it. For more on tools and practice systems, see our technology coverage.

Take the course: Before You Build

The course behind this post has been adapted for the AI era and is live in the SPU community as Before You Build: Mapping Your Practice for AI, included with SPU membership. Process mapping is one part of it. It also covers value and waste, Kaizen and DMAIC, 5S, knowledge management, and worksheets you can use on your own practice. SPU membership gets you the community, monthly strategy sessions and the full course library.

THE WEEKLY SPU BRIEF

Get one practical lesson for your firm every week.

Free, from practicing lawyers. Every issue includes a lesson from the archive. Unsubscribe anytime.

ABOUT THE AUTHOR
The SPU Team

The SPU Team writes and edits Solo Practice University's articles. Susan Cartier Liebel founded SPU in 2009 to teach lawyers the practical side of building a practice, the part law school leaves out, with courses taught by practicing lawyers. Today SPU is a community for solo and small-firm lawyers, with an AI Fluency program for firms putting AI to work. Nothing here is legal advice: check your own jurisdiction's rules.

About Solo Practice University →