Most leaders learn to work with legal counsel the hard way: they send a contract over the night before signing, get back a wall of red ink and a list of objections, and conclude that legal is where momentum goes to die. The problem is rarely the lawyer. It is that the lawyer was handed a finished decision and asked to bless it, instead of being brought into the thinking while it still mattered. Used well, counsel is one of the highest-leverage relationships a leader has. Used badly, it is exactly the bottleneck everyone complains about.

The quick version

  • A lawyer is a risk navigator, not a risk eliminator. Their job is to tell you what could go wrong and how badly, so you can make a clear-eyed business call, not to make the decision for you or stop it.
  • Bring them in early and frame the question well. "Is this allowed?" gets a slow, cautious answer. "Here's what we're trying to achieve and by when, what's the safest way to get there?" gets a useful one.
  • Legal privilege is a real, fragile protection that keeps your candid legal advice confidential, but it only covers advice that is genuinely legal, and copying a lawyer onto a business email does not make it privileged.
  • Counsel sits in a built-in tension between being your partner and being the organisation's guardian. Good lawyers hold both; your job is to make it safe for them to say the uncomfortable thing.

The idea in depth: what a lawyer is actually for

The most useful reframe is the oldest one. Louis M. Brown, the Harvard-trained attorney who founded the discipline of preventive law in the mid-twentieth century, put it in a single line that every leader should internalise: "The time to see an attorney is when you're legally healthy, certainly before the advent of litigation, and prior to the time legal trouble occurs." Brown's whole argument, set out from his 1950 textbook onward, was that law is far cheaper and more effective as prevention than as cure. The lawyer you call after the dispute has started is doing damage control; the one you bring into the deal, the hire, or the launch beforehand is shaping an outcome you can still influence.

So stop treating legal as a checkpoint at the end of a process and start treating it as a lens you apply at the start. In practice that means: when a decision carries real consequence, a major contract, a senior departure, a new market, anything touching customer data, the question is not "will legal sign this off?" but "what would I want a lawyer to have looked at before I commit?" Change the timing and counsel stops being an obstacle and becomes an input.

An honest limitation. Prevention has a cost, and not every decision earns a lawyer's time. Run everything past counsel and you recreate the bottleneck from the other direction, work stalls, and the legal team drowns in trivial reviews while the genuinely risky thing slips past unnoticed. The skill is triage: knowing which decisions are high-consequence or hard-to-reverse enough to warrant the friction, and which are reversible, low-stakes calls a manager should simply make. A lawyer can help you draw that line once; they should not have to be consulted every time you apply it.

The partner-guardian tension, and why you want it

The clearest modern account of what a senior lawyer is for comes from Ben W. Heineman Jr., who served as General Electric's general counsel from 1987 to 2003 and then wrote the definitive book on the role: The Inside Counsel Revolution: Resolving the Partner-Guardian Tension (American Bar Association, 2016). Heineman's central idea is that every good corporate lawyer lives inside a permanent tension. They are a partner to the leaders they advise, helping the business move, win, and grow. But they are also a guardian of the organisation itself: its compliance, its reputation, its long-term licence to operate. The two pull in opposite directions, and the lawyer's craft is holding both at once. Heineman's ideal, drawing on Anthony Kronman's The Lost Lawyer (Harvard University Press, 1993), is the "lawyer-statesman": not merely a technician, but a counsellor whose value lies in judgment, the practical wisdom to weigh a business goal against an institutional risk and say which should win.

