Stop Managing Cases. Design the Pipeline.
Every case you personally shepherd is you doing the system’s job by hand. Design the path once and the work travels it without you standing at every corner.
Open your case list. Look at how you actually move through it. You check what happened on this one, decide the next step, nudge someone, come back tomorrow, decide again. Forty cases, forty separate acts of judgment, repeated every week. That is not management. That is you performing the operating system manually, in real time, with your own hands.
It feels productive because things move when you touch them. That is exactly the trap. Every case that only advances because you looked at it is proof that nothing was designed to advance it for you. The firm does not have a process. It has you, running the same decisions over and over on slightly different facts.
If the case moves because you looked at it, you don’t have a pipeline. You are the pipeline.
Law Firm Architects · Process Design
01Case-by-case management is a design failure
Managing individual cases is the most expensive possible way to run a firm, because the cost scales one-for-one with volume. Twice the cases, twice the decisions, all landing on the same desk. There is no leverage in it — only endurance, and endurance runs out.
Worse, it produces inconsistency at the exact moment you are trying to build a reputation for reliability. When each matter is steered by whatever you noticed that day, the client’s experience becomes a function of your attention span. Two clients with identical matters get two different firms.
- Decisions repeat: the same routing call gets made forty times instead of once.
- Nothing compounds: last week’s judgment is not captured anywhere the team can reuse.
- Attention becomes the constraint: whatever you did not look at, did not move.
- Quality drifts: outcomes track your bandwidth instead of a standard.
02A pipeline is a decision you make once
A pipeline is not a board, a status column, or a folder structure. It is the designed path a matter travels from first contact to closed file, built so the path itself carries the case forward. Four things make it real, and all four are written down before a single case enters it.
Stages. The named steps a matter passes through — not a task list, but a sequence of designed states, each with a beginning and an end.
Owners. One role accountable for each stage. Not a person by name, a role — so the design survives the day someone resigns.
Triggers. The specific event that pulls a case into the next stage. Without one, cases start by accident and you become the human start button.
Handoffs. What moves, in what format, to which role, and how the sender knows it landed. This is where momentum dies in every undesigned firm.
Default / Managing Cases
- Decide per matter
- Owner routes everything
- Movement follows attention
- Cost scales with volume
- Experience varies by client
Designed / Pipeline
- Decide once, apply always
- Stage owners route
- Movement follows triggers
- Cost scales with design
- Experience is standard
You are not supposed to manage forty cases. You are supposed to manage one pipeline that forty cases run through — and then fix the pipeline when a case gets stuck in it.
03What changes the week it exists
The first visible shift is the nature of your questions. You stop asking “where is the Delgado matter” and start asking “why do matters sit in stage three for nine days.” One of those questions you have to ask forty times. The other you ask once, and answering it improves every case at the same time.
The second shift is who gets interrupted. When a stage has an owner, a trigger, and a written exit, staff stop routing decisions upward because the answer is already in the stage. Your calendar quietly empties of status conversations.
The third is that problems become visible as patterns instead of emergencies. A case stuck in a designed pipeline is a data point about the design. A case stuck in an undesigned firm is a fire, and fires only ever get handled by the person holding the hose.
04Build one pipeline this week
Do not attempt the whole firm. Take your highest-volume case type — the one you run most often and understand best — and lay its stages on a single page in order. Six is usually enough. Ten means you are writing tasks, not stages.
Then, for each stage, write four lines: who owns it, what event starts it, what must be true to leave it, and what gets handed to whom when it ends. That is an afternoon of work, not a quarter. When it is done, stop touching individual cases in that track for one week and watch where they pile up. The pile is the design flaw, and now you can see it.
This is the shift that separates a firm you run from a firm that runs. You are still accountable for the work — you are just accountable at the level of the system instead of the matter. Design the pipeline, and every case that enters it inherits the best version of your thinking. Manage cases, and each one only ever gets whatever attention you had left that day.
Luis designs law firm operating systems — the people, process, and technology architecture that lets a firm grow without running on burnout. He writes The Blueprint every week.
Ready To Design Your Firm?
If every case still moves because you moved it, we’ll help you design the pipeline that carries them — stages, owners, triggers, and handoffs built around how your firm actually works.
Book Your Free Strategy Call →