What Every GC's Sunday Sort Reveals About Legal Ops
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.
A legal department can add capacity when demand grows, at least in principle, but the hours available to the person leading it are fixed by nature. That asymmetry sits at the center of “Leaders Shouldn’t Try to Do It All,” published by A.G. Lafley and Roger Martin in the January–February 2025 issue of Harvard Business Review. Leaders facing lengthening lists of important work respond by working harder and longer, which the authors call a losing game, and their prescription is a discipline of selection: remove the tasks where you hold no absolute advantage, delegate those where your comparative advantage is thin, take on the work where your comparative advantage is strong, and protect enough time for the things only you can do.
Applying that discipline in the general counsel’s seat is complicated by the fact that a legal department runs on two layers. The practice layer is the legal work itself: the advice, the drafting, the judgment. The operational layer is the system that work moves through: intake and triage, assignment and reassignment, chasing status, balancing workloads, keeping the master spreadsheet honest, so that anyone can know what is expected, what is in motion, and what is at risk. The GC sits atop both, and running the Lafley and Martin sort on a GC’s week produces a pile from each.
The practice-layer pile is the familiar one. The legal work that genuinely requires the seat is short: counsel to the board and the chief executive, judgment on risks that reach the enterprise, engagement with regulators and the external relationships that matter most. The rest is work others on the team could do as well, kept close because handing it over feels like exposure and doing it yourself feels like assurance, an instinct the profession trains into everyone who reaches the seat. The costs of the grip are well understood: the leader exhausts herself on work beneath the seat, and the people below never build the judgment that comes from finishing consequential work in their own hands.
The operational-layer pile is the overlooked one, and under Lafley and Martin’s framework it belongs in the first category: tasks where the leader holds no absolute advantage. Nothing in a legal education, and nothing in the years of practice that lead to the GC seat, trains a person to design an intake process, measure throughput, see where work is stuck, or balance load across a team. Operations is a discipline of its own, with its own evidence base, and the team feels every shortfall in it directly. When expectations are set by inference, people guess at what is expected of them. When no one can evaluate performance and risk across the whole book of work, problems surface late and arrive as emergencies. When workloads are balanced by intuition, the reliable people quietly absorb the overflow until their enthusiasm gives out. It is what happens when management work is done in stolen hours by people trained for something else.
The two piles differ in one more way. The practice pile at least has somewhere to go: the team is full of lawyers, and delegating within it is mostly a question of will. The operational pile is harder to place. Most legal departments never invested in the operational layer, so its work defaults upward to the most expensive and least suited person in the room, and it stays there. Removing it, in Lafley and Martin’s sense, means building the capacity to receive it: people, practices, and some way of seeing the department’s work whole.
The sort itself takes a Sunday afternoon and feels like progress. Surviving the week that follows is the harder test, because in most departments the operational layer is embedded in memory, inboxes, and hallway conversation, with no shape anyone can look at. Delegation that can’t be seen can’t be trusted, and delegation that can’t be trusted gets quietly reclaimed: the associate stops at the moment of decision because the authority stayed behind, two people discover they are doing the same work, something important turns out to be nobody’s, and the GC reinserts herself because reinsertion is the only assurance available. The test of whether a department has built an operational layer worthy of the name is whether four questions can be answered well.
What are you responsible for, and how do you know?
What have you delegated, and with what authority?
To whom?
How has that changed over time?
A leader who can answer them holds a map of the department’s work and can watch it move. A leader who can’t is managing on recollection, and the Sunday sort, however honest, will need doing again and again.
Chime In. Be Heard.
The four questions above are easy to read and hard to sit with. If you've actually run them against your own department, the rest of us would benefit from what you found. What surprised you when you tried to answer them? Was there a piece of the operational layer that turned out to be nobody's? Tell us what the sort revealed.
A.G. Lafley and Roger L. Martin, “Leaders Shouldn’t Try to Do It All,” Harvard Business Review, January–February 2025.
mot-r is a Customer-Aligned 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.
