Operating model mapping
An org chart shows who reports to whom. It does not show how a matter moves, where it waits, who touches it twice, or which steps have quietly stopped earning their place. The map is the thing every other decision depends on.
The problem this solves
Ask four partners how a matter gets from a signed engagement letter to a filed document and you will get four different answers, all of them sincere and none of them complete. That is not a failure of memory. It is what happens when a process was never designed, only accumulated, one workaround at a time, across years of people leaving and arriving.
The cost of that shows up everywhere else and gets blamed on other things. Missed deadlines get blamed on workload. Rework gets blamed on carelessness. A tool that nobody adopted gets blamed on the vendor. Underneath all three is the same gap: nobody agreed what the process was, so nobody could tell when it broke.
If the process lives in someone's head, it is not a process. It is a dependency.
What gets produced
A production map of each main matter type, traced against what your systems actually record rather than what people remember. Every step is interrogated the same way, so the map answers questions the firm has never been able to answer consistently:
- Who owns each step, by role rather than by name.
- Where the work waits, and how long it waits before anyone touches it.
- Where it fails quietly, and who finds out.
- Which steps are load-bearing, and which are habit that nothing downstream needs.
That last one is where the surprises are. The interrogation itself is part of the engagement rather than something to hand over on a page.
What changes as a result
The map is not the deliverable. What it unlocks is: a defensible order of work, because you can finally see which bottleneck is upstream of the others; an accountability chart that follows production rather than hierarchy; and a baseline that makes every later claim of improvement measurable rather than asserted.
It also settles arguments. Once the map exists, a disagreement about how the firm works becomes a question with an answer instead of a contest between confident people.
Read the reasoning in full
The thinking behind this is published at length and free to read: why the org chart misleads you and what a production map shows instead. The instruments used to build one across a whole firm are part of the engagement.
What this feeds into
AI adoption policy
The map is what makes classification possible. Without it there is nothing to classify.
See moreIntake and conversion
The front of the map is usually where the largest and cheapest wins are sitting.
See morePractice area economics
Step-level time data is what turns a revenue number into a real margin.
See more