The MATTER Method: The Six Things Every Legal Matter Actually Is

Ask a lawyer what a legal practice is made of and you get a list of things: clients, cases, documents, deadlines, courts, fees. All true, none structural. It is like describing a building as bricks, glass and people, accurate, and useless for actually building anything.

I have built roughly 200 systems for lawyers and firms over nine years, starting with no-code tools and following the tooling forward through every generation up to agentic AI today. The question underneath every one of those builds was the same: what is this process actually made of? The answer, after enough repetitions, stopped being a list and became a structure. Six primitives. I call it the MATTER Method.

Why a method, not a checklist

Every profession eventually names its primitives. Accounting found the debit, the credit, the ledger. Software engineering found the function, the repository, the commit. Medicine found the chart, the vitals, the protocol. Law never did this properly. For most of legal history that did not matter, because the constraint on the work was judgement, and judgement lived in people. It stops being survivable once machines can execute a meaningful share of the work, because a machine cannot execute what has never been named.

The MATTER Method is a claim about what matter-based work is actually made of, underneath every practice area, jurisdiction and firm size. All of it decomposes into six primitives: Matter, Actions, Time, Team, Evidence, Research.

1. Matter: the container everything attaches to

The matter, not the client, the document or the task, is the atomic unit everything else attaches to. Most practices are organised around something else entirely: a solo lawyer's inbox, a small firm's people, a document-heavy shop's folder structure. The MATTER position is that the matter itself must be the container, so that if someone asks where a matter stands, the answer exists as a fact you can look at, not a reconstruction performed from memory and three phone calls.

The test: hand a competent stranger one matter file. Could they state its full status inside ten minutes without a single call?

2. Actions: the repeatable moves that resolve it

Within any given matter type, the actions repeat. Two disputes in different cities are rarely the same case, but they are overwhelmingly the same sequence of actions with different facts poured in. Practitioners experience this repetition as expertise, but expertise is often just an action library stored in one person's head, retrievable only by that person and lost when they leave. The MATTER position is to extract the library: a written, ordered, improvable action sequence for every matter type the practice handles.

3. Time: managed, not just recorded

The billable hour trained an entire profession to record time rather than manage it. Meanwhile the two forms of time that actually decide outcomes, deadlines and durations, go largely unmanaged, because nobody named the actions in the first place. The MATTER position treats time as a property of the matter: dates surface themselves before they become urgent, and durations accumulate as real data across every matter, permanently. A practice that knows its true durations can price fixed fees with confidence instead of fear.

4. Team: who does it, who reviews it, who decides

Traditional practice answers this by hierarchy and habit. Work flows to whoever is available, review happens if someone senior has time, and responsibility gets discovered retroactively, usually after something has gone wrong. The MATTER position is that roles attach to actions explicitly. Once roles are explicit, "team member" stops being a category limited to humans. Most organisations cannot safely delegate to AI because they never built a delegation structure for humans either.

5. Evidence: the connections, not the pile

Everything asserted in matter-based work stands on something: a document, a testimony, a precedent, a fact. Evidence is the primitive of grounding, and it is usually the most disorganised of all six. The documents exist by the thousand, but the connections do not; the link between a clause and the page that supports it lives in the drafting lawyer's memory, rebuilt live, under pressure, months later. The MATTER position is that every claim in every draft should be anchored to its source, page and paragraph, as structure, not memory.

6. Research: a stock, not a flow

The traditional model treats research as an event: a question arises, someone researches it, an answer comes back, and the work evaporates into a folder. Next year the same question arises in a different matter, and someone researches it again from zero. The MATTER position is that every question answered should compound into a growing, searchable body of institutional knowledge attached to the matters it served but living beyond them.

The sequence is the doctrine

Name the primitives. Systematise them, moving each one out of memory and into structure. Only then automate them, because that is the point at which machines have something to grip. Most organisations run this backwards, buying automation for practices they have never systematised, built on primitives they have never named, then blaming the tools when it fails. Naming costs nothing but honesty. Systematising pays for itself before any AI is involved. The order is not a preference, it is the whole doctrine.

I put the full worked version of this, worksheets included, in the MATTER Method Playbook. It is the cheapest thing in the store on purpose: it is the map everything else, including my own software, is built on top of.