Process Mapping & SOPs

Before you automate, consolidate a stack, or deploy AI, you have to know how the work actually moves. Process mapping is the unglamorous foundation under every other legal operations improvement: a clear, agreed picture of how a request travels from arrival to done, who touches it, where it waits, and which steps exist only because they always have. It is the first thing we do in most Legal Operations engagements, because everything downstream depends on it.

The map is not the org chart

How work is supposed to flow and how it actually flows are rarely the same. The official process is in a handbook; the real one is in the shortcuts, the rework loops, and the one person everything routes through. We map the real one, with the people who do the work, because the waste and the risk both live in the gap between the two. The exercise alone often surfaces the change worth making before any software is bought.

What we map, and what we look for

From map to SOP to system

A map on its own is a diagram. The value is what follows: a redesigned process with the dead steps removed, a short standard operating procedure so the new way is the documented way, and a clear specification for what should be automated and what stays human judgement. The SOP is also what makes a process survive a key person leaving, and what a new joiner can actually follow.

Common pitfalls we are brought in to fix

• Mapping the ideal, not the real. A pretty diagram of how it should work changes nothing.
• Boiling the ocean. Map the high-volume, high-pain processes first, not all of them at once.
• Map and forget. Without a redesign and an SOP, the map is a wall poster.
• No measurement. Capture wait times, or you cannot prove the redesign helped.

What good looks like

A team with a clear map of its core processes can see exactly where time is lost, has retired the steps that never earned their place, and has the new way written down so it sticks. That clarity is what makes the next matter-management or automation project land instead of stall.

A worked example

A firm wanted to automate its client onboarding and asked us to build the workflow. We mapped it first, and the map told a different story: half the delay was a compliance check that waited days in an inbox, and two of the eight steps duplicated each other. We removed the duplication, parallelised the compliance check, and only then specified what to automate. The redesign alone cut the timeline before a single line of automation was built, which is the usual lesson: the map is often worth more than the tool, and the team that has it can see exactly where its time goes.

The SOP is what makes it last

A redesigned process that lives only in a consultant’s deck reverts the moment attention moves on. The short standard operating procedure is the durable artefact: the new way, written plainly enough that a new joiner can follow it and a busy lawyer will actually use it. It is also what protects the firm when the person who held the process in their head leaves, turning individual knowledge into something the firm owns rather than rents.

Mapping is the cheapest risk control you have

Beyond efficiency, a clear process map is a quiet form of risk management. It surfaces the steps where a deadline can be missed, the handoffs where a conflict check can be skipped, the points where confidential material changes hands. Naming those before they fail is far cheaper than discovering them in a complaint or a client audit, and it is the groundwork the firm’s AI governance and automation both build on.

How we run the mapping

Mapping is only useful if it captures the real process, which means it has to be done with the people who actually do the work, not inferred from a policy document or a manager’s description. We run short, focused working sessions, walking a real example through end to end, and we capture it in simple, standard notation that a non-specialist can read, not a diagram only a consultant understands. The aim is a picture the team recognises as their own, because that recognition is what gives them the standing to agree the redesign.

A map is also not a one-time artefact. The processes worth mapping are the ones that change, and a map that is never revisited drifts back into fiction. So we leave the firm able to maintain it: the notation is simple enough to update, the SOP is short enough to keep current, and the map is tied to the metrics from reporting so a rising cycle time flags a process that needs re-mapping. That turns process mapping from a one-off cleanup into the start of a continuous-improvement habit the firm owns.

How we engage

We run working sessions with the people who do the work, map the real flow, quantify the waits, redesign with them, and leave a short SOP plus a prioritised list of what to automate next. Fast, practical, and built to be owned.

Where mapping leads

Process mapping is the first step, not the destination. A clear map of how work really flows is what makes automation safe to build, what tells a matter-management implementation which fields actually matter, and what surfaces the risk points a firm needs to control before they fail. On its own a map changes nothing; as the foundation for the work that follows, it is what stops the firm from automating chaos or buying software to manage a process it has never agreed on. We treat mapping as the diagnostic that directs everything else, because the cheapest improvement is almost always the one you find before you have spent money building around a process that should have been fixed first.

The quickest win is often visible within the first mapping session: a duplicated step, an approval that waits days for no reason, a handoff that bounces back half the time. We flag those immediately, because fixing one obvious piece of waste early earns the credibility to tackle the harder redesign. Mapping does not have to be a long programme before it pays; the first clear picture of how work really moves usually surfaces something worth fixing that same afternoon, and that early win is what carries the rest of the effort.