Pattern Counsel is written for General Counsel, Chief Legal Officers and their teams — and for the law firms, legal operations professionals and technology providers who work alongside them. This work is AI-assisted — read about how I work.

Pattern Counsel reflects my vision of how in-house legal functions could work. Many General Counsel will see it differently.

Introduction

Being inside is not the same as learning from inside.

The first instalment of Pattern Counsel argued that legal value compounds through embeddedness. Being inside the enterprise produces a different kind of knowledge, and each cycle of presence can sharpen the next judgment.

The second looked more closely at what “inside” means. Position matters: where legal sits, who it reports to, which rooms it can enter. But position does not guarantee presence across the enterprise’s work. Processual embeddedness is something different: legal being present in the phases where the enterprise’s work creates, manifests or exposes legal risk.

There is another consequence of that distinction. Processual embeddedness does not simply put legal in the work early enough to influence it. It puts the lawyer inside an experience from which she can learn — seeing choices being made, living with what happens to them and remaining present when the consequences become clear.

That changes the lawyer.

Changing the lawyer is not the purpose of embeddedness. The purpose is what the enterprise can do differently because legal is there.

What do you know?

A month before I became Head of Group Legal South Africa for a multinational mining company in 2010, I met one of the general counsel whose world I was about to enter. He had been in the system for years. I had not.

He looked at me across the table. “What do you know?”

It was a formidable question because he knew an enormous amount. Mining law. Regulatory history. The institution. The matters that had shaped it. I knew very little of that. For a while I tried to catch up.

It was miserable.

There was always another piece of legislation, another regulatory turn, another fact buried in years of correspondence or litigation. What I understood only later was that there were different ways of being inside. That veteran of Group Legal was profoundly positionally embedded. Years inside had given him knowledge I could not reproduce by reading harder.

But position is not the same thing as being embedded in the processes through which the enterprise does its work.

My mistake was thinking the answer to “What do you know?” was simply to know more law.

The more consequential opportunity was to get further inside the work.

Learning from the process

A lawyer can know almost everything about a matter without having experienced the process that produced it. An external lawyer can reconstruct a transaction from the papers. A litigator can reconstruct a dispute. A regulatory specialist can master the history of a permit. All may know more law than the lawyer inside.

Processual embeddedness offers something different.

At Plan, you experience why choices are made while alternatives are still open. At Do, you watch those choices encounter operations, economics, regulators and people. At Study, you see which assumptions held and which consequences nobody predicted. At Act, you see what the enterprise decides to carry into the next cycle. Then you arrive at the next Plan.

The cycle belongs to the enterprise, not legal. Legal rarely runs it. The value lies in being sufficiently present to read it from inside: to see how different disciplines interact, where risk actually emerges and what becomes significant when a choice encounters reality.

That last part matters. The record can tell you that an option was abandoned. Participation may tell you why an apparently minor operational constraint suddenly made it impossible. The papers can record what a regulator said. Being there may teach you why one comment changed the room while another was ignored. A risk register can tell you what people thought might happen. Staying through the work tells you what actually constrained the decision.

That is more than additional information. It is learning what acquired significance. And because you were accountable alongside others for some part of the outcome, the consequence is not merely something you observe. You have to live with what the judgment did.

The first instalment called the result “diagnostic precision”: the lawyer who had lived successive permitting cycles knew which questions to ask because she had been there when the earlier answers formed. She was accountable alongside engineers, hydrologists and the community team for whether the permit landed or failed.

The record tells you what happened. Participation begins to change what you notice next.

What you begin to notice

Over time I developed a habit of looking backwards before answering forwards. What happened before this? Why are we here? Who has seen another part of it? What apparently unrelated work touches this? What happens if we pull that loose strand?

Earlier experience began doing something more useful than supplying answers.

Sometimes it supplied a question.

That is a small distinction, but I think an important one. Processual experience creates a reference set. You have seen choices become consequences. You have seen legal, operational, financial, human and regulatory considerations interact rather than arrive as separate inputs. You have learned something about what matters here, rather than what ought to matter in theory. That begins to change how the next problem looks.

It can also mislead you.

I learned that on work in Latin America. A community challenge around a water-use licence looked familiar through my South African experience. Community litigation. Organised opposition. Mining. A colleague asked a simple question that made me look again.

The mechanism I had read as opposition was, in that setting, part of an ordinary way in which a licensing decision could be challenged or reconsidered. My experience had allowed me to recognise a pattern quickly. It had also allowed me to recognise the wrong one.

That is an important limit to the embeddedness claim.

Experience does not automatically become judgment. Sometimes it makes you wrong faster.

The reference set has to remain open to context.

Learning safety from pilots