flowchart LR
  L(["Your legal counsel"]) --> P(["PARTNER
help the business
move, win, grow"])
  L --> G(["GUARDIAN
protect compliance,
reputation, the institution"])
  P --> J{"Tension held
with judgment"}
  G --> J
  J --> O(["Lawyer-statesman:
a clear-eyed call,
not a reflex 'no'"])
Heineman's partner-guardian tension, the good lawyer holds both sides, rather than collapsing into either a yes-machine or a no-machine. Leaders Loop

This matters for how you behave, not just how you hire. A lawyer who is punished, even subtly, with cold shoulders or excluded meetings, for raising the guardian concern will quietly stop raising it, and you lose the early warning you were paying for. So reward the inconvenient truth. Thank counsel when they flag the thing you did not want to hear. Separate the message from the messenger. Make clear that "here's the risk you're taking" is exactly the service you want, not obstruction. The leaders who get the most from legal are the ones who make it safe to be the guardian.

Where this gets harder. Heineman is describing an ideal, and the inside-counsel role he champions sits mostly in large corporations with mature legal functions. A founder with a single outside lawyer on a fixed fee, or a manager whose only access to legal is a shared inbox, lives in a thinner version of this world. The principle still holds, you want judgment, not just a rubber stamp, but be realistic about the relationship you actually have, and invest in deepening it before you expect statesman-grade advice from it.

How privilege really works, and how leaders break it

One piece of legal machinery is worth every leader understanding directly, because misusing it is common and the consequences are real: legal professional privilege (called attorney-client privilege in the US). Privilege is the protection that keeps confidential communications between a client and their lawyer, made for the purpose of giving or getting legal advice, out of the hands of opponents and courts. It exists so that you can be fully candid with your lawyer, describe the problem honestly, warts and all, without that frankness being used against you later. It is genuinely valuable, and it is genuinely easy to lose.

The trap, well documented by the American Bar Association and litigators on both sides of the Atlantic, is the belief that you can make any message confidential by adding a lawyer to it. You cannot. Privilege attaches to legal advice, not to business advice that happens to pass a lawyer's desk, and where a lawyer wears both hats, courts look at the dominant purpose of the communication. As privilege specialists repeatedly warn, you cannot make a communication privileged simply by copying counsel on it; a routine business email cc'd to the legal team is still a business email, and reflexively adding a lawyer can even turn them into a witness rather than a protector.

Privilege protects legal advice, not any email you decide to copy a lawyer onto.

What this looks like in practice is mundane and worth the discipline. When you genuinely want legal advice, ask for it explicitly and keep that thread separate from operational chatter. Mark advice-seeking communications clearly, but do not scatter "privileged and confidential" across everything, over-labelling weakens the claim when it matters. Keep the recipient list to those who actually need the advice; the wider you forward it, the more you risk waiving the protection for everyone. And remember the limit: privilege does not cover the underlying facts, and it offers no shelter for advice sought to further a fraud. This is jurisdiction-specific and the details differ between, say, England and the US, so confirm the local rules with a qualified lawyer. The principle, though, travels: privilege is for legal advice, deliberately sought and carefully kept.

A worked example

Take a mid-sized software company, call it Brightwell, about to sign its largest customer yet, a deal worth a meaningful slice of next year's revenue. (Illustrative figures and scenario throughout; this is a teaching example, not real events or legal advice.) The commercial team has negotiated for six weeks. Two days before signing, someone remembers to "send it to legal."

The general counsel reads it overnight and comes back with three problems: an uncapped liability clause that could, in a worst case, cost several times the contract's value; a data-processing term that conflicts with what Brightwell has promised its other customers; and an auto-renewal the sales lead did not notice. In the late-handover version of this story, the deal team hears "legal is blocking us," tempers flare, and either the deal slips or someone signs anyway and inherits the risk.

flowchart TD
  S(["Big deal in motion"]) --> Q{"When is counsel
brought in?"}
  Q -->|"Two days before signing"| L(["Wall of red ink
deal stalls or risk is signed"])
  Q -->|"At the negotiation kick-off"| E(["Counsel sets the
liability cap up front"])
  E --> F(["Risks framed as trade-offs
commercial team chooses"])
  F --> W(["Signed on time,
eyes open"])
Same deal, same lawyer, different timing, early framing turns "legal blocked us" into "legal got us there safely." Leaders Loop

Now run it Brown's way. At the negotiation kick-off, the deal lead spends twenty minutes with counsel: here's the customer, here's the revenue, here's the deadline, what should we protect? The lawyer flags the liability cap as the one non-negotiable and explains the data term's knock-on effect on existing customers. Those become negotiating positions the commercial team owns, not last-minute objections. When the customer pushes on the cap, the team already understands the trade-off and can decide, accept a higher cap for a price concession, say, with the risk priced in rather than discovered later. The deal signs on time. The difference was not a better lawyer or a softer one. It was the same advice, delivered while it could still change the outcome.

Frequently asked questions

When should I actually bring in legal counsel?

The trigger is consequence and reversibility, not job title. Bring counsel in early for anything that is expensive to undo or carries outsized downside: significant contracts, anything touching personal data or regulated activity, senior hires and exits, equity and fundraising, intellectual property, and any real dispute. For low-stakes, easily reversed decisions, a manager should just decide. When in doubt on a big, irreversible call, a short early conversation is almost always cheaper than a late clean-up.

How do I get a straight answer instead of "it depends"?

Give the lawyer the context they need to commit to a view. Lawyers hedge when they are handed a narrow legal question with no business goal attached, because the only safe answer is the cautious one. Instead, frame the objective, the deadline, and your risk appetite: "We want to do X by Friday, we can tolerate some risk on Y but none on Z, what's the safest route?" That invites a recommendation rather than a disclaimer, and it lets counsel weigh the risk against the prize you are actually chasing.

Do I need an in-house lawyer, or is outside counsel enough?

It depends on the volume and the stakes, not the size of the logo. Outside counsel is efficient when legal needs are occasional and specialised; the cost of a full-time general counsel only makes sense once the day-to-day legal work is constant and woven into the business. Many growing companies bridge the gap with a fractional or part-time general counsel, senior judgment on tap without a full-time salary. The deeper point from Heineman's work is that whoever holds the role needs proximity to the business to give the partner-grade advice that detached outside counsel struggles to.

Won't involving lawyers just slow everything down?

It slows things down when you involve them late, on finished decisions, and ask them to find every possible problem with no sense of what matters. It speeds things up when you involve them early, with a clear goal and a sense of your risk appetite, so they can clear the path rather than barricade it. The bottleneck is usually a symptom of bad timing and bad framing, not of having a lawyer at all.

What's the one privilege mistake to stop making today?

Stop cc'ing a lawyer onto business emails in the belief it makes them confidential. It does not, and it can backfire by dragging counsel into the factual record. Keep genuine requests for legal advice in their own clearly-marked threads, limited to the people who need them, and treat "privileged and confidential" as a label you use deliberately, not a default footer. (Privilege rules vary by jurisdiction; confirm the specifics with a qualified lawyer.)

Related in the Toolkit

Working well with counsel underpins almost everything else in this area, the day you most need a lawyer's judgment is usually the day a contract goes wrong (contract fundamentals) or someone questions who owns what you built (intellectual property).

Where to go next