The company needed to grow up. Regulatory complexity increased, deals had more zeros, and the risks were getting bigger and less comfortable. So you hired your first General Counsel.
Something changed. Deals that once closed in days now take weeks. Decisions you made over lunch now require pre-meetings, alignment calls, review cycles, and committee approvals. Follow-ups to confirm what was already agreed. More sets of eyes. More process.
Some of this is normal. Professionalization requires process. Risk management takes time. Growing up means slowing down. It’s a comforting explanation, but it’s also dangerous and incomplete.
Because somewhere along the way, your team stopped asking, "How can we do this?” and started asking, "Are we allowed to?” People hesitate. They ask for guidance they don’t actually need. Energy dissipates in inboxes and calendar holds.
You are not slower because your risks are more complex. You are slower because you built a legal function that optimizes for defensibility over velocity. And unlike most operational problems, this one is not a tolerable tax on growth. It compounds and left unchecked, it becomes slow-motion suicide disguised as organizational maturity.
Pretending it’s accidental is the mistake that kills otherwise healthy companies.
The Bait and Switch
When you hired a GC, you thought you were buying judgment at scale. Someone who could help you make faster, better decisions as complexity increased. Someone who understood that perfect is the enemy of shipped.
What most companies actually buy is a professional risk-diffusion system.
This is not a competence problem. It is an incentive problem. The modern legal profession is trained to treat concentrated decision-making as reckless and distributed consensus as mature. The GC role traditionally rewards insulation from blame, not velocity or outcomes.
In practice, fast, accountable, and occasionally dangerous founder judgment is replaced by process. Decisions are documented, documents are reviewed, and positions are tested.
Six months later, no single decision looks unreasonable. The company is just heavier. Everything takes longer. But legal risk is contained.
Other companies, maybe your competitors, are moving faster. Not because they are ignoring risk, but because they built different decision-processing architectures.
Is Legal Scaling Your Company or Killing It
If you want to know whether your legal function is adding leverage or drag, ask these three diagnostic questions:
1. Who Actually Decides?
For any meaningful legal or business decision, can you name the single person accountable for the call? Not who weighs in. Not who reviews. Who decides?
In high-velocity companies, the answer is immediate. One person owns the yes or no. Everyone else provides input, flags risk, and supplies context.
In many professionalized legal functions, the answer is unclear. Decisions emerge from a process. Authority dissolves into workflow, and we call it "governance."
If you cannot immediately name the decider for your three most common high-stakes decisions, you have designed velocity out of your system.
Good legal process informs judgment. It does not replace it. Legal exists to make accountable decision-makers faster, not to dissolve responsibility until speed becomes impossible.
2. Do Teams Operate Inside Clear Constraints or Ask Permission to Function?
Early teams move fast because they understand the boundaries and operate freely within them. They do not ask permission for everything. They exercise judgment.
Professional legal systems invert this. Legal becomes a gate, not a guardrail. Teams learn to escalate defensively. “Check with legal” becomes the safest default move. Velocity dies not through overt restriction but through an institutionalized permission culture.
This is a key dynamic. When your team asks permission for everything, they are not managing risk; they are managing their relationship with legal. The system has trained them to optimize for not getting blamed rather than getting things done.
Legal is no longer infrastructure that enables the business. It is a separate internal stakeholder that must be satisfied before action is possible. And every internal stakeholder you add is a tax on velocity.
Ask your team leads what they can do without involving legal. If the answer is vague or caveated, you’ve built a permission-based organization. And permission-based organizations seldom move fast.
Good legal infrastructure defines hard constraints. Plots the small set of truly existential risks: regulatory tripwires, irreversible commitments, and asymmetric downside. Inside the boundaries, everything else is presumptively allowed. Outside them, escalation is immediate and expected.
This requires trust and judgment and a GC willing to accept personal exposure.
3. Does Documentation Sharpen Judgment or Create Alibis?
Documentation is where decay becomes undeniable.
Good writing, business documents, position papers, and even legal memos exist to clarify thinking, memorialize decisions, and enable faster action later. Those documents are sparse and consequential on purpose.
However, somewhere along the way, documentation starts serving a different purpose. The moment there’s a “memo for the file,” you’re no longer recording reality; you’re justifying it. Paper accumulates so no one can later be accused of recklessness, even when the act of writing it down is what creates the risk.
Here’s a test. Pull your last three legal memos. Ask whether they made your company faster or smarter. If the honest answer is “no, but they made us more defensible,” you are paying for cover, not counsel. And cover is cheaper to buy than to staff.
Good legal documentation exists only when it improves decisions, enables delegation, or preserves reasoning for future action. Everything else is camouflage.
What To Do About It
There are only two questions that matter. First, does your legal function make decisions faster, or merely easier to defend after the fact? And, second, is that a tradeoff you are consciously choosing?
If you have a General Counsel who understands the difference, you’re ahead. They will be able to tell you, without defensiveness, who decides, what the real constraints are, and which risks actually justify delay. They will optimize for judgment and accountability, not permission and paper. If they can’t articulate that, the problem isn’t effort or talent. It’s design.
And if you haven’t hired a GC yet, be careful what you optimize for. Most “experienced” legal leaders have been trained to build systems that avoid risk, not manage it, and survive blame, not accelerate decisions.
Legal is underlying business infrastructure. It should concentrate judgment, define hard constraints, and then get out of the way.
Most companies will not make these changes. They will continue to build legal process whose primary function is to make failure explainable rather than success repeatable.
Those companies will look professional and mature right up until a faster, less “well-governed” competitor takes their market.
Legal did not slow them down by mistake. It did exactly what it was hired to do.