I saw the more valuable possibility in a lawyer we deployed into the centre of our mine safety management system. That description matters. He remained a lawyer. He did not run the safety system. But he was accountable from within it, working alongside people whose enterprise objective was to prevent people being injured or killed.

He was no longer encountering safety principally through legislation, investigations and the consequences of incidents. And the system began teaching him.

One of the things he came to see was the strategic importance of learning itself. A serious incident at one operation contained knowledge that might prevent another somewhere else. A safety system therefore needed not merely to investigate incidents, but to allow learning from them to travel.

That created a tension with something legal was doing for perfectly defensible reasons: privilege. There are good reasons to protect investigations and related material when facts are uncertain, consequences serious and legal exposure real. But he was now looking at privilege from inside the safety system. If protection became so complete that one mine could not learn from another, what did that do to the enterprise’s ability to become safer?

The law had not changed. The lawyer had. And that changed the question.

It was no longer simply: what should we protect? It became: how do we preserve the protection genuinely needed while allowing enough learning to travel to help prevent the next injury or fatality?

Then he made another connection. Mining cannot be the only activity in which people make difficult decisions inside complex systems where mistakes can kill. What might mine managers learn from airline pilots? What might both learn from heart surgeons? What had those disciplines discovered about near misses, reporting failure, designing checks and learning without making every admission an allocation of blame?

That insight was his. We opened the door. I am not sure we walked far enough through it. But the sequence matters more than whether we completed the journey.

He went inside a process. The process taught him something. What he learned changed how he saw a legitimate legal practice. And that allowed a lawyer to identify a strategic possibility for the enterprise.

Before the legal question

That is where the change in the lawyer starts to matter to the business.

In-house lawyers often talk about getting involved earlier. But, as the last instalment put it, earlier is a direction, not a diagnosis. A lawyer can arrive earlier and still wait for somebody to ask a legal question.

Processual embeddedness offers something more. The lawyer begins to understand the enterprise problem before it has been reduced to its legal surface.

At its most reactive, legal asks: How do we manage the legal consequences of this decision?

Earlier legal involvement asks: What are the legal risks in the alternatives being considered?

But an embedded lawyer can sometimes ask: Does what we know change the alternatives the enterprise should be considering at all?

That is a different contribution.

Risk changes with it. Once a strategic choice has hardened, risk can be mitigated, allocated, insured, disclosed, litigated or accepted. While the choice can still move, risk can help shape the choice itself.

And this is where the fourth pattern from the first instalment becomes important. If legal is an enterprise resource, its contribution cannot ultimately be measured by the quality or quantity of legal work it produces. The first instalment put the test elsewhere: what the enterprise achieves where legal is embedded.

For the safety lawyer, the important output was not a better privilege memorandum. The enterprise outcome at stake was a safer system. For a lawyer participating in strategy, the measure is not how many legal risks she identifies. It is whether the enterprise makes a better choice because legal judgment was part of making it.

That is ultimately what embeddedness is for. Not changing the lawyer. Changing what the enterprise can do because the lawyer has been changed by being inside its work.

Legal judgment is no longer applied only to strategy after it has been formed. It becomes one of the disciplines from which strategy is formed.

A miner with a law degree

Just before I retired from corporate life, in our final session together, one of my country lead lawyers was preparing for the next stage of her development. She was an exceptional lawyer who had come into mining from an unrelated, highly regulated industry. I asked where she most needed to grow: as a lawyer, as the leader of her team, or as a member of the executive committee?

Mining law worried her. But underneath that was a different anxiety. Not knowing enough about mining made her less confident about what she could contribute when the executive committee was discussing the business rather than the law.

I knew that feeling. My advice was not to start with more mining law.

Study copper mining.

Know the important mines and how they compare. Understand enough geology to know why the orebody matters. Learn about water, communities, logistics, labour, environment and economics. Understand why one mine performs differently from another, what constrains it and what gives it choices. And know as much as you reasonably can about the legal and permitting position of those mines.

The geologist should know more geology. The finance director should know more finance. The specialist external lawyer may know more about a particular field of law. The point is not to beat any of them at their disciplines. It is to understand enough of the enterprise for your discipline to become useful inside the formation of its choices.

My shorthand became simple.

You are a miner with a law degree.

In another enterprise, change the noun. Keep the discipline.

That last part matters. Embeddedness is not an invitation to dissolve into the business. The last instalment argued for calibrated presence, not maximum presence. Legal still needs enough distance to exercise independent judgment and enough professional depth to bring something distinctive to the conversation.

A miner without the law degree is not the objective. Nor is a lawyer standing at the surface of mining. The value lies in the combination.

In another enterprise, change the noun. A banker with a law degree. An investment manager with a law degree. Keep the discipline.

I should add one thing. When I returned to Cape Town, I started my LinkedIn series #MiningIsHuman for much the same reason. If part of my post-corporate life was going to involve working in and around mining, I wanted to keep learning about the industry, not simply its law.

