And Then What? Why Smart Legal Decisions Still Create Bigger Problems.
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.
Legal training produces a specific kind of reasoning. Issue, rule, application, conclusion. It is rigorous, precise, and built for tracing a straight line from cause to effect. This clause caused this breach. This action created this liability. This failure to act produced this harm. It is the intellectual foundation of legal practice, and it is exactly the wrong tool for operational analysis.
In operational analysis, causation is circular. Effects become causes. The root of a problem is often a decision made two stages ago in a different part of the organization, and by the time the effect is visible, the cause is no longer in anyone’s field of view. A department that thinks in lines will consistently misread a system that runs in loops.
The discipline that corrects for this is simple to describe and genuinely difficult to practice: ask “and then what?” three times. First order is the outcome you planned. Second order is the consequence of that outcome. Third order is where the surprises live.
Consider a decision that looks straightforwardly correct. A GC decides not to pursue a technology investment this year. The team is stretched, implementation would be disruptive, and the budget is under pressure. First order: saved budget, avoided disruption, team keeps operating with existing tools. Reasonable. Possibly correct in isolation.
Second order: the investment that was deferred was also the system that would have generated operational data — first response times, volume trends by client unit, workload distribution across the team. Without it, the department continues to manage by instinct. Decisions about staffing, resource allocation, and process improvement are made without evidence.
Third order: eighteen months later, the GC goes to the CFO to request additional headcount. The CFO asks for data. How is the current team’s time allocated? Where are the bottlenecks? What does the current approach cost? The GC cannot answer, because the system that would have produced that data is the one that was deferred. The resource request fails because the evidence that would have made it compelling was never collected. The need is real. The case cannot be made. The data that would have made it — first response times, volume trends by client unit, where matters were actually stalling — was the data the deferred system would have generated.
Or consider the opposite direction: a management response to a visible crisis. After a missed regulatory deadline triggers a board inquiry, new reporting requirements are introduced. Weekly status updates. Escalation procedures. A real-time dashboard for the CLO. First order: leadership feels informed. The specific failure that triggered the response is unlikely to recur in exactly that form.
Second order: the team now spends hours each week producing reports, updating dashboards, and managing escalation workflows. Time not spent on substantive legal work — which increases the volume problem that contributed to the original failure. And the reports are compiled manually, duplicating information that a functioning system would capture once.
Third order: the most capable people on the team read the reporting burden as a signal that leadership does not trust them to manage their work. Engagement drops. Two of them begin exploring other options quietly. The intervention meant to slow the cycle accelerated it, while eroding the intrinsic drive of the people most able to leave.
In both cases the decision was reasonable. The leader who made it was well-intentioned. The first-order outcome was exactly what was planned. Reasonable decisions, made by well-intentioned leaders, produce these outcomes inside systems that cannot be fully seen from any single position within them.
The practice of asking “and then what?” does not require certainty about what will happen. It requires looking further than the first-order outcome before committing to a course of action. Map which parts of the system a decision will touch. Trace the positive chain as well as the risks — a technology implementation that frees attorney time for strategic work produces second and third-order effects worth identifying, not just the first-order cost saving. Apply the same discipline to the consequences you intend as to the ones you are trying to avoid.
The system will teach you things no amount of planning could have predicted. But only if you are paying attention to what actually happens, not just what you planned.
Chime In. Be Heard.
Where have you seen first-order thinking create second- or third-order challenges in your organization? What practices have helped you—and your stakeholders—step back and ask “and then what?” Your experience navigating these loops, tradeoffs, and unintended outcomes can help the broader Legal Ops community move beyond linear thinking—and build more resilient, insight-driven operations.
This post draws on the second paper in the mot-r Foundation Series, Seeing the System: Why Your Legal Department’s Problems Are Connected and What to Do About It, available at mot-r.com/foundation-series.
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.
