Legal services need product managers

A practice group is a product line. Clients feel the seams. Workshops that treat intake, scoping, and knowledge as a journey, not a precedent archive, are where legal CX actually moves.

Partners already run a portfolio. They choose what to pursue, who to staff, what to decline, what to productise as a panel offering. Naming that as product work changes the operating rhythm. It does not turn a partnership into a startup. It stops the firm pretending that client experience is a marketing brochure.

This is a Customer Experience piece for legal, remounted without the innovation vocabulary that makes partners leave the room. Allens in Australia, through the Linklaters alliance, sits in the same global client physics as Linklaters in London and the other firms on that network. The seams are not a secret: the first email, the scope, the document dump, the knowledge that lives in a partner's head, the bill that arrives as a surprise only to the client.

Why "product manager" is the useful insult

It is an insult only if you think product means an app. Product means a repeating offer with a user, a journey, a quality bar, and someone who can say no to scope.

A project-finance practice, a competition practice, an M&A practice: each is a repeating offer. Allens already packages work for panels and for repeat clients. Linklaters already runs global matters that have to survive time zones and handoffs. The missing role is not always a hire. Sometimes it is a partner-plus-coordinator pair who are allowed to keep a backlog of seams and kill work that is not a matter.

Call them a product pair if the word helps. Call them a service owner if it does not. Give them:

• A punch-list map of the last 20 matters (see our CX maps piece).
• Permission to test a template, a first-email standard, or an intake checklist on the next 20.
• A 21-day look-again.
• A metric partners already believe: time to scoped email, rework, write-offs, client repeat questions.

That is product management. The title can wait.

Partners will not fund a journey map. They will fund a change to the first client email if a partner and an operator sat in the room.

The three seams that always pay

Intake. The client (or the inbound partner) sends a dump. Someone has to say what this is, what it is not, who owns it, and what we need next. Allens coordinators already do a version of this. It fails when three partners assume someone else scoped it. A product move: a one-page intake that is mandatory before hours start, tested on 20 matters.

Scoping. The first substantive email is the product. It names the question, the approach, the team, the clock, and the uncertainty. Linklaters-scale global matters fail when each office scopes a different question. A product move: a scoped-email standard and a 48-hour clock from intake to send, measured.

Knowledge handoff. The precedent archive is not knowledge. Knowledge is what the last matter learned that the next matter needs on day one. A product move: a 30-minute close on every matter that writes five lines into a place the next team will actually open. If they will not open it, you built a graveyard. Kill it and try a tighter ritual.

Everything else (portals, AI summarisation, client apps) is downstream. Firms buy the downstream first because it is visible. The seams are not visible in a pitch. They are visible in the client's Thursday.

What a legal CX workshop has to look like

Partners and operators in the same room. The only mix that produces a residue the practice will fund. We have run that mix. Without the partner, you get a coordinator wishlist. Without the operator, you get a partner speech about excellence.

Walk a real matter, not a persona named "General Counsel Gabrielle." Mark the seams. Assign owners. Pick the smallest test (template, checklist, clock, close ritual). Write the metric. Circulate the one-pager before people leave for a client call.

Do not spend the afternoon on "the future of law." The future of law will still have intake.

Don'ts for innovation teams selling into firms

Don't lead with AI. Lead with the seam. AI might draft the scoped email. It will not assign the owner.

Don't run a hackathon for lawyers on a Saturday. They will not come, or they will come and nothing will ship. Run 5 hours on a Wednesday with a matter file.

Don't measure success as "partners engaged." Measure time to scoped email or rework.

Don't treat Allens and Linklaters as one culture. The alliance is a system. Local practice still has local seams. Test locally. Share the play, not a global mural.

Don't put this in marketing. Put it in the practice. Marketing can have the brochure after the clock moves.

For the managing partner

Pick one practice. Name a product pair (partner + coordinator). Give them 21 days and 20 matters. Require a scoped-email standard and an intake page. Report time and rework. If it moves, expand. If it does not, you learned the seam was elsewhere. That is still a result.

Collective Campus runs legal service-design T&E for that residue. We are not trying to make you a software company. We are trying to make the journey a client would recognise on a punch list.

What "good" looks like in 21 days

A partner can open the last 20 matters and see an intake page on each. A coordinator can tell you who owns every live file. First scoped emails go out on a clock the practice named. Rework on the next similar matter drops because the close ritual was short enough that people did it. Allens can measure that in one practice without a firm-wide programme. Linklaters-shaped offices can measure it on one matter type.

If 21 days later you have a mural and a working group, you ran theatre. If you have a clock and a pair, you ran product. Clients will not send a thank-you note about your working group. They will notice the email.

The 20-matter experiment

Pick one practice. Name a product pair: a partner plus a coordinator. Give them 21 days and the next 20 matters that fit a type you already recognise (a panel stream, a repeating advisory, a familiar dispute shape). Do not pick "all work." All work is how this becomes a transformation programme. Allens can run this in one Australian practice without a firm-wide poster. A Linklaters-shaped office can run it on one matter type. A mid-market firm in Singapore, Toronto, or London can run it on a Wednesday.

Write the rules on a page the pair can hold up in a practice meeting.