And then there is AI

Which brings us back to the pressure with which this series began.

The first instalment deliberately rejected legal expertise as the defensible asset. Expertise is available outside, and AI can already hold more legal information than an in-house team.

AI will increasingly read the contracts, permits, board papers and investigations. It will retrieve history, compare positions, draft, analyse and find connections across a record at a scale no individual lawyer can match.

Good. Use it.

I would not build an in-house career around a list of things we hope machines will never do. That list will keep moving. Nor would I claim that participation creates some mysterious category of knowledge that machines can never reach. Much of what lawyers learn through experience can be recorded, reconstructed or inferred, and technology will become better at doing all three.

The more useful distinction is what participation does to judgment. It exposes the lawyer to consequence, interaction and context. It teaches what acquired significance when choices met reality. Repeated often enough, it creates a reference set against which the next problem is read — imperfectly, as my Latin American mistake shows. And because the lawyer remains inside the enterprise’s work, that changed judgment can be brought back into the next choice.

AI offers no immunity from that challenge. It sharpens it.

The more technology can do at the legal surface, the harder it becomes to justify spending scarce embedded human capacity there.

Use the machine at the surface. Use presence where participation can change what you learn and what the enterprise does.

What being inside is for

So perhaps I finally have a better answer to the Veteran.

“What do you know?”

Knowledge matters. His certainly did. But positional knowledge was not the whole opportunity I had been given by being inside. The larger opportunity was to participate deeply enough in the enterprise’s work for the enterprise itself to become part of my education.

To see choices become consequences. To learn what became significant and why. To see disciplines collide around the same problem. To carry one experience into another without assuming they were the same. To allow what I learned to change the question before reaching for the answer. And then to bring the discipline of law back into the next enterprise choice.

That is the loop.

The enterprise teaches the lawyer. The lawyer brings what she has learned back into the enterprise. Sometimes that changes what the enterprise does next.

That is the point.

And if AI continues to make the legal surface easier and cheaper to service, the question for an in-house lawyer becomes less comfortable, but perhaps more useful:

Are you merely inside the organisation, or are you sufficiently inside its work for it to be changing what you can contribute?

Because legal is an enterprise resource only to the extent that being inside ultimately changes the enterprise outcome.

A note on sources

This instalment is more experiential than the first two. Its central argument comes principally from things I saw while working inside legal functions: how participation in enterprise processes changed what lawyers noticed, what they learned from consequence, and what they were subsequently able to contribute.

There is a substantial literature around experiential and situated learning, tacit knowledge and professional judgment. I have deliberately not used it to build the argument here. Pattern Counsel started with practice, and this instalment stays particularly close to it.

The examples are therefore offered for what they are: experience from which I have tried to identify a pattern, rather than evidence that the pattern is universally true.

Continue the discussion

If this reading matches your own experience, or if it points somewhere different, I would value the exchange.

Kevin Lester is an independent counsel and thinking partner. He spent fifteen years as a Country Head of Legal and subsequently as General Counsel at Anglo American. He advises General Counsel, senior executives, and boards at kevinlester.co.za.

Subscribe to Kevin Lester

Please subscribe. There’s no cost. When you subscribe, you get free access to essays, stories and advisory notes on in-house legal, mining and regulated sectors, and the decisions that shape organisations under pressure. Always free.

Pattern Counsel is written for General Counsel, Chief Legal Officers and their teams — and for the law firms, legal operations professionals and technology providers who work alongside them. Originally published on LinkedIn. This work is AI-assisted—read about how I work.

Pattern Counsel reflects my vision of how in-house legal functions could work. Many General Counsel will see it differently—and in the coming months, I’ll invite some of them to share their own visions.

Introduction

Being inside is two things, not one.

A position in the enterprise: where legal sits, who it reports to, which rooms it is allowed into. And a presence across the enterprise’s work: whether legal is there across the phases where the work creates, manifests or exposes legal risk—or only in the phases into which it is invited. Most functions win the seat and assume it guarantees that presence. It doesn’t.

The first instalment, last month, put the model plainly. Legal is an enterprise resource, not a service provider. It compounds value through embeddedness, in the business and across the phases of work that demand it. It trades replicable work out to a governed process. And it is judged by what the enterprise achieves where legal is embedded, not by what legal produces.

One of those four patterns—that value compounds only from inside—depended on when the lawyer was present, not where she sat. I offered it as a pattern I’d noticed, not a theory I’d built. This instalment gives that pattern a method, with the same caution.

Two words, kept apart

The argument depends on separating two things the profession often treats as one.

Positional embeddedness is where legal sits in the enterprise: its place on the org chart, its reporting line and its seat at the table. It is about structure and relationships—who trusts legal, who brings it into the work and how close it is to the people making decisions.

