Back
Engineering In-House Legal Team Performance
Why In-House Legal Teams Cannot Scale Without a Deliberate Human Capital System
7 mins • 17 Jan 26
“Legal performance doesn’t break because lawyers aren’t capable. It breaks because the system they operate within was never designed to scale. When performance is engineered — not improvised — capability finally compounds.”
Matt Glynn, Director – GLS Group
Engineering Legal Performance
How the GLS Human Capital Line Makes Performance Scalable
1. Executive Premise: Performance Is an Engineered Outcome
Legal performance does not scale naturally. We covered this extensively in our knowledge piece Managing Lawyers to Engineering Legal Performance - Why Traditional In-House Legal Models No Longer Scale.
For much of the profession’s history, in-house legal teams operated in environments where this did not matter. Work volumes were lower, timing pressure was episodic, and legal advice moved at the pace of scheduled meetings, paper files, and considered correspondence. Performance could be inferred from competence and experience because the system was forgiving.
That environment no longer exists.
Modern in-house legal teams operate in an always-on, high-velocity environment where legal demand is continuous, timing pressure is constant, and the cost of delay is visible immediately. In this context, performance does not emerge from talent alone. It depends on whether the system lawyers operate within has been deliberately designed to allow performance to scale, repeat, and endure.
The question facing legal leaders is no longer “are our lawyers good enough?”
It is “is the system they work within engineered for performance at scale?”
2. What “Engineered Legal Performance” Actually Means
Engineered performance is defined by outputs, not inputs.
It is not measured by seniority, headcount, or training spend. It is measured by whether legal can deliver consistently, predictably, and sustainably as demand grows and conditions change.
Engineered legal performance is characterised by:
◼️ Consistent legal judgment across people and matters
◼️ Predictable throughput and decision velocity
◼️ Ability to scale without linear headcount growth
◼️ Clear authority and escalation boundaries
◼️ Verified quality, not assumed competence
◼️ Sustainable capacity that survives churn
If these outcomes are not present, performance is not engineered — it is improvised. Many legal teams operate closer to improvisation than they realise.
3. Why Traditional Legal Talent Models Cannot Produce These Outcomes
Traditional in-house legal talent models were not irrational. They were simply designed for a different operating context.
They evolved when:
◼️ Work volumes were materially lower
◼️ Timing pressure was episodic rather than constant
◼️ Legal demand was batch-based, not continuous
◼️ Advice cycles were slower and more forgiving
◼️ Email, instant escalation, and real-time decisioning did not exist
Within that context, it was reasonable for:
◼️ Authority to remain informal
◼️ Legal method to live in individual judgment
◼️ Capability to reside in people rather than systems
◼️ Performance to be inferred rather than measured
◼️ Sustainability to be assumed rather than designed
Those assumptions no longer hold.
What matters now is not whether these models were once sufficient, but whether they can be optimised to produce engineered outcomes in today’s environment. They cannot — because they were never designed to function as performance systems.
4. Performance Engineering Requires a System, Not Interventions
When performance strain appears, legal teams typically respond with interventions:
◼️ More training
◼️ More hiring
◼️ New tools
◼️ Greater leadership intensity
Each can help at the margin. None can engineer performance on its own.
Performance engineering requires simultaneous design across multiple causal dimensions — authority, method, structure, infrastructure, enablement, measurement, and sustainability — operating together as a system. Addressing one in isolation simply shifts the constraint elsewhere.
This is the point at which most legal transformation efforts stall. Not because of lack of intent, but because performance is being treated as something to improve, rather than something to engineer.
5. The GLS Human Capital Line and the System Beneath It
The GLS Human Capital Line is the navigable interface to a deeper performance engineering system.
The Line does not create performance. It allows legal leaders to see, explore, and diagnose the system conditions that either enable or constrain performance.
Beneath the Line sit eight foundational dimensions. These are not thematic buckets or improvement categories. They are the architectural components of a deliberately designed system that engineers legal performance.
The Line makes that system visible.
The system is what actually does the work.
6. How the Eight Dimensions Engineer Legal Performance
It is important to be explicit about what follows.
The eight dimensions below are not initiatives to be implemented independently. They are the interacting components of a performance engineering system. Performance only emerges when the system is operated as a whole.
Each dimension:
◼️ Removes a specific performance constraint
◼️ Forces design decisions most legal teams avoid
◼️ Produces observable or measurable performance effects
6.1 Mandate & Authority
Constraint removed:
Ambiguity over what legal does, what it is responsible for, and where accountability sits.
In high-velocity environments, unclear mandate generates rework, defensive behaviour, and internal friction. Energy is spent managing boundaries instead of delivering outcomes.
Design forced:
◼️ Explicit ownership of decisions
◼️ Clear escalation thresholds
◼️ Defined accountability for outcomes, not just advice
Performance effect:
◼️ Fewer border skirmishes
◼️ Faster decisions
◼️ Clearer accountability
◼️ Energy redirected from politics to performance
6.2 Legal Method (Processes & Procedures)
Constraint removed:
Inconsistent judgment and person-dependent outcomes.
Judgment that lives only in individuals cannot scale. It fragments under volume and collapses under churn.
Design forced:
◼️ Codified legal approaches embedded in processes and procedures
◼️ Explicit treatment of risk calibration
◼️ Clear standards for when judgment is applied, escalated, or constrained
Processes and procedures are not documentation. They are the mechanism by which legal judgment is institutionalised.
Performance effect:
◼️ Repeatable outcomes
◼️ Scalable quality
◼️ Predictable risk application
◼️ Ability to scale support without linear headcount growth
6.3 Team Selection & Composition
Constraint removed:
Capability mismatch and senior-lawyer bottlenecks.
Teams built without deliberate organisation design inevitably over-rely on senior lawyers and under-utilise system leverage.
Design forced:
◼️ Role clarity based on work type and judgment intensity
◼️ Deliberate staffing models
◼️ Use of agile and flexible resourcing as capability augmenters
Performance effect:
◼️ Improved flow
◼️ Greater output per lawyer
◼️ Increased strategic capacity
◼️ Better cost effectiveness
6.4 Essential Operating Infrastructure
Constraint removed:
Friction, waste, and invisible performance drag.
Without infrastructure, legal teams operate on sand. No amount of effort can stabilise performance without foundations.
Design forced:
◼️ Non-negotiable operating systems
◼️ Data structures that make work visible
◼️ Processes and procedures treated as operating infrastructure, not reference material
Performance effect:
◼️ Stable throughput
◼️ Production-level delivery capability
◼️ Visibility into demand and capacity
6.5 Team Enablement
Constraint removed:
Execution drag that sits above infrastructure.
Even well-designed systems underperform when lawyers cannot access guidance, knowledge, or tools at the point of need.
Design forced:
◼️ Removal of avoidable friction
◼️ Embedded access to templates, guidance, and precedents
◼️ Enablement designed around how work is actually done
Performance effect:
◼️ Faster execution
◼️ Greater confidence in delivery
◼️ Reduced dependency on individual memory
6.6 Lawyer Development & Progression
Constraint removed:
Capability stagnation and attrition.
When development is informal and progression opaque, capability does not compound.
Design forced:
◼️ Explicit progression logic
◼️ Capability-based development pathways
◼️ Objective readiness assessment
Performance effect:
◼️ Compounding capability
◼️ Stronger bench depth
◼️ Reduced key-person dependency
6.7 Securing Team Performance
Constraint removed:
Unverified outcomes and assumed value.
Performance that is inferred cannot be improved or defended.
Design forced:
◼️ Explicit performance metrics
◼️ Feedback loops tied to outcomes
◼️ Accountability mechanisms
Performance effect:
◼️ Measurable value creation
◼️ Continuous improvement
◼️ Credible conversations with the business
6.8 Continuity, Governance & Sustainability
Constraint removed:
Capability loss through churn.
Without institutionalisation, performance resets every time someone leaves.
Design forced:
◼️ Codification of knowledge and method
◼️ Governance that reinforces standards
◼️ Sustainability treated as a design objective
Performance effect:
◼️ Resilience through change
◼️ Durable capability
◼️ Reduced burnout risk
7. Why the Dimensions Must Operate Together
Performance does not emerge from isolated excellence.
◼️ Strong method without authority creates compliance drag
◼️ Infrastructure without method amplifies inconsistency
◼️ Measurement without development drives gaming
◼️ Sustainability without structure merely slows decline
Performance is an emergent property of the system, not the sum of its parts. This is why the Human Capital Line is explored as a whole — not implemented sequentially.
8. Using the Human Capital Line in Practice
At the station level, the Human Capital Line allows legal leaders to:
◼️ Understand what each dimension covers
◼️ See the value it brings to the business and to legal
◼️ Understand the cost of getting it wrong
◼️ Access optimisation strategies and supporting intelligence
This enables leaders to diagnose where performance is constrained and design a targeted, engineered response rather than a generic transformation programme.
9. Why This Is Now a GC-Level Leadership Issue
Expectations on legal have changed.
Boards expect evidence, not reassurance. Businesses expect velocity, not explanation. Talent markets are tightening, and endurance is no longer a viable strategy.
Performance engineering cannot be delegated. It requires leadership decisions about authority, method, investment, and design.
This is now squarely a GC-level responsibility.
10. Conclusion: From Managing Lawyers to Engineering Performance
The evidence is now clear.
◼️ The old model does not scale
◼️ Performance cannot be improvised at enterprise level
◼️ Legal performance must be engineered
The GLS Human Capital Line exists to make that system visible and usable. What sits beneath it is the performance engineering logic required to let legal performance scale, repeat, and endure.
Matt Glynn – Final Word
Legal performance does not improve because lawyers work harder. It improves because the system they operate within has been deliberately engineered to let performance emerge.
Tips & Observations: Performance Engineering Legal Talent
◼️ Performance emerges from system design, not effort: Legal teams improve when constraints are removed and design decisions are made explicitly — not when lawyers simply work harder or longer.
◼️ Authority clarity unlocks throughput: When legal mandate and decision rights are explicit, teams spend less energy on boundary disputes and more on delivery.
◼️ Codify method, don’t rely on memory: Processes and procedures are the mechanism by which legal judgment becomes repeatable and scalable — without them, performance remains person-dependent.
◼️ Organisational design drives flow: A deliberate staffing model focused on role clarity and agile resourcing produces higher output per lawyer and smoother work flow than headcount expansion alone.
◼️ Infrastructure is foundational: Systems, data visibility, and standardised workflows are not optional accessories — they are the surfaces on which performance is built.
◼️ Enablement eliminates friction: Providing lawyers with templates, guidance, and point-of-need support removes execution drag that infrastructure alone cannot address.
◼️ Development must be systemic: Progression tied to capabilities (not tenure) allows capability to compound and builds resilience against churn.
◼️ Measure what matters: Performance that is inferred cannot be improved. Explicit metrics and feedback loops anchor continuous improvement and business credibility.
◼️ Continuity beats churn: Institutionalising knowledge and governance prevents capability loss when people leave and ensures performance endures through change.