For Lawyers, By Lawyers. Is That Good?
Welcome to Legal Ops Briefs—inspired by the mot-r mindset, this blog series of 3-minute reads gives in-house Legal Ops quick, operational insights. Each post will explore the tech, trends, and tactics that boost operational effectiveness and ease legal team stress—without adding to the noise.
Who built the software and whether it works are different questions. Legal training produces good lawyers. Designing operational systems is a different discipline. “For lawyers, by lawyers” describes the first while implying it delivers the second.
A high-performing in-house legal department has to deliver reliable service to the business, manage organizational risk systematically, and enable the business to adapt with confidence. The proposition that legal practice experience is a sufficient design standard for all three is hubris dressed up as a credential.
The data on how the business actually experiences legal departments is not ambiguous. 73% of legal professionals think the relationship is working. 27% of the people they serve agree. Two-thirds of enterprise employees bypass legal entirely, knowing it breaks policy, because the system has taught them that going around legal is faster than going through it. When people route around legal, they create risk nobody is managing, and that risk eventually lands back on legal’s desk.
77% of in-house legal teams have experienced a failed technology implementation, according to the industry’s own customers reporting on the industry’s own products.
“For lawyers, by lawyers” describes who built the software. It does not address how the software performs for the department that has to use it. A practice credential is being asked to do the work of operational evidence. That substitution is one a lawyer is trained to recognize.
When other business functions have closed a similar gap between what the function believed it was delivering and how the business experienced it, they did so by redesigning the operating model around the outcomes the business actually needed. That work draws on disciplines purpose-built for it: operations management, service design, process redesign, structured client feedback. None of these disciplines are taught in law school, and practice does not reliably produce them. “By lawyers” speaks only to that.
The question that matters is whether the software makes the department work better for everyone who depends on it. Who built it is a different question.
Chime In. Be Heard.
Most Legal Ops professionals have seen the gap between what legal technology promised and what it delivered. If you've been through a successful implementation or a painful rollout, share what you learned. Your experience can help the broader Legal Ops community make smarter decisions about the systems and operating models that will shape the future of legal service delivery.
Sources: Onit/Provoke Insights, Enterprise Legal Reputation Report (2023). Survey of 4,000 enterprise employees and 500 legal professionals across the U.S., U.K., France, and Germany. Onit is a legal technology vendor; the survey was independently administered by Provoke Insights. Technology implementation failure data: ContractWorks/Censuswide (2022), survey of 350 in-house legal professionals. ContractWorks is owned by Onit; the survey was independently administered.
mot-r is the next-generation ELM platform for modern Legal Ops teams. Unlike traditional ELMs, CLM tools, or disconnected point solutions, mot-r provides a low-risk way to resolve the structural causes of legal overload—not just track matters after the fact. By bringing structure to legal intake and visibility to execution, mot-r helps legal teams improve service quality, regain capacity, and reduce burnout. The result is better decisions, higher-value legal service, and an operating model teams can sustain as demand grows.