Processual embeddedness is legal’s presence across the enterprise’s work. Enterprise work moves through phases. However those phases are described, one of the central insights of modern management is that work unfolds as a process. Processual embeddedness means having legal present in the phases where that work creates legal risk.

Position tells us where legal sits. Process tells us when legal is present across the enterprise’s work.

To be clear from the outset, this essay is not about legal’s process. The processes discussed here belong to the enterprise. Legal will have processes of its own, but it must design them around the enterprise’s work, not mistake them for that work. When the enterprise must hand its work over to a separate legal process, legal remains outside the work it seeks to shape.

Both dimensions are necessary. Positional embeddedness does not deliver processual embeddedness.

Three answers to where

In my experience, strong positional embeddedness takes three common, often overlapping forms.

The trusted advisor. The General Counsel as counsel to the chief executive, the chair and the executive team. Influence through relationship and proximity to power.

The governance model. Legal placed at the enterprise’s formal gates: the approver of contracts, the keeper of the delegation framework and the desk to which trouble is brought. Authority by mandate rather than relationship.

And the distributed model. From my own experience, this is most developed in financial services. Trusted advisors embedded in business units or product lines, reporting to a group General Counsel who advises the group chief executive. It is the strongest answer the positional axis has produced: a lawyer in every lane, close to every business and senior enough to be heard.

When I first encountered the distributed model during a visit to a long-term insurer in 2015, I was convinced it was the whole answer. It is not. A function can place a trusted lawyer in every unit and still bring each of them in only at execution, after the choices shaping the risk have been made. Structurally present. Temporally absent. Seating a lawyer inside the business settles where she sits, not when she enters the work.

Another common arrangement is a Head of Legal reporting to the CFO. This is a positionally constrained answer to where. Legal sits a step removed from the chief executive and the executive team, with access often mediated through another function. Processual weakness is not inevitable, but it becomes more likely: the further legal sits from those directing the work, the more likely it is to enter only when invited.

All of these arrangements answer where legal sits. None, by position alone, answers when legal is present across the work.

The experiment already ran

Here is the helpful part. Legal is not the first support function asked to move from the back office into the business. Finance did it. HR did it. Risk and compliance did it. Each developed a model, tested it at scale and left a record legal can learn from.

Finance developed business partnering. HR developed the HR business partner model. Risk and compliance developed the three lines model. Each sought, in different ways, to move closer to the business.

In each case, the position was secured but the value did not always follow. The literature on HR business partnering is particularly blunt: the model has often fallen short of its promise. A recurring reason is that position did not become presence. Being at the table is not the same as being in the work the table decides.

This is not peculiar to legal, or to mining. It is what happens when a function treats the seat as the destination.

Finance, HR and risk won the seat. The seat was not the thing.

The lament, and the layer under it

Every in-house lawyer has made the same complaint. I wish they’d involved me earlier.

It is a real signal. The lawyer has felt, without quite naming it, that the work has a shape and that the timing of legal’s presence affects whether it can add genuine value or prevent its loss. Legal keeps arriving at the wrong point in that shape—often after the choices that mattered have been made. That is the processual axis surfacing.

But the complaint turns that insight into a blanket prescription: bring legal in earlier and involve it more. Neither is always the right answer. Sometimes the answer is less legal involvement at execution and more at review. Sometimes it is no involvement at all in a phase legal has attended only out of habit.

Earlier is a direction, not a diagnosis. It tells us to change the timing, but not which phase requires legal’s presence.

There is a subtler error beneath this instinct, and it is where most coverage mapping goes wrong. When a General Counsel maps the function’s coverage, the map is almost always drawn against the org chart. Do we support HR? Do we cover business development? That is the positional instinct applied to a processual question. It produces a picture of which departments legal is near, rather than of the enterprise’s work in which legal is present.

The load-bearing work does not stay within departmental portfolios. It moves through streams that cut across them: a single transaction may draw in finance, commercial, tax and operations at once. Each stream, in turn, moves through phases. The executive committee sees portfolios. A processual map must go two levels deeper: first to the streams that cross them, and then to the phases within each stream. Most coverage maps never reach that second level.

How the work is shaped

A stream of enterprise work has a shape, and the shape has phases. Deming gave a clean version, building on Shewhart before him: plan, do, study, act, a loop in which acting on the lesson becomes the next plan. Last time I ran on three phases, planning, execution and review. This is the same shape read closer. Study and Act separate review into its two real parts: judging what happened and carrying that judgment into the next plan. The distinction matters because carrying the lesson forward is where the compounding occurs.

I use Deming because the cycle is clean, not because it is the only one; a gated model or a lifecycle model would do the same job. The claim is not about Deming. It is about reading the enterprise’s own work into phases so that, at each one, you can ask a single question. Does this phase expose, manifest or create legal risk, and am I present where it matters?

