Five Lessons From HBO’s “Hacks” That Unlock the Unwritten Rules of Legal Ops

By Adam Becker and Tommie Tavares-Ferreira

June 3, 2026

Five Lessons From HBO’s “Hacks” That Unlock the Unwritten Rules of Legal Ops

Adam Becker is the Director of Legal Operations at Cockroach Labs and has held legal operations leadership roles at Endeavor and MetLife. Adam is currently on the Corporate Legal Operations Consortium (CLOC) Board of Directors. He spent a decade working in law firms focusing on operations & management, professional development, and recruiting.

Tommie Tavares-Ferreira is the Chief Strategy Officer at Lawtrades, where she leads strategy, innovation, content, and community. With more than 15 years of experience scaling legal operations at high-growth companies like Cedar, Peloton, Rakuten, and HBO, she now leverages that expertise to shape go-to-market execution, product direction, and legal innovation. She is a frequent public speaker on AI, legal innovation, operationalizing legal departments, and leadership.

In HBO’s hit show “Hacks,” a Millennial/Gen Z comedy writer and baby boomer comedian form an unlikely professional partnership that proves mutually beneficial—and hilarious. But even if you are an ardent viewer of the comedy that just capped its five-season run, you might not realize something about it: it provides the perfect parallel to how legal operatives do their jobs and relate to others in their organizations.

“Hacks,” starring Jean Smart as Deborah Vance and Hannah Einbinder as Ava Daniels, is built around a relationship most legal ops leaders will recognize instantly. One character has the platform (Las Vegas-based comedian Deborah); the other character makes the platform better (early-career writer Ava). Ava is legal ops. We see the department like Ava sees Deborah. We understand what legal is trying to do, we have that relationship with the GC, and we figure out how to get that expertise out to the business in exactly the right way.

At the 2026 CLOC Global Institute in Chicago, we delivered a fast version of this concept—four hacks, four themes, ten minutes—on the Hacks stage (ironically the same name, no relation to our session). We had to keep our presentation extremely brief and high level, so we wrote this article to go into more detail and present a fifth hack we did not have time to deliver. In some ways, it’s the one we wish we had learned first.

None of these hacks are the north star. They are small learnings. But small learnings, done consistently, are what separate the legal ops leaders who quietly stall from those who continually advance to a bigger stage. Let’s break down the hacks—one per season—in a digestible and spoiler-free format for you and your team.

Hack 1: Own your onboarding

Season 1 is, among other things, a masterclass in how to lose control of your own onboarding. Ava lets other people define what her job is: what she does, what she does not do, who she reports to in practice. She spends most of the season trying to claw that definition back. The legal ops parallel writes itself.

The GC introduces you to the legal team and, perhaps, their key stakeholders. IT sets up your access based on whoever last sat in your seat. Finance hands you a budget you did not build. Procurement assumes you are theirs. Three months in, nobody knows what you actually do, but they all have ideas about what you should do.

The Hack: control your onboarding, ideally before you arrive. Decide in advance what legal operations handles in this company, and, importantly, what legal operations should not oversee. Define what success looks like at day 90, day 180, and day 365 in language a GC would nod at in affirmation. Then schedule your own introductions. Define the role yourself. Send the one-pager to your GC as a “here is what I am hearing, please correct me” document, not as a manifesto. The point is not to be right. The point is to be the one holding the pen.

In 90 days, the hacked legal operations leader can define both the overriding purpose of the function and what the legal ops team controls and what it should not handle. The answer should be a clear mandate that the GC can repeat to their C-suite peers and legal department leaders. Define that story before someone else does.

Hack 2: Track before you’re asked

Season 2 hinges on a quiet disagreement about how success gets measured. Deborah is using old yardsticks: did the room laugh, did the local paper write it up? Ava quietly builds a data layer Deborah didn’t ask for, joke by joke, reaction by reaction. That data layer is what makes the season a success.

It is now expected that legal departments will have and use data to make decisions. The nature of that data differs from company to company, but at some point, every legal ops leader will be asked to tell a story with data. Some data already exists and some is accessible but needs to be harmonized. And then there is all the other data no one else is thinking about. The thoughtful legal ops leader is always focused on where the business is going and what the department is going to need a year from now. The company’s long-term strategy illustrates which data will be prioritized in the future. The hack is to start collecting that data today, even if no one is asking.

The art is to capture it in the least invasive way. Ideally, this data exists though may not be obvious—it could quietly hibernate in a matter management or Contract Lifecycle Management (CLM) system. In other instances, people may have to provide more information to build a data set and that requires laying groundwork with people who will have to take extra steps—even one additional click in a system can create friction. The legal operative picks data points that provide returns immediately (e.g., cycle time per stakeholder rather than total cycle time, third-party versus templates, in-sourced vs. outsourced) and avoids unhelpful (or perhaps, vanity) metric requests.

Legal operations pros know that predictive value is a significant value they add. It avoids any scramble for data and story when something comes up unexpectedly to everyone else, but totally expectedly to you. Imagine quelling a panic in a leadership meeting simply by saying: “We have actually been tracking that data point for a year.”

Hack 3: Strategize success

