Implementing legal operations around the capabilities the business needs
Implementing legal operations requires deciding what the legal function needs to be able to do and how to sustain it in everyday work. This guide brings together questions of diagnosis, design and governance from The Legal Function as a System. It helps define a manageable intervention and revisit its conditions as work progresses.
Daniel AcevedoDefining the need before committing to a solution
A complaint such as 'Legal takes too long' deserves attention but leaves several explanations open. In an illustrative contracting situation, the delay might arise from incomplete requests, unclear approval authority or a negotiation requiring specialist analysis. Diagnosis examines where it occurs, whom it affects and which decision loses value while an answer is pending. This account gives people a shared purpose for discussing alternatives.
The definition of need describes the current condition, the contribution sought and the reason for acting now, without naming a platform, supplier or new role. The depth of diagnosis should reflect the commitment involved. A small, reversible exploration can begin with uncertainty; a reorganisation or an integration that is difficult to unwind requires greater clarity about its consequences.
The capability and its dependencies
The book defines capability as what an organisation can do deliberately and repeatedly to fulfil a purpose. Daniel develops The LaitHaus Method and its application, LTH In-House, to examine that question through four dimensions, fifteen development factors and eighty-two capabilities. The map connects leadership, legal work, protection and operations. Its dimensions are concurrent perspectives; they do not prescribe departments or mandatory implementation stages.
The team selects the capabilities relevant to the need and defines what will change now. The analysis makes dependencies visible even when they sit outside the initial scope. CLOC Core 12 and the ACC Legal Operations Maturity Model 2.0, compared in the book, retain their own authorship and uses. They can coexist with LTH In-House. Their categories cannot be mapped to one another through an automatic one-to-one correspondence.
How the work will operate
The design describes future operations from beginning to end: how a need enters, who recognises its nature, what information supports the decision and who handles an exception. It assigns authority alongside responsibility and identifies the authoritative source of current templates or guidance, including who can update or withdraw it. The people who will maintain the service after the project take part while the design is still open.
Technology has a specific role within that arrangement. The intervention might also clarify a responsibility, simplify a policy or improve access to knowledge. A pilot needs tasks and participants close to ordinary operations, explicit boundaries and a decision that learning can change. A favourable trial does not by itself establish that the solution will work at a different scale.
Governance while the service continues
The same people often handle daily matters and contribute to transformation. A review of initiatives together reveals how they may compete for specialists, decisions, data or users' time. Protecting capacity means deciding which work will be postponed, reduced or supported by additional resources. Assigning someone to a project is difficult to reconcile with leaving every existing obligation untouched.
Sponsorship should protect the purpose and enable decisions beyond the team's authority. Governance establishes who can approve changes, accept temporary conditions or stop an intervention whose justification has weakened. Transition arrangements clarify which requests use each route, who resolves exceptions and how essential work will continue. These conditions are reassessed before scope expands or further resources are committed.
Assessing the contribution and preparing for continuity
Measures are selected around specific decisions. Response time requires a defined start and end, population and period. The assessment considers quality, rework and effort transferred to other functions alongside speed. Available licences, recorded activity and adoption describe different phenomena. A change in definition can invalidate a trend even when each number is individually correct.
The handover requires named owners, resources, access, knowledge and unresolved matters. Institutionalisation means being able to maintain, correct or retire the practice without relying on the temporary team. Repeated questions, alternative channels or growing dependence on one person may indicate deterioration. The response calls for an examination of what has changed and adjustments to operations. Closing the project should leave learning active.
Questions for the next implementation decision
- Does the need remain clear when the proposed solution's name is removed?
- Which capability must endure, and which dependencies shape its development?
- Who decides, handles exceptions and takes ownership after the project?
- Which work will change to create real capacity during the transition?
- What evidence will support reassessment, and who will maintain the practice?
A capability may be sustained with simple tools and require no permanent project.
The Legal Function as a System, chapter 22
About this guide
An editorial adaptation of Chapters 1–5, 8, 18 and 21–24 of The Legal Function as a System by Daniel Acevedo. This guide uses new wording to synthesise the material. Its five sections are not a universal implementation sequence or a transcription of the book.
View the book on Amazon