Legal’s task here is rarely to run the work. It is to read it: to understand how it moves through its phases, to recognise where legal risk is created, manifested and carried forward, and to decide where its own presence changes the outcome. That is the whole difference.

Take the work legal is most certain it owns. A major commercial contract.

Plan: The enterprise plans it before there is anything to draft. The commercial team decides to enter the arrangement, settles on the counterparty, fixes the shape in principle: price, volume, duration, exclusivity, the terms of exit. No clause exists yet. Every consequential legal risk does. Whether the counterparty can be relied on to perform. Whether the structure trips merger control. What dependence is being locked in, and on whom. Decided in that room, by non-lawyers, before a word is drafted. This is where being inside pays out. The lawyer who lived the last three deals of this shape knows which counterparty defaulted, where the regulator pressed, what the exclusivity cost when the market turned. She is one of the few whose presence changes the outcome. Not drafting. Interrogating the structure while it is still soft enough to move.

Do: Then the enterprise does it. The deal is papered, negotiated, closed. Here legal genuinely produces, and the drafting is real, skilled work. Here is the trap. This is the one phase where legal makes something, so it is the phase legal mistakes for the whole stream. The risk is manifested here, allocated by the words on the page, but it is barely created here, because the room to create it closed at Plan. Legal is one of many now: commercial holds the terms, finance holds the model, legal holds the paper. Being the drafter at execution tells you nothing about whether anyone was present when the exposure was set. Most functions arrive at this phase and call it involvement.

Study: Then the enterprise studies what it signed, if anyone does. The contract runs. Clauses are invoked, or they leak. The counterparty behaves as the paper assumed, or it does not. The pricing does something when the market moves. This is the business living with its own decision, and reading it with legal eyes is work only someone who was inside the deal can do. One of the few again. Most functions skip it. Close the deal, move to the next.

Act: Then the enterprise acts. The lesson carries into the next arrangement of this shape: the template amended, the position for this kind of counterparty improved, the next deal begun from higher ground. The compounding is the enterprise’s, not legal’s, and legal’s presence at Study is what feeds the better Plan. Act into Plan is where the line becomes a loop, and the loop is the whole mechanism.

A single contract does not loop; it is signed once and done. The class of contract loops. Supply agreements, offtakes and outsourcing deals recur, and the compounding lives at the level of the type, not the instrument. That is where the template and the playbook accumulate.

The result is not another legal framework. It is a diagnostic for reading the enterprise’s work: four questions, asked stream by stream.

• Do we need to be at this phase at all?

• In what form: leading, influencing, contributing, or only watching?

• How much legal presence does this phase demand?

• Are we present enough to fulfil the role we claim as an enterprise resource?

The diagnostic has only one purpose. It tells you where legal presence is genuinely demanded and where it is merely habitual. You do not yet need to decide what to release. You now know where to look.

The questions are allowed to answer no. They are allowed to answer less. A function present everywhere at full weight is not the ideal. It is over-embedded, too close to the business to see it clearly, and its judgment suffers as a result. Calibration is not a concession to a tight headcount. It is the correct shape.

The same shape, without a mine in it

The pattern is not mining’s. It is not the contract’s either. A regulatory affairs specialist in a pharmaceutical company works through the same pattern. A drug moves through a gated lifecycle: discovery, preclinical, trials, submission, approval, and the long tail of market surveillance, each submission resting on the documented history of the one before it. The specialist who was present when the early regulatory strategy was set reads the later submission with knowledge that is not in the file: what the agency signalled and never wrote down, why a design choice was made, where the last application met resistance. One of the few at the front. One of many in the machinery of a filing. One of the few again when the regulator responds and the next submission is shaped. No tailings dam in sight. The same pattern exactly.

A deliberate act

None of this happens by good intention. A function does not drift into presence across the phases that matter. It maps the enterprise’s work and designs its presence against it, or it arrives where habit and invitation put it.

For a mature function, the mapping is an audit, and an uncomfortable one: going stream by stream and asking honestly where we arrive against where the value accrues. Most functions that run it find the same answer. We arrive at Do—present for execution across almost everything and for planning across almost nothing—and we have been calling the execution half coverage. The diagnostic turns a vague unease into a specific question. The map itself is already valuable. Most functions have never seen their work arranged this way.

Designing that presence from the beginning is different work altogether. It belongs to function design rather than function audit, and it is the subject of a later instalment.

Presence across the enterprise’s work is designed, or it is accidental. There is no third case.

What it costs, and what pays for it

I will not pretend this is free. Reading every load-bearing stream at the level of its phases, then ensuring legal is present where judgment compounds, is more work than turning up at execution and drafting well. And it lands at the worst possible moment, when the enterprise is asking legal to cost less, not do more.