Season 3 has a clearly defined goal: Deborah wants the late-night show gig. There is, however, almost no defined plan for how to reach that goal. What follows is a series of delightful hijinks and questionable decisions. Many different attempts at the same end, with no coherent strategy underneath. It works out, but barely, and the cost is enormous.

Every unsuccessful legal innovation initiative or system introduction fails because there was no plan, or the plan described only the destination. Knowing what success looks like is not the same as knowing how you get there. Success doesn’t happen by osmosis, brute force, or by hope. Success emerges from a clearly defined view of the goal, that is reached through a specific, named sequence of phases, owners, and decision points.

The Hack: borrow the project plan, wholesale, from others at the company who already do this well. Sometimes that’s the product team, they define “done” before they start, they run in sprints, and they treat every phase as its own release. Marketing has a detailed plan when they roll out a launch and align every team behind it. Find the function that runs the most disciplined launches and emulate their format.

There is another benefit to borrowing a project plan: it’s immediately understandable to the rest of the enterprise. When leading any cross-departmental project, use the format, language, and style of cross-functional partners to remove an unspoken category of friction. Sometimes it is literally how the plan looks: one-page Product Requirements Document (PRD) or a detailed slide deck? Meet partners where they are and bring them into the legal operations mindset because legal projects are, at their core, company projects.

Hack 4: Map the real org chart

Season 4 hinges on a slowly dawning realization that there are more decision-makers in the company than Deborah knew. People keep showing up who appear to outrank the people we thought were in charge. The organizational chart on the wall turns out not to be the structure that runs the place.

This holds true in every legal department. There is the org chart on the intranet, which shows who reports to whom. Separately and invisibly, there is the org chart of influence which lays out who actually shapes decisions. This is not about politics. It highlights a simple fact: leaders do not always have leader titles. Some people have been involved in every major technology or process decision in the department for years, and even though you may not be working on something in their lane, they may have more say than their title suggests. Some of them are not in the legal department at all.

The Hack: map the real org chart before presenting a plan generally. Some GCs understand this concept and tell their newly initiated legal ops leaders: “you need to know these people.” Treasure that GC. Most of the time, you have to assemble the map yourself. For each of the top initiatives this year, determine who controls the actual budget, who controls the timeline, who controls the risk tolerance, who needs to feel credited for the win, and who has a dotted-line relationship that is invisible on the chart.

A useful flip: sometimes you are the influencer that other people are trying to find. You may have a history with a vendor from a prior role. You may be the person who can get legal on board with a non-legal initiative. Knowing where you sit on other teams’ influence maps is just as important as knowing where they sit on yours.

Hack 5: Manage your successor before you need one

For the first four hacks, we have been Ava—the perceptive one figuring out how to make the platform work. The fifth hack, which we did not deliver in Chicago, requires us to flip the lens. This time we are Deborah, and the trajectory of the show makes the next move obvious. The relationship between mentor and protégé has been swinging between collaboration and rivalry for four seasons. The unspoken question of the final season is the one every legal ops leader will eventually face: who comes after you, and are you building for them, or are you stalling their success when they walk in the door?

Most legal ops leaders do not plan succession. We plan retention. But succession is a gateway to greater success. It’s the deliberate, multi-year practice of making yourself replaceable in your current seat so that you can be promoted out of it, or so that the function survives if you leave. The reason most legal ops leaders never become chief legal operations officers or get tapped for a broader COO-style role, is not that the seat does not exist. It is that they have made themselves indispensable in the wrong way. There is no one behind them who can hold the function, so the function holds them.

The Hack: pick one person on your team (or one who could be on your team within a year) and purposely run the protégé play on them. Three power moves:

  1. Hand them one standing executive forum as a presenter, then, socialize their leadership in that area.
  2. Give them a project that is genuinely above their level and resist the urge to rescue them. The cost of one rough quarter is lower than the cost of a function that cannot scale past you.
  3. Write the job description for the role you want in two years, share it with your GC as a planning document. It should pair with the career plan for your protégé.  That document is the single most underused career tool in legal ops.

The mentor-protégé dynamic on “Hacks” is not a cautionary tale about being replaced. It is an instruction manual for staying relevant by building up the person who could replace you.

The real unwritten rule

Unwritten rules survive technology advancements, new platforms, and departmental transformation. Knowing those rules requires judgment about people, trust, credit, development, mentorship and allyship. No platform has ever automated that. None will.

Careers in high-judgment, low-playbook functions are built in the same way our favorite shows are built—by the people perceptive enough to see what the job calls for, and disciplined enough to deliver it in a form the department can use. Legal ops is the same. Deliverables matter but the leaders who deliver durable functions—and durable careers—are the ones who treat onboarding as a script they write, metrics as a story they start telling a year early, project plans as borrowed playbooks, org charts as living maps of influence, and succession as a multi-year, deliberate act of growth.

Four seasons gave us four hacks. The fifth season, and the fifth hack, is the one that ties them together: the unwritten rules are the job. The work is making them visible, repeatable, and teachable, first to yourself, and then to whoever goes on stage after you.

To read more articles about the latest legal operations trends and issues, check out this special edition of the Today’s General Counsel magazine.

Must read intelligence for general counsel

Subscribe to the Daily Updates newsletter to be at the forefront of best practices and the latest legal news.

Daily Updates

Sign up for our free daily newsletter for the latest news and business legal developments.

Scroll to Top