Roles, Not Names

Ask who owns intake at your firm and you’ll get a name. Ask who owns it when that name is on vacation, on leave, or on the way out the door — and you’ll get a pause. That pause is the sound of a firm built around people instead of roles.

Building around names feels natural. Karen is great at intake, so intake becomes Karen’s thing. It even works — right up until Karen is out for a week, buried in volume, or gone for good. Then you discover that the firm never owned the intake process at all. Karen did. And she took it with her.

The fix is a design move, not a hiring move: assign ownership to roles, not people. People change; roles persist.

Ownership pinned to a person walks out the door when they do.

Law Firm Architects · Delegation Machine, Worksheet 3

01The name trap

When ownership belongs to a name, every process becomes a negotiation. Work doesn’t move because a stage was designed to hand it off; it moves because someone asked someone else, personally, as a favor. That’s not an operating system. That’s office diplomacy. And it fails in predictable ways:

• Turnover erases the system: when the person leaves, the process leaves with them — there was never anything else holding it.
• Every handoff is a negotiation: work moves by favor and memory, so it moves at the speed of the relationship, not the design.
• Cross-training has no target: you can’t train someone into Karen. You can train someone into a defined role.
• Accountability blurs: “that’s her thing” ends every improvement conversation before it starts.

02Roles persist. People change.

A role is a stable slot in the design: a named bundle of stage ownerships, each with a definition of done. Intake Owner is a role. It owns the intake stage, its entry trigger, its exit condition, and the standard the work has to meet. Who fills that slot this quarter is a staffing decision — a completely separate question from how the firm works.

Separate those two questions and everything gets calmer. The design question gets answered once, in writing. The staffing question gets answered as often as life demands — without touching the system.

03Build the Role Ownership Matrix

This is Worksheet 3 of our Delegation Machine, and it fits on one page. Rows are the stages of your case lifecycle. Columns are three: the role that owns the stage, what that role does inside it, and what done looks like. No people anywhere on the page. If you catch yourself writing a first name in the owner column, stop — you’re documenting the current workaround, not designing the firm.

04What changes on Monday

You don’t need a reorg to start. List the stages of your highest-volume case type. For each one, write the role that owns it — invent the role names if you have to. Then, on a separate line, map your actual people to those roles. If one person currently fills three roles, fine. Write it that way. Now the load is visible, the hiring plan writes itself, and the day that person is promoted, out sick, or gone, you reassign a role — you don’t rebuild a firm.

The goal isn’t to make people interchangeable. It’s to make the system independent of any one of them — so your best people can take a vacation, take a promotion, or take a risk without the firm holding its breath.