The additional work is not overhead. It is what makes legal an enterprise resource, and it is funded the only way it can be: by releasing the replicable work that does not compound, the work an external channel, properly instructed, would do just as well.

The presence you owe is paid for by the delivery you let go of.

Which work belongs in each channel, and how you decide it without losing hold of what matters, is a later question. It is the same diagnostic turned inward, onto legal’s own work. This instalment has used it to read the enterprise; a later one will use it to redesign the function itself.

Concluding this instalment

This is the discipline the series set out to take up: where presence is demanded, and where it isn’t.

Being inside is two things. A position, and a presence. Position is necessary and routinely mistaken for sufficient. Finance, HR and risk each won it and learned the hard way that it did not carry the presence, and legal is about to be asked the same question under AI’s pressure. The method for answering is not a framework to adopt. It is a way of reading the enterprise’s own work into phases and asking, stream by stream, where legal risk is made and whether the function is there when it is. Designed presence, or accidental. There is no third case.

Why presence compounds at all—what kind of knowledge being inside the work produces that being outside it cannot—is the subject of the next instalment.

A note on sources

The word embedded is not mine, and I have tried not to use it loosely. I did not arrive at the idea through economic sociology. I arrived at it through practice, and only later found that others had been working on embeddedness for decades. Looking back, it echoes Mark Granovetter’s work on how economic action is embedded in social relationships, and Brian Uzzi’s work on how those relationships affect organisational performance. Uzzi also shows that embeddedness has limits: beyond a point, it can impair rather than improve judgment. That finding supports this instalment’s argument for calibrated rather than maximum presence.

That legal makes its value upstream, before the problem rather than after, is the heart of the Nordic School of Proactive Law, and of Helena Haapio’s work in particular. It gave a rigorous vocabulary to something I had already been watching.

I learned most from the functions that made this journey before legal: finance business partnering, Dave Ulrich’s HR business partner model and the honest post-mortems on it, and the three lines model in risk. Their failures taught me more than their successes.

Deming and Shewhart supplied the cycle. I borrowed it as a way of reading enterprise work, not as a quality-management method.

One honest gap remains. I could not find a study that puts a number on the cost of late legal involvement in corporate decision-making. The proactive-law literature makes the case in principle; the analogue functions show the pattern in practice; legal’s own number is not yet in, and I will not pretend otherwise.

Continue the discussion

If this reading matches your own experience, or if it points somewhere different, I would value the exchange.

Kevin Lester is an independent counsel and thinking partner. He spent fifteen years as a Country Head of Legal and subsequently as General Counsel at Anglo American. He advises General Counsel, senior executives, and boards at kevinlester.co.za.

Pattern Counsel is written for General Counsel, Chief Legal Officers and their teams—and for the law firms, legal operations professionals and technology providers who work alongside them. Originally published on LinkedIn. This work is AI-assisted—read about how I work.

Introduction

Legal is an enterprise resource, not a service provider.

It compounds value through embeddedness — in the business and across the phases of production that demand it. It trades replicable work out to a governed process to maximise compounding value. And it is judged by what the enterprise achieves where legal is embedded, not by what legal produces.

That is not a theory I built. It is a pattern I recognised, late, after fifteen years running a legal function while it was being cut. I am not certain it is new, and I don’t need it to be. I arrived at it from the inside, through a long contraction, and I am setting it down now for one reason.

The same pressure my teams faced is reaching the entire profession again, but now from a different direction. The CFO asking the legal team to do more with AI is not, at the level that matters, asking for better law. The word is “improvement.” The instruction beneath it is to spend less on this and relieve the business’s dependence on it.

My version of that pressure came from a commodity cycle, not a technology. The cause was nothing alike. But the shape of the pressure was the same. And for in-house legal teams across industries, there is no cycle to wait out this time. With the arrival of AI, the cost of sourcing legal support is not dipping; it is resetting.

So I’m setting it down here, in parts, as a newsletter. Each instalment takes one piece of the pattern and reads it out. This is not a model to adopt; it’s the shape of what one function found it could not give away. And it’s now being offered to a profession that’s being asked the very same questions.

Here is where those patterns came from.

The story

I built the South African and later global upstream legal functions of a global diversified mining company from 2010, integrating lawyers drawn from diverse teams that had run separately, with their own habits and loyalties. Each time I took on this challenge, the early work was exhilarating and focused on construction.

Then inevitably, the moment would come when the economics or the group strategy would shift, and the work would become subtraction.

What followed, for the better part of one and a half decades, was retrenchment, in both senses of the word. The business would shed people, and the function that advised on the shedding would be under the same pressure to shrink. Every cycle, the question returned, in one form or another. Why does this cost what it costs, and what happens if there is less of it?

