Your legal team can be busy every day and still struggle to explain what an extra hire or a new system would change. A legal operations strategy should answer that question. It connects a business priority to a problem in legal delivery, then identifies an improvement the department has the capacity to carry out.
Start With the Work the Business Needs
CLOC’s 2026 State of the Industry Report draws on a survey of 135 law departments across industries and regions. Only 32% expected attorney headcount to increase. These are survey findings, not a staffing benchmark for every department, but they explain why teams are looking closely at how existing capacity is used.
Begin with a business priority, such as opening a facility or onboarding customers. Ask what legal work it creates and where that work waits. If supplier agreements sit in an inbox because the requester has not identified the contracting entity, the first improvement may be better intake rather than another reviewer.
Choose the Next Commitment
Use CLOC’s Core 12 to check whether the plan overlooks an important part of the legal function. Then narrow the first commitment. Describe the problem, the proposed change and the person who can approve it. Estimate the time required from lawyers and business partners as well as the purchase cost.
For a proposed intake pilot, name the request types it will cover and the people who will test it. Define what improvement would justify expanding it. A roadmap that assigns every initiative to the same already-busy person needs to be revised before it is approved.
| What the Evidence Shows | Appropriate Next Decision |
|---|---|
| Demand Is Poorly Understood | Sample requests and waiting points before funding a system. |
| One Problem Has a Clear Owner and Defined Users | Approve a limited test with acceptance criteria. |
| A Trial Improves Speed but Introduces Quality Issues | Revise the process before expanding it. |
| Quality and Business Effect Are Demonstrated | Consider the next phase against available capacity. |
Worked Example: A U.S. Manufacturer Adds Locations
A manufacturer plans to open two U.S. facilities. Its legal team faces lease questions, supplier agreements and recurring operating requirements. Instead of starting with a new dashboard, the team identifies the requests tied to opening readiness. It selects one shared intake path, a responsibility register and a view of unresolved decisions for an initial trial.
The sponsor chooses the scope and assigns time for the people who will test it. A separate technology purchase waits until the team knows which requirements its existing tools cannot meet.
Review the Choices at Each Milestone
At each review, ask whether the business priority still holds and whether the expected capacity is available. Compare the evidence with the original problem. Fewer incomplete requests may justify expansion; moving the same queue into a new system may call for a different change.
Record the next decision and who will make it. Legal leaders retain professional judgment, and authorized budget owners decide spending. The roadmap gives those people a practical basis for continuing, changing or stopping the initiative.
Experience Across Different Operating Environments
Start with the demands on your own team when you build the roadmap. Jonathan Wu’s work at Niagara Bottling, Oaktree Capital Management, Fisker and Robert Half spanned manufacturing, investment management, automotive operations and professional services. Each environment calls for a different operating model.
At Oaktree, for example, he led Global Entity Management and KYC Operations across 11,280 entities. At that scale, a roadmap needs to specify who owns each record and how updates will reach the teams that rely on it. Use the same questions to choose priorities that fit your team’s workload and capacity.