The GC’s Loneliness Isn’t a Personal Problem. It’s an Operational One

There’s a LinkedIn post by Jason Weiss, a fractional general counsel, that’s getting traction with GCs because it names something people feel but rarely say out loud.

The GC gets the 6 a.m. call, the 11 p.m. text, and the “hey, do you have a minute” that takes three hours. They make decisions when there is no good answer. They protect people who will never know they were protected. The post called it loneliness, and it was spot on.

But here’s what that post didn’t get to: the loneliness of the GC chair isn’t just emotional. It’s structural. And unlike the inherent weight of the role, the structural piece is fixable.

This is what loneliness actually looks like in practice: a GC says, “I need to know what the team is working on.” That gets heard as a control impulse when it’s actually a visibility gap. The GC doesn’t have the data story they need to walk into the room, advise the business, and lead. That gap is more widespread than most organizations want to admit.

Three gaps that sustain the problem:

1. The gap between the GC and their own team. Direct reports work in execution mode, managing the queue, processing the work, and hitting deadlines. The GC needs something different: pattern recognition, risk trending, workload visibility, and early warning signals. When reporting is manual and built on demand, the answer is always a day late. The GC is reactive when the role requires them to be proactive. That’s not a people problem. It’s a process design problem.
2. The gap between legal and the business. Procurement sees legal as a cost center. Finance sees it as a line item. None of them see legal the way the GC does: as a risk function, a business partner, and increasingly a strategic voice. When the GC asks for investment in legal-specific technology, they’re met with: “Can’t you just use what we already have?” The answer is often no, legal data has confidentiality requirements that general enterprise tools weren’t built to protect. Matter management, contract governance, spend oversight, and privilege considerations require purpose-built architecture. The script that works: stop leading with legal’s needs and start leading with organizational exposure. “If contracts aren’t tracked in a governed system, we can’t tell you what our liability is.” That’s not a legal preference. That’s a business problem.
3. The gap inside the legal team itself. Matters managed through email. Contracts tracked in spreadsheets. Knowledge held individually, not institutionally. This isn’t a character flaw; it’s a product of how legal has historically been resourced and run. But the business has moved. The expectation of legal has moved. When a GC introduces structured intake or a matter management system, they’re not just implementing software. They’re asking people to change how they practice. The GC sits in the middle of that tension: accountable for the team’s performance, unable to mandate change without buy-in, and often without the bandwidth to lead a full change management initiative while simultaneously doing the actual legal work.

The loneliness of the chair is real. But a significant portion of it is solvable through better infrastructure.

The bandwidth problem: build internally or bring in help?

There’s a pattern that repeats itself: a legal department decides to transform its operating model, assigns the work to the people already running the department, and wonders why nothing changes. You cannot ask the same team that manages the queue, closes contracts, and responds to the business to simultaneously redesign how all that work gets done. This isn’t a motivation problem. It’s a capacity problem.

Build internally when you have legal ops capacity, a clear starting point, and a team stable enough to absorb change incrementally. Bring in outside support when the gap between current and required state is large, when adoption has already failed once, or when executive pressure demands a pace that internal capacity can’t support. The right model is usually both: external expertise to design and accelerate, internal ownership to sustain. The most expensive mistake isn’t choosing the wrong tool; it’s choosing the right tool and never actually changing how people work.

The visibility stack: a practical framework

Legal Maxxing is about intentionally designing the conditions that allow legal professionals to operate at their highest level. What GCs are missing isn’t motivation or talent. It’s infrastructure. That infrastructure has three interdependent layers.

• Layer 1: trusted data: Not dashboards. Not sophisticated analytics. The basics. Matters categorized consistently. Contracts with accurate metadata. Intake through defined channels, not inboxes and Teams messages. Documents attached to records. Key dates, owners, and status documented and current. None of this is glamorous, but all of it is essential. Because without it, the GC can’t see what’s happening in their own department. AI does not fix this. AI scales whatever is already there. If the underlying data is fragmented, AI produces faster, more confident fragmentation. The sequence matters: stabilize first, then accelerate.

• Layer 2: processes that surface signal: When intake is standardized and workflows are visible, the GC stops being the last to know and starts being the first to see patterns. “I need to know what the team is working on” stops being a management request and becomes a dashboard view. Workload concentration becomes visible before burnout happens. Risk trends surface before they escalate. This is how the GC gets the data story they need to walk into the board meeting and lead, not react.

• Layer 3: AI as amplifier, not shortcut: AI layered on a sound operating model expands what a GC can see, synthesize, and act on without adding cognitive load. Used correctly, on top of trusted data and visible processes, AI can summarize matter histories, identify clause patterns across large contract sets, and flag risk trends before they become crises. AI layered on broken processes produces faster, more confident mistakes.

Five practical actions the GC can take now:

1. Audit your current state honestly. Before buying another tool, spend a few weeks observing how work actually enters, moves through, and exits your department. Intake happening through email; matter records opened after work is already done; contracts tracked in someone’s personal spreadsheet; knowledge that walks out the door when people leave. What you find will tell you where the friction is and what not to automate yet. Automating a broken process makes it a faster broken process.
2. Define your data minimum. Not the ideal state. The minimum. What fields must be complete for a matter record to be useful? What metadata does a contract need to be workable? Set a baseline, communicate it, and hold the line. Consistency at a minimum level is more valuable than aspiration at a higher level that no one maintains.
3. Build the business case in their language. When making the case for legal-specific investment, translate it. Don’t lead with legal’s needs. Lead with organizational risk. Framing it as enterprise risk management rather than a departmental request will always land better.
4. Make one workflow visible before trying to change everything. Pick the highest-volume, most chaotic entry point (usually intake or contract review) and build one structured, repeatable process around it. Define a clear rule: a matter must be opened before work begins, not after. Standardize the required fields. Build intake through a defined workflow, not an inbox. Then measure the before and after. Before: Someone pulls a spreadsheet when the GC asks what the team is working on. After: The GC opens a dashboard and sees active matters by practice area, owner, and status without having to ask anyone. One workflow, done consistently, creates more organizational appetite for change than any strategic plan.
5. Lead the culture shift explicitly, not by assumption. Most legal technology implementations follow the same pattern: the tool goes live, a few training sessions get scheduled, an email goes out, and leadership assumes adoption will follow. It doesn’t. What just happened wasn’t change management. It was communication. And communication alone has never changed behavior.

Real change management means naming what you’re asking people to shift and why the old way no longer serves the team. It means acknowledging friction honestly, making the personal benefit explicit -less repetitive work, fewer dropped balls, more time for the judgment and strategy lawyers are actually trained to do.

Change management is also continuous, not a launch event. The GC’s informal signals matter as much as the formal ones. What gets reinforced in a 1:1, what gets named in a team meeting, and what the GC visibly uses and references are signals that shape behavior faster than any training session. If the GC doesn’t model the operating model, the team won’t either.

What legal leadership actually looks like when the infrastructure is right

The GC who has built the visibility stack operates differently, meaning they:

• Know what the team is working on without asking
• Walk into every executive conversation with current data, not reconstructed context
• Make the case for resources with workload trends and capacity gaps, not narrative alone
• Spot risk before it escalates instead of explaining it after it does

The loneliness of the chair doesn’t disappear. GCs will still carry things others don’t see. They will still protect people who will never know they needed protecting. That’s the role.

But the part of the loneliness that comes from operating without visibility, without organizational alignment, and without infrastructure built for how legal actually needs to function—that’s a choice. Not always a conscious one. But a choice.

Legal Maxxing is about making the other choice: building the people, process, and technology foundation that allows legal leaders to lead, not just survive the chair. Build toward it.