That’s my story, but I have no doubt it’s been your story too.

I never found clean answers to that pressure when it was at its worst. But I eventually found four patterns that emerged within those cycles. I offer them as field notes rather than theories or models.

First pattern: a resource is not a service.

The pressure to cut is indiscriminate when it arrives at scale.

I have seen mining companies cut engineers, investment banks cut risk analysts, life insurers cut actuaries. Nothing is sacred. But there is a distinction worth holding, even if it offers no immunity.

When a mining company cuts engineers because it is producing less, it is making a production decision — the business needs fewer because it is doing less. When a business cuts its legal function because it believes the work can be sourced more cheaply outside — through a law firm, an outsourcer, an AI-assisted platform — it is making a sourcing decision dressed as a capacity decision. The legal work has not contracted. The business has concluded it is paying for a service it can buy differently. Legal is especially easy to miscategorise this way, because the work is intangible and the sourcing alternatives are multiplying.

The function that accepts the service-provider description has confirmed the sourcing logic. Every efficiency it delivers becomes evidence that more can be extracted. Every technology it adopts becomes the justification for the next reduction. The contraction is not a risk it might lose. It is the trajectory the framing invites.

What the business loses when it reduces legal on sourcing grounds is not volume. It is position: the embedded judgment that cannot be bought back in when the exposure arrives. You cannot rehire the accumulated knowledge of how this particular enterprise makes its decisions, which risks it has actually lived, what its regulators have said and not said over twenty years. That is not on any market.

A business does not replace its own judgment with a cheaper version of itself. It replaces services. Legal’s claim — the only one that holds under sustained pressure — is that it is the former, not the latter.

Second pattern: value compounds, and only from inside.

The obvious answer to what makes an in-house legal function valuable is the wrong one. It is not legal expertise. Legal expertise is everywhere, and a well-trained large language model now holds more legal information, instantly, than any team ever will. If information were the asset, the work would have left already.

What being inside the business produces is a different kind of knowledge, and it has no market. How decisions actually get made here, as against how the policy says they do. Which risks turn real and which only sit on a register, year after year. Who in the room can move a decision and who merely attends. None of that is in any document. It accumulates in the people who stay long enough to watch the same patterns return.

And it compounds. Each cycle of presence sharpens the next judgment, because the next judgment is made by someone who was there when the last one landed. An adviser reading the file afterwards reads what was written. The person who was inside reads that, and everything around it that never reached the page.

There was a lawyer on a team I once led who was accountable for mining, environmental law, and permitting. A tailings dam is built in stages, raised in successive lifts, with the permitting regime requiring each new lift to be separately licensed before the next can begin. She knew every permit through every cycle of its evolution — why each prior lift had been approved the way it was, where the regulator had pressed, what the record did and did not say. That is the compounding asset made literal: a structure that physically accumulates, where the licence for this lift rests on the history of the last, read by someone who had lived the whole climb.

But the memory was only the first part of it. She sat on the permitting governance committee — often co-chaired it — accountable alongside the engineers, the hydrologists, and the community team for whether the permit landed or failed. She was part of a legal team led by a senior lawyer who sat on the business Exco. Three layers, each doing its part. None of it reducible to a person who happened to be good.

Her presence wasn’t uniform across the cycle. At the front, when each lift’s application was being designed, she was one of the few whose contributions were most consequential. In the execution phase, all disciplines contributed alongside each other — she was one of many. At the back, when the outcome was reviewed and the next application’s strategy shaped, she was one of the few again. Front and back: that is where the compounding happened.

She knew which questions to ask at each lift because she had been there for the ones before. Did the hydrologist’s analysis in this cycle account for what the record showed in the last. How did that administrative decision — the one that read as procedural at the time — carry into the licence conditions being built on now. An external adviser instructed at this lift does not know which of those questions matter, because they were not there when the answers formed. She was.

That diagnostic precision, knowing the shape of what might have been missed, across every discipline, across every cycle, is not in any record. It lives in the person who has been present and is accountable for what comes next. There are no mines without permits.

The rejoinder is that artificial intelligence changes this. A model can read every contract, every board paper, every permit ever filed. But it accumulates the record. The record is what was decided. Judgment is the call about what to do next, made by someone who can be held to account for it, who reads the room as well as the file, and who carries the cost when it goes wrong. A system can hold the whole history of the enterprise and still not own a single decision.

Accumulation is not judgment, and it does not become judgment by getting larger.

That judgment, to mean anything, has to be present at the moments that shape what the enterprise does next. Every stream of work the enterprise undertakes has the same three moments: a planning phase, where what will be done and how is determined; an execution phase, where it is carried out; and a review phase, where outcomes are assessed and lessons carried into the next plan. A market entry, a major contract, a regulatory response, a restructuring — the enterprise moves through that shape every time. Legal’s compounding happens when it is present inside the planning and the review, not summoned only after the plan is already set and execution is underway. The question worth asking is at which moment your function typically arrives — and whether that matches where the value actually accumulates.