1. No hours start without an intake page. What this is, what it is not, who owns it, what we need from the client before the clock runs. If three partners assume someone else scoped it, the page failed. Redo it before anyone bills.
2. A scoped email goes out on a clock the practice named. Forty-eight hours from intake to send, where the matter allows. If the matter cannot allow it, write why on the intake page. Silence is not a reason.
3. A five-line close at the end of each of the 20, in a place the next team will actually open. If they will not open it, kill the location and pick a tighter one. Precedent archives are not knowledge.
4. Look-again on day 21. Time to owner, time to scoped email, repeat client questions, rework on the next similar file. Partners already believe those numbers. Do not add a delight score.
5. Named stopper. The partner on the pair can say no to scope that is not a matter. The coordinator can say no to hours without an intake page. A product line needs a no.

Walk a real file on day one, not a persona named after a general counsel. Mark the seams. Assign the pair. Start the 20. Circulate the one-pager before people leave for a client call.

What "good" looks like is boring. A partner can open the last 20 and see an intake page on each. A coordinator can tell you who owns every live file. First scoped emails go out on the clock. The close ritual was short enough that people did it. If 21 days later you have a mural and a working group, you ran theatre. If you have a clock and a pair, you ran product.

We will not invent a write-off percentage for Allens or anyone else. We will not quote a living partner. We will say the experiment is the smallest test that treats a practice group as a product line. Clients will not send a thank-you note about your working group. They will notice the email.

A practical kickoff sentence:

We are not standing up an innovation function. We are running 20 matters with an intake page, a scoped-email clock, and a five-line close. Day 21 we keep, kill, or rewrite the standard. Marketing can have the brochure after the clock moves.

A scoped email you can steal (generic, not a client)

This is a product artefact. It is the first substantive email. It names the question, the approach, the team, the clock, and the uncertainty. Linklaters-scale global matters fail when each office scopes a different question. Allens-scale panel work fails when the email is late and foggy. Steal the skeleton. Do not paste a real client into a newsletter. The example below is invented and generic on purpose.

Subject: Scope for your question on [plain-language topic], and what happens next

Hello [name],

The question we think you have asked. You want to know whether [specific decision or risk] is likely, what we would need to be more certain, and what you should do in the next [n] days. If that is the wrong question, reply to this email before we go further. We would rather rewrite the question than staff the wrong matter.

What we will do. We will [read the papers you already sent / interview the two people you named / check the specific rule we believe applies]. We will not [open a wide due diligence / start a parallel workstream in another office] unless you ask us to in writing.

Who owns it. [Partner name] owns the advice. [Coordinator name] owns intake, documents, and the clock. If the alliance or another office is in play, [named person] is the handoff. One owner of the question. Extra names are support, not a committee.

Clock. You will hear from us by [date and time zone]. If we are blocked because a document is missing, [coordinator] will ask once, in a list, not in a drip.

Uncertainty. We do not yet know [the fact or the other side's position]. That uncertainty may change the hours. We will say so before we spend them.

What we need from you. A yes that this is the question. The two documents in the list below, if you have them. The name of the person who can answer [one factual gap].

This is not a love letter to legal design. This is a definition of done a coordinator can run. AI might draft a first pass. It will not assign the owner. Do not lead the workshop with a model. Lead with the seam.

Partners will mark this. General counsel-shaped clients will mark this. If a partner refuses to send something this plain, you learned the seam is ego, not knowledge. That is still a result. Write it down in the look-again.

Knowledge close that is not a graveyard

The precedent archive is where good intentions go to be unread. Knowledge, for a product pair, is five lines the next matter needs on day one.

Make the close mandatory on the 20. Time-box to 30 minutes after the substantive work, not a week later.

1. What the question actually was, after it changed.
2. The one rule, clause, or regulator letter that mattered.
3. The document that unlocked the file.
4. The handoff that nearly dropped (office, team, or client-side).
5. What we would do on hour one if this arrived again tomorrow.

Put it where the next team already looks: the matter opening checklist, not a separate wiki that needs a priest. If Allens knowledge and Linklaters knowledge sit in different places, test locally. Share the play, not a global mural. If nobody opened the last ten closes, kill the location. Try a shorter ritual. Do not add a portal.

What the product pair reports to the practice

A practice meeting can live with a half page. It cannot live with a CX showcase.

• Matters in the 20: how many have an intake page and an owner.
• Median time to scoped email, and how many missed the clock.
• Repeat client questions on those emails.
• Closes completed. Closes skipped, with a reason.
• One no the pair issued (scope that was not a matter, hours that were not allowed to start).
• One seam to test next, or a funeral for a standard that did not run.

If the managing partner wants a firm-wide programme after one practice moves, make them fund another 20 in a second practice, not a vendor day. If they want AI, put it on the scoped-email draft after the owner exists. If they want a Saturday hackathon, send them the hackathon piece and offer five hours on a Wednesday with a file.

A practical 21-day brief to the managing partner:

One practice. One pair. Twenty matters. Intake page, scoped-email standard, five-line close. We will report time and rework, not partner engagement. If it moves, we expand to a second practice. If it does not, we learned the seam was elsewhere. That is still a result. We will not book a future-of-law keynote.