Third pattern: trade the replicable out, but keep the governing

Not all work compounds. The work that doesn’t is the work whose value doesn’t depend on being inside — work where an external provider, properly instructed, would reach the same result. It leaves nothing behind that sharpens the next pass. The enterprise loses nothing by sourcing it from outside, because being inside added nothing to it. That is the work to trade out.

Give it away. The capacity that frees is not spent going faster; it is spent where value compounds.

Delivery is divestible. The oversight is not.

I learned the limit of that the hard way. The moment we sent the managing of the work out along with the doing of it, we had not saved capacity. We had lost hold of it. Drawing the boundary of what the external channel does, routing each matter to the right channel, catching the error that replicates silently across a thousand instances before anyone reads them: these are not coordination tasks. They are embedded judgments, and they belong inside.

There is a decision underneath this that I will return to in a later instalment — which streams of work warrant keeping inside, and which are better sourced. The axis that matters is not the difficulty of the work. It is whether being inside changes the outcome, and whether presence across many instances builds something that compounds. That question, and the decision it drives, deserves its own treatment.

Fourth pattern: judged by the enterprise, not the department.

Legal’s contribution is measured by what the enterprise achieves where legal is embedded — not by the volume or efficiency of the legal work it produces.

This is not an argument against measurement. It is an argument against mismeasurement.

The function evidences its contribution. It does not reduce it to a figure.

The value resists pricing, and honestly so. It is a stock that builds invisibly and shows mostly in absence — the loss that did not occur, the exposure caught before it formed, the decision shaped at the front of the cycle rather than contested at the back. Activity metrics fail here not because they are inaccurate but because they count motion while the asset is stock. The harder I pushed legal risk to translate into what the business already knew how to count, the more it came to look like counting motion. I watched good lawyers before me lose that argument by accepting the wrong scoreboard, and I understand why they accepted it. The pressure for a number is relentless. But a function that answers with a number is confirming that a number is what it is worth. It isn’t. It is worth what the enterprise achieves, in the work it was embedded in.

That is not a soft claim. It is a harder one. It asks the function to stand behind outcomes rather than outputs, and to resist the safety of metrics that prove only that it was busy.

Concluding this instalment.

Four patterns. None designed. All arrived at by watching what could not be removed without something being quietly lost that could not be bought back.

The instalments that follow take each one further — the full logic of the resource distinction, the epistemology of embedded knowledge and why AI sharpens rather than dissolves it, the discipline of determining where presence is demanded and where it isn’t, and the honest architecture of measurement.

What was still standing when it had done its work is what the rest of this sets out.

A note on sources

This essay emerged from experience rather than research, but experience and reading rarely stay separate for long. Over fifteen years inside a function that was repeatedly asked to justify its existence, I read widely about where legal thought leadership was taking the profession. Some of that reading sharpened ideas I was already forming; some of it named things I had felt but not yet articulated. I cannot always say which is which.

Simmons and Dinnage wrote seriously about why continuous presence inside the enterprise creates value that episodic engagement cannot replicate — and gave me a way to name what I had been watching. Ben Heineman’s case for the lawyer-statesman, set out in The Inside Counsel Revolution, shaped how I thought about what a general counsel is actually for. Deming and Shewhart’s improvement cycle gave me a convenient way to name the phases of work, even if I have borrowed the lens without adopting the whole frame. And CLOC’s emerging standard for legal operations measurement is the reference point against which the measurement argument in this essay pushes back: not because the metrics are wrong, but because they count motion while the asset is stock.

The perception gap between general counsel and the executives they serve has proven remarkably persistent — and has, if anything, widened. Bain first documented it in 2010, finding that almost forty percent of CLOs rated their function highly for commercial value while only fourteen percent of CEOs agreed. Sixteen years later, Thomson Reuters found the gap had grown: eighty-six percent of general counsel believed their department contributed significantly to organisational objectives, while only seventeen percent of the C-suite agreed — and forty-two percent said legal contributed little or nothing at all. That is not a communication failure. It is a framing one. And it is what put a number on something I had lived without being able to prove.

I offer these acknowledgements not as a bibliography but as an honest account of how thinking forms — from pressure, from practice, and from the writers who happened to be working in the same space.

Continue the Discussion

If these patterns resonate with your own experience, or if your experience points in a different direction, I would genuinely value the discussion.

Kevin Lester is an independent counsel and thinking partner. He spent fifteen years as a Country Head of Legal and subsequently as General Counsel at Anglo American. He advises General Counsel, senior executives, and boards at kevinlester.co.za.